
From descombes@lpsc.in2p3.fr  Mon Jul  1 02:04:17 2013
Return-Path: <descombes@lpsc.in2p3.fr>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EC8B21F9C2B for <ietf@ietfa.amsl.com>; Mon,  1 Jul 2013 02:04:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uoRM4Ooz4S+u for <ietf@ietfa.amsl.com>; Mon,  1 Jul 2013 02:04:11 -0700 (PDT)
Received: from lpsc-mail.in2p3.fr (lpsc-mail.in2p3.fr [134.158.40.8]) by ietfa.amsl.com (Postfix) with ESMTP id DDFB321F9C81 for <ietf@ietf.org>; Mon,  1 Jul 2013 02:04:10 -0700 (PDT)
Received: from [134.158.40.158] (lpsc0158x.in2p3.fr [134.158.40.158]) by lpsc-mail.in2p3.fr (8.13.1/8.13.1/In2p3) with ESMTP id r61948jr025532 for <ietf@ietf.org>; Mon, 1 Jul 2013 11:04:09 +0200
Message-ID: <51D14680.90809@lpsc.in2p3.fr>
Date: Mon, 01 Jul 2013 11:06:08 +0200
From: DESCOMBES Thierry <descombes@lpsc.in2p3.fr>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130523 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: sending strings data into IPfix stream
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Jul 2013 09:04:17 -0000

Hello,
Not sure if this is the right list for this type of message ...
I am developing an IPFIX exporter. It exports IP flows, and I'd like now 
to export some extra information (strings) about the machines on the LAN 
(the hostname of the machine, and others information ...)
What is the right way to do that (IPFIX fields to use, template options 
or not ...)
Thank you very much in advance. Regards
T. Descombes

From fanf2@hermes.cam.ac.uk  Mon Jul  1 02:22:40 2013
Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 996A521F9C95 for <ietf@ietfa.amsl.com>; Mon,  1 Jul 2013 02:22:40 -0700 (PDT)
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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xmSAGZ-H8ewR for <ietf@ietfa.amsl.com>; Mon,  1 Jul 2013 02:22:39 -0700 (PDT)
Received: from ppsw-33.csi.cam.ac.uk (ppsw-33.csi.cam.ac.uk [IPv6:2001:630:212:8::e:f33]) by ietfa.amsl.com (Postfix) with ESMTP id 4D42621F9C6C for <ietf@ietf.org>; Mon,  1 Jul 2013 02:22:38 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-2.csi.cam.ac.uk ([131.111.8.54]:39458) by ppsw-33.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:25) with esmtpa (EXTERNAL:fanf2) id 1UtaJg-0004GY-hB (Exim 4.80_167-5a66dd3) (return-path <fanf2@hermes.cam.ac.uk>); Mon, 01 Jul 2013 10:22:36 +0100
Received: from fanf2 by hermes-2.csi.cam.ac.uk (hermes.cam.ac.uk) with local id 1UtaJg-00019K-BN (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Mon, 01 Jul 2013 10:22:36 +0100
Date: Mon, 1 Jul 2013 10:22:36 +0100
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-2.csi.cam.ac.uk
To: Riccardo Bernardini <framefritti@gmail.com>
Subject: Re: RFC 6234 code
In-Reply-To: <CABSMSPXBAAXjyt4EHck4f0haHfXtwnnouDTEwyzv-zoLbnLJPA@mail.gmail.com>
Message-ID: <alpine.LSU.2.00.1307011022100.24099@hermes-2.csi.cam.ac.uk>
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097AA4@GLKXM0002V.GREENLNK.net> <51CC67D0.8050600@isdg.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097B24@GLKXM0002V.GREENLNK.net> <51CC94B2.2060507@isdg.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097CC1@GLKXM0002V.GREENLNK.net> <51CD9987.8010401@att.com> <CABSMSPXBAAXjyt4EHck4f0haHfXtwnnouDTEwyzv-zoLbnLJPA@mail.gmail.com>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Cc: RFC Interest <rfc-interest@rfc-editor.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Jul 2013 09:22:41 -0000

Riccardo Bernardini <framefritti@gmail.com> wrote:
>
> This came to my mind while reading: why not embedding the archive in
> the text with some special "line header" that makes automatic
> extraction possible?

Like RCF 6716.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Forties, Cromarty: East, veering southeast, 4 or 5, occasionally 6 at first.
Rough, becoming slight or moderate. Showers, rain at first. Moderate or good,
occasionally poor at first.

From trammell@tik.ee.ethz.ch  Mon Jul  1 02:28:36 2013
Return-Path: <trammell@tik.ee.ethz.ch>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AA2421F9E2C for <ietf@ietfa.amsl.com>; Mon,  1 Jul 2013 02:28:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XLew9gepp-kN for <ietf@ietfa.amsl.com>; Mon,  1 Jul 2013 02:28:29 -0700 (PDT)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id E005021F9EAE for <ietf@ietf.org>; Mon,  1 Jul 2013 02:28:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 13168D9305; Mon,  1 Jul 2013 11:28:26 +0200 (MEST)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id JwJE9YMRZSXJ; Mon,  1 Jul 2013 11:28:25 +0200 (MEST)
Received: from pb-10243.ethz.ch (pb-10243.ethz.ch [82.130.102.152]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: briant) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id C7B9DD9304; Mon,  1 Jul 2013 11:28:25 +0200 (MEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: sending strings data into IPfix stream
From: Brian Trammell <trammell@tik.ee.ethz.ch>
In-Reply-To: <51D14680.90809@lpsc.in2p3.fr>
Date: Mon, 1 Jul 2013 11:28:25 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <180BD9A1-3325-471A-8BB6-F80A73F5535A@tik.ee.ethz.ch>
References: <51D14680.90809@lpsc.in2p3.fr>
To: DESCOMBES Thierry <descombes@lpsc.in2p3.fr>
X-Mailer: Apple Mail (2.1508)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Jul 2013 09:28:36 -0000

Hi, Thierry,

Have a look in the IANA information element registry =
(http://www.iana.org/assignments/ipfix) to see if there are existing IEs =
for the information you want to export.=20

Hostnames, I think, are not there -- in general, IPFIX exporters deal in =
addresses taken from observed packets and leave it up to the collector =
to do reverse resolution, due to (1) the amount of time DNS reverse =
lookups can take, blocking measurement activity on a (presumably) =
resource-constrained metering process, as well as (2) the ambiguity =
inherent within reverse lookups (due to e.g. misconfigured local and/or =
authoritative resolvers). In an environment where you have a good, =
internal database of hostnames (e.g. because the metering process is =
colocated with a DHCP server), this is more likely to be useful, though.

If you'd like to export information _not_ in the IANA Information =
Element registry, you have two options; (1) defining new =
enterprise-specific IEs scoped by your Private Enterprise Number (see =
Section 3.2 and example A.2.2. in =
http://tools.ietf.org/html/draft-ietf-ipfix-protocol-rfc5101bis) or (2) =
submitting a new Information Element definition for addition to the IANA =
registry (see http://tools.ietf.org/html/draft-ietf-ipfix-ie-doctors-07/ =
for guidelines on writing such a definition).

Keep in mind, for strings, you'll almost certainly be dealing with =
variable-length IE export; see section 7 of =
http://tools.ietf.org/html/draft-ietf-ipfix-protocol-rfc5101bis.

Cheers,

Brian


On 1 Jul 2013, at 11:06 , DESCOMBES Thierry <descombes@lpsc.in2p3.fr> =
wrote:

> Hello,
> Not sure if this is the right list for this type of message ...
> I am developing an IPFIX exporter. It exports IP flows, and I'd like =
now to export some extra information (strings) about the machines on the =
LAN (the hostname of the machine, and others information ...)
> What is the right way to do that (IPFIX fields to use, template =
options or not ...)
> Thank you very much in advance. Regards
> T. Descombes


From chris.dearlove@baesystems.com  Mon Jul  1 04:14:43 2013
Return-Path: <chris.dearlove@baesystems.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 112B021F9B17 for <ietf@ietfa.amsl.com>; Mon,  1 Jul 2013 04:14:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9ouh5fAZjqNf for <ietf@ietfa.amsl.com>; Mon,  1 Jul 2013 04:14:38 -0700 (PDT)
Received: from ukmta3.baesystems.com (ukmta3.baesystems.com [20.133.40.55]) by ietfa.amsl.com (Postfix) with ESMTP id 6637C21F901A for <ietf@ietf.org>; Mon,  1 Jul 2013 04:14:38 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,973,1363132800"; d="scan'208";a="296745758"
Received: from unknown (HELO baemasodc005.greenlnk.net) ([10.108.52.29]) by Baemasodc001ir.sharelnk.net with ESMTP; 01 Jul 2013 12:14:33 +0100
X-IronPort-AV: E=Sophos;i="4.87,973,1363132800"; d="scan'208";a="20658772"
Received: from glkxh0002v.greenlnk.net ([10.109.2.33]) by baemasodc005.greenlnk.net with ESMTP; 01 Jul 2013 12:14:33 +0100
Received: from GLKXM0002V.GREENLNK.net ([169.254.2.180]) by GLKXH0002V.GREENLNK.net ([10.109.2.33]) with mapi id 14.02.0328.009; Mon, 1 Jul 2013 12:14:33 +0100
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: Joe Abley <jabley@hopcount.ca>, Paul Hoffman <paul.hoffman@vpnc.org>
Subject: RE: RFC 6234 code
Thread-Topic: RFC 6234 code
Thread-Index: AQHOdD/gHirQWo7qWku6uA/H1V6pk5lPr6Uw
Date: Mon, 1 Jul 2013 11:14:33 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D25099133@GLKXM0002V.GREENLNK.net>
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097AA4@GLKXM0002V.GREENLNK.net> <51CC67D0.8050600@isdg.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097B24@GLKXM0002V.GREENLNK.net> <51CC94B2.2060507@isdg.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097CC1@GLKXM0002V.GREENLNK.net> <51CD9987.8010401@att.com>	<BEFC413A958E9B25913F2FE9@JcK-HP8200.jck.com> <D3A3A63A-0CB1-4254-A087-655F9BDA6CEC@vpnc.org> <DB3A3E49-13C6-4CE3-87D5-8F86B37DFC57@hopcount.ca>
In-Reply-To: <DB3A3E49-13C6-4CE3-87D5-8F86B37DFC57@hopcount.ca>
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: John C Klensin <john-ietf@jck.com>, RFC Interest <rfc-interest@rfc-editor.org>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Jul 2013 11:14:43 -0000

That's 20 minutes per person of course.

-- =

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-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Joe=
 Abley
Sent: 28 June 2013 21:41
To: Paul Hoffman
Cc: John C Klensin; RFC Interest; ietf@ietf.org list
Subject: Re: RFC 6234 code

----------------------! WARNING ! ----------------------
This message originates from outside our organisation,
either from an external partner or from the internet.
Keep this in mind if you answer this message.
Follow the 'Report Suspicious Emails' link on IT matters
for instructions on reporting suspicious email messages.
--------------------------------------------------------

On 2013-06-28, at 15:19, Paul Hoffman <paul.hoffman@vpnc.org> wrote:

> The RFC Editor is publishing code in a text file that is formatted like a=
n RFC. The proposal is for the RFC Editor to publish *the exact same code* =
in a file without the RFC wrapping.
> =

> If you really think you see a legal difference in doing the second, fine;=
 I propose that you are just searching for problems that do not exist.

Quite possibly they don't, and I'm not presuming to talk for John. But the =
vague thoughts that crossed my mine were the issues that allowed Phil Zimme=
rman to publish PGP source code in book form and avoid conviction for munit=
ions export without a licence.


Perhaps this is no longer an issue in the US following Bernstein vs. United=
 States and Junger vs. Daley.

Just thinking aloud, really.

I will observe that far more than 20 minutes of combined person-minutes hav=
e been consumed by this thread already, and the approach of minimum collect=
ive effort is still "scrape the code from the RFC yourself and compile it".


Joe
********************************************************************
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 nomcom-chair-2013@ietf.org  Mon Jul  1 16:57:08 2013
Return-Path: <nomcom-chair-2013@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B93111E833B; Mon,  1 Jul 2013 16:57:08 -0700 (PDT)
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=[AWL=0.698, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id blJfpcEiJCFB; Mon,  1 Jul 2013 16:57:07 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 522FF11E8333; Mon,  1 Jul 2013 16:57:07 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: NomCom Chair 2013 <nomcom-chair-2013@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: Nomcom 2013-14 - Timeline and Seeds for Random Selection
X-Test-IDTracker: no
X-IETF-IDTracker: 4.51.p2
Message-ID: <20130701235707.22721.72561.idtracker@ietfa.amsl.com>
Date: Mon, 01 Jul 2013 16:57:07 -0700
Cc: IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: 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, 02 Jul 2013 00:24:42 -0000

This messages provides the details for the random selection of =

the ten voting members of the 2013-14 Nomcom.  =


We will once again be using the publicly verifiable random algorithm =

specified in RFC 3797.  This message contains both the timeline for =

performing the publicly verifiable selection and also the random seeds
that will be used as input to the selection algorithm.

Please get in touch with me if you have any questions about the
timeline below or the selection seeds specified here.

Timeline:
---------
The following is the current timeline for the 2023-14 Nomcom:

   * Nomcom Chair Announcement made: Apr 16, 2013;
   * First Call for Volunteers issued: May 13, 2013;
   * Second Call for Volunteers issued: May 29, 2013;
   * First Announcement of Qualified Volunteers: May 31, 2013;
   * Second Announcement of Qualified Volunteers: Jun 19, 2013;
   * Third Call for Volunteers issued: Jul 01, 2013;
   * Random Selection Seeds and Timeline announced: Jul 01, 2013;
   * Call for Volunteers closes: July 04, 2013 at 23:59 EDT (UTC -4)
   * Final Announcement of Qualified Volunteers: Jul 05, 2013
   * Raise issues on Qualified Volunteers by 23:59 EDT: Jul 12, 2013;
   * Seed values available from seed sources: Jul 13, 2013;
   * Run random selection algorithm and publish results: Jul 13, 2013;
   * Start Challenge period at 09:00 EDT:  Jul 13, 2013;
   * End of challenge period at 09:00 EDT : Jul 20, 2013;
   * Final List of Nomcom members published 10:00 EDT : Jul 20, 2013;
   * First Call for Nominations: Jul 20, 2013;
   * Nomcom 2013-2104 organizes during IETF-87: Jul 28-Aug 02, 2013;
   * ... (1)

(1)  As soon as possible after the Nomcom organizes, an updated timeline
     covering the rest of the cycle will be published.

Seeds:
-------
The following are the seed sources (in order) that will be used in
selecting the 2013-14 NomCom members:

Canadian Lottery Lotto 649
Wednesday, July 10, 2013 Results:
http://lotoquebec.com/loteries/nav/fr/a-tirage/lotto-6-49/resultats-detaill=
es
  (7 numbers including the bonus number: numbers between 1 and 49)

US National debt ("Debt Held by the Public"), published by the
Treasury department as of Thursday, July 11, 2013
http://www.treasurydirect.gov/NP/BPDLogin?application=3Dnp =

  Last 8 digits, ignore the commas and periods

US National debt ("Intragovernmental Holdings"), published by the
Treasury department as of Thursday, July 11, 2013
http://www.treasurydirect.gov/NP/BPDLogin?application=3Dnp =

  Last 8 digits, ignore the commas and periods

Euromillions Lottery
Friday July 12, 2013 Results:
http://www.europeanlotteryguild.com/lottery_results/euromillions_results/
  (7 numbers including the star balls: 5 numbers between 1 and 50 and 2
   star balls between 1 and 11)

All the above seeds will be provided (in the order listed above) as
input to the RFC 3797 selection algorithm to determine the ten
voting members of the 2013-14 Nomcom.

Allison

Allison Mankin
Nomcom Chair 2013-14
nomcom-chair-2013@ietf.org

From nomcom-chair-2013@ietf.org  Mon Jul  1 16:40:31 2013
Return-Path: <nomcom-chair-2013@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84B9B11E833A; Mon,  1 Jul 2013 16:40:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.204
X-Spam-Level: 
X-Spam-Status: No, score=-101.204 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u9cTQc8P6gXX; Mon,  1 Jul 2013 16:40:31 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 08D6121F9B00; Mon,  1 Jul 2013 16:40:31 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: NomCom Chair 2013 <nomcom-chair-2013@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: NOMCOM 2013-14 Volunteering - 3rd and Final Call for Volunteers
X-Test-IDTracker: no
X-IETF-IDTracker: 4.51.p2
Message-ID: <20130701234030.24738.41427.idtracker@ietfa.amsl.com>
Date: Mon, 01 Jul 2013 16:40:30 -0700
Cc: IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: 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, 02 Jul 2013 00:24:42 -0000

Hi, everyone,

We are short of our goal of 200 volunteers for the upcoming nomcom.  =

Please do volunteer.  Our publicly verifiable random algorithm has fully =

adequate entropy for a flood of volunteers - more names, more names, more =

names, more brains --- er, oops, not yet a zombie.  =


The more volunteers we get, the better chance we have of choosing a =

random yet representative cross section of the IETF.  Respond to this =

challenge and strengthen our statistical significance just by hitting =

Reply (but not Reply-All, please).  =


Oh, first, please do check the official information:
The IETF nominating committee (nomcom) process for 2013-14 is under way. Th=
e =

IETF nomcom appoints folks to fill the open slots on the IAOC, the IAB,
and the IESG. Ten voting members for the nomcom are selected in a verifiably
random way from a pool of volunteers. =


The details of the selection and operation of the nomcom can be found =

in RFCs 3777, 5078, 5633, 5680, and 6859.  Four of those RFCs  (3777, 5633, =

5680 and 6859)  comprise BCP 10. We will also reference RFC 3797.

Volunteers must have attended 3 of the past 5 IETF meetings.  As specified =
in
RFC 3777, that means three out of the five past meetings up to the time this
email announcement goes out to start the solicitation of volunteers. The fi=
ve
meetings out of which you must have attended three are IETF 82, 83, 84, 85,=
 86.

If you qualify, reply to this email and volunteer.  =


The list of people and posts whose terms end with the March 2014 IETF
meeting, and thus the positions for which this nomcom is responsible, are
IAOC:
Chris Griffiths

IAB:
Bernard Aboba
Marc Blanchet
Ross Callon
Eliot Lear
Hannes Tschofenig

IESG:
Barry Leiba (Applications)
Brian Haberman (Internet)
Benoit Claise (Operations and Management)
Gonzalo Camarillo (RAI)
Stewart Bryant (Routing)
Sean Turner (Security)
Martin Stiemerling (Transport)

The primary activity for this nomcom will begin in July 2013 and should be
completed in January 2014.  Being a nomcom member will require some time
commitment - there will be interviews with candidates at meetings, regularly
scheduled conference calls to ensure progress, collection and review of =

requirements from the commitment, review of candidate questionnaires and
of community feedback.  A more detailed timetable for the nomcom tasks
will appear soon.

Please respond to this email before 23:59 EDT (UTC -4 hours) =

July 04, 2013.  In the body include: =

 1. your Given Name as you enter it when you register for the IETF
 2. your Family Name as you enter it when you register for the IETF
 3. your current primary affilation (the information you enter into the Com=
pany field)
 4. any/all email addresses you've used to register for IETF meetings =

 5. which email address you prefer =

 6. your phone number (for our use in confirming you if selected).

On July 05, 2013 there will be an announcement of validated volunteers.  If=
 you =

haven't received an acknowledgement message from me to your email =

(indicating that you are or are not eligible) and you do not see your name =

in the July 05 list, contact me AS SOON AS POSSIBLE, on or before July 06.  =


Looking forward to adding your name to the "hat" very soon,

Allison =


Allison Mankin
Nomcom Chair 2013-2014


From rbonica@juniper.net  Mon Jul  1 19:47:59 2013
Return-Path: <rbonica@juniper.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61AAF11E838D for <ietf@ietfa.amsl.com>; Mon,  1 Jul 2013 19:47:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.467
X-Spam-Level: 
X-Spam-Status: No, score=-99.467 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, UNRESOLVED_TEMPLATE=3.132, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rH2KKoWHIVdy for <ietf@ietfa.amsl.com>; Mon,  1 Jul 2013 19:47:48 -0700 (PDT)
Received: from db8outboundpool.messaging.microsoft.com (mail-db8lp0189.outbound.messaging.microsoft.com [213.199.154.189]) by ietfa.amsl.com (Postfix) with ESMTP id 03E4011E8304 for <ietf@ietf.org>; Mon,  1 Jul 2013 19:47:47 -0700 (PDT)
Received: from mail131-db8-R.bigfish.com (10.174.8.243) by DB8EHSOBE025.bigfish.com (10.174.4.88) with Microsoft SMTP Server id 14.1.225.23; Tue, 2 Jul 2013 02:47:46 +0000
Received: from mail131-db8 (localhost [127.0.0.1])	by mail131-db8-R.bigfish.com (Postfix) with ESMTP id 365344E0206	for <ietf@ietf.org>; Tue,  2 Jul 2013 02:47:46 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:66.129.224.51; KIP:(null); UIP:(null); IPV:NLI; H:P-EMHUB03-HQ.jnpr.net; RD:none; EFVD:NLI
X-SpamScore: -18
X-BigFish: VPS-18(zz1432I9a6kzz1f42h1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz1033IL8275dhz2fh2a8h683h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0h162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1d07h1d0ch1d2eh1d3fh1dc1h1de9h1dfeh1dffh1e1dh1155h)
Received-SPF: pass (mail131-db8: domain of juniper.net designates 66.129.224.51 as permitted sender) client-ip=66.129.224.51; envelope-from=rbonica@juniper.net; helo=P-EMHUB03-HQ.jnpr.net ; -HQ.jnpr.net ; 
X-Forefront-Antispam-Report-Untrusted: CIP:157.56.238.5; KIP:(null); UIP:(null); (null); H:BY2PRD0512HT002.namprd05.prod.outlook.com; R:internal; EFV:INT
Received: from mail131-db8 (localhost.localdomain [127.0.0.1]) by mail131-db8 (MessageSwitch) id 1372733263634598_4514; Tue,  2 Jul 2013 02:47:43 +0000 (UTC)
Received: from DB8EHSMHS023.bigfish.com (unknown [10.174.8.247])	by mail131-db8.bigfish.com (Postfix) with ESMTP id 96444380047	for <ietf@ietf.org>; Tue,  2 Jul 2013 02:47:43 +0000 (UTC)
Received: from P-EMHUB03-HQ.jnpr.net (66.129.224.51) by DB8EHSMHS023.bigfish.com (10.174.4.33) with Microsoft SMTP Server (TLS) id 14.16.227.3; Tue, 2 Jul 2013 02:47:43 +0000
Received: from P-CLDFE01-HQ.jnpr.net (172.24.192.59) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.213.0; Mon, 1 Jul 2013 19:47:41 -0700
Received: from o365mail.juniper.net (207.17.137.149) by o365mail.juniper.net (172.24.192.59) with Microsoft SMTP Server id 14.1.355.2; Mon, 1 Jul 2013 19:47:40 -0700
Received: from DB8EHSOBE002.bigfish.com (213.199.154.185) by o365mail.juniper.net (207.17.137.149) with Microsoft SMTP Server (TLS) id 14.1.355.2; Mon, 1 Jul 2013 19:51:43 -0700
Received: from mail182-db8-R.bigfish.com (10.174.8.253) by DB8EHSOBE002.bigfish.com (10.174.4.65) with Microsoft SMTP Server id 14.1.225.23; Tue, 2 Jul 2013 02:47:38 +0000
Received: from mail182-db8 (localhost [127.0.0.1])	by mail182-db8-R.bigfish.com (Postfix) with ESMTP id B5761A40199	for <ietf@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Tue,  2 Jul 2013 02:47:38 +0000 (UTC)
Received: from mail182-db8 (localhost.localdomain [127.0.0.1]) by mail182-db8 (MessageSwitch) id 1372733256627578_12998; Tue,  2 Jul 2013 02:47:36 +0000 (UTC)
Received: from DB8EHSMHS018.bigfish.com (unknown [10.174.8.241])	by mail182-db8.bigfish.com (Postfix) with ESMTP id 8C80B40045	for <ietf@ietf.org>; Tue,  2 Jul 2013 02:47:36 +0000 (UTC)
Received: from BY2PRD0512HT002.namprd05.prod.outlook.com (157.56.238.5) by DB8EHSMHS018.bigfish.com (10.174.4.28) with Microsoft SMTP Server (TLS) id 14.16.227.3; Tue, 2 Jul 2013 02:47:36 +0000
Received: from BY2PRD0512MB653.namprd05.prod.outlook.com ([169.254.5.72]) by BY2PRD0512HT002.namprd05.prod.outlook.com ([10.255.243.35]) with mapi id 14.16.0324.000; Tue, 2 Jul 2013 02:47:34 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Last Call: <draft-ietf-lisp-deployment-08.txt> (LISP Network Element Deployment Considerations) to Informational RFC 
Thread-Topic: Last Call: <draft-ietf-lisp-deployment-08.txt> (LISP Network Element Deployment Considerations) to Informational RFC 
Thread-Index: Ac52zoCWFQguQHNYSxaUp6rLOV9jKQ==
Date: Tue, 2 Jul 2013 02:47:34 +0000
Message-ID: <2CF4CB03E2AA464BA0982EC92A02CE2509F8E998@BY2PRD0512MB653.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.232.2]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%12219$Dn%IETF.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Jul 2013 02:47:59 -0000

Folks,

In keeping with the WG Charter, draft-ietf-lisp-deployment should be labele=
d EXPERIMENTAL, not INFORMATIONAL. For supporting information, please see t=
he following milestone in the LISP Charter:

- Sep 2012	Submit a deployment model document to the IESG for publication a=
s an Experimental RFC

Also in keeping with the LISP charter, draft-ietf-lisp-deployment should in=
clude the following disclaimer, which is taken from RFC 6830:

-  This experimental specification has areas that require additional experi=
ence and measurement.  It is NOT RECOMMENDED for deployment beyond experime=
ntal situations.  Results of experimentation may lead to modifications and =
enhancements of protocol mechanisms defined in this document.  See Section =
15 [of RFC 6830] for specific, known issues that are in need of further wor=
k during development, implementation, and experimentation.

I say this because of the following text, taken from the LISP WG Charter:

- The specifications developed by the WG are Experimental and labeled with =
accurate disclaimers about their limitations and not fully understood impli=
cations for Internet traffic. In addition, as these issues are understood, =
the working group will analyze and document the implications of LISP on Int=
ernet traffic, applications, routers, and security.

                                                               Ron




> From: The IESG <iesg-secretary@ietf.org>=20
> To: IETF-Announce <ietf-announce@ietf.org>=20
> Reply-to: iesg-secretary@ietf.org=20
> Subject: Last Call: <draft-ietf-lisp-deployment-08.txt> (LISP Network Ele=
ment Deployment Considerations) to Informational RFC=20
> X-C5I-RSN: 1/0/934/11346/12106=20
>=20
> The IESG has received a request from the Locator/ID Separation Protocol=20
> WG (lisp) to consider the following document:=20
> - 'LISP Network Element Deployment Considerations'=20
> <draft-ietf-lisp-deployment-08.txt> as Informational RFC=20
>=20
> The IESG plans to make a decision in the next few weeks, and solicits=20
> final comments on this action. Please send substantive comments to the=20
> ietf@ietf.org mailing lists by 2013-07-15. Exceptionally, comments may be=
=20
> sent to iesg@ietf.org instead. In either case, please retain the=20
> beginning of the Subject line to allow automated sorting.=20
=20




From descombes@lpsc.in2p3.fr  Tue Jul  2 06:56:33 2013
Return-Path: <descombes@lpsc.in2p3.fr>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66C9A21F9EB7 for <ietf@ietfa.amsl.com>; Tue,  2 Jul 2013 06:56:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4ItenECPcWWn for <ietf@ietfa.amsl.com>; Tue,  2 Jul 2013 06:56:29 -0700 (PDT)
Received: from lpsc-mail.in2p3.fr (lpsc-mail.in2p3.fr [134.158.40.8]) by ietfa.amsl.com (Postfix) with ESMTP id C448C21F99BA for <ietf@ietf.org>; Tue,  2 Jul 2013 06:56:27 -0700 (PDT)
Received: from [134.158.40.158] (lpsc0158x.in2p3.fr [134.158.40.158]) by lpsc-mail.in2p3.fr (8.13.1/8.13.1/In2p3) with ESMTP id r62DuNhY027480; Tue, 2 Jul 2013 15:56:23 +0200
Message-ID: <51D2DC7E.60301@lpsc.in2p3.fr>
Date: Tue, 02 Jul 2013 15:58:22 +0200
From: DESCOMBES Thierry <descombes@lpsc.in2p3.fr>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130523 Thunderbird/17.0.6
MIME-Version: 1.0
To: Brian Trammell <trammell@tik.ee.ethz.ch>
Subject: Re: sending strings data into IPfix stream
References: <51D14680.90809@lpsc.in2p3.fr> <180BD9A1-3325-471A-8BB6-F80A73F5535A@tik.ee.ethz.ch>
In-Reply-To: <180BD9A1-3325-471A-8BB6-F80A73F5535A@tik.ee.ethz.ch>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Jul 2013 13:56:33 -0000

Hi Brian,
Thanks a lot for your answer.
Our IPFIX exporter is a bit specific, and we'd like to export 
periodically a list of hostname, ipaddress and related data (that are 
not available from the collector: owner, serial number, ...)
It should be easier to send this list using IPFIX stream (and this deals 
with all security/filtering policy)...
The transmission frequency of this list will be quite low. What is the 
right way to dothat ? Do I have to use IPFIX option templates to send 
such data, or not ?
Thanks a lot. Cheers
Thierry



On 01/07/2013 11:28, Brian Trammell wrote:
> Hi, Thierry,
>
> Have a look in the IANA information element registry (http://www.iana.org/assignments/ipfix) to see if there are existing IEs for the information you want to export.
>
> Hostnames, I think, are not there -- in general, IPFIX exporters deal in addresses taken from observed packets and leave it up to the collector to do reverse resolution, due to (1) the amount of time DNS reverse lookups can take, blocking measurement activity on a (presumably) resource-constrained metering process, as well as (2) the ambiguity inherent within reverse lookups (due to e.g. misconfigured local and/or authoritative resolvers). In an environment where you have a good, internal database of hostnames (e.g. because the metering process is colocated with a DHCP server), this is more likely to be useful, though.
>
> If you'd like to export information _not_ in the IANA Information Element registry, you have two options; (1) defining new enterprise-specific IEs scoped by your Private Enterprise Number (see Section 3.2 and example A.2.2. in http://tools.ietf.org/html/draft-ietf-ipfix-protocol-rfc5101bis) or (2) submitting a new Information Element definition for addition to the IANA registry (see http://tools.ietf.org/html/draft-ietf-ipfix-ie-doctors-07/ for guidelines on writing such a definition).
>
> Keep in mind, for strings, you'll almost certainly be dealing with variable-length IE export; see section 7 of http://tools.ietf.org/html/draft-ietf-ipfix-protocol-rfc5101bis.
>
> Cheers,
>
> Brian
>
>
> On 1 Jul 2013, at 11:06 , DESCOMBES Thierry <descombes@lpsc.in2p3.fr> wrote:
>
>> Hello,
>> Not sure if this is the right list for this type of message ...
>> I am developing an IPFIX exporter. It exports IP flows, and I'd like now to export some extra information (strings) about the machines on the LAN (the hostname of the machine, and others information ...)
>> What is the right way to do that (IPFIX fields to use, template options or not ...)
>> Thank you very much in advance. Regards
>> T. Descombes


From chair@ietf.org  Tue Jul  2 07:44:01 2013
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1632321F9F6E; Tue,  2 Jul 2013 07:44:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.6
X-Spam-Level: 
X-Spam-Status: No, score=-103.6 tagged_above=-999 required=5 tests=[AWL=1.000,  BAYES_00=-2.599, GB_I_INVITATION=-2, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i-FG7LSHwq+e; Tue,  2 Jul 2013 07:44:00 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B4F721F9F6A; Tue,  2 Jul 2013 07:44:00 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Chair <chair@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: Invitation to request an IETF mentor
X-Test-IDTracker: no
X-IETF-IDTracker: 4.51.p2
Message-ID: <20130702144400.5250.85365.idtracker@ietfa.amsl.com>
Date: Tue, 02 Jul 2013 07:44:00 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 02 Jul 2013 14:44:01 -0000

All,

During IETF 87 in Berlin, we will be running a trial of the IETF Mentoring =
Program. The goal of the IETF Mentoring Program is to match people new to t=
he IETF (people who have participated in three or fewer face-to-face meetin=
gs or anyone registering as a student) with experienced IETF mentors. As a =
mentoring participant, your mentor will personally introduce you to the IET=
F community, help you find your way around the IETF & the meeting, explain =
things, and introduce you to other attendees you might like to meet. Basica=
lly, your mentor will be your personal buddy during the meeting week, and p=
ossibly afterwards.

The IETF Mentoring Program was created to help new IETF participants to get=
 up to speed rapidly and help them begin to contribute to the IETF quickly =
and easily.  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 then introduce you to each =
other by email, and invite you to meet up in person at the IETF Meet & Gree=
t event on Sunday afternoon in Berlin. From there on, you and your mentor d=
ecide 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 t=
he IETF Mentoring Program will be a great way for new participants to get i=
ntroduced to the IETF by an experienced participant with matching interest.

Regards,
Jari Arkko
IETF Chair

From Johannes.Merkle@secunet.com  Tue Jul  2 05:24:00 2013
Return-Path: <Johannes.Merkle@secunet.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB7C711E8106; Tue,  2 Jul 2013 05:24:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F95jR3mT7OOr; Tue,  2 Jul 2013 05:23:56 -0700 (PDT)
Received: from a.mx.secunet.com (a.mx.secunet.com [195.81.216.161]) by ietfa.amsl.com (Postfix) with ESMTP id 8794411E80A2; Tue,  2 Jul 2013 05:23:56 -0700 (PDT)
Received: from localhost (alg1 [127.0.0.1]) by a.mx.secunet.com (Postfix) with ESMTP id 479D81A0084; Tue,  2 Jul 2013 14:23:54 +0200 (CEST)
X-Virus-Scanned: by secunet
Received: from a.mx.secunet.com ([127.0.0.1]) by localhost (a.mx.secunet.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id HEfdQQ3hfsdN; Tue,  2 Jul 2013 14:23:51 +0200 (CEST)
Received: from mail-srv1.secumail.de (unknown [10.53.40.200]) by a.mx.secunet.com (Postfix) with ESMTP id EB0C01A0085; Tue,  2 Jul 2013 14:23:51 +0200 (CEST)
Received: from [10.208.1.73] ([10.208.1.73]) by mail-srv1.secumail.de with Microsoft SMTPSVC(6.0.3790.4675); Tue, 2 Jul 2013 14:23:51 +0200
Message-ID: <51D2C656.3080608@secunet.com>
Date: Tue, 02 Jul 2013 14:23:50 +0200
From: Johannes Merkle <johannes.merkle@secunet.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Roni Even <ron.even.tlv@gmail.com>
Subject: Re: Gen-ART LC review of draft-merkle-tls-brainpool-02
References: <048001ce755d$505996e0$f10cc4a0$@gmail.com>
In-Reply-To: <048001ce755d$505996e0$f10cc4a0$@gmail.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 02 Jul 2013 12:23:52.0016 (UTC) FILETIME=[031BAD00:01CE771F]
X-Mailman-Approved-At: Tue, 02 Jul 2013 08:33:49 -0700
Cc: gen-art@ietf.org, ietf@ietf.org, draft-merkle-tls-brainpool.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Jul 2013 12:24:00 -0000

a new version addressing your review is on its way.

Johannes


Roni Even schrieb am 30.06.2013 08:44:
> 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-merkle-tls-brainpool-02
> 
> Reviewer: Roni Even
> 
> Review Date:2013𤖭0
> 
> IETF LC End Date: 2013-7�23
> 
> IESG Telechat date:
> 
>  
> 
> Summary: This draft is almost ready for publication as Standard track RFC.
> 
>  
> 
>  
> 
> Major issues:
> 
>  
> 
> Minor issues:
> 
>  
> 
> In section 1 you reference TLS 1.0 and 1.1 usage based on RFC 4492. What about TLS 1.2 usage specified in RFC5246 A.7
> 
>  
> 
>  
> 
>  
> 
> Nits/editorial comments:
> 
>  1. In section 3 the  registry name is EC Named Curve
>  2. In section 3 change 搒uitability� to 搒uitable�
> 
>  
> 


-- 

Mit freundlichen Gren,
Dr. Johannes Merkle
Principal Beratung, Elektronische Identit鋞en
Public Sector
secunet Security Networks AG
Mergenthaler Allee 77
65760 Eschborn
Germany
Telefon +49 201 54 54-3091
Telefax +49 201 54 54-1325
Mobil   +49 175 2224439
johannes.merkle@secunet.com
www.secunet.com

From michael_oreirdan@cable.comcast.com  Mon Jul  1 17:49:39 2013
Return-Path: <michael_oreirdan@cable.comcast.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A05811E834E; Mon,  1 Jul 2013 17:49:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.231
X-Spam-Level: 
X-Spam-Status: No, score=-5.231 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oCkkngn6eoUW; Mon,  1 Jul 2013 17:49:33 -0700 (PDT)
Received: from cable.comcast.com (copdcavout01.cable.comcast.com [76.96.32.253]) by ietfa.amsl.com (Postfix) with ESMTP id 11CC421F99E1; Mon,  1 Jul 2013 17:49:32 -0700 (PDT)
Received: from ([24.40.56.114]) by copdcavout01.cable.comcast.com with ESMTP  id C7WM3M1.80425013; Mon, 01 Jul 2013 18:48:17 -0600
Received: from PACDCEXHUB05.cable.comcast.com (24.40.56.122) by PACDCEXHUB01.cable.comcast.com (24.40.56.114) with Microsoft SMTP Server (TLS) id 14.2.318.1; Mon, 1 Jul 2013 20:49:29 -0400
Received: from PACDCEXMB13.cable.comcast.com ([169.254.5.141]) by pacdcexhub05.cable.comcast.com ([fe80::3d40:bdea:7266:7f5a%18]) with mapi id 14.02.0318.001; Mon, 1 Jul 2013 20:49:29 -0400
From: "O'Reirdan, Michael" <Michael_OReirdan@Cable.Comcast.com>
To: "<ietf@ietf.org>" <ietf@ietf.org>, "<nomcom-chair-2013@ietf.org>" <nomcom-chair-2013@ietf.org>
Subject: Re: NOMCOM 2013-14 Volunteering - 3rd and Final Call for Volunteers
Thread-Topic: NOMCOM 2013-14 Volunteering - 3rd and Final Call for Volunteers
Thread-Index: AQHOdrrx6uLGqe5nNEuaJs4U1hzhYZlQjo4v
Date: Tue, 2 Jul 2013 00:49:29 +0000
Message-ID: <54AC6C53-7EDA-4674-9760-D077D6625A7D@Cable.Comcast.com>
References: <20130701234030.24738.41427.idtracker@ietfa.amsl.com>
In-Reply-To: <20130701234030.24738.41427.idtracker@ietfa.amsl.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 02 Jul 2013 08:34:31 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Jul 2013 00:49:39 -0000

Michael O'Reirdan
Attended 84, 85, 86
Comcast
Michael_oreirdan@cable.comcast.com
Use above address please
703-981-8895 or 856-433-0047


Sent from my iPhone

On Jul 1, 2013, at 20:27, "NomCom Chair 2013" <nomcom-chair-2013@ietf.org> =
wrote:

> Hi, everyone,
>=20
> We are short of our goal of 200 volunteers for the upcoming nomcom. =20
> Please do volunteer.  Our publicly verifiable random algorithm has fully=
=20
> adequate entropy for a flood of volunteers - more names, more names, more=
=20
> names, more brains --- er, oops, not yet a zombie. =20
>=20
> The more volunteers we get, the better chance we have of choosing a=20
> random yet representative cross section of the IETF.  Respond to this=20
> challenge and strengthen our statistical significance just by hitting=20
> Reply (but not Reply-All, please). =20
>=20
> Oh, first, please do check the official information:
> The IETF nominating committee (nomcom) process for 2013-14 is under way. =
The=20
> IETF nomcom appoints folks to fill the open slots on the IAOC, the IAB,
> and the IESG. Ten voting members for the nomcom are selected in a verifia=
bly
> random way from a pool of volunteers.=20
>=20
> The details of the selection and operation of the nomcom can be found=20
> in RFCs 3777, 5078, 5633, 5680, and 6859.  Four of those RFCs  (3777, 563=
3,=20
> 5680 and 6859)  comprise BCP 10. We will also reference RFC 3797.
>=20
> Volunteers must have attended 3 of the past 5 IETF meetings.  As specifie=
d in
> RFC 3777, that means three out of the five past meetings up to the time t=
his
> email announcement goes out to start the solicitation of volunteers. The =
five
> meetings out of which you must have attended three are IETF 82, 83, 84, 8=
5, 86.
>=20
> If you qualify, reply to this email and volunteer. =20
>=20
> The list of people and posts whose terms end with the March 2014 IETF
> meeting, and thus the positions for which this nomcom is responsible, are
> IAOC:
> Chris Griffiths
>=20
> IAB:
> Bernard Aboba
> Marc Blanchet
> Ross Callon
> Eliot Lear
> Hannes Tschofenig
>=20
> IESG:
> Barry Leiba (Applications)
> Brian Haberman (Internet)
> Benoit Claise (Operations and Management)
> Gonzalo Camarillo (RAI)
> Stewart Bryant (Routing)
> Sean Turner (Security)
> Martin Stiemerling (Transport)
>=20
> The primary activity for this nomcom will begin in July 2013 and should b=
e
> completed in January 2014.  Being a nomcom member will require some time
> commitment - there will be interviews with candidates at meetings, regula=
rly
> scheduled conference calls to ensure progress, collection and review of=20
> requirements from the commitment, review of candidate questionnaires and
> of community feedback.  A more detailed timetable for the nomcom tasks
> will appear soon.
>=20
> Please respond to this email before 23:59 EDT (UTC -4 hours)=20
> July 04, 2013.  In the body include:=20
> 1. your Given Name as you enter it when you register for the IETF
> 2. your Family Name as you enter it when you register for the IETF
> 3. your current primary affilation (the information you enter into the Co=
mpany field)
> 4. any/all email addresses you've used to register for IETF meetings=20
> 5. which email address you prefer=20
> 6. your phone number (for our use in confirming you if selected).
>=20
> On July 05, 2013 there will be an announcement of validated volunteers.  =
If you=20
> haven't received an acknowledgement message from me to your email=20
> (indicating that you are or are not eligible) and you do not see your nam=
e=20
> in the July 05 list, contact me AS SOON AS POSSIBLE, on or before July 06=
. =20
>=20
> Looking forward to adding your name to the "hat" very soon,
>=20
> Allison=20
>=20
> Allison Mankin
> Nomcom Chair 2013-2014
>=20

From rex_corpuz2003@yahoo.com  Mon Jul  1 22:51:51 2013
Return-Path: <rex_corpuz2003@yahoo.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC57911E83F1 for <ietf@ietfa.amsl.com>; Mon,  1 Jul 2013 22:51:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o-RExRXi6CTI for <ietf@ietfa.amsl.com>; Mon,  1 Jul 2013 22:51:34 -0700 (PDT)
Received: from nm13-vm3.bullet.mail.gq1.yahoo.com (nm13-vm3.bullet.mail.gq1.yahoo.com [98.136.218.222]) by ietfa.amsl.com (Postfix) with ESMTP id D179C11E83F5 for <ietf@ietf.org>; Mon,  1 Jul 2013 22:51:31 -0700 (PDT)
Received: from [216.39.60.184] by nm13.bullet.mail.gq1.yahoo.com with NNFMP; 02 Jul 2013 05:51:30 -0000
Received: from [208.71.42.211] by tm20.bullet.mail.gq1.yahoo.com with NNFMP; 02 Jul 2013 05:51:30 -0000
Received: from [127.0.0.1] by smtp222.mail.gq1.yahoo.com with NNFMP; 02 Jul 2013 05:51:30 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1372744290; bh=9UfZF2smgy8+A4kyYzzNCUoS248x3VBAXFNM+6ig7yg=; h=X-Yahoo-Newman-Id:Message-ID:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:X-Rocket-Received:MIME-Version:To:From:Subject:Date:Content-Type; b=5NuZJuWp9jjp6MGMCEWeQHopBQLcdQ9d1rWBiYeE0JuZ6lJx1wh5uK4H1oxzkrMUiFXSER+CxOQ8qHwV2oGW800mS8m4RgE/HyLgfNAg0Ve20E/vWAouHX2zdHuEGb/+kTuX0pzA52/UsxyMc6IidkOjf+mLMp0UJSJcR5hDza0=
X-Yahoo-Newman-Id: 246026.38898.bm@smtp222.mail.gq1.yahoo.com
Message-ID: <246026.38898.bm@smtp222.mail.gq1.yahoo.com>
X-Yahoo-Newman-Property: ymail-3
X-YMail-OSG: 5dBsQKAVM1nsU6dT7xeNU7Q3_v_6JxJFvoLeththOWnD2VE d2cG9RMxdsV2Nubxo2MW82eKotV.85kjqZaxbby9gmHjycPBSfrEPLVH24hv aeOf6X_rsNzlraHoRTkL72nw84s3QVCPnzbUOREPhbW6CLIxxyLp10Q_Qinj VdEjsvgrkiQP4to2ru2KHjSonT1I5ssPhGmWHO78kFhRndyQOW51uLk_kTJK TG3J0McG7Bz4CA_q6fk7S6o_E_95y.QzO9T8cQnSHaqlWzalhcTJBUNaF1DO Py8yjdbE4ZjrJWlYlFcP5W8IsE5fSNqp5ljeViiJcxnVDuCk2ydwfkaK.zSf IlDLpvK2X2rovEbbN3sFsS2Dv.s_G1esCqFlGSw3_3_n5qpQ3XgFmIej48dW jAV72CGVKL1Pcd8lB6EsJSFWX00w3bVVq8NpnzRFIu0A8yWwO.O7dBk6WmM1 LJkHKZvASs3gZsY6Yk20fYdVOsv3FINwL0PoyCzb4m5xy53wnCv7Tp_NJ5vW .o4E0hlJlRasxP2cYCQD26UCB4ZY.o0wvC5GVkdYjvYnTcQH23UvYYg2jotq OH_TUCTiGLQvoxwc-
X-Yahoo-SMTP: Rxz35suswBAnLITQGJxQaW6U75iVIxFKK88D
X-Rocket-Received: from [10.88.81.136] (rex_corpuz2003@112.198.90.223 with ) by smtp222.mail.gq1.yahoo.com with SMTP; 02 Jul 2013 05:51:30 +0000 UTC
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>,  "nomcom-chair-2013@ietf.org" <nomcom-chair-2013@ietf.org>
From: rex corpuz <rex_corpuz2003@yahoo.com>
Subject: RE: NOMCOM 2013-14 Volunteering - 3rd and Final Call for Volunteers
Date: Tue, 2 Jul 2013 13:50:54 +0800
Content-Type: multipart/alternative; boundary="_1C40C33D-6A36-4C5C-A102-1656E4B2BF2C_"
X-Mailman-Approved-At: Tue, 02 Jul 2013 08:34:46 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Jul 2013 05:51:51 -0000

--_1C40C33D-6A36-4C5C-A102-1656E4B2BF2C_
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"



-----Original Message-----
From: "NomCom Chair 2013" <nomcom-chair-2013@ietf.org>
Sent: =E2=80=8E7/=E2=80=8E2/=E2=80=8E2013 8:27 AM
To: "IETF Announcement List" <ietf-announce@ietf.org>
Cc: "IETF Discuss" <ietf@ietf.org>
Subject: NOMCOM 2013-14 Volunteering - 3rd and Final Call for Volunteers

Hi, everyone,

We are short of our goal of 200 volunteers for the upcoming nomcom. =20
Please do volunteer.  Our publicly verifiable random algorithm has fully=20
adequate entropy for a flood of volunteers - more names, more names, more=20
names, more brains --- er, oops, not yet a zombie. =20

The more volunteers we get, the better chance we have of choosing a=20
random yet representative cross section of the IETF.  Respond to this=20
challenge and strengthen our statistical significance just by hitting=20
Reply (but not Reply-All, please). =20

Oh, first, please do check the official information:
The IETF nominating committee (nomcom) process for 2013-14 is under way. Th=
e=20
IETF nomcom appoints folks to fill the open slots on the IAOC, the IAB,
and the IESG. Ten voting members for the nomcom are selected in a verifiabl=
y
random way from a pool of volunteers.=20

The details of the selection and operation of the nomcom can be found=20
in RFCs 3777, 5078, 5633, 5680, and 6859.  Four of those RFCs  (3777, 5633,=
=20
5680 and 6859)  comprise BCP 10. We will also reference RFC 3797.

Volunteers must have attended 3 of the past 5 IETF meetings.  As specified =
in
RFC 3777, that means three out of the five past meetings up to the time thi=
s
email announcement goes out to start the solicitation of volunteers. The fi=
ve
meetings out of which you must have attended three are IETF 82, 83, 84, 85,=
 86.

If you qualify, reply to this email and volunteer. =20

The list of people and posts whose terms end with the March 2014 IETF
meeting, and thus the positions for which this nomcom is responsible, are
IAOC:
Chris Griffiths

IAB:
Bernard Aboba
Marc Blanchet
Ross Callon
Eliot Lear
Hannes Tschofenig

IESG:
Barry Leiba (Applications)
Brian Haberman (Internet)
Benoit Claise (Operations and Management)
Gonzalo Camarillo (RAI)
Stewart Bryant (Routing)
Sean Turner (Security)
Martin Stiemerling (Transport)

The primary activity for this nomcom will begin in July 2013 and should be
completed in January 2014.  Being a nomcom member will require some time
commitment - there will be interviews with candidates at meetings, regularl=
y
scheduled conference calls to ensure progress, collection and review of=20
requirements from the commitment, review of candidate questionnaires and
of community feedback.  A more detailed timetable for the nomcom tasks
will appear soon.

Please respond to this email before 23:59 EDT (UTC -4 hours)=20
July 04, 2013.  In the body include:=20
 1. your Given Name as you enter it when you register for the IETF
 2. your Family Name as you enter it when you register for the IETF
 3. your current primary affilation (the information you enter into the Com=
pany field)
 4. any/all email addresses you've used to register for IETF meetings=20
 5. which email address you prefer=20
 6. your phone number (for our use in confirming you if selected).

On July 05, 2013 there will be an announcement of validated volunteers.  If=
 you=20
haven't received an acknowledgement message from me to your email=20
(indicating that you are or are not eligible) and you do not see your name=
=20
in the July 05 list, contact me AS SOON AS POSSIBLE, on or before July 06. =
=20

Looking forward to adding your name to the "hat" very soon,

Allison=20

Allison Mankin
Nomcom Chair 2013-2014


--_1C40C33D-6A36-4C5C-A102-1656E4B2BF2C_
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="utf-8"

<HTML><HEAD>
<META content=3D"text/html; charset=3Dutf-8" http-equiv=3DContent-Type></HE=
AD>
<BODY>
<DIV>
<DIV style=3D"FONT-SIZE: 11pt; FONT-FAMILY: Calibri,sans-serif"></DIV></DIV=
>
<DIV dir=3Dltr>
<HR>
<SPAN style=3D"FONT-SIZE: 11pt; FONT-FAMILY: Calibri,sans-serif; FONT-WEIGH=
T: bold">From: </SPAN><SPAN style=3D"FONT-SIZE: 11pt; FONT-FAMILY: Calibri,=
sans-serif"><A href=3D"mailto:nomcom-chair-2013@ietf.org">NomCom Chair 2013=
</A></SPAN><BR><SPAN style=3D"FONT-SIZE: 11pt; FONT-FAMILY: Calibri,sans-se=
rif; FONT-WEIGHT: bold">Sent: </SPAN><SPAN style=3D"FONT-SIZE: 11pt; FONT-F=
AMILY: Calibri,sans-serif">=E2=80=8E7/=E2=80=8E2/=E2=80=8E2013 8:27 AM</SPA=
N><BR><SPAN style=3D"FONT-SIZE: 11pt; FONT-FAMILY: Calibri,sans-serif; FONT=
-WEIGHT: bold">To: </SPAN><SPAN style=3D"FONT-SIZE: 11pt; FONT-FAMILY: Cali=
bri,sans-serif"><A href=3D"mailto:ietf-announce@ietf.org">IETF Announcement=
 List</A></SPAN><BR><SPAN style=3D"FONT-SIZE: 11pt; FONT-FAMILY: Calibri,sa=
ns-serif; FONT-WEIGHT: bold">Cc: </SPAN><SPAN style=3D"FONT-SIZE: 11pt; FON=
T-FAMILY: Calibri,sans-serif"><A href=3D"mailto:ietf@ietf.org">IETF Discuss=
</A></SPAN><BR><SPAN style=3D"FONT-SIZE: 11pt; FONT-FAMILY: Calibri,sans-se=
rif; FONT-WEIGHT: bold">Subject: </SPAN><SPAN style=3D"FONT-SIZE: 11pt; FON=
T-FAMILY: Calibri,sans-serif">NOMCOM 2013-14 Volunteering - 3rd and Final C=
all for Volunteers</SPAN><BR><BR></DIV>Hi, everyone,<BR><BR>We are short of=
 our goal of 200 volunteers for the upcoming nomcom.&nbsp; <BR>Please do vo=
lunteer.&nbsp; Our publicly verifiable random algorithm has fully <BR>adequ=
ate entropy for a flood of volunteers - more names, more names, more <BR>na=
mes, more brains --- er, oops, not yet a zombie.&nbsp; <BR><BR>The more vol=
unteers we get, the better chance we have of choosing a <BR>random yet repr=
esentative cross section of the IETF.&nbsp; Respond to this <BR>challenge a=
nd strengthen our statistical significance just by hitting <BR>Reply (but n=
ot Reply-All, please).&nbsp; <BR><BR>Oh, first, please do check the officia=
l information:<BR>The IETF nominating committee (nomcom) process for 2013-1=
4 is under way. The <BR>IETF nomcom appoints folks to fill the open slots o=
n the IAOC, the IAB,<BR>and the IESG. Ten voting members for the nomcom are=
 selected in a verifiably<BR>random way from a pool of volunteers. <BR><BR>=
The details of the selection and operation of the nomcom can be found <BR>i=
n RFCs 3777, 5078, 5633, 5680, and 6859.&nbsp; Four of those RFCs&nbsp; (37=
77, 5633, <BR>5680 and 6859)&nbsp; comprise BCP 10. We will also reference =
RFC 3797.<BR><BR>Volunteers must have attended 3 of the past 5 IETF meeting=
s.&nbsp; As specified in<BR>RFC 3777, that means three out of the five past=
 meetings up to the time this<BR>email announcement goes out to start the s=
olicitation of volunteers. The five<BR>meetings out of which you must have =
attended three are IETF 82, 83, 84, 85, 86.<BR><BR>If you qualify, reply to=
 this email and volunteer.&nbsp; <BR><BR>The list of people and posts whose=
 terms end with the March 2014 IETF<BR>meeting, and thus the positions for =
which this nomcom is responsible, are<BR>IAOC:<BR>Chris Griffiths<BR><BR>IA=
B:<BR>Bernard Aboba<BR>Marc Blanchet<BR>Ross Callon<BR>Eliot Lear<BR>Hannes=
 Tschofenig<BR><BR>IESG:<BR>Barry Leiba (Applications)<BR>Brian Haberman (I=
nternet)<BR>Benoit Claise (Operations and Management)<BR>Gonzalo Camarillo =
(RAI)<BR>Stewart Bryant (Routing)<BR>Sean Turner (Security)<BR>Martin Stiem=
erling (Transport)<BR><BR>The primary activity for this nomcom will begin i=
n July 2013 and should be<BR>completed in January 2014.&nbsp; Being a nomco=
m member will require some time<BR>commitment - there will be interviews wi=
th candidates at meetings, regularly<BR>scheduled conference calls to ensur=
e progress, collection and review of <BR>requirements from the commitment, =
review of candidate questionnaires and<BR>of community feedback.&nbsp; A mo=
re detailed timetable for the nomcom tasks<BR>will appear soon.<BR><BR>Plea=
se respond to this email before 23:59 EDT (UTC -4 hours) <BR>July 04, 2013.=
&nbsp; In the body include: <BR>1. your Given Name as you enter it when you=
 register for the IETF<BR>2. your Family Name as you enter it when you regi=
ster for the IETF<BR>3. your current primary affilation (the information yo=
u enter into the Company field)<BR>4. any/all email addresses you've used t=
o register for IETF meetings <BR>5. which email address you prefer <BR>6. y=
our phone number (for our use in confirming you if selected).<BR><BR>On Jul=
y 05, 2013 there will be an announcement of validated volunteers.&nbsp; If =
you <BR>haven't received an acknowledgement message from me to your email <=
BR>(indicating that you are or are not eligible) and you do not see your na=
me <BR>in the July 05 list, contact me AS SOON AS POSSIBLE, on or before Ju=
ly 06.&nbsp; <BR><BR>Looking forward to adding your name to the "hat" very =
soon,<BR><BR>Allison <BR><BR>Allison Mankin<BR>Nomcom Chair 2013-2014<BR><B=
R></BODY></HTML>=

--_1C40C33D-6A36-4C5C-A102-1656E4B2BF2C_--


From john-ietf@jck.com  Tue Jul  2 09:10:10 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2188921F9B9C; Tue,  2 Jul 2013 09:10:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level: 
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o2ud0bazl4aG; Tue,  2 Jul 2013 09:10:04 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id A22B221F9977; Tue,  2 Jul 2013 09:09:35 -0700 (PDT)
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 1Uu395-000PgU-7R; Tue, 02 Jul 2013 12:09:35 -0400
Date: Tue, 02 Jul 2013 12:09:30 -0400
From: John C Klensin <john-ietf@jck.com>
To: nomcom-chair-2013@ietf.org
Subject: RE: NOMCOM 2013-14 Volunteering - 3rd and Final Call for Volunteers
Message-ID: <4A633BA297B3C6F1CD64C02C@JcK-HP8200.jck.com>
In-Reply-To: <246026.38898.bm@smtp222.mail.gq1.yahoo.com>
References: <246026.38898.bm@smtp222.mail.gq1.yahoo.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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Jul 2013 16:10:10 -0000

Allison,

Just one or two observations...

--On Tuesday, July 02, 2013 13:50 +0800 rex corpuz
<rex_corpuz2003@yahoo.com> wrote:

>...
> The more volunteers we get, the better chance we have of
> choosing a  random yet representative cross section of the
> IETF.  Respond to this  challenge and strengthen our
> statistical significance...

You must know that statement isn't true and I think it would
actually help the IETF is we stopped kidding ourselves about it.
>From an almost-elementary statistical standpoint, increasing the
sample proportion within a particular subset of a population has
nothing to do with strengthening the statistical significance or
representativeness of the total population.

As other recent conversations have illustrated, that particular
subset excludes those who don't attend lots of meetings f2f, it
excludes those who are wiling to serve in positions the Nomcom
appoints (and who believe that they have or could obtain the
resources and support to do so), and it excludes anyone who
lacks the time, support, and resources to make a major
commitment to the Nomcom for an extended period.  Some of the
community would argue that those restrictions are A Good Thing
and create a better Nomcom than we would have with a
representative cross section of the IETF.  Others would (and
have) argued that those restrictions are both a problem in
themselves and an important contributor to less diversity than
they think desirable.  But it is, IMO, impossible to argue that
a group selected under those restrictions represents a
statistically-valid sample of the community (or, in different
language, a cross-section of that community).  Selecting more
people from that same pool doesn't increase the odds of getting
a valid cross-section of the community, it just increases the
odds of getting a valid cross-section of the pool.

Again, I'm not arguing, at least in this note, that the pool
from which you are soliciting volunteers isn't appropriate
and/or the absolutely best we can do or even what we want
whether it is or not.  But we should stop pretending that it
represents a statistically-valid cross-section of the community,
much less that getting more volunteers has anything to do with
that.

best,
  john




From d3e3e3@gmail.com  Tue Jul  2 09:59:56 2013
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F66611E80CC for <ietf@ietfa.amsl.com>; Tue,  2 Jul 2013 09:59:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mf33KiypX0au for <ietf@ietfa.amsl.com>; Tue,  2 Jul 2013 09:59:55 -0700 (PDT)
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 75A2411E80AD for <ietf@ietf.org>; Tue,  2 Jul 2013 09:59:55 -0700 (PDT)
Received: by mail-oa0-f48.google.com with SMTP id f4so6733327oah.35 for <ietf@ietf.org>; Tue, 02 Jul 2013 09:59:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=hB5IS4YtPXME5SX59ahcLpRGcagbpZHw8ob0okpL+yk=; b=gJm3bGWpV3Ybz4CqDnQjFCwpTPeAKrb20OTg9Sdusl4Gn9enQ3+iAfCWP0ml/ncZ3P 71W2pmX0kTrVEqp+sr7qzrb4roCkWOR8PFu9u2D9tbaeH7fKvUGabREYkW64Ac+fRG97 HZt+96RxK124kCExC2lWXfdfBNxL+NOqUmqOQDaflTf58bL7XRpKWgu53LuulQB6tzBE 5XyE6zx3bnFKb+Whz8jXFjUN5mLFa6Wlz/escIb7cwo8grOb+8EM4PQirx814pWyL2lo G9jGFpgMZKo8U8je1ZvcJWKdhaAQZ5xvJCj3uQP2OKlBlgsVWgFNVBUIn+9XGWuBK901 b+6A==
X-Received: by 10.60.42.101 with SMTP id n5mr12056777oel.4.1372784395024; Tue, 02 Jul 2013 09:59:55 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.73.106 with HTTP; Tue, 2 Jul 2013 09:59:34 -0700 (PDT)
In-Reply-To: <20130701234030.24738.41427.idtracker@ietfa.amsl.com>
References: <20130701234030.24738.41427.idtracker@ietfa.amsl.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 2 Jul 2013 12:59:34 -0400
Message-ID: <CAF4+nEFBcy0KwXqfDpNARcmk-EdyyJfanCmc_=Fp7D06nAtwzg@mail.gmail.com>
Subject: Re: NOMCOM 2013-14 Volunteering - 3rd and Final Call for Volunteers
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Jul 2013 16:59:56 -0000

Hi,

On Mon, Jul 1, 2013 at 7:40 PM, NomCom Chair 2013
<nomcom-chair-2013@ietf.org> wrote:
> Hi, everyone,
>
> We are short of our goal of 200 volunteers for the upcoming nomcom.
> Please do volunteer.  Our publicly verifiable random algorithm has fully
> adequate entropy for a flood of volunteers - more names, more names, more
> names, more brains --- er, oops, not yet a zombie.
>
> The more volunteers we get, the better chance we have of choosing a
> random yet representative cross section of the IETF.  Respond to this
> challenge and strengthen our statistical significance just by hitting
> Reply (but not Reply-All, please).

The "goal" of 200 volunteers seems totally arbitrary to me. I
understand that there is a wide range of opinions here, but I do not
believe that the noncom is intended to be or should be a
"representative" sample from those who just barely qualify as eligible
to be volunteers under the current rules.

Why is the "quality" of volunteers ignored in comparison with the
quantity? No doubt many will strongly object to my use of "quality"
but by that I mean understanding of the IETF culture and the IETF goal
of benefiting the Internet community and a goodly amount of experience
with IETF processes.

For example, producing RFCs is clearly a large part of the IETF. Let's
assume that, under current conditions, using only recent attendance as
a qualifying criterion, we can get ~200 eligible volunteers but that
adding the additional restriction that volunteers must have been a
front page author/editor of an RFC issued within the past X years for
some X would reduce the number of eligible volunteers to ~100. While I
admit there is some volunteer pool size that would be "too small" (40?
opinions will differ), my opinion is that 100 is more than enough and
that such a change, to produce a pool of stronger and better qualified
volunteers, would be an improvement.

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

> Oh, first, please do check the official information:
> The IETF nominating committee (nomcom) process for 2013-14 is under way. The
> IETF nomcom appoints folks to fill the open slots on the IAOC, the IAB,
> and the IESG. Ten voting members for the nomcom are selected in a verifiably
> random way from a pool of volunteers.
>
> The details of the selection and operation of the nomcom can be found
> in RFCs 3777, 5078, 5633, 5680, and 6859.  Four of those RFCs  (3777, 5633,
> 5680 and 6859)  comprise BCP 10. We will also reference RFC 3797.
>
> Volunteers must have attended 3 of the past 5 IETF meetings.  As specified in
> RFC 3777, that means three out of the five past meetings up to the time this
> email announcement goes out to start the solicitation of volunteers. The five
> meetings out of which you must have attended three are IETF 82, 83, 84, 85, 86.
>
> If you qualify, reply to this email and volunteer.
>
> The list of people and posts whose terms end with the March 2014 IETF
> meeting, and thus the positions for which this nomcom is responsible, are
> IAOC:
> Chris Griffiths
>
> IAB:
> Bernard Aboba
> Marc Blanchet
> Ross Callon
> Eliot Lear
> Hannes Tschofenig
>
> IESG:
> Barry Leiba (Applications)
> Brian Haberman (Internet)
> Benoit Claise (Operations and Management)
> Gonzalo Camarillo (RAI)
> Stewart Bryant (Routing)
> Sean Turner (Security)
> Martin Stiemerling (Transport)
>
> The primary activity for this nomcom will begin in July 2013 and should be
> completed in January 2014.  Being a nomcom member will require some time
> commitment - there will be interviews with candidates at meetings, regularly
> scheduled conference calls to ensure progress, collection and review of
> requirements from the commitment, review of candidate questionnaires and
> of community feedback.  A more detailed timetable for the nomcom tasks
> will appear soon.
>
> Please respond to this email before 23:59 EDT (UTC -4 hours)
> July 04, 2013.  In the body include:
>  1. your Given Name as you enter it when you register for the IETF
>  2. your Family Name as you enter it when you register for the IETF
>  3. your current primary affilation (the information you enter into the Company field)
>  4. any/all email addresses you've used to register for IETF meetings
>  5. which email address you prefer
>  6. your phone number (for our use in confirming you if selected).
>
> On July 05, 2013 there will be an announcement of validated volunteers.  If you
> haven't received an acknowledgement message from me to your email
> (indicating that you are or are not eligible) and you do not see your name
> in the July 05 list, contact me AS SOON AS POSSIBLE, on or before July 06.
>
> Looking forward to adding your name to the "hat" very soon,
>
> Allison
>
> Allison Mankin
> Nomcom Chair 2013-2014
>

From l.wood@surrey.ac.uk  Tue Jul  2 16:39:20 2013
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B7D511E80E6 for <ietf@ietfa.amsl.com>; Tue,  2 Jul 2013 16:39:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 47PJEztbdCwK for <ietf@ietfa.amsl.com>; Tue,  2 Jul 2013 16:39:16 -0700 (PDT)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.165]) by ietfa.amsl.com (Postfix) with ESMTP id A362811E80F2 for <ietf@ietf.org>; Tue,  2 Jul 2013 16:39:14 -0700 (PDT)
Received: from [195.245.230.131:57896] by server-5.bemta-3.messagelabs.com id B8/78-15398-1A463D15; Tue, 02 Jul 2013 23:39:13 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-7.tower-78.messagelabs.com!1372808352!27123843!1
X-Originating-IP: [131.227.200.35]
X-StarScan-Received: 
X-StarScan-Version: 6.9.9; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 9623 invoked from network); 2 Jul 2013 23:39:13 -0000
Received: from exht021p.surrey.ac.uk (HELO EXHT021P.surrey.ac.uk) (131.227.200.35) by server-7.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 2 Jul 2013 23:39:13 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT021P.surrey.ac.uk ([131.227.200.35]) with mapi; Wed, 3 Jul 2013 00:39:12 +0100
From: <l.wood@surrey.ac.uk>
To: <ietf@ietf.org>
Date: Wed, 3 Jul 2013 00:37:10 +0100
Subject: RE: Appeal Response to Abdussalam Baryun regarding draft-ietf-manet-nhdp-sec-threats
Thread-Topic: Appeal Response to Abdussalam Baryun regarding draft-ietf-manet-nhdp-sec-threats
Thread-Index: Ac53cxt+ShobSeljSVqU9lT9TWbFpQACfdAo
Message-ID: <290E20B455C66743BE178C5C84F12408223F494ECC@EXMB01CMS.surrey.ac.uk>
References: <20130702222442.2467.13086.idtracker@ietfa.amsl.com>
In-Reply-To: <20130702222442.2467.13086.idtracker@ietfa.amsl.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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Jul 2013 23:39:20 -0000

Do we have any statistics on how many appeals to the IESG fail and how many=
 succeed?

If I knew that 97% of appeals get rejected, I wouldn't even bother writing =
one...

(On the other hand, that might simply be because 97% of the appeals are wri=
tten by loons. Statistics can't tell us everything.)

Lloyd Wood
http://sat-net.com/L.Wood/


________________________________________
From: ietf-announce-bounces@ietf.org [ietf-announce-bounces@ietf.org] On Be=
half Of The IESG [iesg@ietf.org]
Sent: 02 July 2013 23:24
To: abdussalambaryun@gmail.com
Cc: ietf-announce@ietf.org
Subject: Appeal Response to Abdussalam Baryun regarding draft-ietf-manet-nh=
dp-sec-threats

The IESG has reviewed the appeal of Abdussalam Baryun dated June 19,
2013 on the subject of inclusion in the acknowledgments section of
draft-ietf-manet-nhdp-sec-threats:

http://www.ietf.org/iesg/appeal/baryun-2013-06-19.txt

This is a dispute about a matter in a working group. The same matter has
previously been raised with the working group chairs and responsible
Area Director, as specified in RFC 2026 Section 6.5.1.

Writing acknowledgments sections is largely a matter of editorial
discretion, where good sense and general attribution practices are the
primary guidelines, although RFC 2026 Section 10.3.1 has some specific
rules regarding acknowledgment of major contributors, copyright, and
IPR.

After reviewing the appeal, including the associated list discussion and
draft revisions, the IESG concludes that the authors made a reasonable
editorial choice that was well within their discretion and that none of
the messages at issue fall under the required acknowledgment rules of
RFC 2026 Section 10.3.1 and RFC 5378 Sections 5.6a and 1c. The IESG
finds that the chairs and responsible AD handled complaints about the
matter appropriately.

From bob.hinden@gmail.com  Tue Jul  2 17:09:00 2013
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 231AC21F99A9 for <ietf@ietfa.amsl.com>; Tue,  2 Jul 2013 17:09:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zxHmXc3SmXz1 for <ietf@ietfa.amsl.com>; Tue,  2 Jul 2013 17:08:59 -0700 (PDT)
Received: from mail-qa0-x230.google.com (mail-qa0-x230.google.com [IPv6:2607:f8b0:400d:c00::230]) by ietfa.amsl.com (Postfix) with ESMTP id 2376321F99A1 for <ietf@ietf.org>; Tue,  2 Jul 2013 17:08:59 -0700 (PDT)
Received: by mail-qa0-f48.google.com with SMTP id cm16so3250482qab.14 for <ietf@ietf.org>; Tue, 02 Jul 2013 17:08:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=JRie1QMriHikXqSmoLXO475bMP5fpgGX8Qjoj/v70Pw=; b=L9XqX6ddmsP7Lv3JBcNG78OnbTQH/Iar7jAzppib/RwRQPA38BkVi/8TPs0dToraYU 8TqU7p+e6/nb2rDSKz5Qz9hWpGycoifU05JTPynECQNHyM8miVMkH/+FNL13p95AYVEB 5W5v11SE76kLKz6QXG7MsIrF6b2KTXru7IE4I1ckmcyTWHBFectjTNhkcs0qxiSmkTPB YbnhHnjNiU5WzgWIX7MYEzJkOs2xM1TvW5ez2jtf9eCZlRZY70x/B80YGCBadB6rrRsM 0xy31qrwSG3VNpasLFuqSRGmTgBT8LxEQ5vRPy91XqFocZV+3rmMN3U9h0DZrnXQvgRD /KAA==
X-Received: by 10.229.114.85 with SMTP id d21mr9698544qcq.1.1372810138633; Tue, 02 Jul 2013 17:08:58 -0700 (PDT)
Received: from [172.16.224.219] ([209.97.127.34]) by mx.google.com with ESMTPSA id n7sm40258742qat.1.2013.07.02.17.08.56 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 02 Jul 2013 17:08:57 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Appeal Response to Abdussalam Baryun regarding draft-ietf-manet-nhdp-sec-threats
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <290E20B455C66743BE178C5C84F12408223F494ECC@EXMB01CMS.surrey.ac.uk>
Date: Tue, 2 Jul 2013 17:08:55 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <CA708780-4D97-4E34-8EDD-BAC7D2E8FE93@gmail.com>
References: <20130702222442.2467.13086.idtracker@ietfa.amsl.com> <290E20B455C66743BE178C5C84F12408223F494ECC@EXMB01CMS.surrey.ac.uk>
To: l.wood@surrey.ac.uk
X-Mailer: Apple Mail (2.1508)
Cc: Bob Hinden <bob.hinden@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Jul 2013 00:09:00 -0000

Lloyd,



On Jul 2, 2013, at 4:37 PM, l.wood@surrey.ac.uk wrote:

> Do we have any statistics on how many appeals to the IESG fail and how =
many succeed?

Appeals are listed at:

   https://www.ietf.org/iesg/appeal.html

Bob

>=20
> If I knew that 97% of appeals get rejected, I wouldn't even bother =
writing one...
>=20
> (On the other hand, that might simply be because 97% of the appeals =
are written by loons. Statistics can't tell us everything.)
>=20
> Lloyd Wood
> http://sat-net.com/L.Wood/
>=20


From randy@psg.com  Tue Jul  2 17:19:31 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BCC921F8E2A for <ietf@ietfa.amsl.com>; Tue,  2 Jul 2013 17:19:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.578
X-Spam-Level: 
X-Spam-Status: No, score=-2.578 tagged_above=-999 required=5 tests=[AWL=0.021,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0gazhGg2nJbG for <ietf@ietfa.amsl.com>; Tue,  2 Jul 2013 17:19:31 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 0366D21F8C4B for <ietf@ietf.org>; Tue,  2 Jul 2013 17:19:31 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1UuAnB-000J9j-Nf; Wed, 03 Jul 2013 00:19:30 +0000
Date: Wed, 03 Jul 2013 09:19:28 +0900
Message-ID: <m2mwq4o5pr.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: <l.wood@surrey.ac.uk>
Subject: Re: Appeal Response to Abdussalam Baryun regarding	draft-ietf-manet-nhdp-sec-threats
In-Reply-To: <290E20B455C66743BE178C5C84F12408223F494ECC@EXMB01CMS.surrey.ac.uk>
References: <20130702222442.2467.13086.idtracker@ietfa.amsl.com> <290E20B455C66743BE178C5C84F12408223F494ECC@EXMB01CMS.surrey.ac.uk>
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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Jul 2013 00:19:31 -0000

> If I knew that 97% of appeals get rejected, I wouldn't even bother
> writing one...

i have never considered writng one.  sour grapes make bad wine.

randy

From housley@vigilsec.com  Tue Jul  2 19:23:46 2013
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50FBF11E813B for <ietf@ietfa.amsl.com>; Tue,  2 Jul 2013 19:23:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.508
X-Spam-Level: 
X-Spam-Status: No, score=-102.508 tagged_above=-999 required=5 tests=[AWL=0.091, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lnXfTT1ZCNIo for <ietf@ietfa.amsl.com>; Tue,  2 Jul 2013 19:23:41 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 1D60111E80AD for <ietf@ietf.org>; Tue,  2 Jul 2013 19:23:41 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 4D83DF2407E; Tue,  2 Jul 2013 22:23:45 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id M6wh-Y0HQEj8; Tue,  2 Jul 2013 22:23:38 -0400 (EDT)
Received: from [192.168.2.109] (pool-96-241-156-29.washdc.fios.verizon.net [96.241.156.29]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id DF3FDF2407C; Tue,  2 Jul 2013 22:23:43 -0400 (EDT)
Subject: Re: Appeal Response to Abdussalam Baryun regarding draft-ietf-manet-nhdp-sec-threats
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <290E20B455C66743BE178C5C84F12408223F494ECC@EXMB01CMS.surrey.ac.uk>
Date: Tue, 2 Jul 2013 22:23:36 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <EAC216DF-EB02-4BD2-A9DC-37873F3DFD0E@vigilsec.com>
References: <20130702222442.2467.13086.idtracker@ietfa.amsl.com> <290E20B455C66743BE178C5C84F12408223F494ECC@EXMB01CMS.surrey.ac.uk>
To: <l.wood@surrey.ac.uk>
X-Mailer: Apple Mail (2.1085)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Jul 2013 02:23:46 -0000

http://www.ietf.org/iesg/appeal.html

Every appeal ever submitted to the IESG and its response can be found =
here.




On Jul 2, 2013, at 7:37 PM, <l.wood@surrey.ac.uk> wrote:

> Do we have any statistics on how many appeals to the IESG fail and how =
many succeed?
>=20
> If I knew that 97% of appeals get rejected, I wouldn't even bother =
writing one...
>=20
> (On the other hand, that might simply be because 97% of the appeals =
are written by loons. Statistics can't tell us everything.)
>=20
> Lloyd Wood
> http://sat-net.com/L.Wood/
>=20
>=20
> ________________________________________
> From: ietf-announce-bounces@ietf.org [ietf-announce-bounces@ietf.org] =
On Behalf Of The IESG [iesg@ietf.org]
> Sent: 02 July 2013 23:24
> To: abdussalambaryun@gmail.com
> Cc: ietf-announce@ietf.org
> Subject: Appeal Response to Abdussalam Baryun regarding =
draft-ietf-manet-nhdp-sec-threats
>=20
> The IESG has reviewed the appeal of Abdussalam Baryun dated June 19,
> 2013 on the subject of inclusion in the acknowledgments section of
> draft-ietf-manet-nhdp-sec-threats:
>=20
> http://www.ietf.org/iesg/appeal/baryun-2013-06-19.txt
>=20
> This is a dispute about a matter in a working group. The same matter =
has
> previously been raised with the working group chairs and responsible
> Area Director, as specified in RFC 2026 Section 6.5.1.
>=20
> Writing acknowledgments sections is largely a matter of editorial
> discretion, where good sense and general attribution practices are the
> primary guidelines, although RFC 2026 Section 10.3.1 has some specific
> rules regarding acknowledgment of major contributors, copyright, and
> IPR.
>=20
> After reviewing the appeal, including the associated list discussion =
and
> draft revisions, the IESG concludes that the authors made a reasonable
> editorial choice that was well within their discretion and that none =
of
> the messages at issue fall under the required acknowledgment rules of
> RFC 2026 Section 10.3.1 and RFC 5378 Sections 5.6a and 1c. The IESG
> finds that the chairs and responsible AD handled complaints about the
> matter appropriately.


From johnl@iecc.com  Tue Jul  2 19:43:53 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46B5C11E8141 for <ietf@ietfa.amsl.com>; Tue,  2 Jul 2013 19:43:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.608
X-Spam-Level: 
X-Spam-Status: No, score=-110.608 tagged_above=-999 required=5 tests=[AWL=0.591, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JRY5R6L2D-5Z for <ietf@ietfa.amsl.com>; Tue,  2 Jul 2013 19:43:39 -0700 (PDT)
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 9557D11E8135 for <ietf@ietf.org>; Tue,  2 Jul 2013 19:43:39 -0700 (PDT)
Received: (qmail 20870 invoked from network); 3 Jul 2013 02:43:36 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 3 Jul 2013 02:43:36 -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=51d38fd8.xn--yuvv84g.k1307; i=johnl@user.iecc.com; bh=2A9fIcO3qYcUY5yVSx3y60bX4xRHQan9hXKY4akiJaQ=; b=zlaW13+gsa5uzunI2oPkyNn67WXnCHtlPGCgjn7FdxQN5YQ240yHMIC1OdsGLWO7h8Fax0bOUXaSevTP3Wj7TvF4uOLeC0L2yBPUQBgg9JDsLChwLuRCGIXwTH+7Oodwpplnhtog1CiVt7ubFII9wXXcCA3/fNPzNOBdHYDAKZ8KP+wQKrWWW7cjzegKVK8EyUcLGIU7hOulPKl0iJemdp6B7WkjvOKZeKVGrBu8v7Gjgp0eWxtRwzZlIcRGrTjm
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=51d38fd8.xn--yuvv84g.k1307; olt=johnl@user.iecc.com; bh=2A9fIcO3qYcUY5yVSx3y60bX4xRHQan9hXKY4akiJaQ=; b=MkT8E7RsRhauDUJvQIElbHOkqjx0mvRPXfZkcE7vHgIqFKYygc381LyKZmcPczEWNsh8QeH5XXlr/ACpbc2HvY9Mhge/EWVRSDASUdukXh9MGo50fsBSMhcR2baWPRu1mDnfq1GZwMnzBP7OGZqQiaqeiRvbz5Y9HlY6qpkpj+esWShZqD2uVh5fQcJ7xx//m0UjD967yemalzM2HpLUIaE/Y0g/4Zfddbr+UF7TelLPW7qiE0HG0VuEnFt4aloF
Date: 3 Jul 2013 02:43:13 -0000
Message-ID: <20130703024313.23209.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: submission tool not sending confirmations ?
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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Jul 2013 02:43:53 -0000

I'm trying to submit and I-D, and I'm not getting the usual
confirmation mail.  My mail logs show nothing, no attempts, no
failures.  It worked the last time I tried it on Sunday.  (Yes,
I gave it a working address.)

Anyone else seeing this?

R's,
John



From brian.e.carpenter@gmail.com  Tue Jul  2 20:10:23 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D121B11E8149 for <ietf@ietfa.amsl.com>; Tue,  2 Jul 2013 20:10:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.392
X-Spam-Level: 
X-Spam-Status: No, score=-102.392 tagged_above=-999 required=5 tests=[AWL=0.207, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iSAgluFARSvs for <ietf@ietfa.amsl.com>; Tue,  2 Jul 2013 20:10:23 -0700 (PDT)
Received: from mail-pb0-x22d.google.com (mail-pb0-x22d.google.com [IPv6:2607:f8b0:400e:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 36A8511E8135 for <ietf@ietf.org>; Tue,  2 Jul 2013 20:10:23 -0700 (PDT)
Received: by mail-pb0-f45.google.com with SMTP id mc8so6845464pbc.32 for <ietf@ietf.org>; Tue, 02 Jul 2013 20:10:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=aB2p7Dm4ytcXBVYHgSV7c8qPzY1GeEv0FO9fX5fB7X0=; b=dywHOtY4jOi1a/0bizAgziOIY3C0szXuhCwH4h3dCoGqMTgyhCH5Y7Qtq//gWepPWa HeptC01HwczsMoE1xxtNyYHdn402RnjmVrVlARWNptEmuEIVTwPE3snRC/8knHT9lDUl jO9qvoYAUSsteyV6Bwjy1LXl7cQg10OqFar3Or636iOUiwGakv7c8anuX8+NTsUKgLE3 sswKKdFAS0oQunHJLyrbn/QkbSVIe6Okp0hfqSw63wcA72equoN7XWq/WC2eM580cD2q aci+RXwnQsbknytNntkd4kk/oui8WMknEYwgQsC1TUIOofadhQlmzOKSQSEGuzwWxont +WgA==
X-Received: by 10.66.144.199 with SMTP id so7mr557130pab.99.1372821022899; Tue, 02 Jul 2013 20:10:22 -0700 (PDT)
Received: from [192.168.178.23] (209.198.69.111.dynamic.snap.net.nz. [111.69.198.209]) by mx.google.com with ESMTPSA id wi6sm29761858pbc.22.2013.07.02.20.10.20 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 02 Jul 2013 20:10:22 -0700 (PDT)
Message-ID: <51D3961F.6010008@gmail.com>
Date: Wed, 03 Jul 2013 15:10:23 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
Subject: Re: Appeal Response to Abdussalam Baryun regarding draft-ietf-manet-nhdp-sec-threats
References: <20130702222442.2467.13086.idtracker@ietfa.amsl.com>	<290E20B455C66743BE178C5C84F12408223F494ECC@EXMB01CMS.surrey.ac.uk> <EAC216DF-EB02-4BD2-A9DC-37873F3DFD0E@vigilsec.com>
In-Reply-To: <EAC216DF-EB02-4BD2-A9DC-37873F3DFD0E@vigilsec.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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Jul 2013 03:10:23 -0000

On 03/07/2013 14:23, Russ Housley wrote:
> http://www.ietf.org/iesg/appeal.html
> 
> Every appeal ever submitted to the IESG and its response can be found here.

...since late 2002, that is. There were appeals earlier in history. The
first one I recall reached the IAB in 1995, and had presumably already
been rejected by the IESG. However, statistics since 2002 are probably
enough.

I'd say that rejected appeals quite often lead to clarification of
procedures for the future; therefore they have value, even if it
isn't immediately obvious.

   Brian

From warren@kumari.net  Tue Jul  2 20:33:11 2013
Return-Path: <warren@kumari.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2D6711E814C for <ietf@ietfa.amsl.com>; Tue,  2 Jul 2013 20:33:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w4940f0zXzxE for <ietf@ietfa.amsl.com>; Tue,  2 Jul 2013 20:33:06 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1831611E8149 for <ietf@ietf.org>; Tue,  2 Jul 2013 20:33:05 -0700 (PDT)
Received: from [192.168.1.153] (unknown [66.84.81.89]) by vimes.kumari.net (Postfix) with ESMTPSA id 3BFB91B407D8; Tue,  2 Jul 2013 23:33:04 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [IETF] submission tool not sending confirmations ?
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <20130703024313.23209.qmail@joyce.lan>
Date: Tue, 2 Jul 2013 23:33:02 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <F25FEA5D-0377-4065-87DD-FEE026B8FFD8@kumari.net>
References: <20130703024313.23209.qmail@joyce.lan>
To: "John Levine" <johnl@taugh.com>
X-Mailer: Apple Mail (2.1508)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Jul 2013 03:33:12 -0000

On Jul 2, 2013, at 10:43 PM, "John Levine" <johnl@taugh.com> wrote:

> I'm trying to submit and I-D, and I'm not getting the usual
> confirmation mail.  My mail logs show nothing, no attempts, no
> failures.  It worked the last time I tried it on Sunday.  (Yes,
> I gave it a working address.)
>=20
> Anyone else seeing this?

Happened to me recently -- I ended up opening a ticket..=20

Then I discovered the issue -- I was adding myself as a co-author on an =
existing draft -- in order to prevent shenanigans, an *existing* author =
has to submit it.=20
Perhaps this is your issue?

Anyway, Henrik / the tools folk are planning on adding a descriptive =
error message for the above.

W

>=20
> R's,
> John
>=20
>=20

--
"I think perhaps the most important problem is that we are trying to =
understand the fundamental workings of the universe via a language =
devised for telling one another when the best fruit is." --Terry =
Prachett=20



From dhc@dcrocker.net  Tue Jul  2 20:44:16 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1400421F8C4B for <ietf@ietfa.amsl.com>; Tue,  2 Jul 2013 20:44:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HmZBh+O01KzL for <ietf@ietfa.amsl.com>; Tue,  2 Jul 2013 20:44:11 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id A607721F994A for <ietf@ietf.org>; Tue,  2 Jul 2013 20:44:11 -0700 (PDT)
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 r633i64D014844 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 2 Jul 2013 20:44:09 -0700
Message-ID: <51D39DF8.6020300@dcrocker.net>
Date: Tue, 02 Jul 2013 20:43:52 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Appeal Response to Abdussalam Baryun regarding draft-ietf-manet-nhdp-sec-threats
References: <20130702222442.2467.13086.idtracker@ietfa.amsl.com>	<290E20B455C66743BE178C5C84F12408223F494ECC@EXMB01CMS.surrey.ac.uk> <EAC216DF-EB02-4BD2-A9DC-37873F3DFD0E@vigilsec.com> <51D3961F.6010008@gmail.com>
In-Reply-To: <51D3961F.6010008@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Tue, 02 Jul 2013 20:44:09 -0700 (PDT)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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, 03 Jul 2013 03:44:16 -0000

On 7/2/2013 8:10 PM, Brian E Carpenter wrote:
> On 03/07/2013 14:23, Russ Housley wrote:
>> http://www.ietf.org/iesg/appeal.html
>>
>> Every appeal ever submitted to the IESG and its response can be found here.
>
> ...since late 2002, that is. There were appeals earlier in history. The
> first one I recall reached the IAB in 1995, and had presumably already
> been rejected by the IESG. However, statistics since 2002 are probably
> enough.


I believe I submitted the first appeal.  It was to break a logjam with 
the the IETF's failure to sign an agreement with Sun, to get NFS brought 
into the IETF.  I had been the cognizant AD when they approached the 
IETF, but the ball got dropped after that.

So it wasn't so much 'rejected' by the IESG as it was cast in terms of 
IESG failure, although really no one was quite sure who needed to sign 
the contract with Sun and everyone was afraid of doing it.

My reading of the appeal was that it succeeded, in that the agreement 
with Sun was signed shortly after that and the IETF took over the NFS 
specification.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From jari.arkko@piuha.net  Tue Jul  2 22:19:28 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5D1C21F9051 for <ietf@ietfa.amsl.com>; Tue,  2 Jul 2013 22:19:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.619
X-Spam-Level: 
X-Spam-Status: No, score=-102.619 tagged_above=-999 required=5 tests=[AWL=-0.020, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z9-8LwbPCDVq for <ietf@ietfa.amsl.com>; Tue,  2 Jul 2013 22:19:23 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 3340721F8F38 for <ietf@ietf.org>; Tue,  2 Jul 2013 22:19:23 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id AC02E2CC53; Wed,  3 Jul 2013 08:19:21 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zdwU0GQbi0bS; Wed,  3 Jul 2013 08:19:21 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id B42AF2CC3C; Wed,  3 Jul 2013 08:19:20 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Appeal Response to Abdussalam Baryun regarding	draft-ietf-manet-nhdp-sec-threats
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <m2mwq4o5pr.wl%randy@psg.com>
Date: Wed, 3 Jul 2013 07:19:20 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <95D1F4E7-E98D-4188-A54F-2E705EED6FF9@piuha.net>
References: <20130702222442.2467.13086.idtracker@ietfa.amsl.com> <290E20B455C66743BE178C5C84F12408223F494ECC@EXMB01CMS.surrey.ac.uk> <m2mwq4o5pr.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.1508)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Jul 2013 05:19:28 -0000

> i have never considered writng one.  sour grapes make bad wine.

Errors do happen, for everyone and for all organisations. We do not =
treat appeals as sour grapes at the IESG, IAB or other places that =
receive them. We consider them an opportunity to review whether =
something was missed. At the same time, we do not intend to give special =
treatment to an argument just because it is labeled as an appeal. =
Sometimes legitimate differences of opinion are just that, and consensus =
was rough.

Jari


From william.mccall@gmail.com  Wed Jul  3 03:39:58 2013
Return-Path: <william.mccall@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5640A21F9C21 for <ietf@ietfa.amsl.com>; Wed,  3 Jul 2013 03:39:58 -0700 (PDT)
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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6iKRAtykZEli for <ietf@ietfa.amsl.com>; Wed,  3 Jul 2013 03:39:58 -0700 (PDT)
Received: from mail-ob0-x236.google.com (mail-ob0-x236.google.com [IPv6:2607:f8b0:4003:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id E255921F9BAD for <ietf@ietf.org>; Wed,  3 Jul 2013 03:39:57 -0700 (PDT)
Received: by mail-ob0-f182.google.com with SMTP id va7so6719738obc.41 for <ietf@ietf.org>; Wed, 03 Jul 2013 03:39:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=E2+kM6S8824TBVpapNw18MoCNQdi93MwMLK87UfvotY=; b=zGMk2+gKn+M589bFzUHIQB7xz71WbCUJDl0gM2goPxgb0awBhd0GnZTVts1zVC5GG7 OkVZ7RkV7qRFdhna8sHrilc4+/TUF6XowALaGPE/Np+B1BBI6Y1pVy0ZreNn+jZjmJGB 21ZUPJIlBgkiyGgjJB0qQmYs8Ul4O6huXdqP8vJozZCGhSuEXedrCjFDzVwRuUIRlt5U YcV2Libo/dCYpvstH6R8eTirekxcYmsllTeYVLO4WO186wzEWu0akbvYIj2DanPuPyS4 AdyQy6t680tPv2rfDzUqRVPh3huQIdCdcK2VH0zL5HpAqXOOeprz2f4VGyubAQX8dBS4 2NMg==
X-Received: by 10.182.92.225 with SMTP id cp1mr123542obb.97.1372847997213; Wed, 03 Jul 2013 03:39:57 -0700 (PDT)
Received: from [10.10.0.56] (cpe-66-25-3-111.tx.res.rr.com. [66.25.3.111]) by mx.google.com with ESMTPSA id x10sm10509302obw.13.2013.07.03.03.39.55 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 03 Jul 2013 03:39:56 -0700 (PDT)
Message-ID: <51D3FF7D.5050107@gmail.com>
Date: Wed, 03 Jul 2013 05:39:57 -0500
From: William McCall <william.mccall@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
Subject: Re: Appeal Response to Abdussalam Baryun regarding draft-ietf-manet-nhdp-sec-threats
References: <20130702222442.2467.13086.idtracker@ietfa.amsl.com> <290E20B455C66743BE178C5C84F12408223F494ECC@EXMB01CMS.surrey.ac.uk> <m2mwq4o5pr.wl%randy@psg.com>
In-Reply-To: <m2mwq4o5pr.wl%randy@psg.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Jul 2013 10:39:58 -0000

On 07/02/2013 07:19 PM, Randy Bush wrote:
>> If I knew that 97% of appeals get rejected, I wouldn't even bother
>> writing one...
> i have never considered writng one.  sour grapes make bad wine.
>
> randy
I used to read the appeals for my own education. Some pretty hilarious 
stuff in there. I feel this contributor's frustration though (even 
though the IESG is right).

I'd tend to agree with you Randy... save it for something worth 
advocating for.

From presnick@qti.qualcomm.com  Wed Jul  3 09:32:44 2013
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D85621F9DEB for <ietf@ietfa.amsl.com>; Wed,  3 Jul 2013 09:32:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nPqKMsizEh5b for <ietf@ietfa.amsl.com>; Wed,  3 Jul 2013 09:32:40 -0700 (PDT)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) by ietfa.amsl.com (Postfix) with ESMTP id ACA4221F9DDD for <ietf@ietf.org>; Wed,  3 Jul 2013 09:32:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1372869160; x=1404405160; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=k8SupP75KFS2RSafPwsuQvtqvoeVzOJBDnt/8qMfVRI=; b=KjpWhA2sgB5CPEWdkpf2slB3MwQ5xkX3eMxTSdF5YWEF0X4TzCZ9aEue bfe+F2kZ+sIb4KZh1xw3JOYimjhuXssla/NwKjtKFN6aRcdzRI/Va+oo/ WFVJqgN5Ifd22xt3hEI8+wx+6JNSI8helZVTOz0TEIR8+nNAFXsAUPWtb Q=;
X-IronPort-AV: E=Sophos;i="4.87,989,1363158000"; d="scan'208";a="46688950"
Received: from ironmsg04-l.qualcomm.com ([172.30.48.19]) by sabertooth01.qualcomm.com with ESMTP; 03 Jul 2013 09:32:40 -0700
X-IronPort-AV: E=Sophos;i="4.87,988,1363158000"; d="scan'208";a="474024525"
Received: from nasanexhc01.na.qualcomm.com ([172.30.48.25]) by Ironmsg04-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 03 Jul 2013 09:32:40 -0700
Received: from nasanexhc05.na.qualcomm.com (172.30.48.2) by NASANEXHC01.na.qualcomm.com (172.30.48.25) with Microsoft SMTP Server (TLS) id 14.2.318.4; Wed, 3 Jul 2013 09:32:39 -0700
Received: from presnick-mac.local (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.2) with Microsoft SMTP Server (TLS) id 14.2.318.4; Wed, 3 Jul 2013 09:32:39 -0700
Message-ID: <51D45225.1000804@qti.qualcomm.com>
Date: Wed, 3 Jul 2013 11:32:37 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: <l.wood@surrey.ac.uk>
Subject: Re: Appeal Response to Abdussalam Baryun regarding	draft-ietf-manet-nhdp-sec-threats
References: <20130702222442.2467.13086.idtracker@ietfa.amsl.com> <290E20B455C66743BE178C5C84F12408223F494ECC@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F12408223F494ECC@EXMB01CMS.surrey.ac.uk>
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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Jul 2013 16:32:44 -0000

On 7/2/13 6:37 PM, l.wood@surrey.ac.uk wrote:
> Do we have any statistics on how many appeals to the IESG fail and how many succeed?
>    

My quick read of http://www.ietf.org/iesg/appeal.html:

Accepted: 6
Denied: 25
Withdrawn: 1

One appellant appealed 12 times and all of the appeals were denied. One 
appellant appealed 4 times, all denied. One appellant appealed 3 times, 
all denied.

At least two of the accepted appeals resulted in a different remedy than 
requested by the appellant (i.e., adding an IESG Note to a document 
instead of making other changes or rejecting the document).

At least two of the denied appeals were on strictly procedural grounds; 
one came over two months after the action, one was appealing an IAB 
decision that was out of jurisdiction for the IESG to decide.

Interpret the above as you see fit.

pr

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


From eckert@cisco.com  Wed Jul  3 09:54:42 2013
Return-Path: <eckert@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD2AB21F9A29 for <ietf@ietfa.amsl.com>; Wed,  3 Jul 2013 09:54:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tu135kpHLsDh for <ietf@ietfa.amsl.com>; Wed,  3 Jul 2013 09:54:37 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id 9861521F994B for <ietf@ietf.org>; Wed,  3 Jul 2013 09:54:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2048; q=dns/txt; s=iport; t=1372870477; x=1374080077; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=XT21NwgL1JAy3LSuB2gPGryltZoQpQi3SzTnSxIYhzE=; b=g+egu4cUwXYlWBfs44R0303/osD4juGTMSeTddHqdSyq9RbyovYgZcdN t8f4r36oPCdrsqFzoce0b/piCL0rHWskAbqJWUkSChHG4OGvROsZ76l/M URzO0Udn2eBPp6mhKL/eL+N2JFYamlohHAfKuyr/vGj5vKDVdV2KNIHEK o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ai4FAPtW1FGrRDoH/2dsb2JhbABagwnBMIEEFnSCIwEBAQQ6PxALGAklDwVJE4gOuw2PaweDBGkDiSOOJQGRRYFYgVkc
X-IronPort-AV: E=Sophos;i="4.87,989,1363132800"; d="scan'208";a="82117901"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-1.cisco.com with ESMTP; 03 Jul 2013 16:54:30 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by mtv-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r63GsTO2028880 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 3 Jul 2013 16:54:29 GMT
Received: from mcast-linux1.cisco.com (localhost.cisco.com [127.0.0.1]) by mcast-linux1.cisco.com (8.13.8/8.13.8) with ESMTP id r63GsSZ1007490;  Wed, 3 Jul 2013 09:54:28 -0700
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id r63GsQMF007488; Wed, 3 Jul 2013 09:54:26 -0700
Date: Wed, 3 Jul 2013 09:54:26 -0700
From: Toerless Eckert <eckert@cisco.com>
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: Appeal Response to Abdussalam Baryun regarding	draft-ietf-manet-nhdp-sec-threats
Message-ID: <20130703165426.GA6039@cisco.com>
References: <20130702222442.2467.13086.idtracker@ietfa.amsl.com> <290E20B455C66743BE178C5C84F12408223F494ECC@EXMB01CMS.surrey.ac.uk> <m2mwq4o5pr.wl%randy@psg.com> <95D1F4E7-E98D-4188-A54F-2E705EED6FF9@piuha.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <95D1F4E7-E98D-4188-A54F-2E705EED6FF9@piuha.net>
User-Agent: Mutt/1.4.2.2i
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Jul 2013 16:54:42 -0000

Jari, *:

Disclaimer: see signature (i do not know the details of this specific case).

To me the problem seems to be going back to the means the IETF has for providing recognition
to participants contributing by review/feedback. As long as recognition for that contribution
is primarily left to the disgression of the listed draft authors, it will negatively impact
the amount of especially critical feedback/review the IETF will see. Unless a contributor has
a specific business reason to reject or help to improve a drafts, its most likely not worth
their time to fight / improve documents without better means of recognition than how its
defined today. Especially if their job role lives off showing recognition for their contribution
to their employer/sponsor.

As much as i hate overboarding processes, an explicit review tool tracking feedback
and approval/disapproval of documents may be able to help here. Especially given how
there is already tooling to show some form of IETF score based on explicit
authorship. You know who's tool i am talking about ;-)

Not claiming i am persuaded that the problem is significant enough to invest into an
explicit review tool, just saying its more than just difference of opinions or rough
consensus as you seem to claim (if i undestood you correctly).

Cheers
    Toerless

On Wed, Jul 03, 2013 at 07:19:20AM +0200, Jari Arkko wrote:
> 
> > i have never considered writng one.  sour grapes make bad wine.
> 
> Errors do happen, for everyone and for all organisations. We do not treat appeals as sour grapes at the IESG, IAB or other places that receive them. We consider them an opportunity to review whether something was missed. At the same time, we do not intend to give special treatment to an argument just because it is labeled as an appeal. Sometimes legitimate differences of opinion are just that, and consensus was rough.
> 
> Jari
> 

-- 
---
Toerless Eckert, eckert@cisco.com
It's much easier to have an opinion if you do not understand the problem.


From warren@kumari.net  Wed Jul  3 10:02:50 2013
Return-Path: <warren@kumari.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BED7811E80F2 for <ietf@ietfa.amsl.com>; Wed,  3 Jul 2013 10:02:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cjoiEiBqj0wU for <ietf@ietfa.amsl.com>; Wed,  3 Jul 2013 10:02:46 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1856C11E820D for <ietf@ietf.org>; Wed,  3 Jul 2013 10:02:39 -0700 (PDT)
Received: from [192.168.1.153] (unknown [66.84.81.89]) by vimes.kumari.net (Postfix) with ESMTPSA id DC27B1B403E8; Wed,  3 Jul 2013 13:02:37 -0400 (EDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [IETF] Re: Appeal Response to Abdussalam Baryun regarding	draft-ietf-manet-nhdp-sec-threats
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <51D45225.1000804@qti.qualcomm.com>
Date: Wed, 3 Jul 2013 13:02:36 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <1B046143-4B0E-41C0-9F50-09A87206FCE9@kumari.net>
References: <20130702222442.2467.13086.idtracker@ietfa.amsl.com> <290E20B455C66743BE178C5C84F12408223F494ECC@EXMB01CMS.surrey.ac.uk> <51D45225.1000804@qti.qualcomm.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
X-Mailer: Apple Mail (2.1508)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Jul 2013 17:02:50 -0000

On Jul 3, 2013, at 12:32 PM, Pete Resnick <presnick@qti.qualcomm.com> =
wrote:

> On 7/2/13 6:37 PM, l.wood@surrey.ac.uk wrote:
>> Do we have any statistics on how many appeals to the IESG fail and =
how many succeed?
>>  =20
>=20
> My quick read of http://www.ietf.org/iesg/appeal.html:
>=20
> Accepted: 6
> Denied: 25
> Withdrawn: 1
>=20
> One appellant appealed 12 times and all of the appeals were denied. =
One appellant appealed 4 times, all denied. One appellant appealed 3 =
times, all denied.
>=20
> At least two of the accepted appeals resulted in a different remedy =
than requested by the appellant (i.e., adding an IESG Note to a document =
instead of making other changes or rejecting the document).
>=20
> At least two of the denied appeals were on strictly procedural =
grounds; one came over two months after the action, one was appealing an =
IAB decision that was out of jurisdiction for the IESG to decide.
>=20
> Interpret the above as you see fit.

Thank you -- another worthwhile thing to do is look at who all has =
appealed and ask yourself "Do I really want to be part of this club?"

Other than a *very* small minority of well known and well respected folk =
the http://www.ietf.org/iesg/appeal.html page is basically a handy kook =
reference.

W


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

--
It is impossible to sharpen a pencil with a blunt axe.  It is equally =
vain
to try to do it with ten blunt axes instead.
    --  E.W Dijkstra, 1930-2002




From dhc@dcrocker.net  Wed Jul  3 10:51:52 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40B1021F9C72 for <ietf@ietfa.amsl.com>; Wed,  3 Jul 2013 10:51:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8N8FtXXyeN18 for <ietf@ietfa.amsl.com>; Wed,  3 Jul 2013 10:51:47 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id C617F21F99B0 for <ietf@ietf.org>; Wed,  3 Jul 2013 10:51:46 -0700 (PDT)
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 r63Hph2d030838 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Wed, 3 Jul 2013 10:51:46 -0700
Message-ID: <51D464A1.6050905@dcrocker.net>
Date: Wed, 03 Jul 2013 10:51:29 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: Fwd: Doug Engelbart
References: <478D5E2C-B966-4DC3-9851-F2234169F76D@webhistory.org>
In-Reply-To: <478D5E2C-B966-4DC3-9851-F2234169F76D@webhistory.org>
X-Forwarded-Message-Id: <478D5E2C-B966-4DC3-9851-F2234169F76D@webhistory.org>
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, 03 Jul 2013 10:51:46 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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, 03 Jul 2013 17:51:52 -0000

> From: Christina Engelbart <christina.engelbart@gmail.com>
> <mailto:christina.engelbart@gmail.com>>
> Date: Wednesday, July 3, 2013 6:31 AM
> Subject: update on my father
>
> Very sorry to inform my father passed away in his sleep peacefully at
> home last night. His health had been deteriorating of late, and took
> turn for worse on the weekend. I will circle back around soon, for now
> just wanted to give you all advance notice and look forward to
> discussing your thoughts as I am a bit fuzzy at present.


Besides the considerable technical contributions of Doug's project at 
SRI, theirs was a group that did much to create the open and 
collaborative tone of the Internet that we've come to consider as 
automatic and natural, but were unusual in those days.

As a junior staffer responsible for documentation at the UCLA Arpanet 
project, I used the SRI-ARC NLS system tools over the net.  Partly for 
the capabilities, but partly because it was always a cool group to 
interact with.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net



-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From john-ietf@jck.com  Wed Jul  3 11:10:59 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B57A221F9DB7 for <ietf@ietfa.amsl.com>; Wed,  3 Jul 2013 11:10:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.499
X-Spam-Level: 
X-Spam-Status: No, score=-102.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YijKvFjVrjTi for <ietf@ietfa.amsl.com>; Wed,  3 Jul 2013 11:10:55 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id F070C21F9DAB for <ietf@ietf.org>; Wed,  3 Jul 2013 11:10:54 -0700 (PDT)
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 1UuRW0-0002aG-W1; Wed, 03 Jul 2013 14:10:52 -0400
Date: Wed, 03 Jul 2013 14:10:47 -0400
From: John C Klensin <john-ietf@jck.com>
To: Warren Kumari <warren@kumari.net>, Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: [IETF] Re: Appeal Response to Abdussalam Baryun	regarding	draft-ietf-manet-nhdp-sec-threats
Message-ID: <FDE04DA5C72B9B80DCC2FE15@JcK-HP8200.jck.com>
In-Reply-To: <1B046143-4B0E-41C0-9F50-09A87206FCE9@kumari.net>
References: <20130702222442.2467.13086.idtracker@ietfa.amsl.com> <290E20B455C66743BE178C5C84F12408223F494ECC@EXMB01CMS.surrey.ac.uk> <51D45225.1000804@qti.qualcomm.com> <1B046143-4B0E-41C0-9F50-09A87206FCE9@kumari.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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Jul 2013 18:10:59 -0000

--On Wednesday, July 03, 2013 13:02 -0400 Warren Kumari
<warren@kumari.net> wrote:

> Thank you -- another worthwhile thing to do is look at who all
> has appealed and ask yourself "Do I really want to be part of
> this club?"

I am honored to be a member of that club.   Remembering that
appeals, as others have pointed out, a mechanism for requesting
a second look at some issue, they are an important, perhaps
vital, part of our process.  We probably don't have enough of
them.  Effectively telling people to not appeal because they
will be identified as "kooks" hurts the process model by
suppressing what might be legitimate concerns.

In addition, it is important to note that the page does _not_
list every appeal since 2002.  If one reads Section 6.5 of RFC
2026, it describes a multi-step process for appears in each of a
collection of categories.  The web page lists only those that
were escalated to full IESG review.  That is important for two
reasons:

* The majority of appeals, and a larger majority of those that
are consistent with community consensus or technical
reasonableness, are resolved well before the issues involved
come to the formal attention of the full IESG.  If an issue is
appealed but discussions with WG Chairs, individuals ADs, or the
IETF Chair result in a review of the issues and a satisfactory
resolution, then that is an that is completely successful in
every respect (including minimization of IETF time) but does not
show up in the list on the web page or statistics derived from
it.

* A few minutes of thought will probably suffice to show you
that appeals that have significant merit are far more likely to
be resolved at stages prior to full IESG review.   By contrast,
a hypothetical appeal that was wholly without merit, or even
filed with the intent of annoying the IESG, is almost certain to
reach the IESG and end up on the list, badly distorting the
actual situation.

best,
   john

p.s. to any IESG members who are reading this: community
understanding of the process might be enhanced by putting a note
on the appeals page that is explicit about what that list
represents, i.e., only appeals that reached full IESG review and
not all appeals.



> Other than a *very* small minority of well known and well
> respected folk the http://www.ietf.org/iesg/appeal.html page
> is basically a handy kook reference.





From iab-chair@iab.org  Wed Jul  3 11:14:00 2013
Return-Path: <iab-chair@iab.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEEEB21F9DCE; Wed,  3 Jul 2013 11:14:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fUY83qHiv07d; Wed,  3 Jul 2013 11:14:00 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.21]) by ietfa.amsl.com (Postfix) with ESMTP id 6A01821F9DDB; Wed,  3 Jul 2013 11:13:59 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id AF1A8A89E2; Wed,  3 Jul 2013 11:13:09 -0700 (PDT)
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 Oj0q9gihaND7; Wed,  3 Jul 2013 11:13:09 -0700 (PDT)
Received: from [192.168.2.109] (pool-96-241-156-29.washdc.fios.verizon.net [96.241.156.29]) by c9a.amsl.com (Postfix) with ESMTPSA id 1F858A896E; Wed,  3 Jul 2013 11:13:09 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Subject: Call for Comment on draft-iab-anycast-arch-implications-09 on "Architectural Considerations of IP Anycast"
Mime-Version: 1.0 (Apple Message framework v1085)
From: IAB Chair <iab-chair@iab.org>
Date: Wed, 3 Jul 2013 14:13:57 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <2C891F70-34C8-441A-8085-38A9F2F13D5B@iab.org>
To: IETF Announce <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1085)
Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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, 03 Jul 2013 18:14:01 -0000

This is an announcement of an IETF-wide Call for Comment on =
"Architectural Considerations of IP Anycast" =
(draft-iab-anycast-arch-implications-09).=20

The document is being considered for publication as an Informational RFC =
within the IAB stream, and is available for inspection here:=20
https://datatracker.ietf.org/doc/draft-iab-anycast-arch-implications/

The Call for Comment will last until August 1, 2013. Please send =
comments to iab@iab.org or submit them via TRAC (see below).=20

Russ Housley
IAB Chair

=3D =3D =3D =3D =3D =3D =3D =3D =3D =3D

Submitting Comments via TRAC

1. To submit an issue in TRAC, you first need to login to the IAB site =
on the tools server:=20
http://tools.ietf.org/wg/iab/trac/login=20

2. If you don't already have a login ID, you can obtain one by =
navigating to this site:=20
http://trac.tools.ietf.org/newlogin=20

3. Once you have obtained an account, and have logged in, you can file =
an issue by navigating to the ticket entry form:=20
http://trac.tools.ietf.org/wg/iab/trac/newticket=20

4. When opening an issue:=20
a. The Type: field should be set to "defect" for an issue with the =
current document text, or "enhancement" for a proposed addition of =
functionality (such as an additional requirement).=20
b. The Priority: field is set based on the severity of the Issue. For =
example, editorial issues are typically "minor" or "trivial".=20
c. The Milestone: field should be set to milestone1 (useless, I know).=20=

d. The Component: field should be set to the document you are filing the =
issue on.=20
e. The Version: field should be set to "1.0".=20
f. The Severity: field should be set to based on the status of the =
document (e.g. "In WG Last Call" for a document in IAB last call)=20
g. The Keywords: and CC: fields can be left blank unless inspiration =
seizes you.=20
h. The Assign To: field is generally filled in with the email address of =
the editor.=20

5. Typically it won't be necessary to enclose a file with the ticket, =
but if you need to, select "I have files to attach to this ticket".=20

6. If you want to preview your Issue, click on the "Preview" button. =
When you're ready to submit the issue, click on the "Create Ticket" =
button.=20

7. If you want to update an issue, go to the "View Tickets" page:=20
http://trac.tools.ietf.org/wg/iab/trac/report/1=20

Click on the ticket number you want to update, and then modify the =
ticket fields as required.=20


From dhc@dcrocker.net  Wed Jul  3 11:19:24 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC78621F9931 for <ietf@ietfa.amsl.com>; Wed,  3 Jul 2013 11:19:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AymBevMvHZub for <ietf@ietfa.amsl.com>; Wed,  3 Jul 2013 11:19:19 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id A0A5011E81F9 for <ietf@ietf.org>; Wed,  3 Jul 2013 11:19:01 -0700 (PDT)
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 r63IIvdd031391 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Wed, 3 Jul 2013 11:19:01 -0700
Message-ID: <51D46B04.4010104@dcrocker.net>
Date: Wed, 03 Jul 2013 11:18:44 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Appeal Response to Abdussalam Baryun regarding	draft-ietf-manet-nhdp-sec-threats
References: <20130702222442.2467.13086.idtracker@ietfa.amsl.com> <290E20B455C66743BE178C5C84F12408223F494ECC@EXMB01CMS.surrey.ac.uk> <51D45225.1000804@qti.qualcomm.com>
In-Reply-To: <51D45225.1000804@qti.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Wed, 03 Jul 2013 11:19:01 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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, 03 Jul 2013 18:19:24 -0000

On 7/3/2013 9:32 AM, Pete Resnick wrote:
> Interpret the above as you see fit.


As with most 'social' analyses, it's usually a good idea to look for a 
bit more than an entirely trivial numbers game, such as by trying to 
find some criterion that helps to distinguish amongst the appellants.

In this case, I think that a reasonable distinction could be made 
between real participants in the community, versus, ummmm... others. A 
plausible-if-simplistic criterion could be noting whether the appellant 
had authored at least one RFC.

As with most heuristics, it doesn't provide a guarantee.  Still, it 
looks like a useful filter.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From hartmans@mit.edu  Wed Jul  3 11:47:14 2013
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8327E11E8200 for <ietf@ietfa.amsl.com>; Wed,  3 Jul 2013 11:47:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OYxWKHxWjIeM for <ietf@ietfa.amsl.com>; Wed,  3 Jul 2013 11:47:08 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id ADF7E11E81F8 for <ietf@ietf.org>; Wed,  3 Jul 2013 11:47:07 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 947202013A; Wed,  3 Jul 2013 14:42:37 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SlZ-0v0EKo2A; Wed,  3 Jul 2013 14:42:36 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (c-98-216-0-82.hsd1.ma.comcast.net [98.216.0.82]) (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,  3 Jul 2013 14:42:36 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 83F4B81454; Wed,  3 Jul 2013 14:46:27 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: John C Klensin <john-ietf@jck.com>
Subject: Re: [IETF] Re: Appeal Response to Abdussalam Baryun	regarding	draft-ietf-manet-nhdp-sec-threats
References: <20130702222442.2467.13086.idtracker@ietfa.amsl.com> <290E20B455C66743BE178C5C84F12408223F494ECC@EXMB01CMS.surrey.ac.uk> <51D45225.1000804@qti.qualcomm.com> <1B046143-4B0E-41C0-9F50-09A87206FCE9@kumari.net> <FDE04DA5C72B9B80DCC2FE15@JcK-HP8200.jck.com>
Date: Wed, 03 Jul 2013 14:46:27 -0400
In-Reply-To: <FDE04DA5C72B9B80DCC2FE15@JcK-HP8200.jck.com> (John C. Klensin's message of "Wed, 03 Jul 2013 14:10:47 -0400")
Message-ID: <tsly59nh470.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
Cc: Pete Resnick <presnick@qti.qualcomm.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Jul 2013 18:47:14 -0000

>>>>> "John" == John C Klensin <john-ietf@jck.com> writes:


Strong agreement.
I'm not currently a member of that club, although if I stick around the
IETF long enough it's bound to happen.
I've certainly received and reviewed appeals that I thought were a valid
contribution to the process.

Don't appeal if there is a better way to address your concerns, but if
an appeal is the right approach, then file one.

From sm@resistor.net  Wed Jul  3 12:08:59 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E9A321F9BAD for <ietf@ietfa.amsl.com>; Wed,  3 Jul 2013 12:08:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id khw-l6brBxR1 for <ietf@ietfa.amsl.com>; Wed,  3 Jul 2013 12:08:58 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 84E5C21F9B92 for <ietf@ietf.org>; Wed,  3 Jul 2013 12:08:58 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r63J8idF016669; Wed, 3 Jul 2013 12:08:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1372878529; bh=RQYdZYm6BaYtpSz03o65UKF+fwKuNH1JscVi9RavhV0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Tiak6ex3NEJc/fQskQnO0vHkNV2xFggt9E+IofhtAcdsZH5anxn03kaDo853G2Rjt FAx4HA1j1/DZfeA4EV5+MaZP+yyN22zEp06W9wBe2Rf4kFpynG/4nTjbXSpNE+cSEL 96p/OjxCqLJdPtYaOLLyz2HIXzQEKzGZ4gI2TcWk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1372878529; i=@resistor.net; bh=RQYdZYm6BaYtpSz03o65UKF+fwKuNH1JscVi9RavhV0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=j6bb+tfFZEmdnK3dGdb6nhn03UKkx74Z9fwQxs5lElyrhZ8AuL4OBs4oQs5OMx6DU PaWNLQlwhJu7pFdDQcA16mdIHuihUcSJTXFddLgpl9kw3h+bMXO0x+7PGlncGYNi2g hK5F/i0b6v3koBIWsZLyT/Rr7L7jDW1D8sXV6eyA=
Message-Id: <6.2.5.6.2.20130703083609.0dd81668@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 03 Jul 2013 10:24:50 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Appeal Response to [removed] regarding draft-ietf-manet-nhdp-sec-threats
In-Reply-To: <51D3FF7D.5050107@gmail.com>
References: <20130702222442.2467.13086.idtracker@ietfa.amsl.com> <290E20B455C66743BE178C5C84F12408223F494ECC@EXMB01CMS.surrey.ac.uk> <m2mwq4o5pr.wl%randy@psg.com> <51D3FF7D.5050107@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: "Toerless Eckert <eckert@cisco.com>. John C Klensin" <john-ietf@jck.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Jul 2013 19:08:59 -0000

At 03:39 03-07-2013, William McCall wrote:
>I used to read the appeals for my own education. Some pretty 
>hilarious stuff in there. I feel this contributor's frustration 
>though (even though the IESG is right).

The decision of the respected members of the IESG was 
predictable.  There may be a minor issue.  I cannot comment about that.

The appellant mentioned that he worked hard and he has been 
excluded.  In my opinion any other contributor might be frustrated in 
similar circumstances.  The IETF is a place of many 
misunderstandings.  Maybe one day something good will come out of all that.

At 09:54 03-07-2013, Toerless Eckert wrote:
>To me the problem seems to be going back to the means the IETF has 
>for providing recognition
>to participants contributing by review/feedback. As long as 
>recognition for that contribution
>is primarily left to the disgression of the listed draft authors, it 
>will negatively impact
>the amount of especially critical feedback/review the IETF will see. 
>Unless a contributor has
>a specific business reason to reject or help to improve a drafts, 
>its most likely not worth
>their time to fight / improve documents without better means of 
>recognition than how its
>defined today. Especially if their job role lives off showing 
>recognition for their contribution
>to their employer/sponsor.

Yes.

There are more incentives not to perform a critical review of a draft 
instead of doing the reverse.  If contributors operate solely for 
business reasons it can lead to IETF structural issues.

At 11:10 03-07-2013, John C Klensin wrote:
>I am honored to be a member of that club.   Remembering that

:-)

>appeals, as others have pointed out, a mechanism for requesting
>a second look at some issue, they are an important, perhaps
>vital, part of our process.  We probably don't have enough of
>them.  Effectively telling people to not appeal because they
>will be identified as "kooks" hurts the process model by
>suppressing what might be legitimate concerns.

Yes.

>come to the formal attention of the full IESG.  If an issue is
>appealed but discussions with WG Chairs, individuals ADs, or the
>IETF Chair result in a review of the issues and a satisfactory
>resolution, then that is an that is completely successful in
>every respect (including minimization of IETF time) but does not

Agreed.

Sometimes a gesture of goodwill is all that it takes.

Regards,
-sm  


From braden@isi.edu  Wed Jul  3 12:12:54 2013
Return-Path: <braden@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 297AC21F9CCE for <ietf@ietfa.amsl.com>; Wed,  3 Jul 2013 12:12:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.999
X-Spam-Level: 
X-Spam-Status: No, score=-105.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_83=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vaaOgag5Nozm for <ietf@ietfa.amsl.com>; Wed,  3 Jul 2013 12:12:44 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id E4DBB21F9C5F for <ietf@ietf.org>; Wed,  3 Jul 2013 12:12:43 -0700 (PDT)
Received: from [192.168.1.27] (c1-vpn1.isi.edu [128.9.176.27]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r63JBKdU005742 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 3 Jul 2013 12:11:21 -0700 (PDT)
Message-ID: <51D4773C.2030509@isi.edu>
Date: Wed, 03 Jul 2013 12:10:52 -0700
From: Bob Braden <braden@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Fwd: Doug Engelbart
References: <478D5E2C-B966-4DC3-9851-F2234169F76D@webhistory.org> <51D464A1.6050905@dcrocker.net>
In-Reply-To: <51D464A1.6050905@dcrocker.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: braden@isi.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Jul 2013 19:12:54 -0000

Wikipedia defines "genius" as "a person who displays exceptional 
intellectual ability, creativity, or originality"
All three applied to Doug Engelbart. He belongs up there with other 
creative  geniuses I have had the privilege of meeting during 50 years 
in computing -- Al Perlis,   Dick Hamming, John McCarthy,and Don Knuth 
come immediately to mind.

Bob Braden'



From Ted.Lemon@nominum.com  Wed Jul  3 12:16:33 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF44921F9D2A for <ietf@ietfa.amsl.com>; Wed,  3 Jul 2013 12:16:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NQZKlIvEmgZE for <ietf@ietfa.amsl.com>; Wed,  3 Jul 2013 12:16:27 -0700 (PDT)
Received: from exprod7og127.obsmtp.com (exprod7og127.obsmtp.com [64.18.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id 5647621F9D34 for <ietf@ietf.org>; Wed,  3 Jul 2013 12:16:26 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob127.postini.com ([64.18.6.12]) with SMTP ID DSNKUdR4iQevj5zcqtxPHjpITWvhSaSQl9Cx@postini.com; Wed, 03 Jul 2013 12:16:26 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 9A23F1B821C for <ietf@ietf.org>; Wed,  3 Jul 2013 12:16:25 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 4A0E919005D; Wed,  3 Jul 2013 12:16:24 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Wed, 3 Jul 2013 12:16:24 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "<dcrocker@bbiw.net>" <dcrocker@bbiw.net>
Subject: Re: Appeal Response to Abdussalam Baryun	regarding draft-ietf-manet-nhdp-sec-threats
Thread-Topic: Appeal Response to Abdussalam Baryun	regarding draft-ietf-manet-nhdp-sec-threats
Thread-Index: AQHOeAr6jJNMZG4uG0u15Lq4M4CaQJlTuMMAgAAQHIA=
Date: Wed, 3 Jul 2013 19:16:24 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751FB1A0@mbx-01.win.nominum.com>
References: <20130702222442.2467.13086.idtracker@ietfa.amsl.com> <290E20B455C66743BE178C5C84F12408223F494ECC@EXMB01CMS.surrey.ac.uk> <51D45225.1000804@qti.qualcomm.com> <51D46B04.4010104@dcrocker.net>
In-Reply-To: <51D46B04.4010104@dcrocker.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <3924A35029F2E1478D8E8FDE2A14FFAE@nominum.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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Jul 2013 19:16:33 -0000

On Jul 3, 2013, at 2:18 PM, Dave Crocker <dhc@dcrocker.net> wrote:
> As with most 'social' analyses, it's usually a good idea to look for a bi=
t more than an entirely trivial numbers game, such as by trying to find som=
e criterion that helps to distinguish amongst the appellants.

Yup.   E.g., it's worth reading the IESG response to John Klensin's appeal,=
 and also the IESG response to Dean's most recent appeal.   I wasn't on the=
 IESG for either of these, so I have no attachment to the text as written, =
but in both cases it seems very clear to me that the right thing was done, =
and that the responses were well reasoned and thorough.


From presnick@qti.qualcomm.com  Wed Jul  3 12:31:43 2013
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0558A21F9D5D for <ietf@ietfa.amsl.com>; Wed,  3 Jul 2013 12:31:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.313
X-Spam-Level: 
X-Spam-Status: No, score=-106.313 tagged_above=-999 required=5 tests=[AWL=0.285, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U9kUz0hnvlJB for <ietf@ietfa.amsl.com>; Wed,  3 Jul 2013 12:31:30 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id 7FD7B21F9D68 for <ietf@ietf.org>; Wed,  3 Jul 2013 12:31:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1372879890; x=1404415890; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=/5SMhzNkzRk1W61sgtOAbDMauXFzkAipksqGG+R/E0E=; b=nGDaZK/Ve6pG3UezKbSDJEI0Xwktbj4vZO61jgQNwmB+8mB+sGTeWgev TauK5C5A66HKCqmvAZrsPqLoBBEJeTbFf7zc9Y4ZfL5GZXdLYbnui39fo SibO8NDJegEFtHpEMgVd+d9PL+mQU/sELp0BspCZh2GUeqiADxWZRG4dv g=;
X-IronPort-AV: E=Sophos;i="4.87,990,1363158000"; d="scan'208,217";a="60623854"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by wolverine02.qualcomm.com with ESMTP; 03 Jul 2013 12:31:30 -0700
X-IronPort-AV: E=Sophos;i="4.87,989,1363158000";  d="scan'208,217";a="499664882"
Received: from nasanexhc10.na.qualcomm.com ([172.30.48.3]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 03 Jul 2013 12:31:29 -0700
Received: from nasanexhc05.na.qualcomm.com (172.30.48.2) by nasanexhc10.na.qualcomm.com (172.30.48.3) with Microsoft SMTP Server (TLS) id 14.2.318.4; Wed, 3 Jul 2013 12:31:27 -0700
Received: from presnick-mac.local (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.2) with Microsoft SMTP Server (TLS) id 14.2.318.4; Wed, 3 Jul 2013 12:31:26 -0700
Message-ID: <51D47C0C.3040603@qti.qualcomm.com>
Date: Wed, 3 Jul 2013 14:31:24 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: [IETF] Re: Appeal Response to Abdussalam	Baryun	regarding	draft-ietf-manet-nhdp-sec-threats
References: <20130702222442.2467.13086.idtracker@ietfa.amsl.com>	<290E20B455C66743BE178C5C84F12408223F494ECC@EXMB01CMS.surrey.ac.uk>	<51D45225.1000804@qti.qualcomm.com>	<1B046143-4B0E-41C0-9F50-09A87206FCE9@kumari.net> <FDE04DA5C72B9B80DCC2FE15@JcK-HP8200.jck.com>
In-Reply-To: <FDE04DA5C72B9B80DCC2FE15@JcK-HP8200.jck.com>
Content-Type: multipart/alternative; boundary="------------080504090104090700060408"
X-Originating-IP: [172.30.48.1]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Jul 2013 19:31:43 -0000

--------------080504090104090700060408
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit

On 7/3/13 1:10 PM, John C Klensin wrote:
> --On Wednesday, July 03, 2013 13:02 -0400 Warren Kumari
> <warren@kumari.net>  wrote:
>
>    
>> Thank you -- another worthwhile thing to do is look at who all has appealed and ask yourself "Do I really want to be part of this club?"
>>
>> Other than a*very*  small minority of well known and well respected folk thehttp://www.ietf.org/iesg/appeal.html  page is basically a handy kook reference.
>>      

I think this is a bit overstated. There are 14 unique names of 
appellants (2 of which are groups of appellants). As I stated, 3 of 
those appellants account for 19 appeals, all denied. Perhaps you don't 
want to be part of the club with those 3 who make up 60% of the 
appealing, but if you simply remove those, you get:

13 appeals for 11 appellants (2 of them appealed twice, with years in 
between appeals)
1 appeal withdrawn before the IESG decided
6 appeals accepted
6 appeals denied.

So the small minority are actually the repeat appealers. Of the rest, 
over half I would instantly recognize as well-known and long-time 
participants, and (without naming names) half of *those* folks were 
denied and half were accepted.

So appeals that get to the level of the IESG from the group of 11 are 
accepted half of the time. That means that these folks are bringing 
issues to the IESG that, after having gone through the WG, the chairs, 
and the cognizant AD, half the time are still accepted by the IESG. That 
is, there's a 50/50 shot they've found a serious problem that the IESG 
agrees the rest of us in the IETF have missed.

I'd be part of that club.

> I am honored to be a member of that club.   Remembering that
> appeals, as others have pointed out, a mechanism for requesting
> a second look at some issue, they are an important, perhaps
> vital, part of our process.  We probably don't have enough of
> them.  Effectively telling people to not appeal because they
> will be identified as "kooks" hurts the process model by
> suppressing what might be legitimate concerns.
>    

Agreed. In any dispute process, there will be some folks who are 
outliers that make up an awful lot of the total load. But that shouldn't 
take away from those who are using it for its designed purpose.

> In addition, it is important to note that the page does _not_
> list every appeal since 2002.  If one reads Section 6.5 of RFC
> 2026, it describes a multi-step process for appears in each of a
> collection of categories.  The web page lists only those that
> were escalated to full IESG review.

Interestingly, 2026 6.5 only refers to things that get to the IESG, IAB, 
or ISOC BoT as "appeals". The rest of the "discussions" are simply part 
of "dispute" or "disagreement" resolution.

But John's central point still stands: Most of the dispute resolution 
takes place before it ever gets to the IESG, IAB, or ISOC BoT as a 
formal appeal.

> p.s. to any IESG members who are reading this: community
> understanding of the process might be enhanced by putting a note
> on the appeals page that is explicit about what that list
> represents, i.e., only appeals that reached full IESG review and
> not all appeals.
>    

Good idea.

pr

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


--------------080504090104090700060408
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 text="#000000" bgcolor="#ffffff">
On 7/3/13 1:10 PM, John C Klensin wrote:
<blockquote cite="mid:FDE04DA5C72B9B80DCC2FE15@JcK-HP8200.jck.com"
 type="cite">
  <pre wrap="">--On Wednesday, July 03, 2013 13:02 -0400 Warren Kumari
<a class="moz-txt-link-rfc2396E" href="mailto:warren@kumari.net">&lt;warren@kumari.net&gt;</a> wrote:

  </pre>
  <blockquote type="cite">
    <pre wrap="">Thank you -- another worthwhile thing to do is look at who all has appealed and ask yourself "Do I really want to be part of this club?"

Other than a <b class="moz-txt-star"><span class="moz-txt-tag">*</span>very<span
 class="moz-txt-tag">*</span></b> small minority of well known and well respected folk the <a
 class="moz-txt-link-freetext"
 href="http://www.ietf.org/iesg/appeal.html">http://www.ietf.org/iesg/appeal.html</a> page is basically a handy kook reference.
    </pre>
  </blockquote>
</blockquote>
<br>
I think this is a bit overstated. There are 14 unique names of
appellants (2 of which are groups of appellants). As I stated, 3 of
those appellants account for 19 appeals, all denied. Perhaps you don't
want to be part of the club with those 3 who make up 60% of the
appealing, but if you simply remove those, you get:<br>
<br>
13 appeals for 11 appellants (2 of them appealed twice, with years in
between appeals)<br>
1 appeal withdrawn before the IESG decided<br>
6 appeals accepted<br>
6 appeals denied.<br>
<br>
So the small minority are actually the repeat appealers. Of the rest,
over half I would instantly recognize as well-known and long-time
participants, and (without naming names) half of *those* folks were
denied and half were accepted.<br>
<br>
So appeals that get to the level of the IESG from the group of 11 are
accepted half of the time. That means that these folks are bringing
issues to the IESG that, after having gone through the WG, the chairs,
and the cognizant AD, half the time are still accepted by the IESG.
That is, there's a 50/50 shot they've found a serious problem that the
IESG agrees the rest of us in the IETF have missed.<br>
<br>
I'd be part of that club.<br>
<br>
<blockquote cite="mid:FDE04DA5C72B9B80DCC2FE15@JcK-HP8200.jck.com"
 type="cite">
  <pre wrap="">I am honored to be a member of that club.   Remembering that
appeals, as others have pointed out, a mechanism for requesting
a second look at some issue, they are an important, perhaps
vital, part of our process.  We probably don't have enough of
them.  Effectively telling people to not appeal because they
will be identified as "kooks" hurts the process model by
suppressing what might be legitimate concerns.
  </pre>
</blockquote>
<br>
Agreed. In any dispute process, there will be some folks who are
outliers that make up an awful lot of the total load. But that
shouldn't take away from those who are using it for its designed
purpose.<br>
<br>
<blockquote cite="mid:FDE04DA5C72B9B80DCC2FE15@JcK-HP8200.jck.com"
 type="cite">
  <pre wrap="">In addition, it is important to note that the page does _not_
list every appeal since 2002.  If one reads Section 6.5 of RFC
2026, it describes a multi-step process for appears in each of a
collection of categories.  The web page lists only those that
were escalated to full IESG review.</pre>
</blockquote>
<br>
Interestingly, 2026 6.5 only refers to things that get to the IESG,
IAB, or ISOC BoT as "appeals". The rest of the "discussions" are simply
part of "dispute" or "disagreement" resolution.<br>
<br>
But John's central point still stands: Most of the dispute resolution
takes place before it ever gets to the IESG, IAB, or ISOC BoT as a
formal appeal.<br>
<br>
<blockquote cite="mid:FDE04DA5C72B9B80DCC2FE15@JcK-HP8200.jck.com"
 type="cite">
  <pre wrap="">p.s. to any IESG members who are reading this: community
understanding of the process might be enhanced by putting a note
on the appeals page that is explicit about what that list
represents, i.e., only appeals that reached full IESG review and
not all appeals.
  </pre>
</blockquote>
<br>
Good idea.<br>
<br>
pr<br>
<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>

--------------080504090104090700060408--

From hallam@gmail.com  Wed Jul  3 12:41:35 2013
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1C8F11E820D for <ietf@ietfa.amsl.com>; Wed,  3 Jul 2013 12:41:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.212
X-Spam-Level: 
X-Spam-Status: No, score=-2.212 tagged_above=-999 required=5 tests=[AWL=0.387,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eun1AbMo67PZ for <ietf@ietfa.amsl.com>; Wed,  3 Jul 2013 12:41:34 -0700 (PDT)
Received: from mail-wi0-x22e.google.com (mail-wi0-x22e.google.com [IPv6:2a00:1450:400c:c05::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 3455011E8202 for <ietf@ietf.org>; Wed,  3 Jul 2013 12:41:34 -0700 (PDT)
Received: by mail-wi0-f174.google.com with SMTP id k10so5605897wiv.7 for <ietf@ietf.org>; Wed, 03 Jul 2013 12:41:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=fi12SpI1LzQV0xebAJGWZs1/UM/rGdW395lsdGBPLAc=; b=OVN3XoM+bh/8uKI+nE7YxPzyKY82Td1vTE+GpnqVgw4rFmpwebAZvq183pRGMmEe/X ZwpcLAfLHmt4n0JeXKUvqsS4yWmFnPdU0TfUcM1ccWBttjbtQovnGf2u9KVcaoGa4mLV kcCaPOwRHzo8PqVPUVYgnwaRfzYyZkawi+E4FFtS4RkYzLcypjSML6Dzq1T1ei4q6V+z 5XFE1d3xx4aG9p1VHs67e+1gOlw8om1hzzUOD6S4xcSXMQH//xKXLJ6hfzHf2bxFNcjx UoR+5OTEwVpGwR3+t0a/mM/193vL9odnoLbabNOiFAkDeLRFAFximeM8juYJshLTpPmr LnVw==
MIME-Version: 1.0
X-Received: by 10.194.179.33 with SMTP id dd1mr1504132wjc.51.1372880493272; Wed, 03 Jul 2013 12:41:33 -0700 (PDT)
Received: by 10.194.6.65 with HTTP; Wed, 3 Jul 2013 12:41:33 -0700 (PDT)
In-Reply-To: <51D47C0C.3040603@qti.qualcomm.com>
References: <20130702222442.2467.13086.idtracker@ietfa.amsl.com> <290E20B455C66743BE178C5C84F12408223F494ECC@EXMB01CMS.surrey.ac.uk> <51D45225.1000804@qti.qualcomm.com> <1B046143-4B0E-41C0-9F50-09A87206FCE9@kumari.net> <FDE04DA5C72B9B80DCC2FE15@JcK-HP8200.jck.com> <51D47C0C.3040603@qti.qualcomm.com>
Date: Wed, 3 Jul 2013 15:41:33 -0400
Message-ID: <CAMm+LwgpWZ6bP6Q4chfa-fOjQ3MBBfr0CW6SxzKFPnLe=cgpYA@mail.gmail.com>
Subject: Re: [IETF] Re: Appeal Response to Abdussalam Baryun regarding draft-ietf-manet-nhdp-sec-threats
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Content-Type: multipart/alternative; boundary=089e013d0f801ee4ae04e0a0a6e1
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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Jul 2013 19:41:35 -0000

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

+1

And don't lets forget that plenty of people have proposed schemes that WGs
have turned down and then been proven right years later.

If people are just saying what everyone else is saying here then they are
not adding any value. Rather too often WGs are started by folk seeking a
mutual appreciation society that will get through the process as quickly as
possible. They end up with a scheme that meets only the needs of the mutual
appreciation society.




On Wed, Jul 3, 2013 at 3:31 PM, Pete Resnick <presnick@qti.qualcomm.com>wrote:

> **
> On 7/3/13 1:10 PM, John C Klensin wrote:
>
> --On Wednesday, July 03, 2013 13:02 -0400 Warren Kumari<warren@kumari.net> <warren@kumari.net> wrote:
>
>
>
>  Thank you -- another worthwhile thing to do is look at who all has appealed and ask yourself "Do I really want to be part of this club?"
>
> Other than a **very** small minority of well known and well respected folk the http://www.ietf.org/iesg/appeal.html page is basically a handy kook reference.
>
>
>
> I think this is a bit overstated. There are 14 unique names of appellants
> (2 of which are groups of appellants). As I stated, 3 of those appellants
> account for 19 appeals, all denied. Perhaps you don't want to be part of
> the club with those 3 who make up 60% of the appealing, but if you simply
> remove those, you get:
>
> 13 appeals for 11 appellants (2 of them appealed twice, with years in
> between appeals)
> 1 appeal withdrawn before the IESG decided
> 6 appeals accepted
> 6 appeals denied.
>
> So the small minority are actually the repeat appealers. Of the rest, over
> half I would instantly recognize as well-known and long-time participants,
> and (without naming names) half of *those* folks were denied and half were
> accepted.
>
> So appeals that get to the level of the IESG from the group of 11 are
> accepted half of the time. That means that these folks are bringing issues
> to the IESG that, after having gone through the WG, the chairs, and the
> cognizant AD, half the time are still accepted by the IESG. That is,
> there's a 50/50 shot they've found a serious problem that the IESG agrees
> the rest of us in the IETF have missed.
>
> I'd be part of that club.
>
>
>  I am honored to be a member of that club.   Remembering that
> appeals, as others have pointed out, a mechanism for requesting
> a second look at some issue, they are an important, perhaps
> vital, part of our process.  We probably don't have enough of
> them.  Effectively telling people to not appeal because they
> will be identified as "kooks" hurts the process model by
> suppressing what might be legitimate concerns.
>
>
>
> Agreed. In any dispute process, there will be some folks who are outliers
> that make up an awful lot of the total load. But that shouldn't take away
> from those who are using it for its designed purpose.
>
>
>  In addition, it is important to note that the page does _not_
> list every appeal since 2002.  If one reads Section 6.5 of RFC
> 2026, it describes a multi-step process for appears in each of a
> collection of categories.  The web page lists only those that
> were escalated to full IESG review.
>
>
> Interestingly, 2026 6.5 only refers to things that get to the IESG, IAB,
> or ISOC BoT as "appeals". The rest of the "discussions" are simply part of
> "dispute" or "disagreement" resolution.
>
> But John's central point still stands: Most of the dispute resolution
> takes place before it ever gets to the IESG, IAB, or ISOC BoT as a formal
> appeal.
>
>
>  p.s. to any IESG members who are reading this: community
> understanding of the process might be enhanced by putting a note
> on the appeals page that is explicit about what that list
> represents, i.e., only appeals that reached full IESG review and
> not all appeals.
>
>
>
> Good idea.
>
>
> pr
>
> --
> Pete Resnick <http://www.qualcomm.com/~presnick/> <http://www.qualcomm.com/~presnick/>
> Qualcomm Technologies, Inc. - +1 (858)651-4478
>
>


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

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

<div dir=3D"ltr">+1=A0<div><br></div><div>And don&#39;t lets forget that pl=
enty of people have proposed schemes that WGs have turned down and then bee=
n proven right years later.</div><div><br></div><div style>If people are ju=
st saying what everyone else is saying here then they are not adding any va=
lue. Rather too often WGs are started by folk seeking a mutual appreciation=
 society that will get through the process as quickly as possible. They end=
 up with a scheme that meets only the needs of the mutual appreciation soci=
ety.</div>
<div style><br></div><div><br></div></div><div class=3D"gmail_extra"><br><b=
r><div class=3D"gmail_quote">On Wed, Jul 3, 2013 at 3:31 PM, Pete Resnick <=
span dir=3D"ltr">&lt;<a href=3D"mailto:presnick@qti.qualcomm.com" target=3D=
"_blank">presnick@qti.qualcomm.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"><u></u>


 =20

<div text=3D"#000000" bgcolor=3D"#ffffff"><div class=3D"im">
On 7/3/13 1:10 PM, John C Klensin wrote:
</div><blockquote type=3D"cite"><div class=3D"im">
  <pre>--On Wednesday, July 03, 2013 13:02 -0400 Warren Kumari
<a href=3D"mailto:warren@kumari.net" target=3D"_blank">&lt;warren@kumari.ne=
t&gt;</a> wrote:

  </pre>
  </div><blockquote type=3D"cite">
    <pre>Thank you -- another worthwhile thing to do is look at who all has=
 appealed and ask yourself &quot;Do I really want to be part of this club?&=
quot;

Other than a <b><span>*</span>very<span>*</span></b> small minority of well=
 known and well respected folk the <a href=3D"http://www.ietf.org/iesg/appe=
al.html" target=3D"_blank">http://www.ietf.org/iesg/appeal.html</a> page is=
 basically a handy kook reference.
    </pre>
  </blockquote>
</blockquote>
<br>
I think this is a bit overstated. There are 14 unique names of
appellants (2 of which are groups of appellants). As I stated, 3 of
those appellants account for 19 appeals, all denied. Perhaps you don&#39;t
want to be part of the club with those 3 who make up 60% of the
appealing, but if you simply remove those, you get:<br>
<br>
13 appeals for 11 appellants (2 of them appealed twice, with years in
between appeals)<br>
1 appeal withdrawn before the IESG decided<br>
6 appeals accepted<br>
6 appeals denied.<br>
<br>
So the small minority are actually the repeat appealers. Of the rest,
over half I would instantly recognize as well-known and long-time
participants, and (without naming names) half of *those* folks were
denied and half were accepted.<br>
<br>
So appeals that get to the level of the IESG from the group of 11 are
accepted half of the time. That means that these folks are bringing
issues to the IESG that, after having gone through the WG, the chairs,
and the cognizant AD, half the time are still accepted by the IESG.
That is, there&#39;s a 50/50 shot they&#39;ve found a serious problem that =
the
IESG agrees the rest of us in the IETF have missed.<br>
<br>
I&#39;d be part of that club.<div class=3D"im"><br>
<br>
<blockquote type=3D"cite">
  <pre>I am honored to be a member of that club.   Remembering that
appeals, as others have pointed out, a mechanism for requesting
a second look at some issue, they are an important, perhaps
vital, part of our process.  We probably don&#39;t have enough of
them.  Effectively telling people to not appeal because they
will be identified as &quot;kooks&quot; hurts the process model by
suppressing what might be legitimate concerns.
  </pre>
</blockquote>
<br></div>
Agreed. In any dispute process, there will be some folks who are
outliers that make up an awful lot of the total load. But that
shouldn&#39;t take away from those who are using it for its designed
purpose.<div class=3D"im"><br>
<br>
<blockquote type=3D"cite">
  <pre>In addition, it is important to note that the page does _not_
list every appeal since 2002.  If one reads Section 6.5 of RFC
2026, it describes a multi-step process for appears in each of a
collection of categories.  The web page lists only those that
were escalated to full IESG review.</pre>
</blockquote>
<br></div>
Interestingly, 2026 6.5 only refers to things that get to the IESG,
IAB, or ISOC BoT as &quot;appeals&quot;. The rest of the &quot;discussions&=
quot; are simply
part of &quot;dispute&quot; or &quot;disagreement&quot; resolution.<br>
<br>
But John&#39;s central point still stands: Most of the dispute resolution
takes place before it ever gets to the IESG, IAB, or ISOC BoT as a
formal appeal.<div class=3D"im"><br>
<br>
<blockquote type=3D"cite">
  <pre>p.s. to any IESG members who are reading this: community
understanding of the process might be enhanced by putting a note
on the appeals page that is explicit about what that list
represents, i.e., only appeals that reached full IESG review and
not all appeals.
  </pre>
</blockquote>
<br></div>
Good idea.<div class=3D"im"><br>
<br>
pr<br>
<pre cols=3D"72">--=20
Pete Resnick <a href=3D"http://www.qualcomm.com/~presnick/" target=3D"_blan=
k">&lt;http://www.qualcomm.com/~presnick/&gt;</a>
Qualcomm Technologies, Inc. - <a href=3D"tel:%2B1%20%28858%29651-4478" valu=
e=3D"+18586514478" target=3D"_blank">+1 (858)651-4478</a></pre>
</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>

--089e013d0f801ee4ae04e0a0a6e1--

From lear@cisco.com  Wed Jul  3 13:08:55 2013
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5676D21F9C06 for <ietf@ietfa.amsl.com>; Wed,  3 Jul 2013 13:08:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.416
X-Spam-Level: 
X-Spam-Status: No, score=-110.416 tagged_above=-999 required=5 tests=[AWL=0.183, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zfv9zMxaCWMi for <ietf@ietfa.amsl.com>; Wed,  3 Jul 2013 13:08:50 -0700 (PDT)
Received: from ams-iport-4.cisco.com (ams-iport-4.cisco.com [144.254.224.147]) by ietfa.amsl.com (Postfix) with ESMTP id C71DB21F99BB for <ietf@ietf.org>; Wed,  3 Jul 2013 13:08:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=448; q=dns/txt; s=iport; t=1372882130; x=1374091730; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=3AC0ZdeRvXJ2iRBy0lH4e+6yDZbDBloaJDbTjRmdwcE=; b=VXkP+j3OxadvX89NY5+I7A4jv1Ele0E+KYK4TM/f9OsIFD8rEIiK9ECP yV8SuptVlviJ6J/IEvtKDV3O+qs/RFprUhrJU8+9z/VqJ1gY4S8mpGw7K WzvCEi1r56T8mb390rZ0dIDYKXThVA48X4iEpKfUZRpXT3W6MV/3k7JrO g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjEFAMGD1FGQ/khL/2dsb2JhbABagwmEA70vgQgWdIIkAQEEI1UBEAsaAgUWCwICCQMCAQIBKxoGDQEHAQGIC6kQkQ6BJo5FB4JRgRwDl0mRRYMTOg
X-IronPort-AV: E=Sophos;i="4.87,990,1363132800"; d="scan'208";a="15282760"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-4.cisco.com with ESMTP; 03 Jul 2013 20:08:48 +0000
Received: from mctiny.local ([10.61.175.226]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r63K8k6e016537 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 3 Jul 2013 20:08:46 GMT
Message-ID: <51D484CE.1070806@cisco.com>
Date: Wed, 03 Jul 2013 22:08:46 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: Appeal Response to [removed] regarding draft-ietf-manet-nhdp-sec-threats
References: <20130702222442.2467.13086.idtracker@ietfa.amsl.com> <290E20B455C66743BE178C5C84F12408223F494ECC@EXMB01CMS.surrey.ac.uk> <m2mwq4o5pr.wl%randy@psg.com> <51D3FF7D.5050107@gmail.com> <6.2.5.6.2.20130703083609.0dd81668@resistor.net>
In-Reply-To: <6.2.5.6.2.20130703083609.0dd81668@resistor.net>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "Toerless Eckert <eckert@cisco.com>. John C Klensin" <john-ietf@jck.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Jul 2013 20:08:55 -0000

No hat on and I'm not commenting on the specific case at hand.

On the general point, I think it's better to err a bit toward the
generous side.  As an author I use as a rule of thumb whether or not I
or the working group has taken someone's suggestion and put it into
text.  And it has to be more than editorial.  A missing "," doesn't get
you into acknowlegments, but highlighting confusion or clarifying
language probably does.

Eliot

From mstjohns@comcast.net  Wed Jul  3 14:04:11 2013
Return-Path: <mstjohns@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F06D11E824A for <ietf@ietfa.amsl.com>; Wed,  3 Jul 2013 14:04:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.437
X-Spam-Level: 
X-Spam-Status: No, score=-0.437 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YMuMvc6wctEe for <ietf@ietfa.amsl.com>; Wed,  3 Jul 2013 14:04:05 -0700 (PDT)
Received: from QMTA11.westchester.pa.mail.comcast.net (qmta11.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:211]) by ietfa.amsl.com (Postfix) with ESMTP id 9CE6111E8217 for <ietf@ietf.org>; Wed,  3 Jul 2013 14:04:05 -0700 (PDT)
Received: from omta17.westchester.pa.mail.comcast.net ([76.96.62.89]) by QMTA11.westchester.pa.mail.comcast.net with comcast id vtJm1l0011vXlb85Bx44cW; Wed, 03 Jul 2013 21:04:04 +0000
Received: from Mike-T530.comcast.net ([68.83.212.126]) by omta17.westchester.pa.mail.comcast.net with comcast id vx441l00A2kB7pQ3dx44lP; Wed, 03 Jul 2013 21:04:04 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 03 Jul 2013 17:04:06 -0400
To: ietf@ietf.org
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: Appeal Response to [removed] regarding draft-ietf-manet-nhdp-sec-threats
In-Reply-To: <51D484CE.1070806@cisco.com>
References: <20130702222442.2467.13086.idtracker@ietfa.amsl.com> <290E20B455C66743BE178C5C84F12408223F494ECC@EXMB01CMS.surrey.ac.uk> <m2mwq4o5pr.wl%randy@psg.com> <51D3FF7D.5050107@gmail.com> <6.2.5.6.2.20130703083609.0dd81668@resistor.net> <51D484CE.1070806@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=1372885444; bh=N/O/hxwvBJ98FmdPUZkLRy9DVH+uIxSNzD91j72Uhg8=; h=Received:Received:Date:To:From:Subject:Mime-Version:Content-Type; b=IChfgqd6UqOCI2s9aF/cqqRggv5KnipyUKGc1B9OO6nuTNMnqxkApMg+tash6/zKH v6ASWxCAAiIKD5Nld84XQArx4Ee7CtDkeuTELBDiSta7R1I5Xh+16TYvrWdbsZVTqk 4Qq99efUK+lh+XRmMQ7TubxaskewsLO/tB1rtO80BczhmJKrsrrCuqKvbhP/+ndJNo ZuEaws8KzqAlhOgZyOqIaUq3V5YnZaTfYJAmHTswAOtefa4IwCSgnutKwxhcbDGEIM aU4pYZf+7d3+9Ahfggm4nOIpasAMEq2k9txgT7oyXrkygQ8HOllIWwGoRA8gcf4KXK XP+deSiD/BSWA==
Message-Id: <20130703210405.9CE6111E8217@ietfa.amsl.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Jul 2013 21:04:11 -0000

Before we go down this rathole too far again -

1) If you want to second guess the working group, AD and IESG, then the best approach is to probably review the bidding by reading the emails on the working group list and then forming an opinion based on that record.  I have and I'm pretty content with the current result.

2) With respect to credit, I would add that even to be considered for it a contributor's balance of payments on a document, standard etc needs to be substantially net positive.  If you're trying to claim credit for a reasonable suggestion, but its one of 10s or 100s of unreasonable ones, and you've pretty much disrupted the working group while making said suggestions..... well why reward that?

3) I think we need to continue to give each WG and each AD deference to their established ways of proceeding - unless and until there is some determination supported by facts that there is a problem.  


Mike





At 04:08 PM 7/3/2013, Eliot Lear wrote:
>No hat on and I'm not commenting on the specific case at hand.
>
>On the general point, I think it's better to err a bit toward the
>generous side.  As an author I use as a rule of thumb whether or not I
>or the working group has taken someone's suggestion and put it into
>text.  And it has to be more than editorial.  A missing "," doesn't get
>you into acknowlegments, but highlighting confusion or clarifying
>language probably does.
>
>Eliot



From iad@ietf.org  Wed Jul  3 14:31:09 2013
Return-Path: <iad@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F6A411E821B; Wed,  3 Jul 2013 14:31:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.204
X-Spam-Level: 
X-Spam-Status: No, score=-101.204 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id joM-hYTC5mva; Wed,  3 Jul 2013 14:31:09 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EF21911E80F6; Wed,  3 Jul 2013 14:31:08 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Administrative Director <iad@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: IETF 87 Registration Suspended
X-Test-IDTracker: no
X-IETF-IDTracker: 4.51.p2
Message-ID: <20130703213108.25309.83377.idtracker@ietfa.amsl.com>
Date: Wed, 03 Jul 2013 14:31:08 -0700
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.12
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: Wed, 03 Jul 2013 21:31:09 -0000

Registration for IETF87 in Berlin has been suspended to consider the impact =

of a change in the VAT rules on Registration Fees.  We expect registration =

to open as soon as this matter has been clarified.

Ray
IETF Administrative Director

From warren@kumari.net  Wed Jul  3 15:59:05 2013
Return-Path: <warren@kumari.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4879C11E8243 for <ietf@ietfa.amsl.com>; Wed,  3 Jul 2013 15:59:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.514
X-Spam-Level: 
X-Spam-Status: No, score=-102.514 tagged_above=-999 required=5 tests=[AWL=0.085, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vkHBbwCBs-Lk for <ietf@ietfa.amsl.com>; Wed,  3 Jul 2013 15:59:00 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id C525811E80E0 for <ietf@ietf.org>; Wed,  3 Jul 2013 15:59:00 -0700 (PDT)
Received: from [192.168.1.153] (unknown [66.84.81.89]) by vimes.kumari.net (Postfix) with ESMTPSA id 744461B41028; Wed,  3 Jul 2013 18:58:59 -0400 (EDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [IETF] Re: [IETF] Re: Appeal Response to Abdussalam Baryun regarding draft-ietf-manet-nhdp-sec-threats
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <CAMm+LwgpWZ6bP6Q4chfa-fOjQ3MBBfr0CW6SxzKFPnLe=cgpYA@mail.gmail.com>
Date: Wed, 3 Jul 2013 18:58:56 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <C03016D1-A784-4F4E-9A31-9824DE080F65@kumari.net>
References: <20130702222442.2467.13086.idtracker@ietfa.amsl.com> <290E20B455C66743BE178C5C84F12408223F494ECC@EXMB01CMS.surrey.ac.uk> <51D45225.1000804@qti.qualcomm.com> <1B046143-4B0E-41C0-9F50-09A87206FCE9@kumari.net> <FDE04DA5C72B9B80DCC2FE15@JcK-HP8200.jck.com> <51D47C0C.3040603@qti.qualcomm.com> <CAMm+LwgpWZ6bP6Q4chfa-fOjQ3MBBfr0CW6SxzKFPnLe=cgpYA@mail.gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
X-Mailer: Apple Mail (2.1508)
Cc: John C Klensin <john-ietf@jck.com>, Pete Resnick <presnick@qti.qualcomm.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Jul 2013 22:59:05 -0000

On Jul 3, 2013, at 3:41 PM, Phillip Hallam-Baker <hallam@gmail.com> =
wrote:

> +1=20
>=20
> And don't lets forget that plenty of people have proposed schemes that =
WGs have turned down and then been proven right years later.
>=20
> If people are just saying what everyone else is saying here then they =
are not adding any value. Rather too often WGs are started by folk =
seeking a mutual appreciation society that will get through the process =
as quickly as possible. They end up with a scheme that meets only the =
needs of the mutual appreciation society.
>=20
>=20
>=20
>=20
> On Wed, Jul 3, 2013 at 3:31 PM, Pete Resnick =
<presnick@qti.qualcomm.com> wrote:
> On 7/3/13 1:10 PM, John C Klensin wrote:
>> --On Wednesday, July 03, 2013 13:02 -0400 Warren Kumari
>>=20
>> <warren@kumari.net>
>>  wrote:
>>=20
>>  =20
>>=20
>>> Thank you -- another worthwhile thing to do is look at who all has =
appealed and ask yourself "Do I really want to be part of this club?"
>>>=20
>>> Other than a=20
>>> *very* small minority of well known and well respected folk the =
http://www.ietf.org/iesg/appeal.html
>>>  page is basically a handy kook reference.
>>>    =20
>>>=20
>=20
> I think this is a bit overstated.

Yes. It was a flippant response and there should probably have been a =
smiley somewhere in it...


> There are 14 unique names of appellants (2 of which are groups of =
appellants). As I stated, 3 of those appellants account for 19 appeals, =
all denied. Perhaps you don't want to be part of the club with those 3 =
who make up 60% of the appealing,

Yup, that is the club I was meaning.

> but if you simply remove those, you get:
>=20
> 13 appeals for 11 appellants (2 of them appealed twice, with years in =
between appeals)
> 1 appeal withdrawn before the IESG decided
> 6 appeals accepted
> 6 appeals denied.
>=20
> So the small minority are actually the repeat appealers.

Yeah, you are right.
I was simply looking at the list of repeats.=20

> Of the rest, over half I would instantly recognize as well-known and =
long-time participants, and (without naming names) half of *those* folks =
were denied and half were accepted.
>=20
> So appeals that get to the level of the IESG from the group of 11 are =
accepted half of the time. That means that these folks are bringing =
issues to the IESG that, after having gone through the WG, the chairs, =
and the cognizant AD, half the time are still accepted by the IESG. That =
is, there's a 50/50 shot they've found a serious problem that the IESG =
agrees the rest of us in the IETF have missed.
>=20
> I'd be part of that club.

Yup, fair 'nuff -- as would I.

>=20
>=20
>> I am honored to be a member of that club.   Remembering that
>> appeals, as others have pointed out, a mechanism for requesting
>> a second look at some issue, they are an important, perhaps
>> vital, part of our process.  We probably don't have enough of
>> them.  Effectively telling people to not appeal because they
>> will be identified as "kooks" hurts the process model by
>> suppressing what might be legitimate concerns.
>>  =20
>>=20
>=20
> Agreed. In any dispute process, there will be some folks who are =
outliers that make up an awful lot of the total load. But that shouldn't =
take away from those who are using it for its designed purpose.

Agreed. The dispute / appeals process is important, and needed -- it has =
served, and I'm sure will continue to serve, a useful purpose.=20



But, before filing an appeal I think one should take a step back, wait a =
day or three to calm down and ask oneself:
A: is this really worthy of an appeal?=20
B: how / why did we end up here?=20
C: does my appeal look more like the club of 3, or the club of 11?=20
D: have I tried to resolve this without resorting to appeals? really?
E: do I actually understand how this IETF thingie works? =20
F: was there any sort of process violation or am I simply annoyed that =
no-one likes / listens to me?
G: have I filed more appeals than actual contributions?
H: does my appeal text Contain Randomly capitalized Text or excessive =
exclamation marks? Have I made up words?
I: am I grandstanding?
J: am I simply on the rough side of consensus?
K: is this really worthy of an appeal?=20


W
>=20
>=20
>> In addition, it is important to note that the page does _not_
>> list every appeal since 2002.  If one reads Section 6.5 of RFC
>> 2026, it describes a multi-step process for appears in each of a
>> collection of categories.  The web page lists only those that
>> were escalated to full IESG review.
>>=20
>=20
> Interestingly, 2026 6.5 only refers to things that get to the IESG, =
IAB, or ISOC BoT as "appeals". The rest of the "discussions" are simply =
part of "dispute" or "disagreement" resolution.
>=20
> But John's central point still stands: Most of the dispute resolution =
takes place before it ever gets to the IESG, IAB, or ISOC BoT as a =
formal appeal.
>=20
>=20
>> p.s. to any IESG members who are reading this: community
>> understanding of the process might be enhanced by putting a note
>> on the appeals page that is explicit about what that list
>> represents, i.e., only appeals that reached full IESG review and
>> not all appeals.
>>  =20
>>=20
>=20
> Good idea.
>=20
>=20
> pr
> --=20
> Pete Resnick=20
> <http://www.qualcomm.com/~presnick/>
>=20
> Qualcomm Technologies, Inc. -=20
> +1 (858)651-4478
>=20
>=20
>=20
> --=20
> Website: http://hallambaker.com/

--
"Build a man a fire, and he'll be warm for a day. Set a man on fire, and =
he'll be warm for the rest of his life." -- Terry Pratchett



From doug.mtview@gmail.com  Wed Jul  3 16:27:52 2013
Return-Path: <doug.mtview@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C33B11E8104 for <ietf@ietfa.amsl.com>; Wed,  3 Jul 2013 16:27:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_83=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 83E9gE15axlg for <ietf@ietfa.amsl.com>; Wed,  3 Jul 2013 16:27:50 -0700 (PDT)
Received: from mail-pd0-x22d.google.com (mail-pd0-x22d.google.com [IPv6:2607:f8b0:400e:c02::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 76B2811E80FF for <ietf@ietf.org>; Wed,  3 Jul 2013 16:27:50 -0700 (PDT)
Received: by mail-pd0-f173.google.com with SMTP id v14so528208pde.18 for <ietf@ietf.org>; Wed, 03 Jul 2013 16:27:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to:x-mailer; bh=B82iayJE8S8G0Ic4iz/sx8cXwRonfDl/9J5MtnhgJ4E=; b=P/OfkfsVx9HtszV85qyuH8nOqZxKk3fT/kS7HfjWyEaKAaFVxKBnGitK7eL4TrW5B/ Z9lpBD06pwiRx/NAneiCDF0ceF4MsJv7V0mgYXMMVG2YO5GsoapqUzooPqkte7ANAil9 azns7QgjNcD7D39XO5fz5Wou1cCYzfHLSa9/zoMtDpZLCCaRP8eRcv3t2fXSSjPb7h5r Mq+Z6NzR4x1TeMgjuChg7bHjB/0c6Tt2+Xw6WB02HISlY6Y8ANMif97arp6OP9NdlrWg 2yud/6M7MsvqDnLeptuiz3Wj9cFV8e39GUfjHfm7EzYnqAnyU9pbO8L8UuxeGlnYxeN0 CYRQ==
X-Received: by 10.68.171.196 with SMTP id aw4mr2982527pbc.78.1372894070131; Wed, 03 Jul 2013 16:27:50 -0700 (PDT)
Received: from [192.168.1.194] (c-24-4-157-244.hsd1.ca.comcast.net. [24.4.157.244]) by mx.google.com with ESMTPSA id bn10sm664583pad.9.2013.07.03.16.27.47 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 03 Jul 2013 16:27:48 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_A43632BB-F825-4AD9-8F0D-4B2DA48D6A3C"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Doug Engelbart
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <51D4773C.2030509@isi.edu>
Date: Wed, 3 Jul 2013 16:27:46 -0700
Message-Id: <2C4A0645-AA36-4225-A2B7-74878218FFE7@gmail.com>
References: <478D5E2C-B966-4DC3-9851-F2234169F76D@webhistory.org> <51D464A1.6050905@dcrocker.net> <51D4773C.2030509@isi.edu>
To: Bob Braden <braden@isi.edu>
X-Mailer: Apple Mail (2.1508)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Jul 2013 23:27:52 -0000

--Apple-Mail=_A43632BB-F825-4AD9-8F0D-4B2DA48D6A3C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On Jul 3, 2013, at 12:10 PM, Bob Braden <braden@isi.edu> wrote:

>=20
> Wikipedia defines "genius" as "a person who displays exceptional =
intellectual ability, creativity, or originality"
> All three applied to Doug Engelbart. He belongs up there with other =
creative  geniuses I have had the privilege of meeting during 50 years =
in computing -- Al Perlis,   Dick Hamming, John McCarthy,and Don Knuth =
come immediately to mind.


Dear Bob,

Here is a video of Doug Engelbar's 1968 demo of SRI's work.
http://vimeo.com/32381658

In the early seventies, most work used mini computers where faults were =
diagnosed using the front key panel and bit light displays.  I even had =
the misfortune of debugging early production of MITS Altar systems that =
were flakey by connecting front panel LEDs directly to the data bus. As =
a consultant in 1985, I worked at Xerox Parc on the Xerox Star 6085 =
adding a cartridge tape drive.   They relied on the tape drive to =
distribute OS updates in a timely fashion because their 10 Mbit Ethernet =
offered less than 3 Mbit throughput across dozens of test systems.  By =
then, they were using Bill English's mouse design.  Being relatively =
sheltered in the lab, this was my first encounter with a GUI interface.  =
I needed to access my test programs but was dumbfounded by a display =
that did nothing when you typed on the keyboard.  The secret was to drag =
the arrow icon over the terminal icon and click.  This finally provided =
access to a terminal display that responded to the keyboard.

Until then, my editing made use of multiple screens navigated with the =
use of key combinations.  To this day, I don't think GUI really offered =
improved productivity.  It was sexy and you did not need to remember all =
those damn key sequences.  The systems at Xerox Parc made use of the SRI =
developments which then spawned Windows and Macs introducing personal =
computers to the masses.  Keeping the masses safe has been an ongoing =
struggle requiring creative genius often evidenced in algorithms rather =
than hardware.  The evolution of computers has been awe inspiring, and =
Steve Jobs proved genius makes a difference in hardware as well.   As =
Isaac Newton said "If I have seen further it is by standing on the =
shoulders of giants."

Regards,
Douglas Otis


--Apple-Mail=_A43632BB-F825-4AD9-8F0D-4B2DA48D6A3C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Diso-8859-1"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Jul 3, 2013, at 12:10 PM, Bob Braden &lt;<a =
href=3D"mailto:braden@isi.edu">braden@isi.edu</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><br>Wikipedia defines "genius" as "a person who displays =
exceptional intellectual ability, creativity, or originality"<br>All =
three applied to Doug Engelbart. He belongs up there with other creative =
&nbsp;geniuses I have had the privilege of meeting during 50 years in =
computing -- Al Perlis, &nbsp;&nbsp;Dick Hamming, John McCarthy,and Don =
Knuth come immediately to =
mind.<br></blockquote></div><div><br></div><div>Dear =
Bob,</div><div><br></div><div>Here is a video of Doug Engelbar's 1968 =
demo of SRI's work.</div><div><a =
href=3D"http://vimeo.com/32381658">http://vimeo.com/32381658</a></div><div=
><br></div><div>In the early seventies, most work used mini computers =
where faults were diagnosed using the front key panel and bit light =
displays. &nbsp;I even had the misfortune of debugging early production =
of MITS Altar systems that were flakey by connecting front panel LEDs =
directly to the data bus. As a consultant in 1985, I worked at Xerox =
Parc on the&nbsp;Xerox Star 6085 adding a cartridge tape drive. &nbsp; =
They relied on the tape drive to distribute OS updates in a timely =
fashion because their 10 Mbit Ethernet offered less than 3 Mbit =
throughput across dozens of test systems. &nbsp;By then, they were using =
Bill English's mouse design. &nbsp;Being relatively sheltered in the =
lab, this was my first encounter with a GUI interface. &nbsp;I needed to =
access my test programs but was dumbfounded by a display that did =
nothing when you typed on the keyboard. &nbsp;The secret was to drag the =
arrow icon over the terminal icon and click. &nbsp;This finally provided =
access to a terminal display that responded to the =
keyboard.</div><div><br></div><div>Until then, my editing made use of =
multiple screens navigated with the use of key combinations. &nbsp;To =
this day, I don't think GUI really offered improved productivity. =
&nbsp;It was sexy and you did not need to remember all those damn key =
sequences. &nbsp;The systems at Xerox Parc made use of the SRI =
developments which then spawned Windows and Macs introducing personal =
computers to the masses. &nbsp;Keeping the masses safe has been an =
ongoing struggle requiring creative genius often evidenced in algorithms =
rather than hardware. &nbsp;The evolution of computers has been awe =
inspiring, and Steve Jobs proved genius makes a difference in hardware =
as well. &nbsp; As Isaac Newton said "If I have seen further it is by =
standing on the shoulders of =
giants."</div><div><br></div><div>Regards,</div><div>Douglas =
Otis</div><div><br></div></body></html>=

--Apple-Mail=_A43632BB-F825-4AD9-8F0D-4B2DA48D6A3C--

From l.wood@surrey.ac.uk  Wed Jul  3 17:21:27 2013
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C640911E8104 for <ietf@ietfa.amsl.com>; Wed,  3 Jul 2013 17:21:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.098
X-Spam-Level: 
X-Spam-Status: No, score=-3.098 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hp4qROnTUsbb for <ietf@ietfa.amsl.com>; Wed,  3 Jul 2013 17:21:22 -0700 (PDT)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.138]) by ietfa.amsl.com (Postfix) with ESMTP id 94E6F11E80EC for <ietf@ietf.org>; Wed,  3 Jul 2013 17:21:22 -0700 (PDT)
Received: from [85.158.136.51:20748] by server-2.bemta-5.messagelabs.com id C4/04-23285-AFFB4D15; Thu, 04 Jul 2013 00:21:14 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-15.tower-49.messagelabs.com!1372897274!18503964!1
X-Originating-IP: [131.227.200.31]
X-StarScan-Received: 
X-StarScan-Version: 6.9.9; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 32582 invoked from network); 4 Jul 2013 00:21:14 -0000
Received: from exht011p.surrey.ac.uk (HELO EXHT011P.surrey.ac.uk) (131.227.200.31) by server-15.tower-49.messagelabs.com with AES128-SHA encrypted SMTP; 4 Jul 2013 00:21:14 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT011P.surrey.ac.uk ([131.227.200.31]) with mapi; Thu, 4 Jul 2013 01:21:13 +0100
From: <l.wood@surrey.ac.uk>
To: <warren@kumari.net>
Date: Thu, 4 Jul 2013 01:20:29 +0100
Subject: RE: [IETF] Re: [IETF] Re: Appeal Response to Abdussalam Baryun regarding draft-ietf-manet-nhdp-sec-threats
Thread-Topic: [IETF] Re: [IETF] Re: Appeal Response to Abdussalam Baryun regarding draft-ietf-manet-nhdp-sec-threats
Thread-Index: Ac54QQ2o8c1SgjuSRlqIFqj/UgsD/gACzwkv
Message-ID: <290E20B455C66743BE178C5C84F12408223F494EDA@EXMB01CMS.surrey.ac.uk>
References: <20130702222442.2467.13086.idtracker@ietfa.amsl.com> <290E20B455C66743BE178C5C84F12408223F494ECC@EXMB01CMS.surrey.ac.uk> <51D45225.1000804@qti.qualcomm.com> <1B046143-4B0E-41C0-9F50-09A87206FCE9@kumari.net> <FDE04DA5C72B9B80DCC2FE15@JcK-HP8200.jck.com> <51D47C0C.3040603@qti.qualcomm.com> <CAMm+LwgpWZ6bP6Q4chfa-fOjQ3MBBfr0CW6SxzKFPnLe=cgpYA@mail.gmail.com>, <C03016D1-A784-4F4E-9A31-9824DE080F65@kumari.net>
In-Reply-To: <C03016D1-A784-4F4E-9A31-9824DE080F65@kumari.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
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jul 2013 00:21:28 -0000

> C: does my appeal look more like the club of 3, or the club of 11?=20

I think there's a new club of one.

Lloyd Wood
http://sat-net.com/L.Wood/

From dougb@dougbarton.us  Wed Jul  3 17:34:05 2013
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C75F311E810D for <ietf@ietfa.amsl.com>; Wed,  3 Jul 2013 17:34:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.393
X-Spam-Level: 
X-Spam-Status: No, score=-2.393 tagged_above=-999 required=5 tests=[AWL=0.206,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f2nZMymNwqEv for <ietf@ietfa.amsl.com>; Wed,  3 Jul 2013 17:34:00 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [208.79.90.218]) by ietfa.amsl.com (Postfix) with ESMTP id AA5F311E80E3 for <ietf@ietf.org>; Wed,  3 Jul 2013 17:34:00 -0700 (PDT)
Received: from [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b] (unknown [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b]) by dougbarton.us (Postfix) with ESMTPSA id 8187422B13 for <ietf@ietf.org>; Thu,  4 Jul 2013 00:33:57 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1372898037; bh=vPrnIu19N1eifYNcCwptgwNAK8DLfZ1BGcYTVULjptI=; h=Date:From:To:Subject:References:In-Reply-To; b=HnrQkSjFtTZ6hfTePqrDLf3pLjkdIDKbZuGzdQs/KxQfZAd3XG+dwx7IGfzX15xV/ s1k3PmBnFyKD5mS+KjysFNYSk1BcfqRzC9cKoyV9J/+mTPLrQaFzuJCUMbk60GpXp8 RQJ7N8B0qUm/B4soH057EKhKsuD0HTcJc5aleCQQ=
Message-ID: <51D4C2F4.3060003@dougbarton.us>
Date: Wed, 03 Jul 2013 17:33:56 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [IETF] Re: [IETF] Re: Appeal Response to Abdussalam Baryun regarding draft-ietf-manet-nhdp-sec-threats
References: <20130702222442.2467.13086.idtracker@ietfa.amsl.com> <290E20B455C66743BE178C5C84F12408223F494ECC@EXMB01CMS.surrey.ac.uk> <51D45225.1000804@qti.qualcomm.com> <1B046143-4B0E-41C0-9F50-09A87206FCE9@kumari.net> <FDE04DA5C72B9B80DCC2FE15@JcK-HP8200.jck.com> <51D47C0C.3040603@qti.qualcomm.com> <CAMm+LwgpWZ6bP6Q4chfa-fOjQ3MBBfr0CW6SxzKFPnLe=cgpYA@mail.gmail.com>, <C03016D1-A784-4F4E-9A31-9824DE080F65@kumari.net> <290E20B455C66743BE178C5C84F12408223F494EDA@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F12408223F494EDA@EXMB01CMS.surrey.ac.uk>
X-Enigmail-Version: 1.5.2
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jul 2013 00:34:05 -0000

On 07/03/2013 05:20 PM, l.wood@surrey.ac.uk wrote:
>> C: does my appeal look more like the club of 3, or the club of 11?
>
> I think there's a new club of one.

Wait, so now instead of voting we're using clubs? I think I need to pay 
more attention to this thread ...


From dave@cridland.net  Wed Jul  3 17:36:02 2013
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38E2221F85D1 for <ietf@ietfa.amsl.com>; Wed,  3 Jul 2013 17:36:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id In7Dm7EjZCcW for <ietf@ietfa.amsl.com>; Wed,  3 Jul 2013 17:36:01 -0700 (PDT)
Received: from mail-ob0-x233.google.com (mail-ob0-x233.google.com [IPv6:2607:f8b0:4003:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id 94E3C21F8487 for <ietf@ietf.org>; Wed,  3 Jul 2013 17:36:01 -0700 (PDT)
Received: by mail-ob0-f179.google.com with SMTP id xk17so909034obc.24 for <ietf@ietf.org>; Wed, 03 Jul 2013 17:36:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=F0Akm+ycaIohXksk2fqdnVX+P95pibrKJxBfA0sqBI0=; b=BG4ez35AB+2izX2aiq7LGpCwKokwMbWcERoXwfv9ye/3oQy4wseygs//geV+Kh6eyy SNOtd7A/ejUNTqQ0j43wW2xqPuMTAun3lOdrLCwNmpDSAQdDVIdA07/y+omJcn6RvwmH YcyiRQVPFqarvJRA+jJ3Nu+xCX1KAWItzhF98=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=F0Akm+ycaIohXksk2fqdnVX+P95pibrKJxBfA0sqBI0=; b=fx24TRu/KZwlJAb/3ZHl+RhMJOmZi/+UwLxRZInTqAymr4jw5ITvVzcY/BTe4/AEiJ RUC37lMeormsfVJMdEXFL97DlSUpf9e4+JNAD7T/Be9v49Wf5yCeLTTTuLDau28jloJN uZ/LRVFFAVu0buajH2v0Rkmpgmzl6bdgoCHBh4vrar/Xgd40xokX4qgvyDozv886+dMY 30c/g6ZPW9Pr+4cqNPEpCiMvd62zCE6EyYOUJFfYClb3A0aq4Ap0hI4cAoUaqGqvOG4R tVK1h+V4ZMiBnkRuttpu/B5yMWdfKsg0+KdksNK+OvBn35c8LE63QWc6JprvOyavXy11 Iihw==
MIME-Version: 1.0
X-Received: by 10.60.39.193 with SMTP id r1mr3514480oek.40.1372898161133; Wed, 03 Jul 2013 17:36:01 -0700 (PDT)
Received: by 10.60.139.212 with HTTP; Wed, 3 Jul 2013 17:36:01 -0700 (PDT)
Received: by 10.60.139.212 with HTTP; Wed, 3 Jul 2013 17:36:01 -0700 (PDT)
In-Reply-To: <51D4C2F4.3060003@dougbarton.us>
References: <20130702222442.2467.13086.idtracker@ietfa.amsl.com> <290E20B455C66743BE178C5C84F12408223F494ECC@EXMB01CMS.surrey.ac.uk> <51D45225.1000804@qti.qualcomm.com> <1B046143-4B0E-41C0-9F50-09A87206FCE9@kumari.net> <FDE04DA5C72B9B80DCC2FE15@JcK-HP8200.jck.com> <51D47C0C.3040603@qti.qualcomm.com> <CAMm+LwgpWZ6bP6Q4chfa-fOjQ3MBBfr0CW6SxzKFPnLe=cgpYA@mail.gmail.com> <C03016D1-A784-4F4E-9A31-9824DE080F65@kumari.net> <290E20B455C66743BE178C5C84F12408223F494EDA@EXMB01CMS.surrey.ac.uk> <51D4C2F4.3060003@dougbarton.us>
Date: Thu, 4 Jul 2013 01:36:01 +0100
Message-ID: <CAKHUCzxzQDQfXk80QimhO30V17UnX4C+-mzbFKojkt8tFYQW=g@mail.gmail.com>
Subject: Re: [IETF] Re: [IETF] Re: Appeal Response to Abdussalam Baryun regarding draft-ietf-manet-nhdp-sec-threats
From: Dave Cridland <dave@cridland.net>
To: Doug Barton <dougb@dougbarton.us>
Content-Type: multipart/alternative; boundary=089e0149cc46351be204e0a4c336
X-Gm-Message-State: ALoCoQnX8fvJB9Tvp0Y+ASapFHxhMbLraCSH4V+v1zGoh4+xm8PJXWi6gCSw9jixjUWItufUQLwk
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jul 2013 00:36:02 -0000

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

Yeah, but we don't actually count the clubs, so it's okay.

--089e0149cc46351be204e0a4c336
Content-Type: text/html; charset=ISO-8859-1

<p dir="ltr">Yeah, but we don&#39;t actually count the clubs, so it&#39;s okay.</p>

--089e0149cc46351be204e0a4c336--

From barryleiba.mailing.lists@gmail.com  Wed Jul  3 17:39:04 2013
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A91211E810D; Wed,  3 Jul 2013 17:39:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.956
X-Spam-Level: 
X-Spam-Status: No, score=-101.956 tagged_above=-999 required=5 tests=[AWL=0.022, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H4NPhQy5UUZk; Wed,  3 Jul 2013 17:39:03 -0700 (PDT)
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 56E8A11E80E3; Wed,  3 Jul 2013 17:39:03 -0700 (PDT)
Received: by mail-ve0-f173.google.com with SMTP id jw11so624755veb.4 for <multiple recipients>; Wed, 03 Jul 2013 17:39:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=bYTKiij+i1/7wVXUkmidEGb7/PJHoD02ICteOdHqkGg=; b=T516aVhA7mFNOwU0kaQuJawgs4Qm2dEVd6rWTmnoUmcbtTLQUKdwB/lVIYb3wK9VIN ZnhxHDz0QM7cO6emGmKNlJ5IBB4AqVZ7GdEB2naZ0mArWyT9rj1Pzy7U/iA8piYUMJH9 xt+kqx5jiOgbPJdQGO/lPBt2qUK0Kvqnybq2UqeMXd7vTTewF9Ya3u83f3zKbJ40opvr bYWv91X/W8Tr6mUo5CNzBFJ6p3tHfYFQtvo6sJqfD/XxQ5++kLm8ev4TKNCKPBQaeeqd 1uHbMPFnDypEgyrrS443my38QKjL+UkJ0TUNdnKOaiLcWSXfAUa/VX8nmVpfirx6BGL3 EjfA==
MIME-Version: 1.0
X-Received: by 10.220.181.69 with SMTP id bx5mr1084721vcb.71.1372898341728; Wed, 03 Jul 2013 17:39:01 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.137.227 with HTTP; Wed, 3 Jul 2013 17:39:01 -0700 (PDT)
In-Reply-To: <20130703213108.25309.83377.idtracker@ietfa.amsl.com>
References: <20130703213108.25309.83377.idtracker@ietfa.amsl.com>
Date: Wed, 3 Jul 2013 20:39:01 -0400
X-Google-Sender-Auth: bZ4nWxIYowPNskGhAyHUdEnA6ZM
Message-ID: <CAC4RtVD5XLO0iqXAYLZfLsGbaRiAHpL1jNDJLLri9jekAKN7gw@mail.gmail.com>
Subject: Re: IETF 87 Registration Suspended
From: Barry Leiba <barryleiba@computer.org>
To: IETF discussion list <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: iaoc@ietf.org, IAB <iab@iab.org>, IESG <iesg@ietf.org>, Working Group Chairs <wgchairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jul 2013 00:39:04 -0000

> Registration for IETF87 in Berlin has been suspended to consider the impact
> of a change in the VAT rules on Registration Fees.  We expect registration
> to open as soon as this matter has been clarified.

I don't understand what the effect of VAT rules is on money collected
in the U.S. in U.S. Dollars.

But I guess we'll hear more soon.

Barry

From Ted.Lemon@nominum.com  Wed Jul  3 18:09:27 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71FE621F9B95 for <ietf@ietfa.amsl.com>; Wed,  3 Jul 2013 18:09:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2SBwSs1J5vM6 for <ietf@ietfa.amsl.com>; Wed,  3 Jul 2013 18:09:20 -0700 (PDT)
Received: from exprod7og109.obsmtp.com (exprod7og109.obsmtp.com [64.18.2.171]) by ietfa.amsl.com (Postfix) with ESMTP id C06C421F9B8D for <ietf@ietf.org>; Wed,  3 Jul 2013 18:09:20 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob109.postini.com ([64.18.6.12]) with SMTP ID DSNKUdTLQFfb6J6YCtUdR+9h6Pzllk5JczEm@postini.com; Wed, 03 Jul 2013 18:09:20 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 6B7351B821E for <ietf@ietf.org>; Wed,  3 Jul 2013 18:09:20 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 653A5190061; Wed,  3 Jul 2013 18:09:20 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Wed, 3 Jul 2013 18:09:20 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Doug Barton <dougb@dougbarton.us>
Subject: Re: [IETF] [IETF] Re: Appeal Response to Abdussalam Baryun regarding draft-ietf-manet-nhdp-sec-threats
Thread-Topic: [IETF] [IETF] Re: Appeal Response to Abdussalam Baryun regarding draft-ietf-manet-nhdp-sec-threats
Thread-Index: AQHOeFMcwvGtEEuk9kGtuofK1anurg==
Date: Thu, 4 Jul 2013 01:09:19 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751FBD60@mbx-01.win.nominum.com>
References: <20130702222442.2467.13086.idtracker@ietfa.amsl.com> <290E20B455C66743BE178C5C84F12408223F494ECC@EXMB01CMS.surrey.ac.uk> <51D45225.1000804@qti.qualcomm.com> <1B046143-4B0E-41C0-9F50-09A87206FCE9@kumari.net> <FDE04DA5C72B9B80DCC2FE15@JcK-HP8200.jck.com> <51D47C0C.3040603@qti.qualcomm.com> <CAMm+LwgpWZ6bP6Q4chfa-fOjQ3MBBfr0CW6SxzKFPnLe=cgpYA@mail.gmail.com>, <C03016D1-A784-4F4E-9A31-9824DE080F65@kumari.net> <290E20B455C66743BE178C5C84F12408223F494EDA@EXMB01CMS.surrey.ac.uk> <51D4C2F4.3060003@dougbarton.us>
In-Reply-To: <51D4C2F4.3060003@dougbarton.us>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <3CE359527892714CA089BDB8C9311CDE@nominum.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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jul 2013 01:09:27 -0000

On Jul 3, 2013, at 8:33 PM, Doug Barton <dougb@dougbarton.us> wrote:
> Wait, so now instead of voting we're using clubs? I think I need to pay m=
ore attention to this thread ...

If you don't read ietf, you don't get to participate in the consensus... ;)


From duerst@it.aoyama.ac.jp  Wed Jul  3 21:30:02 2013
Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D02F11E8125; Wed,  3 Jul 2013 21:30:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.54
X-Spam-Level: 
X-Spam-Status: No, score=-103.54 tagged_above=-999 required=5 tests=[AWL=0.250, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265,  MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u8XAANh7tEaq; Wed,  3 Jul 2013 21:29:55 -0700 (PDT)
Received: from scintmta02.scbb.aoyama.ac.jp (scintmta02.scbb.aoyama.ac.jp [133.2.253.34]) by ietfa.amsl.com (Postfix) with ESMTP id 90FCF11E8104; Wed,  3 Jul 2013 21:29:55 -0700 (PDT)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta02.scbb.aoyama.ac.jp (secret/secret) with SMTP id r644To6g013215; Thu, 4 Jul 2013 13:29:50 +0900
Received: from (unknown [133.2.206.134]) by scmse02.scbb.aoyama.ac.jp with smtp id 6edc_0b12_5d710b8c_e462_11e2_bf4c_001e6722eec2; Thu, 04 Jul 2013 13:29:49 +0900
Received: from [IPv6:::1] (unknown [133.2.210.1]) by itmail2.it.aoyama.ac.jp (Postfix) with ESMTP id AC1E1BF548; Thu,  4 Jul 2013 13:28:13 +0900 (JST)
Message-ID: <51D4FA2D.3040601@it.aoyama.ac.jp>
Date: Thu, 04 Jul 2013 13:29:33 +0900
From: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: IETF 87 Registration Suspended
References: <20130703213108.25309.83377.idtracker@ietfa.amsl.com> <CAC4RtVD5XLO0iqXAYLZfLsGbaRiAHpL1jNDJLLri9jekAKN7gw@mail.gmail.com>
In-Reply-To: <CAC4RtVD5XLO0iqXAYLZfLsGbaRiAHpL1jNDJLLri9jekAKN7gw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: iaoc@ietf.org, IAB <iab@iab.org>, IETF discussion list <ietf@ietf.org>, Working Group Chairs <wgchairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jul 2013 04:30:02 -0000

Hello Barry,

On 2013/07/04 9:39, Barry Leiba wrote:
>> Registration for IETF87 in Berlin has been suspended to consider the impact
>> of a change in the VAT rules on Registration Fees.  We expect registration
>> to open as soon as this matter has been clarified.
>
> I don't understand what the effect of VAT rules is on money collected
> in the U.S. in U.S. Dollars.

It's usual in the U.S. that taxes on goods bought and sold are levied as 
a consumption tax, at the place (i.e. in the state) where the object is 
bought (and therefore presumably consumed/used).

However, that's not a given, and VAT stands for value added tax, and the 
value addition/consumption can be presumed to happen at the meeting in 
Berlin (and there's no need for consensus here, it's the opinion of the 
local tax authority that counts :-().

Regards,   Martin.

> But I guess we'll hear more soon.
>
> Barry
>

From Sandra.Murphy@sparta.com  Wed Jul  3 15:00:24 2013
Return-Path: <Sandra.Murphy@sparta.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE2E011E823E; Wed,  3 Jul 2013 15:00:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n52RbQ9H03WP; Wed,  3 Jul 2013 15:00:10 -0700 (PDT)
Received: from M4.sparta.com (M4.sparta.com [157.185.61.2]) by ietfa.amsl.com (Postfix) with ESMTP id 2304D11E80EF; Wed,  3 Jul 2013 15:00:03 -0700 (PDT)
Received: from Beta5.sparta.com ([10.62.8.21]) by M4.sparta.com (8.14.4/8.14.4) with ESMTP id r63Lxvw7011170; Wed, 3 Jul 2013 16:59:57 -0500
Received: from CVA-HUB001.centreville.ads.sparta.com ([10.62.108.11]) by Beta5.sparta.com (8.13.8/8.13.8) with ESMTP id r63LxqHq001828; Wed, 3 Jul 2013 16:59:57 -0500
Received: from CVA-MB002.centreville.ads.sparta.com ([fe80::6046:a82a:c500:c9ad]) by CVA-HUB001.centreville.ads.sparta.com ([fe80::8ca8:7aea:3db9:1972%11]) with mapi id 14.02.0342.003; Wed, 3 Jul 2013 18:00:45 -0400
From: "Murphy, Sandra" <Sandra.Murphy@sparta.com>
To: "ietf@ietf.org" <ietf@ietf.org>, IETF Announcement List <ietf-announce@ietf.org>
Subject: RE: IETF 87 Registration Suspended
Thread-Topic: IETF 87 Registration Suspended
Thread-Index: AQHOeDTHd8AOjDX580yU2trk6x9e7ZlTgMe7
Date: Wed, 3 Jul 2013 22:00:45 +0000
Message-ID: <24B20D14B2CD29478C8D5D6E9CBB29F67497638C@CVA-MB002.centreville.ads.sparta.com>
References: <20130703213108.25309.83377.idtracker@ietfa.amsl.com>
In-Reply-To: <20130703213108.25309.83377.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.62.8.137]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Thu, 04 Jul 2013 10:33:39 -0700
Cc: "iaoc@ietf.org" <iaoc@ietf.org>, "iab@iab.org" <iab@iab.org>, "wgchairs@ietf.org" <wgchairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Jul 2013 22:00:24 -0000

Is there a potential for impact to those already registered?  (So we know t=
o watch for the announcement.)=0A=
=0A=
--Sandy=0A=
=0A=
________________________________________=0A=
From: wgchairs-bounces@ietf.org [wgchairs-bounces@ietf.org] on behalf of IE=
TF Administrative Director [iad@ietf.org]=0A=
Sent: Wednesday, July 03, 2013 5:31 PM=0A=
To: IETF Announcement List=0A=
Cc: iaoc@ietf.org; iab@iab.org; ietf@ietf.org; wgchairs@ietf.org=0A=
Subject: IETF 87 Registration Suspended=0A=
=0A=
Registration for IETF87 in Berlin has been suspended to consider the impact=
=0A=
of a change in the VAT rules on Registration Fees.  We expect registration=
=0A=
to open as soon as this matter has been clarified.=0A=
=0A=
Ray=0A=
IETF Administrative Director=0A=

From dhc@dcrocker.net  Thu Jul  4 12:34:58 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE16E11E81A0 for <ietf@ietfa.amsl.com>; Thu,  4 Jul 2013 12:34:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VzQ00wLYa7Xk for <ietf@ietfa.amsl.com>; Thu,  4 Jul 2013 12:34:53 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id CB1EE11E819D for <ietf@ietf.org>; Thu,  4 Jul 2013 12:34:53 -0700 (PDT)
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 r64JYnkU001040 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 4 Jul 2013 12:34:52 -0700
Message-ID: <51D5CE4A.40602@dcrocker.net>
Date: Thu, 04 Jul 2013 12:34:34 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Donald Eastlake <d3e3e3@gmail.com>
Subject: Re: NOMCOM 2013-14 Volunteering - 3rd and Final Call for Volunteers
References: <20130701234030.24738.41427.idtracker@ietfa.amsl.com> <CAF4+nEFBcy0KwXqfDpNARcmk-EdyyJfanCmc_=Fp7D06nAtwzg@mail.gmail.com>
In-Reply-To: <CAF4+nEFBcy0KwXqfDpNARcmk-EdyyJfanCmc_=Fp7D06nAtwzg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Thu, 04 Jul 2013 12:34:52 -0700 (PDT)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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, 04 Jul 2013 19:34:59 -0000

On 7/2/2013 9:59 AM, Donald Eastlake wrote:
> I do not
> believe that the noncom is intended to be or should be a
> "representative" sample from those who just barely qualify as eligible
> to be volunteers under the current rules.
>
> Why is the "quality" of volunteers ignored in comparison with the
> quantity? No doubt many will strongly object to my use of "quality"
> but by that I mean understanding of the IETF culture and the IETF goal
> of benefiting the Internet community and a goodly amount of experience
> with IETF processes.


Most IETF participants have relatively little direct knowledge of IETF 
management and process.  So a larger pool of recent meeting attendees is 
merely likely to get more people without an experiential base for 
judging IETF management candidates.

When the qualification rule was develop for Nomcom, most attendees were 
regulars with broad and deep knowledge of IETF technology and the 
group's operation.  The simplistic rule didn't need to worry about real 
experience; almost everyone attending had it. That changed quite a few 
years ago.

Until we make sure Nomcom's have at least a minimal number of people 
experienced with the workings of IETF process, we will continue to risk 
a Nomcom composed of people having literally no such knowledge.

The risk is actually a certainty, over time, given how statistical 
sampling works, over time.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From brian.e.carpenter@gmail.com  Thu Jul  4 14:09:16 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF95521F9A1D for <ietf@ietfa.amsl.com>; Thu,  4 Jul 2013 14:09:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qo3aWbyVl0Ps for <ietf@ietfa.amsl.com>; Thu,  4 Jul 2013 14:09:15 -0700 (PDT)
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 58A1A21F8F24 for <ietf@ietf.org>; Thu,  4 Jul 2013 14:09:15 -0700 (PDT)
Received: by mail-pa0-f49.google.com with SMTP id ld11so1600390pab.8 for <ietf@ietf.org>; Thu, 04 Jul 2013 14:09:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=62Dw4OuTorqVAqK0taVWjnBSduaTTcFQjsA/kVsukDw=; b=VUl2YygZEv2/T1D0fHoCj4prkgnQ20dRIT9EXwqnAcectsaOyljyDh7Zf0ylkWllIX X5AtI0rpe70+K2Ljn04Xe8mFrckxr7Dc9qHLxRSlEcZvAPBQ6BreZdqByypH414hkLn5 zPwc5UK4MLOHw04DBXo57N41Zf6xxgJbH5Yjq87h1Y/wNVUO74kJlktXmhk7ixw5Qy+K OyMeqZtO8pg+hmql7faOL6mFIfyuW3BMsOmUalLHEypkipOt6WZMkhOa8CX3Zxowgjl1 CS3dO3CJDArPRMp4yI4stqt5lqB7GWQgU8b0wj8S9k6gNzP9St4sr58w+peifnRSVA8z VRJA==
X-Received: by 10.66.190.3 with SMTP id gm3mr8727542pac.72.1372972155110; Thu, 04 Jul 2013 14:09:15 -0700 (PDT)
Received: from [10.1.9.177] ([203.167.141.74]) by mx.google.com with ESMTPSA id vb8sm4179799pbc.11.2013.07.04.14.09.13 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 04 Jul 2013 14:09:14 -0700 (PDT)
Message-ID: <51D5E473.4060105@gmail.com>
Date: Fri, 05 Jul 2013 09:09:07 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: IETF discussion list <ietf@ietf.org>
Subject: Re: Evi Nemeth
References: <51CCC9B3.70606@gmail.com>
In-Reply-To: <51CCC9B3.70606@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jul 2013 21:09:16 -0000

One more update on the search. Family members are still hoping for
a good outcome:

http://www.stuff.co.nz/national/8876799/Lost-text-from-missing-yacht-Nina-crew

(For those who don't remember Evi, she and her students provided IP
multicast services at numerous IETF meetings in the 1990s.)

Regards
   Brian Carpenter

On 28/06/2013 11:24, Brian E Carpenter wrote:
> Evi used to be an IETF regular. There is rather ominous news - she is
> lost at sea between New Zealand and Australia:
> 
> http://www.nzherald.co.nz/nz/news/article.cfm?c_id=1&objectid=10893482
> 
> http://www.nzherald.co.nz/nz/news/article.cfm?c_id=1&objectid=10893503
> 
> Regards
>    Brian Carpenter
> 
> 
> 

From mrex@sap.com  Thu Jul  4 18:07:11 2013
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18B9B11E80E6; Thu,  4 Jul 2013 18:07:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.649
X-Spam-Level: 
X-Spam-Status: No, score=-9.649 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, HELO_EQ_DE=0.35, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rbs9h3k3FPPy; Thu,  4 Jul 2013 18:07:06 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id A810911E8103; Thu,  4 Jul 2013 18:07:04 -0700 (PDT)
Received: from mail05.wdf.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id r6516sY7019524 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 5 Jul 2013 03:06:54 +0200 (MEST)
Subject: Re: IETF 87 Registration Suspended
In-Reply-To: <51D4FA2D.3040601@it.aoyama.ac.jp>
To: =?UTF-8?Q?=22Martin_J=2E_D=C3=BCrst=22?= <duerst@it.aoyama.ac.jp>
Date: Fri, 5 Jul 2013 03:06:54 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="ISO-8859-1"
Message-Id: <20130705010654.ABCA31A87C@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Cc: iaoc@ietf.org, Barry Leiba <barryleiba@computer.org>, IETF discussion list <ietf@ietf.org>, IAB <iab@iab.org>, Working Group Chairs <wgchairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Jul 2013 01:07:11 -0000

"Martin J. D=FCrst" wrote:
>=20
>On 2013/07/04 9:39, Barry Leiba wrote:
>>> Registration for IETF87 in Berlin has been suspended to consider the im=
pact
>>> of a change in the VAT rules on Registration Fees.  We expect registrat=
ion
>>> to open as soon as this matter has been clarified.
>>
>> I don't understand what the effect of VAT rules is on money collected
>> in the U.S. in U.S. Dollars.
>=20
> It's usual in the U.S. that taxes on goods bought and sold are levied as=
=20
> a consumption tax, at the place (i.e. in the state) where the object is=
=20
> bought (and therefore presumably consumed/used).
>=20
> However, that's not a given, and VAT stands for value added tax, and the=
=20
> value addition/consumption can be presumed to happen at the meeting in=20
> Berlin (and there's no need for consensus here, it's the opinion of the=
=20
> local tax authority that counts :-().


If the money that is collected is an entrance/participation fee for
the venue itself, then the local tax authority might require the local
VAT for _all_ visitors, even those that pay in advance or in a
different country.


While it might be possible to make the necessary tweaks about the fee
(maybe not for this meeting, but for future meetings) for the WG sessions
themselves, this would be more difficult to argue for the
breakfast/buffet/brownies/beverages (I assume that still exists)
and the access to the terminal room, where some form of badge
checking is usually done in order to protect the resources.


-Martin


From mrex@sap.com  Thu Jul  4 18:19:20 2013
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4518E21F9957; Thu,  4 Jul 2013 18:19:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.899
X-Spam-Level: 
X-Spam-Status: No, score=-9.899 tagged_above=-999 required=5 tests=[AWL=0.350,  BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0GhTJQUG21OG; Thu,  4 Jul 2013 18:19:15 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 94A3821F83EF; Thu,  4 Jul 2013 18:19:15 -0700 (PDT)
Received: from mail05.wdf.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id r651J8JC012493 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 5 Jul 2013 03:19:08 +0200 (MEST)
Subject: Re: IETF 87 Registration Suspended
In-Reply-To: <20130705010654.ABCA31A87C@ld9781.wdf.sap.corp>
To: mrex@sap.com
Date: Fri, 5 Jul 2013 03:19:08 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="ISO-8859-1"
Message-Id: <20130705011908.697B91A87C@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Cc: Working Group Chairs <wgchairs@ietf.org>, IETF discussion list <ietf@ietf.org>, iaoc@ietf.org, IAB <iab@iab.org>, Barry Leiba <barryleiba@computer.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Jul 2013 01:19:20 -0000

Martin Rex wrote:
> "Martin J. D=FCrst" wrote:
> >=20
> >On 2013/07/04 9:39, Barry Leiba wrote:
> >>> Registration for IETF87 in Berlin has been suspended to consider the =
impact
> >>> of a change in the VAT rules on Registration Fees.  We expect registr=
ation
> >>> to open as soon as this matter has been clarified.
> >>
> >> I don't understand what the effect of VAT rules is on money collected
> >> in the U.S. in U.S. Dollars.
> >=20
> > It's usual in the U.S. that taxes on goods bought and sold are levied a=
s=20
> > a consumption tax, at the place (i.e. in the state) where the object is=
=20
> > bought (and therefore presumably consumed/used).
> >=20
> > However, that's not a given, and VAT stands for value added tax, and th=
e=20
> > value addition/consumption can be presumed to happen at the meeting in=
=20
> > Berlin (and there's no need for consensus here, it's the opinion of the=
=20
> > local tax authority that counts :-().
>=20
>=20
> If the money that is collected is an entrance/participation fee for
> the venue itself, then the local tax authority might require the local
> VAT for _all_ visitors, even those that pay in advance or in a
> different country.

It seems that the rules might be somewhat similar all over europe:

   http://www.tmf-vat.com/vat/german-vat.html


-Martin

From johnl@iecc.com  Thu Jul  4 20:26:12 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3A1811E8114 for <ietf@ietfa.amsl.com>; Thu,  4 Jul 2013 20:26:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.762
X-Spam-Level: 
X-Spam-Status: No, score=-110.762 tagged_above=-999 required=5 tests=[AWL=0.437, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KqF4LSzLx-Kq for <ietf@ietfa.amsl.com>; Thu,  4 Jul 2013 20:26:08 -0700 (PDT)
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 9EF1E21F9DEC for <ietf@ietf.org>; Thu,  4 Jul 2013 20:26:08 -0700 (PDT)
Received: (qmail 60504 invoked from network); 5 Jul 2013 03:26:07 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 5 Jul 2013 03:26:07 -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=51d63ccf.xn--i8sz2z.k1307; i=johnl@user.iecc.com; bh=UCN8UHF7sqsp38h6O6krroyhvdCOODiczqhFLGS00hQ=; b=W0GkFkXtEqVBfHaOIPQ5Uu/hACdD5zPcmUA8gvN48kuw2Vqr2icWy1x4+IifGTWkjM5k2qLvc09j9blMl5Bj+1pscuxxIOdwv0AxrBENyHKjG+ScttbjkJGkCRv4Ir/iGJAje59xTq8z5x+wTS6RkSgTarZoLfhDxETPDvejKVFOB8UqxTgtaFO+S9YBXtKVPZyh4AhYSTOvKDPMmcazfpH45gKE/N40MZ3NdEi8jk7EPELUke1X75iFLPp/3A+f
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=51d63ccf.xn--i8sz2z.k1307; olt=johnl@user.iecc.com; bh=UCN8UHF7sqsp38h6O6krroyhvdCOODiczqhFLGS00hQ=; b=qGyUknrJ8Y8KWYFW+rFfN0axW0REnr0ES1OxFLzEFpd/98xCzi3CsYf8dDFawZQTEAgjVVGnmmzLN50xhJUnt4pNkmn9kn6SqQEU5xWn5JCimmhMOk9Vt9nzyLzVBByLR0kmVat4c8kzp5FzUq/Kr1h/GhV85IHIafzS40jMCJabFxJ6UXud7Aqwr33SIEnc/CSWBdviNo8YGqoj0Cw0ZLPabwIlln1V3Z1sv2XqM0LDR12WujO2nHePYEI6Lc8F
Date: 5 Jul 2013 03:25:45 -0000
Message-ID: <20130705032545.18877.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: IETF 87 Registration Suspended
In-Reply-To: <20130705011908.697B91A87C@ld9781.wdf.sap.corp>
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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Jul 2013 03:26:12 -0000

>It seems that the rules might be somewhat similar all over europe:
>
>   http://www.tmf-vat.com/vat/german-vat.html

You would think so, which leads to the question about what's different
in Berlin from Paris and Prague and Maastricht.

R's,
John





From dwm@xpasc.com  Thu Jul  4 21:02:09 2013
Return-Path: <dwm@xpasc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6386711E8116 for <ietf@ietfa.amsl.com>; Thu,  4 Jul 2013 21:02:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.953
X-Spam-Level: 
X-Spam-Status: No, score=-5.953 tagged_above=-999 required=5 tests=[AWL=-4.646, BAYES_00=-2.599, MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m4BKHfDgWT96 for <ietf@ietfa.amsl.com>; Thu,  4 Jul 2013 21:02:04 -0700 (PDT)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [209.133.53.32]) by ietfa.amsl.com (Postfix) with ESMTP id 8DD6511E80E1 for <ietf@ietf.org>; Thu,  4 Jul 2013 21:02:04 -0700 (PDT)
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 7B06F3F6F6 for <ietf@ietf.org>; Fri,  5 Jul 2013 04:02:02 +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 r6541xbn000502 for <ietf@ietf.org>; Thu, 4 Jul 2013 21:02:02 -0700
Date: Thu, 4 Jul 2013 21:01:59 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
cc: ietf@ietf.org
Subject: Re: IETF 87 Registration Suspended
In-Reply-To: <20130705032545.18877.qmail@joyce.lan>
Message-ID: <alpine.LRH.2.01.1307042101020.31995@egate.xpasc.com>
References: <20130705032545.18877.qmail@joyce.lan>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Milter-Version: master.87-g7939dec
X-AV-Type: clean
X-AV-Accuracy: exact
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 05 Jul 2013 04:02:09 -0000

On Thu, 5 Jul 2013, John Levine wrote:

> >It seems that the rules might be somewhat similar all over europe:
> >
> >   http://www.tmf-vat.com/vat/german-vat.html
> 
> You would think so, which leads to the question about what's different
> in Berlin from Paris and Prague and Maastricht.

Somebody asked the wrong question and discoved a previously unknown
requirement?

From jnc@mercury.lcs.mit.edu  Thu Jul  4 21:11:36 2013
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCDE011E822A for <ietf@ietfa.amsl.com>; Thu,  4 Jul 2013 21:11:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6kfvuvreeiB2 for <ietf@ietfa.amsl.com>; Thu,  4 Jul 2013 21:11:31 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id B5D6611E8227 for <ietf@ietf.org>; Thu,  4 Jul 2013 21:11:31 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id D1F7918C0FC; Fri,  5 Jul 2013 00:11:28 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: IETF 87 Registration Suspended
Message-Id: <20130705041128.D1F7918C0FC@mercury.lcs.mit.edu>
Date: Fri,  5 Jul 2013 00:11:28 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Jul 2013 04:11:36 -0000

    > From: "John Levine" <johnl@taugh.com>

    > what's different in Berlin from Paris and Prague and Maastricht.

The Germans have more 'zealous' tax collectors? :-)

	Noel

From narten@us.ibm.com  Thu Jul  4 21:53:15 2013
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5058711E8230 for <ietf@ietfa.amsl.com>; Thu,  4 Jul 2013 21:53:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7WrCXR6EwK2r for <ietf@ietfa.amsl.com>; Thu,  4 Jul 2013 21:53:08 -0700 (PDT)
Received: from e32.co.us.ibm.com (e32.co.us.ibm.com [32.97.110.150]) by ietfa.amsl.com (Postfix) with ESMTP id 8702121F9DDD for <ietf@ietf.org>; Thu,  4 Jul 2013 21:53:08 -0700 (PDT)
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, 4 Jul 2013 22:53:07 -0600
Received: from d03dlp03.boulder.ibm.com (9.17.202.179) by e32.co.us.ibm.com (192.168.1.132) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 4 Jul 2013 22:53:05 -0600
Received: from d03relay02.boulder.ibm.com (d03relay02.boulder.ibm.com [9.17.195.227]) by d03dlp03.boulder.ibm.com (Postfix) with ESMTP id EB63919D8042 for <ietf@ietf.org>; Thu,  4 Jul 2013 22:52:54 -0600 (MDT)
Received: from d03av06.boulder.ibm.com (d03av06.boulder.ibm.com [9.17.195.245]) by d03relay02.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r654r4RT125134 for <ietf@ietf.org>; Thu, 4 Jul 2013 22:53:04 -0600
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 r654ta37006159 for <ietf@ietf.org>; Thu, 4 Jul 2013 22:55:36 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d03av06.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r654tZTE006153 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 4 Jul 2013 22:55:36 -0600
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.7/8.12.5) with ESMTP id r654r3s4001798 for <ietf@ietf.org>; Fri, 5 Jul 2013 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.7/8.14.7/Submit) id r654r28Z001767 for ietf@ietf.org; Fri, 5 Jul 2013 00:53:02 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201307050453.r654r28Z001767@rotala.raleigh.ibm.com>
Date: Fri, 05 Jul 2013 00:53:02 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13070504-5406-0000-0000-00000A2722FC
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Jul 2013 04:53:15 -0000

Total of 92 messages in the last 7 days.
 
script run at: Fri Jul  5 00:53:02 EDT 2013
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  4.35% |    4 |  4.01% |    25872 | john-ietf@jck.com
  4.35% |    4 |  3.77% |    24329 | mrex@sap.com
  4.35% |    4 |  3.72% |    24024 | dhc@dcrocker.net
  3.26% |    3 |  4.36% |    28144 | chris.dearlove@baesystems.com
  3.26% |    3 |  3.76% |    24231 | d3e3e3@gmail.com
  3.26% |    3 |  3.44% |    22163 | warren@kumari.net
  3.26% |    3 |  3.00% |    19334 | l.wood@surrey.ac.uk
  3.26% |    3 |  2.80% |    18070 | brian.e.carpenter@gmail.com
  3.26% |    3 |  2.65% |    17087 | johnl@taugh.com
  2.17% |    2 |  3.20% |    20669 | presnick@qti.qualcomm.com
  3.26% |    3 |  2.03% |    13113 | jnc@mercury.lcs.mit.edu
  2.17% |    2 |  2.41% |    15515 | michael.tuexen@lurchi.franken.de
  2.17% |    2 |  2.29% |    14782 | nomcom-chair-2013@ietf.org
  2.17% |    2 |  2.19% |    14143 | hannes.tschofenig@gmx.net
  2.17% |    2 |  2.06% |    13293 | ted.lemon@nominum.com
  2.17% |    2 |  2.02% |    13006 | mstjohns@comcast.net
  2.17% |    2 |  1.95% |    12611 | scott.brim@gmail.com
  2.17% |    2 |  1.83% |    11808 | descombes@lpsc.in2p3.fr
  2.17% |    2 |  1.78% |    11464 | paul.hoffman@vpnc.org
  2.17% |    2 |  1.71% |    11056 | dougb@dougbarton.us
  1.09% |    1 |  2.35% |    15138 | hallam@gmail.com
  1.09% |    1 |  2.31% |    14906 | rex_corpuz2003@yahoo.com
  1.09% |    1 |  2.04% |    13179 | ron.even.tlv@gmail.com
  1.09% |    1 |  1.72% |    11083 | doug.mtview@gmail.com
  1.09% |    1 |  1.62% |    10449 | rbonica@juniper.net
  1.09% |    1 |  1.55% |    10013 | narten@us.ibm.com
  1.09% |    1 |  1.37% |     8834 | michael_oreirdan@cable.comcast.com
  1.09% |    1 |  1.35% |     8735 | abdussalambaryun@gmail.com
  1.09% |    1 |  1.26% |     8150 | tony@att.com
  1.09% |    1 |  1.23% |     7921 | framefritti@gmail.com
  1.09% |    1 |  1.21% |     7781 | sm@resistor.net
  1.09% |    1 |  1.20% |     7761 | eckert@cisco.com
  1.09% |    1 |  1.20% |     7713 | rlb@ipv.sx
  1.09% |    1 |  1.18% |     7620 | hsantos@isdg.net
  1.09% |    1 |  1.17% |     7562 | jabley@hopcount.ca
  1.09% |    1 |  1.17% |     7518 | jun@wide.ad.jp
  1.09% |    1 |  1.15% |     7407 | mike5guo@gmail.com
  1.09% |    1 |  1.12% |     7225 | housley@vigilsec.com
  1.09% |    1 |  1.12% |     7196 | iab-chair@iab.org
  1.09% |    1 |  1.08% |     6983 | trammell@tik.ee.ethz.ch
  1.09% |    1 |  1.03% |     6626 | dave@cridland.net
  1.09% |    1 |  0.98% |     6352 | johannes.merkle@secunet.com
  1.09% |    1 |  0.96% |     6174 | bob.hinden@gmail.com
  1.09% |    1 |  0.95% |     6108 | lear@cisco.com
  1.09% |    1 |  0.93% |     6027 | william.mccall@gmail.com
  1.09% |    1 |  0.93% |     6010 | duerst@it.aoyama.ac.jp
  1.09% |    1 |  0.91% |     5900 | sandra.murphy@sparta.com
  1.09% |    1 |  0.90% |     5811 | chair@ietf.org
  1.09% |    1 |  0.90% |     5809 | hartmans-ietf@mit.edu
  1.09% |    1 |  0.90% |     5799 | adrian@olddog.co.uk
  1.09% |    1 |  0.88% |     5679 | lars@netapp.com
  1.09% |    1 |  0.88% |     5660 | dot@dotat.at
  1.09% |    1 |  0.87% |     5627 | barryleiba@computer.org
  1.09% |    1 |  0.86% |     5548 | jari.arkko@piuha.net
  1.09% |    1 |  0.78% |     5034 | dwm@xpasc.com
  1.09% |    1 |  0.78% |     5014 | braden@isi.edu
  1.09% |    1 |  0.75% |     4814 | elwynd@dial.pipex.com
  1.09% |    1 |  0.73% |     4727 | randy@psg.com
  1.09% |    1 |  0.70% |     4502 | iad@ietf.org
--------+------+--------+----------+------------------------
100.00% |   92 |100.00% |   645109 | Total


From l.wood@surrey.ac.uk  Thu Jul  4 23:41:38 2013
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E51D911E8234; Thu,  4 Jul 2013 23:41:38 -0700 (PDT)
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=[AWL=-0.250, BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J4qtokMoUShm; Thu,  4 Jul 2013 23:41:34 -0700 (PDT)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.148]) by ietfa.amsl.com (Postfix) with ESMTP id CED1A11E8255; Thu,  4 Jul 2013 23:41:32 -0700 (PDT)
Received: from [195.245.231.67:3824] by server-12.bemta-5.messagelabs.com id 17/FF-22750-A9A66D15; Fri, 05 Jul 2013 06:41:30 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-6.tower-82.messagelabs.com!1373006489!30395373!1
X-Originating-IP: [131.227.200.43]
X-StarScan-Received: 
X-StarScan-Version: 6.9.9; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 1693 invoked from network); 5 Jul 2013 06:41:30 -0000
Received: from exht022p.surrey.ac.uk (HELO EXHT022P.surrey.ac.uk) (131.227.200.43) by server-6.tower-82.messagelabs.com with AES128-SHA encrypted SMTP; 5 Jul 2013 06:41:30 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT022P.surrey.ac.uk ([131.227.200.43]) with mapi; Fri, 5 Jul 2013 07:41:29 +0100
From: <l.wood@surrey.ac.uk>
To: <mrex@sap.com>, <duerst@it.aoyama.ac.jp>
Date: Fri, 5 Jul 2013 07:40:28 +0100
Subject: RE: IETF 87 Registration Suspended
Thread-Topic: IETF 87 Registration Suspended
Thread-Index: Ac55HBbpEy+OSJiKT+iAinSXcNgHdwALnLrI
Message-ID: <290E20B455C66743BE178C5C84F12408223F494EDC@EXMB01CMS.surrey.ac.uk>
References: <51D4FA2D.3040601@it.aoyama.ac.jp>, <20130705010654.ABCA31A87C@ld9781.wdf.sap.corp>
In-Reply-To: <20130705010654.ABCA31A87C@ld9781.wdf.sap.corp>
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
Cc: iaoc@ietf.org, barryleiba@computer.org, ietf@ietf.org, iab@iab.org, wgchairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Jul 2013 06:41:39 -0000

It strikes me that 'membership fees' as opposed to 'entrance fees' could wo=
rk around this payment issue. Or incur a different tax...

Lloyd Wood
http://sat-net.com/L.Wood/


________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Martin Rex=
 [mrex@sap.com]
Sent: 05 July 2013 02:06
To: "Martin J. D=FCrst"
Cc: iaoc@ietf.org; Barry Leiba; IETF discussion list; IAB; Working Group Ch=
airs
Subject: Re: IETF 87 Registration Suspended

"Martin J. D=FCrst" wrote:
>
>On 2013/07/04 9:39, Barry Leiba wrote:
>>> Registration for IETF87 in Berlin has been suspended to consider the im=
pact
>>> of a change in the VAT rules on Registration Fees.  We expect registrat=
ion
>>> to open as soon as this matter has been clarified.
>>
>> I don't understand what the effect of VAT rules is on money collected
>> in the U.S. in U.S. Dollars.
>
> It's usual in the U.S. that taxes on goods bought and sold are levied as
> a consumption tax, at the place (i.e. in the state) where the object is
> bought (and therefore presumably consumed/used).
>
> However, that's not a given, and VAT stands for value added tax, and the
> value addition/consumption can be presumed to happen at the meeting in
> Berlin (and there's no need for consensus here, it's the opinion of the
> local tax authority that counts :-().


If the money that is collected is an entrance/participation fee for
the venue itself, then the local tax authority might require the local
VAT for _all_ visitors, even those that pay in advance or in a
different country.


While it might be possible to make the necessary tweaks about the fee
(maybe not for this meeting, but for future meetings) for the WG sessions
themselves, this would be more difficult to argue for the
breakfast/buffet/brownies/beverages (I assume that still exists)
and the access to the terminal room, where some form of badge
checking is usually done in order to protect the resources.


-Martin


From elwynd@dial.pipex.com  Fri Jul  5 01:25:48 2013
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8AE711E8268 for <ietf@ietfa.amsl.com>; Fri,  5 Jul 2013 01:25:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -92.599
X-Spam-Level: 
X-Spam-Status: No, score=-92.599 tagged_above=-999 required=5 tests=[AWL=-10.000, BAYES_00=-2.599, URIBL_BLACK=20, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rbGGvfcecskB for <ietf@ietfa.amsl.com>; Fri,  5 Jul 2013 01:25:48 -0700 (PDT)
Received: from auth.a.painless.aa.net.uk (a.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e33]) by ietfa.amsl.com (Postfix) with ESMTP id 1537811E8264 for <ietf@ietf.org>; Fri,  5 Jul 2013 01:25:48 -0700 (PDT)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by a.painless.aa.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <elwynd@dial.pipex.com>) id 1Uv1Kj-0006LN-Ia; Fri, 05 Jul 2013 09:25:44 +0100
Subject: Re: IETF 87 Registration Suspended
From: Elwyn Davies <elwynd@dial.pipex.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
In-Reply-To: <20130705041128.D1F7918C0FC@mercury.lcs.mit.edu>
References: <20130705041128.D1F7918C0FC@mercury.lcs.mit.edu>
Content-Type: text/plain
Date: Fri, 05 Jul 2013 09:22:06 +0100
Message-Id: <1373012526.4524.38502.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
X-Spam-Score-a.painless.aa.net.uk: -4.0
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Jul 2013 08:25:49 -0000

On Fri, 2013-07-05 at 00:11 -0400, Noel Chiappa wrote:
> > From: "John Levine" <johnl@taugh.com>
> 
>     > what's different in Berlin from Paris and Prague and Maastricht.
> 
> The Germans have more 'zealous' tax collectors? :-)
> 
> 	Noel
It appears that the goalposts have been moved - the basic change came in
a couple of years ago:
http://www.uktrainingworldwide.com/BB/vat-rules-for-events-and-seminars.html

but the proximal cause may be to do with an update from last September
(and this was instigated in Germany):
See page 159 of
http://ec.europa.eu/taxation_customs/resources/documents/taxation/vat/key_documents/vat_committee/2012_guidelines-vat-committee-meetings_en.pdf

This is probably ultimately down to the tightening of the inter-country
trading rules after the clampdown on so-called carousel trading.

But with the arcana of VAT rules ... who knows (certainly not me
although I have tangled with a few of them)?

Doubtless clearing this up will require a confrontation of tax lawyer
and VAT officer at dawn in some shady forest glade.

/Elwyn
 



From sm@resistor.net  Fri Jul  5 02:41:13 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E50311E8271; Fri,  5 Jul 2013 02:41:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vakcy-GqBtLh; Fri,  5 Jul 2013 02:41:12 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8621B21F9989; Fri,  5 Jul 2013 02:41:12 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r659f7p5014780; Fri, 5 Jul 2013 02:41:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1373017271; bh=GpUClMCwYqNTs4zRYALhyC5DF6BQuh31mjhMFvCd1SQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=KOa7EXGG95BXZXE4C9avUjQHoUYpgyG79sO7zb/WGtqE7GiN3+L98IbsU7fHnwruP w3d3p4DDXFtpdDCXO2xJGsyZEHjBZdZeS+hk514/K5QucLeNL2woAf9V90M1HOdPqL 8pspr+URTy7M1Hh3O+ICtJoqaeZytrjNBPX13AKQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1373017271; i=@resistor.net; bh=GpUClMCwYqNTs4zRYALhyC5DF6BQuh31mjhMFvCd1SQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=xY+1d12MJeQc6ZKpXiFO0XcVC0pCl6W5FTcONH2dUJ6KW8DZKIiJw9pIH+hgO9z0k 3GduCNkIqLQfJtyh8FC4BYdyggpIn4pmx/5lVJXs4wNSuxebrf3jG01FzfE6U5931S tpKvTf0nzXvSWe2eSrIes6YcTSlAXFdSx0InpIos=
Message-Id: <6.2.5.6.2.20130704224915.0c408718@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 05 Jul 2013 02:05:28 -0700
To: iab@iab.org
From: SM <sm@resistor.net>
Subject: Re: Call for Comment on draft-iab-anycast-arch-implications-09 on "Architectural Considerations of IP Anycast"
In-Reply-To: <2C891F70-34C8-441A-8085-38A9F2F13D5B@iab.org>
References: <2C891F70-34C8-441A-8085-38A9F2F13D5B@iab.org>
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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Jul 2013 09:41:13 -0000

At 11:13 03-07-2013, IAB Chair wrote:
>This is an announcement of an IETF-wide Call for Comment on 
>"Architectural Considerations of IP Anycast" 
>(draft-iab-anycast-arch-implications-09).

The first version of this draft was submitted in February 2010.  The 
IETF-wide Call is a little more than three years after that.

The title of the draft is "Architectural Considerations of IP 
Anycast".  The Abstract mentions "architectural implications of IP 
anycast".  After reading the draft it seems to me that it is more 
about considerations of using IP Anycast.

In Section 1:

   "As of early 2009, at least 10 of the 13 root name servers were
   using IP anycast [RSSAC29]"

;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 62449
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;rssac.org.                     IN      A

rssac.org is having DNS issues.

The above cites a report published in 2007 about root name servers 
using IP anycast in 2009.  That seems incorrect.

In Section 2.1:

  "One of the first documented uses of anycast was in 1994 for a "Video
   Registry" experiment [IMR9401]."

I suggest using 
ftp://ftp.rfc-editor.org/in-notes/museum/imr/imr9401.txt as the 
stable reference for IMR9401.

   "At the same time, site-local-scoped well-known addresses began
    being used for recursive resolvers [I-D.ietf-ipv6-dns-discovery],
    but this use was never standardized (see below in Section 3.4 for
    more discussion)."

That I-D from 2002 is cited as work in progress. :-)

   '"Requirements for a Mechanism Identifying a Name Server Instance"
    [RFC4892] cites the use of anycast with DNS as a motivation to
    identify individual name server instances, and the Name Server ID
    (NSID) option was defined for this purpose [RFC5001].'

 From an architectural point of view I would look at it in terms of 
locator and identifier separation.

In Section 3.4:

   'Section 3.3 of [RFC4339] proposes a "Well-known Anycast Address" for
    recursive DNS service configuration in clients to ease configuration
    and allow those systems to ship with these well-known addresses
    configured "from the beginning, as, say, factory default".  During
    publication the IESG requested that the following "IESG Note" be
    contained in the document:'

Section 3 is about principles.  RFC 4339 was published in 2006.  I 
didn't look into what seems to be the preferred approach since 
then.  The IESG Note quoted in the draft does not convey much 
information from an anycast perspective.  I guess that Section 3.3.2 
of RFC 4339 is more appropriate as it discusses about the 
disadvantages of using the well-known anycast address.

It seems to me that the idea here was more about well-known address 
instead of anycast.  As a comment about history it seems that this 
goes back to the idea of logical addressing mentioned in 1981.  To 
keep matters easy I would go with the idea of locator of ubiquitous 
service which offers flexibility to the host.

Would it be appropriate to say that one of the assumptions for 
anycasting an application is that it has a fail-over mode in addition 
to using a stateless transport?  Otherwise the route has to be 
withdrawn to avoid service outage (see Section 4.5).

The draft was an interesting read.  I didn't catch the potential for 
a cascaded failure at first (see Section 4.4).  On a second read I 
realized that I was confusing a specific case with a general 
approach.  The "many pitfalls and subtleties" mentioned in Section 
1  sums up IP anycast.

Regards,
-sm


From john@jck.com  Fri Jul  5 07:31:01 2013
Return-Path: <john@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E1D911E80F4; Fri,  5 Jul 2013 07:31:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2KDFAL8qtMqV; Fri,  5 Jul 2013 07:30:56 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 0392821F9F71; Fri,  5 Jul 2013 07:30:56 -0700 (PDT)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john@jck.com>) id 1Uv729-0007GS-4s; Fri, 05 Jul 2013 10:30:49 -0400
X-Vipre-Scanned: 023EF5C2002C31023EF70F-TDI
Date: Fri, 05 Jul 2013 10:30:47 -0400
From: John C Klensin <john@jck.com>
To: l.wood@surrey.ac.uk, mrex@sap.com, duerst@it.aoyama.ac.jp
Subject: RE: IETF 87 Registration Suspended
Message-ID: <B83C42E16A057A939FFD3939@[192.168.1.128]>
In-Reply-To: <290E20B455C66743BE178C5C84F12408223F494EDC@EXMB01CMS.surrey.ac.uk>
References: <51D4FA2D.3040601@it.aoyama.ac.jp> ,	<20130705010654.ABCA31A87C@ld9781.wdf.sap.corp> <290E20B455C66743BE178C5C84F12408223F494EDC@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
Cc: iaoc@ietf.org, barryleiba@computer.org, ietf@ietf.org, iab@iab.org, wgchairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Jul 2013 14:31:01 -0000

--On Friday, July 05, 2013 07:40 +0100 l.wood@surrey.ac.uk wrote:

> It strikes me that 'membership fees' as opposed to 'entrance
> fees' could work around this payment issue. Or incur a
> different tax...

But the use of a term like "membership fee" has profound
implications for what the IETF claims is our way of doing
business.

Folks, it is clear that this is both inconvenient and
complicated.  Would it be possible to just let the IAOC engage
in whatever discussions and consultations are needed --i.e.,
allow them to do their jobs-- without endless amateur [1]
speculation on what is going on and what should or could be done
about it.   Since people are obviously curious and in the
interest of openness and transparency, I hope that the IAOC will
explain the details and the solutions when they have things
under control.  But let's let them get them under control first.

Just my opinion, of course.

   john

[1] both amateur lawyers and amateur international taxation
experts.  Anyone who is part of the conversation who is _not_ am
amateur should probably volunteer (or market) her or his
services offlist to the IAOC or directly to Ray at iad@ietf.org




From tjc@ecs.soton.ac.uk  Fri Jul  5 07:34:20 2013
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F222D21F9967; Fri,  5 Jul 2013 07:34:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level: 
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vZA-0HihB-2I; Fri,  5 Jul 2013 07:34:19 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 1985321F9963; Fri,  5 Jul 2013 07:34:18 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost.ecs.soton.ac.uk [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r65EYBsM020319; Fri, 5 Jul 2013 15:34:11 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r65EYBsM020319
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1373034852; bh=3AjnIc9gW+kXXpBln9JqSJBngXI=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=myrX2ZNdA6mXAESr3dGkbBZXCbXNH8In6VlR7/sZY0O7ELB9pITrXA/vj7WGNUpDY Tddm4MPpI7Nl85eja4huG2xRyohJ5FzsQYp3Vc2pasHOrwOQ3hml7gmhE3RrYgeH+5 kUYMW8qjFqIFz2ozcAj8OVO5qzPbBwObICmpZAZs=
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 p64FYB0544538556dx ret-id none; Fri, 05 Jul 2013 15:34:12 +0100
Received: from tjc-vpn.ecs.soton.ac.uk (tjc-vpn.ecs.soton.ac.uk [152.78.236.241]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r65EYAxp001708 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 5 Jul 2013 15:34:10 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: IETF 87 Registration Suspended
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <B83C42E16A057A939FFD3939@[192.168.1.128]>
Date: Fri, 5 Jul 2013 15:34:19 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|f733db8168234a92b6acab0072053be0p64FYB03tjc|ecs.soton.ac.uk|B874A9EC-72A7-4AF6-93AA-34391074AE3D@ecs.soton.ac.uk>
References: <51D4FA2D.3040601@it.aoyama.ac.jp> , <20130705010654.ABCA31A87C@ld9781.wdf.sap.corp> <290E20B455C66743BE178C5C84F12408223F494EDC@EXMB01CMS.surrey.ac.uk> <B83C42E16A057A939FFD3939@[192.168.1.128]> <B874A9EC-72A7-4AF6-93AA-34391074AE3D@ecs.soton.ac.uk>
To: John C Klensin <john@jck.com>
X-Mailer: Apple Mail (2.1508)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p64FYB054453855600; tid=p64FYB0544538556dx; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=9:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r65EYBsM020319
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: wgchairs@ietf.org, ietf@ietf.org, iaoc@ietf.org, iab@iab.org, barryleiba@computer.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Jul 2013 14:34:20 -0000

On 5 Jul 2013, at 15:30, John C Klensin <john@jck.com> wrote:

> --On Friday, July 05, 2013 07:40 +0100 l.wood@surrey.ac.uk wrote:
>=20
>> It strikes me that 'membership fees' as opposed to 'entrance
>> fees' could work around this payment issue. Or incur a
>> different tax...
>=20
> But the use of a term like "membership fee" has profound
> implications for what the IETF claims is our way of doing
> business.

I would add also that many organisations (and funding bodies) would not =
support claims for "membership fees" where conference meeting =
registration fees are perfectly accepted.

Tim=

From carlosm3011@gmail.com  Fri Jul  5 08:16:16 2013
Return-Path: <carlosm3011@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5397B11E82FC for <ietf@ietfa.amsl.com>; Fri,  5 Jul 2013 08:16:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.276
X-Spam-Level: 
X-Spam-Status: No, score=-2.276 tagged_above=-999 required=5 tests=[AWL=0.323,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gGWqhoHbsRJo for <ietf@ietfa.amsl.com>; Fri,  5 Jul 2013 08:16:14 -0700 (PDT)
Received: from mail-ye0-x22c.google.com (mail-ye0-x22c.google.com [IPv6:2607:f8b0:4002:c04::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 5CE3111E82F1 for <ietf@ietf.org>; Fri,  5 Jul 2013 08:16:14 -0700 (PDT)
Received: by mail-ye0-f172.google.com with SMTP id l14so743294yen.31 for <ietf@ietf.org>; Fri, 05 Jul 2013 08:16:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=VPsH7BH5CIsieNti4mtuZCdRHjB7bdYtqWtSkCZ6JVw=; b=PIs6CKNYw4XVrKZD5NkuRc7m9J1LKYBQ2Kv+XpM62hW1F3Z2SReIGHlsyvgpAF/04c IdcguKExPtlj+QebR29JJzP9eXcy1xvuoL24/xQ/ZNyNAQaQ9ZcmnqHGMgq2S60S2MnP dSxaYCi+r4j2ThRVLDLkJbCk430dAkVTKeaPKol8jPt2NDfJ7JvCCEI/xJio8zVCn1A7 hz5oHY2j2zl3V8B0ZnJIu38h4BcOxLwlWRi3Fs1eHNP+da1Q2Oi7uDZx0lgIAEMeMgZA HdRedRy2PgHc/1mYtINuJTJtSURhNH48OJmWxfEgSNbuXxN6vkXNZ9u61H0/gc7qDltd 0CZQ==
X-Received: by 10.236.193.169 with SMTP id k29mr6208152yhn.146.1373037373829;  Fri, 05 Jul 2013 08:16:13 -0700 (PDT)
Received: from 87-7-200.lacnic.net.uy ([200.7.87.57]) by mx.google.com with ESMTPSA id a28sm13366143yha.0.2013.07.05.08.16.11 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 05 Jul 2013 08:16:13 -0700 (PDT)
Message-ID: <51D6E339.2030604@gmail.com>
Date: Fri, 05 Jul 2013 12:16:09 -0300
From: "Carlos M. Martinez" <carlosm3011@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: IETF 87 Registration Suspended
References: <20130705041128.D1F7918C0FC@mercury.lcs.mit.edu>
In-Reply-To: <20130705041128.D1F7918C0FC@mercury.lcs.mit.edu>
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.12
Precedence: list
Reply-To: carlos@lacnic.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, 05 Jul 2013 15:16:16 -0000

Understandable. After all, they need to bail out whole countries on a
regular basis

:)

On 7/5/13 1:11 AM, Noel Chiappa wrote:
>     > From: "John Levine" <johnl@taugh.com>
> 
>     > what's different in Berlin from Paris and Prague and Maastricht.
> 
> The Germans have more 'zealous' tax collectors? :-)
> 
> 	Noel
> 

From mkaushik@us.ibm.com  Thu Jul  4 15:07:08 2013
Return-Path: <mkaushik@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6881911E81F9 for <ietf@ietfa.amsl.com>; Thu,  4 Jul 2013 15:07:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nvBoND1bMP84 for <ietf@ietfa.amsl.com>; Thu,  4 Jul 2013 15:06:57 -0700 (PDT)
Received: from e37.co.us.ibm.com (e37.co.us.ibm.com [32.97.110.158]) by ietfa.amsl.com (Postfix) with ESMTP id D4DD311E81E6 for <ietf@ietf.org>; Thu,  4 Jul 2013 15:06:56 -0700 (PDT)
Received: from /spool/local by e37.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <mkaushik@us.ibm.com>; Thu, 4 Jul 2013 16:06:55 -0600
Received: from d03dlp02.boulder.ibm.com (9.17.202.178) by e37.co.us.ibm.com (192.168.1.137) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 4 Jul 2013 16:06:53 -0600
Received: from d03relay05.boulder.ibm.com (d03relay05.boulder.ibm.com [9.17.195.107]) by d03dlp02.boulder.ibm.com (Postfix) with ESMTP id 3B9593E40040 for <ietf@ietf.org>; Thu,  4 Jul 2013 16:06:32 -0600 (MDT)
Received: from d03av06.boulder.ibm.com (d03av06.boulder.ibm.com [9.17.195.245]) by d03relay05.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r64M6qJJ148890 for <ietf@ietf.org>; Thu, 4 Jul 2013 16:06:52 -0600
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 r64M9NT7015835 for <ietf@ietf.org>; Thu, 4 Jul 2013 16:09:23 -0600
Received: from d03nm691.boulder.ibm.com (d03nm691.boulder.ibm.com [9.63.34.16]) by d03av06.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r64M9N0V015824 for <ietf@ietf.org>; Thu, 4 Jul 2013 16:09:23 -0600
Subject: AUTO: Meenakshi Kaushik is on vacation  (returning 08/05/2013)
Auto-Submitted: auto-generated
From: Meenakshi Kaushik <mkaushik@us.ibm.com>
To: <ietf@ietf.org>
Message-ID: <OF35D975F9.0ED7BFAB-ON87257B9E.007978F3-87257B9E.007978F3@us.ibm.com>
Date: Thu, 4 Jul 2013 16:06:48 -0600
X-MIMETrack: Serialize by Router on D03NM691/03/M/IBM(Release 8.5.3FP2 ZX853FP2HF5|February, 2013) at 07/04/2013 04:06:48 PM
MIME-Version: 1.0
Content-type: multipart/alternative;  Boundary="0__=08BBF10DDFEAFE638f9e8a93df938690918c08BBF10DDFEAFE63"
Content-Disposition: inline
X-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13070422-7408-0000-0000-000011C41A87
X-Mailman-Approved-At: Fri, 05 Jul 2013 08:33:21 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jul 2013 22:07:08 -0000

--0__=08BBF10DDFEAFE638f9e8a93df938690918c08BBF10DDFEAFE63
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: quoted-printable



I am out of the office until 08/05/2013.

Hello, I am on vacation  until Aug 2nd, 2013.

For FC/FCoE discussion, issues, RPQ config validation please contact  B=
adri
Ramaswamy and/or Min Zhuo.

I have uploaded my FC/FCoE presentation slides here  ..
http://cattail.boulder.ibm.com/cattail/#view=3Dmkaushik@us.ibm.com

For QCN and RoCE solutions please contact Keshav Kamble.

For Kraken FC please contact Pramodh Mallipatna.

For any other topics, please connect with my manager David Iles.

Thanks

Best,
Meenakshi


Note: This is an automated response to your message  "[trill] Last Call=
:
<draft-ietf-trill-directory-framework-05.txt>	(TRILL	(Transparent
Interconnection of Lots of Links): Edge	Directory	Assistance Framework)=

to Informational RFC" sent on 07/04/2013 3:45:04 PM.

This is the only notification you will receive while this person is awa=
y.=

--0__=08BBF10DDFEAFE638f9e8a93df938690918c08BBF10DDFEAFE63
Content-type: text/html; charset=US-ASCII
Content-Disposition: inline
Content-transfer-encoding: quoted-printable

<html><body>
<p><font size=3D"1" face=3D"sans-serif">I am out of the office until 08=
/05/2013.<br>
</font><font size=3D"1" face=3D"sans-serif"><br>
</font><font size=3D"1" face=3D"sans-serif">Hello, I am on vacation &nb=
sp;until Aug 2nd, 2013.<br>
</font><font size=3D"1" face=3D"sans-serif"><br>
</font><font size=3D"1" face=3D"sans-serif">For FC/FCoE discussion, iss=
ues, RPQ config validation please contact &nbsp;Badri Ramaswamy and/or =
Min Zhuo. <br>
</font><font size=3D"1" face=3D"sans-serif"><br>
</font><font size=3D"1" face=3D"sans-serif">I have uploaded my FC/FCoE =
presentation slides here &nbsp;.. <a href=3D"http://cattail.boulder.ibm=
.com/cattail/#view=3Dmkaushik@us.ibm.com">http://cattail.boulder.ibm.co=
m/cattail/#view=3Dmkaushik@us.ibm.com</a><br>
</font><font size=3D"1" face=3D"sans-serif"><br>
</font><font size=3D"1" face=3D"sans-serif">For QCN and RoCE solutions =
please contact Keshav Kamble.<br>
</font><font size=3D"1" face=3D"sans-serif"><br>
</font><font size=3D"1" face=3D"sans-serif">For Kraken FC please contac=
t Pramodh Mallipatna.<br>
</font><font size=3D"1" face=3D"sans-serif"><br>
</font><font size=3D"1" face=3D"sans-serif">For any other topics, pleas=
e connect with my manager David Iles.<br>
</font><font size=3D"1" face=3D"sans-serif"><br>
</font><font size=3D"1" face=3D"sans-serif">Thanks<br>
</font><font size=3D"1" face=3D"sans-serif"><br>
</font><font size=3D"1" face=3D"sans-serif">Best,<br>
</font><font size=3D"1" face=3D"sans-serif">Meenakshi<br>
</font><font size=3D"1" face=3D"sans-serif"><br>
</font><font size=3D"1" face=3D"sans-serif"><br>
</font><font size=3D"1" color=3D"#808080" face=3D"sans-serif">Note: Thi=
s is an automated response to your message &nbsp;</font><font size=3D"1=
" face=3D"sans-serif"><b>&quot;[trill] Last Call: &lt;draft-ietf-trill-=
directory-framework-05.txt&gt;	(TRILL	(Transparent Interconnection of L=
ots of Links): Edge	Directory	Assistance Framework) to Informational RF=
C&quot;</b></font><font size=3D"1" color=3D"#808080" face=3D"sans-serif=
">&nbsp;sent on </font><font size=3D"1" face=3D"sans-serif"><b>07/04/20=
13 3:45:04 PM</b></font><font size=3D"1" color=3D"#808080" face=3D"sans=
-serif">. <br>
</font><font size=3D"1" color=3D"#808080" face=3D"sans-serif"><br>
</font><font size=3D"1" color=3D"#808080" face=3D"sans-serif">This is t=
he only notification you will receive while this person is away.</font>=
</body></html>=

--0__=08BBF10DDFEAFE638f9e8a93df938690918c08BBF10DDFEAFE63--


From dmbond@us.ibm.com  Thu Jul  4 19:04:35 2013
Return-Path: <dmbond@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D5CB21F93C4 for <ietf@ietfa.amsl.com>; Thu,  4 Jul 2013 19:04:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6FjcM1Xbggii for <ietf@ietfa.amsl.com>; Thu,  4 Jul 2013 19:04:23 -0700 (PDT)
Received: from e8.ny.us.ibm.com (e8.ny.us.ibm.com [32.97.182.138]) by ietfa.amsl.com (Postfix) with ESMTP id 2D93821F938E for <ietf@ietf.org>; Thu,  4 Jul 2013 19:04:22 -0700 (PDT)
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 <dmbond@us.ibm.com>; Fri, 5 Jul 2013 03:04:22 +0100
Received: from d01dlp03.pok.ibm.com (9.56.250.168) by e8.ny.us.ibm.com (192.168.1.108) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 5 Jul 2013 03:04:20 +0100
Received: from d01relay03.pok.ibm.com (d01relay03.pok.ibm.com [9.56.227.235]) by d01dlp03.pok.ibm.com (Postfix) with ESMTP id EDBB2C90049 for <ietf@ietf.org>; Thu,  4 Jul 2013 22:04:18 -0400 (EDT)
Received: from d01av05.pok.ibm.com (d01av05.pok.ibm.com [9.56.224.195]) by d01relay03.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r6524Jmu304002 for <ietf@ietf.org>; Thu, 4 Jul 2013 22:04:19 -0400
Received: from d01av05.pok.ibm.com (loopback [127.0.0.1]) by d01av05.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r6524J0H026378 for <ietf@ietf.org>; Thu, 4 Jul 2013 22:04:19 -0400
Received: from d01ml076.pok.ibm.com (d01ml076.pok.ibm.com [9.63.8.33]) by d01av05.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r6524JGG026373 for <ietf@ietf.org>; Thu, 4 Jul 2013 22:04:19 -0400
Subject: AUTO: David M Bond is out of the office (returning 07/08/2013)
Auto-Submitted: auto-generated
From: David M Bond <dmbond@us.ibm.com>
To: ietf@ietf.org
Message-ID: <OF86FCE509.5AB296E1-ON85257B9F.000B616D-85257B9F.000B616D@us.ibm.com>
Date: Thu, 4 Jul 2013 22:04:18 -0400
X-MIMETrack: Serialize by Router on D01ML076/01/M/IBM(Release 8.5.3FP2 ZX853FP2HF5|February, 2013) at 07/04/2013 22:04:19
MIME-Version: 1.0
Content-type: multipart/alternative;  Boundary="0__=0ABBF10CDF98E7FD8f9e8a93df938690918c0ABBF10CDF98E7FD"
Content-Disposition: inline
X-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13070502-0320-0000-0000-0000002EB8A6
X-Mailman-Approved-At: Fri, 05 Jul 2013 08:33:21 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Jul 2013 02:04:35 -0000

--0__=0ABBF10CDF98E7FD8f9e8a93df938690918c0ABBF10CDF98E7FD
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: quoted-printable



I am out of the office until 07/08/2013.

I am out of the office until Thursday. If you have an urgent need conta=
ct
Tom Hu for Security issues and Tamanna Sait for other issues.


Note: This is an automated response to your message  "[trill] Last Call=
:
<draft-ietf-trill-directory-framework-05.txt>	(TRILL	(Transparent
Interconnection of Lots of Links): Edge	Directory	Assistance Framework)=

to Informational RFC" sent on 07/04/2013 17:45:04.

This is the only notification you will receive while this person is awa=
y.=

--0__=0ABBF10CDF98E7FD8f9e8a93df938690918c0ABBF10CDF98E7FD
Content-type: text/html; charset=US-ASCII
Content-Disposition: inline
Content-transfer-encoding: quoted-printable

<html><body>
<p><font size=3D"1" face=3D"sans-serif">I am out of the office until 07=
/08/2013.<br>
</font><font size=3D"1" face=3D"sans-serif"><br>
</font><font size=3D"1" face=3D"sans-serif">I am out of the office unti=
l Thursday. If you have an urgent need contact Tom Hu for Security issu=
es and Tamanna Sait for other issues.<br>
</font><font size=3D"1" face=3D"sans-serif"><br>
</font><font size=3D"1" face=3D"sans-serif"><br>
</font><font size=3D"1" color=3D"#808080" face=3D"sans-serif">Note: Thi=
s is an automated response to your message &nbsp;</font><font size=3D"1=
" face=3D"sans-serif"><b>&quot;[trill] Last Call: &lt;draft-ietf-trill-=
directory-framework-05.txt&gt;	(TRILL	(Transparent Interconnection of L=
ots of Links): Edge	Directory	Assistance Framework) to Informational RF=
C&quot;</b></font><font size=3D"1" color=3D"#808080" face=3D"sans-serif=
">&nbsp;sent on </font><font size=3D"1" face=3D"sans-serif"><b>07/04/20=
13 17:45:04</b></font><font size=3D"1" color=3D"#808080" face=3D"sans-s=
erif">. <br>
</font><font size=3D"1" color=3D"#808080" face=3D"sans-serif"><br>
</font><font size=3D"1" color=3D"#808080" face=3D"sans-serif">This is t=
he only notification you will receive while this person is away.</font>=
</body></html>=

--0__=0ABBF10CDF98E7FD8f9e8a93df938690918c0ABBF10CDF98E7FD--


From bob.hinden@gmail.com  Fri Jul  5 08:57:23 2013
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1335D11E831B; Fri,  5 Jul 2013 08:57:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jlWMD9UNjLNt; Fri,  5 Jul 2013 08:57:20 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CB42511E8318; Fri,  5 Jul 2013 08:57:19 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: The IAOC <bob.hinden@gmail.com>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: Registration for IETF 87 in Berlin has re-opened
X-Test-IDTracker: no
X-IETF-IDTracker: 4.51.p2
Message-ID: <20130705155719.21752.810.idtracker@ietfa.amsl.com>
Date: Fri, 05 Jul 2013 08:57:19 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 05 Jul 2013 15:57:23 -0000

Registration was suspended after discussions with tax specialists and attor=
neys convinced
us that that the rules had changed in the EU and Germany with regard to the=
 impact of the
Value Added Tax (VAT) on registration fees.  =


There is an EU requirement to impose the country's Value Added Tax to regis=
tration fees
where the meeting is held.  Accordingly, Germany's 19% VAT has to be collec=
ted and paid
over to the German tax authorities.  =


The IAOC had to decide whether to change the registration fee to add the ta=
x to it, or
whether to keep the fee in place for the meeting and state that the VAT was=
 included in
the fee, which action would result in a registration revenue shortfall grea=
ter than
$100,000 USD. After discussions with the Internet Society the IAOC has deci=
ded not to change
the total registration fee for IETF87 because of the complexity of dealing =
with those who
have already paid, and those who had budgeted assuming a total fee of $650.=
  ISOC has agreed
to cover any resulting yearly budget shortfall resulting from including the=
 VAT in the IETF87
registration fee.  We thank the Internet Society for this support.

You will notice a change in your final receipt for the meeting,  It will in=
clude VAT information
and a VAT identification number.  It is expected that final receipts will b=
ecome available in the
next two weeks.  You or your employer may qualify to recover the VAT.  We w=
ill be providing
guidance on this matter in the next two weeks.

We and the Internet Society have learned that VAT is a very complex matter =
and that expertise
is required on a going forward basis.  To that end the Internet Society is =
considering proposals
to retain a European tax specialist firm to assist us and them in the futur=
e.  We will be
investigating similar issues in other regions.

This decision to not change the fee is for this meeting only. The 2014 Budg=
et will take the VAT
into consideration when the fees are set for meetings in Europe next year a=
nd beyond.  =


We look forward to seeing you in Berlin.

Bob Hinden
IAOC Chair


From jmh@joelhalpern.com  Fri Jul  5 10:18:31 2013
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFD2721F9FD0 for <ietf@ietfa.amsl.com>; Fri,  5 Jul 2013 10:18:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level: 
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o6PG-gYw8JSO for <ietf@ietfa.amsl.com>; Fri,  5 Jul 2013 10:18:25 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by ietfa.amsl.com (Postfix) with ESMTP id E2CE021F9A79 for <ietf@ietf.org>; Fri,  5 Jul 2013 10:18:25 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id B94441C0D2E for <ietf@ietf.org>; Fri,  5 Jul 2013 10:18:25 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [10.10.10.104] (pool-70-106-134-124.clppva.east.verizon.net [70.106.134.124]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 39F131C07FD for <ietf@ietf.org>; Fri,  5 Jul 2013 10:18:25 -0700 (PDT)
Message-ID: <51D6FFDA.5070407@joelhalpern.com>
Date: Fri, 05 Jul 2013 13:18:18 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Registration for IETF 87 in Berlin has re-opened
References: <20130705155719.21752.810.idtracker@ietfa.amsl.com>
In-Reply-To: <20130705155719.21752.810.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Jul 2013 17:18:32 -0000

Thank you, and ISOC.  Well done.
Joel

On 7/5/2013 11:57 AM, The IAOC wrote:
> Registration was suspended after discussions with tax specialists and attorneys convinced
> us that that the rules had changed in the EU and Germany with regard to the impact of the
> Value Added Tax (VAT) on registration fees.
>
> There is an EU requirement to impose the country's Value Added Tax to registration fees
> where the meeting is held.  Accordingly, Germany's 19% VAT has to be collected and paid
> over to the German tax authorities.
>
> The IAOC had to decide whether to change the registration fee to add the tax to it, or
> whether to keep the fee in place for the meeting and state that the VAT was included in
> the fee, which action would result in a registration revenue shortfall greater than
> $100,000 USD. After discussions with the Internet Society the IAOC has decided not to change
> the total registration fee for IETF87 because of the complexity of dealing with those who
> have already paid, and those who had budgeted assuming a total fee of $650.  ISOC has agreed
> to cover any resulting yearly budget shortfall resulting from including the VAT in the IETF87
> registration fee.  We thank the Internet Society for this support.
>
> You will notice a change in your final receipt for the meeting,  It will include VAT information
> and a VAT identification number.  It is expected that final receipts will become available in the
> next two weeks.  You or your employer may qualify to recover the VAT.  We will be providing
> guidance on this matter in the next two weeks.
>
> We and the Internet Society have learned that VAT is a very complex matter and that expertise
> is required on a going forward basis.  To that end the Internet Society is considering proposals
> to retain a European tax specialist firm to assist us and them in the future.  We will be
> investigating similar issues in other regions.
>
> This decision to not change the fee is for this meeting only. The 2014 Budget will take the VAT
> into consideration when the fees are set for meetings in Europe next year and beyond.
>
> We look forward to seeing you in Berlin.
>
> Bob Hinden
> IAOC Chair
>
>

From agenda@ietf.org  Fri Jul  5 17:20:00 2013
Return-Path: <agenda@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9984321F9E08; Fri,  5 Jul 2013 17:20:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.934
X-Spam-Level: 
X-Spam-Status: No, score=-101.934 tagged_above=-999 required=5 tests=[AWL=0.666, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QPAdjj2ghVad; Fri,  5 Jul 2013 17:20:00 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B33821F9DF8; Fri,  5 Jul 2013 17:20:00 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Agenda <agenda@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: IETF 87 Final Agenda
X-Test-IDTracker: no
X-IETF-IDTracker: 4.51.p2
Message-ID: <20130706002000.640.24427.idtracker@ietfa.amsl.com>
Date: Fri, 05 Jul 2013 17:20:00 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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: Sat, 06 Jul 2013 00:20:00 -0000

87th IETF Meeting - Berlin, Germany
July 28 - August 2, 2013

The final agenda has been posted.

https://datatracker.ietf.org/meeting/87/agenda.html
https://datatracker.ietf.org/meeting/87/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 refl=
ected on the web version of the agenda. =


Information about the 87th IETF meeting in Berlin, Germany can be found her=
e: https://www.ietf.org/meeting/87/index.html

Thank you and see you in Berlin!

Sincerely,

The IETF Secretariat

From jabley@hopcount.ca  Fri Jul  5 22:25:44 2013
Return-Path: <jabley@hopcount.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE56811E80C5 for <ietf@ietfa.amsl.com>; Fri,  5 Jul 2013 22:25:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tHHwmrbr-EK1 for <ietf@ietfa.amsl.com>; Fri,  5 Jul 2013 22:25:44 -0700 (PDT)
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 1067521F9C65 for <ietf@ietf.org>; Fri,  5 Jul 2013 22:25:43 -0700 (PDT)
Received: by mail-yh0-f41.google.com with SMTP id z20so1139702yhz.28 for <ietf@ietf.org>; Fri, 05 Jul 2013 22:25:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=VHTrCKtaCdYCjAqddQOJgwGpRbOULi8DC8z8DeZvIoI=; b=EXC2wFdSs9ns5+Fpz2X+f8DbjicQpvIFKUZLXwZL22TLBnleYc3vr5WxxexOlPlrm7 ca9jCwcn8bQ1ABuhVhGJF3c/pymnzhaVPGITLVbjIOatSiTh7wCONxkuOdWkmLT5EgSk AdW8ctw29fbbiJIExjoS2J+/RZBq4+0MIFKoA=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=VHTrCKtaCdYCjAqddQOJgwGpRbOULi8DC8z8DeZvIoI=; b=H1aD5xYIqlpk+0RAC6qLfwwY/0CYn8XaAzrjBkk1gfy/n2QBhq6vBws3e4nT0qLNGM Rh537yS8hss6fxZ+dlyBF26VuSJPJXXwNKFuf3dma/27lWbEcqP2l83tjeMREp3bS6t4 1Q2AwvYTW+Jt/EeYH/epFghO23JyxGnq3+kfecT059TjqtO5AnaPEoYUG4n0gof045bI SZ51nlT9e4Rui4J4dcePElSr/KsETA0yRPAuICiENUriBcgvrbuQIXKNDSPAhGJUftBT OJPLYhKPmASWvzATCSARXnn++YSONjap4aoYTNB+ITntlJXihV6JYDPFx1GpjXkAr6Ld kN1w==
X-Received: by 10.236.14.231 with SMTP id d67mr7504997yhd.244.1373088343483; Fri, 05 Jul 2013 22:25:43 -0700 (PDT)
Received: from [172.20.10.2] (out-pq-233.wireless.telus.com. [216.218.29.233]) by mx.google.com with ESMTPSA id v32sm18394396yhc.12.2013.07.05.22.25.42 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 05 Jul 2013 22:25:42 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Call for Comment on draft-iab-anycast-arch-implications-09 on "Architectural Considerations of IP Anycast"
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <6.2.5.6.2.20130704224915.0c408718@resistor.net>
Date: Sat, 6 Jul 2013 01:25:44 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <0E72ADF2-04B0-4FEC-A8FF-F2FB3963E6D1@hopcount.ca>
References: <2C891F70-34C8-441A-8085-38A9F2F13D5B@iab.org> <6.2.5.6.2.20130704224915.0c408718@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1508)
X-Gm-Message-State: ALoCoQlEY8AVHkddLuuRvlZnN0HPoPHrXULXCpqf40qlaoOso3EXlxngPKoBpHtXCFFUjHhIzoTx
Cc: iab@iab.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Jul 2013 05:25:45 -0000

Hi there,

I haven't reviewed the draft (but I will). One thing stood out though:

On 2013-07-05, at 05:05, SM <sm@resistor.net> wrote:

> ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 62449
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
>=20
> ;; QUESTION SECTION:
> ;rssac.org.                     IN      A
>=20
> rssac.org is having DNS issues.

RSSAC.ORG was registered by an individual with an interest in root =
server operations, but is not (as far as I know) anything to do with =
RSSAC at this time.


Joe


From abdussalambaryun@gmail.com  Sat Jul  6 03:27:47 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C76921F9C2E for <ietf@ietfa.amsl.com>; Sat,  6 Jul 2013 03:27:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9ChI5EKHwWVY for <ietf@ietfa.amsl.com>; Sat,  6 Jul 2013 03:27:47 -0700 (PDT)
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 F032F21F9C31 for <ietf@ietf.org>; Sat,  6 Jul 2013 03:27:46 -0700 (PDT)
Received: by mail-pb0-f51.google.com with SMTP id um15so2830659pbc.24 for <ietf@ietf.org>; Sat, 06 Jul 2013 03:27:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=DRLdTqljd0hofYX4zcoElSTMWEytjUEOoee+IsAOIw4=; b=sKj/ciXquzM2UKe/XZUKZsHaVqU5WRxgIuabZK0NotiuIE6arJ0y4ETEFyo6qJYP8I W/BgFCVU/JQwweUjamtVHTn/tDOwSWYtVnYnrPMWTBTtf/q57+v/XpTVvfiukecg2jxJ 1JqBVDzGrnDzjN+vbTNgXMg0wnTvJhIXxwEaIOdgBRBSwaQVi9UlJFm5AznzpXPvdAms jfz/VugDulZqYMiTUQOTVo6BK/453+LZ/5UyufGtF7jZmMNF+PXe8V5MLdroD2dFCFZu 5zFYKLc0S8qWIHuBrzGpxsZaX11vu+rwOtTuyLqxuBd6V4B555NF2fYgfnfMevwr83eP gdig==
MIME-Version: 1.0
X-Received: by 10.68.175.33 with SMTP id bx1mr13322916pbc.21.1373106466450; Sat, 06 Jul 2013 03:27:46 -0700 (PDT)
Received: by 10.68.250.133 with HTTP; Sat, 6 Jul 2013 03:27:46 -0700 (PDT)
In-Reply-To: <2C891F70-34C8-441A-8085-38A9F2F13D5B@iab.org>
References: <2C891F70-34C8-441A-8085-38A9F2F13D5B@iab.org>
Date: Sat, 6 Jul 2013 12:27:46 +0200
Message-ID: <CADnDZ89D3DoZFUBMK24uVwQ=wizh5_2=NNNtC_hcWRyu-mZ04A@mail.gmail.com>
Subject: Re: Call for Comment on draft-iab-anycast-arch-implications-09 on "Architectural Considerations of IP Anycast"
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: IAB <iab@iab.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Jul 2013 10:27:47 -0000

The informational-draft does not define IP anycast or does not refer
to a document that defines the IP anycast (anycast was defined as
refer to rfc1546). However, I think it is a draft for anycast
services/methods in IP protocols (Internet Anycast), not only IP
anycast.

AB

On 7/3/13, IAB Chair <iab-chair@iab.org> wrote:
> This is an announcement of an IETF-wide Call for Comment on "Architectural
> Considerations of IP Anycast" (draft-iab-anycast-arch-implications-09).
>
> The document is being considered for publication as an Informational RFC
> within the IAB stream, and is available for inspection here:
> https://datatracker.ietf.org/doc/draft-iab-anycast-arch-implications/
>
> The Call for Comment will last until August 1, 2013. Please send comments to
> iab@iab.org or submit them via TRAC (see below).
>
> Russ Housley
> IAB Chair
>
> = = = = = = = = = =
>
> Submitting Comments via TRAC
>
> 1. To submit an issue in TRAC, you first need to login to the IAB site on
> the tools server:
> http://tools.ietf.org/wg/iab/trac/login
>
> 2. If you don't already have a login ID, you can obtain one by navigating to
> this site:
> http://trac.tools.ietf.org/newlogin
>
> 3. Once you have obtained an account, and have logged in, you can file an
> issue by navigating to the ticket entry form:
> http://trac.tools.ietf.org/wg/iab/trac/newticket
>
> 4. When opening an issue:
> a. The Type: field should be set to "defect" for an issue with the current
> document text, or "enhancement" for a proposed addition of functionality
> (such as an additional requirement).
> b. The Priority: field is set based on the severity of the Issue. For
> example, editorial issues are typically "minor" or "trivial".
> c. The Milestone: field should be set to milestone1 (useless, I know).
> d. The Component: field should be set to the document you are filing the
> issue on.
> e. The Version: field should be set to "1.0".
> f. The Severity: field should be set to based on the status of the document
> (e.g. "In WG Last Call" for a document in IAB last call)
> g. The Keywords: and CC: fields can be left blank unless inspiration seizes
> you.
> h. The Assign To: field is generally filled in with the email address of the
> editor.
>
> 5. Typically it won't be necessary to enclose a file with the ticket, but if
> you need to, select "I have files to attach to this ticket".
>
> 6. If you want to preview your Issue, click on the "Preview" button. When
> you're ready to submit the issue, click on the "Create Ticket" button.
>
> 7. If you want to update an issue, go to the "View Tickets" page:
> http://trac.tools.ietf.org/wg/iab/trac/report/1
>
> Click on the ticket number you want to update, and then modify the ticket
> fields as required.
>
>

From peter@akayla.com  Sun Jul  7 20:21:44 2013
Return-Path: <peter@akayla.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B768C21F9DE6; Sun,  7 Jul 2013 20:21:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.949
X-Spam-Level: 
X-Spam-Status: No, score=-1.949 tagged_above=-999 required=5 tests=[AWL=0.650,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g+CcFJkQMRwp; Sun,  7 Jul 2013 20:21:40 -0700 (PDT)
Received: from p3plsmtpa11-03.prod.phx3.secureserver.net (p3plsmtpa11-03.prod.phx3.secureserver.net [68.178.252.104]) by ietfa.amsl.com (Postfix) with ESMTP id AE01821F8D0D; Sun,  7 Jul 2013 20:21:39 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by p3plsmtpa11-03.prod.phx3.secureserver.net with  id xfMd1l0011huGat01fMdwi; Sun, 07 Jul 2013 20:21:38 -0700
From: "Peter Yee" <peter@akayla.com>
To: <draft-jabley-dnsext-eui48-eui64-rrtypes.all@tools.ietf.org>
Subject: Gen-ART LC review of draft-jabley-dnsext-eui48-eui64-rrtypes-05
Date: Sun, 7 Jul 2013 20:21:36 -0700
Message-ID: <02fe01ce7b8a$41f2af50$c5d80df0$@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: Ac57iWpUND76SWuaRiWlOdeUt9Gl4g==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Jul 2013 03:21:44 -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-jabley-dnsext-eui48-eui64-rrtypes-05
Reviewer: Peter Yee
Review Date: July-07-2013
IETF LC End Date: July-17-2013
IESG Telechat date: August-15-2013

Summary: This draft is basically ready for publication as an Informational
RFC, but has nits that should be fixed before publication. [Ready with nits]

This draft defines DNS Resources Record Types for encoding IEEE 802 EUI-48
and EUI-64 addresses.  Potential privacy issues with this scheme have been
soundly beaten to death with extreme prejudice.

Major issues:

Minor issues:

Nits:

Page 1, Abstract, 1st paragraph: After "e.g.", append a comma and delete an
extraneous space before "Ethernet".

Page 3, Introduction, 1st paragraph, 2nd sentence: change "This" to "These"
and change "specification defines" to "specifications define". 

Page 3, Introduction, 2nd paragraph: append a comma after "e.g.".

		-Peter Yee




From peter@akayla.com  Sun Jul  7 22:39:04 2013
Return-Path: <peter@akayla.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C7E611E8186; Sun,  7 Jul 2013 22:39:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.079
X-Spam-Level: 
X-Spam-Status: No, score=-2.079 tagged_above=-999 required=5 tests=[AWL=0.520,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ab0b1qYJB-0x; Sun,  7 Jul 2013 22:38:59 -0700 (PDT)
Received: from p3plsmtpa09-07.prod.phx3.secureserver.net (p3plsmtpa09-07.prod.phx3.secureserver.net [173.201.193.236]) by ietfa.amsl.com (Postfix) with ESMTP id 426A011E8189; Sun,  7 Jul 2013 22:38:59 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by p3plsmtpa09-07.prod.phx3.secureserver.net with  id xheu1l0041huGat01heuhU; Sun, 07 Jul 2013 22:38:55 -0700
From: "Peter Yee" <peter@akayla.com>
To: <draft-ietf-appsawg-rfc5451bis.all@tools.ietf.org>
Subject: Gen-ART Telechat review of draft-ietf-appsawg-rfc5451bis-09
Date: Sun, 7 Jul 2013 22:38:53 -0700
Message-ID: <030301ce7b9d$6f821100$4e863300$@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: Ac57nWUOX1k3nDvKSfOr8IcedY5lqw==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Jul 2013 05:39:04 -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-appsawg-rfc5451bis-09
Reviewer: Peter Yee
Review Date: July-01-2013
IETF LC End Date: June-27-2013
IESG Telechat date: July-11-2013

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 draft defines a message header for conveying message authentication
outcomes from various, existing email authentication standards.  The draft
is well-written with numerous worked out examples.

Major issues:

Minor issues:

Nits:

Page 4, Introduction, 5th paragraph: append a comma after "published".

Page 5, 2nd paragraph after bullet item, 1st sentence: change "pre-standards
DomainKeys defined" to "pre-standard DomainKeys-defined".

Page 6, 2nd paragraph, last sentence: change "their data center" to "its
data center".

Page 6, section 1.3, 2nd sentence: change "encapsualted" to "encapsulated".

Page 7, section 1.5.2, 1st paragraph after bullet points, 2nd sentence: add
commas after "agents" and "authorization)".  Also change "ensures" to
"ensure".

Page 14, section 2.5, 4th sentence: insert ", but" between "document" and
"intended".

Page 17, Section 2.5.5: amend "Authorhized" to "Authorized".

Page 19, 2nd full paragraph, 2nd sentence: "finite" is probably not the best
word to use here.  Perhaps "not unduly taxing to the DNS infrastructure"
would work better?

Page 19, section 4, title: change "A" to "a".

Page 19, section 4, 1st paragraph, second sentence: change "THe" to "The".

Page 20, 2nd full paragraph, 1st sentence: append a comma after "applied".

Page 20, 5th full paragraph, 3rd sentence: insert "placement" between "This"
and "allows".

Page 20, 5th full paragraph, 3rd sentence: regarding whether the field can
be "trusted": why would the MUA check the field in any other location than
prior to the top-most trace field?  If the location is the source of
trustedness, then the MUA shouldn't be checking it anywhere else, right?

Page 22, first full paragraph, 1st sentence: replace "which" with "that".

Page 22, 3rd full paragraph: "this" is an ambiguous reference.  Maybe use
"these topics" or "these issues" if you mean everything in the section?

Page 23, 1st paragraph, last sentence: for clarity, consider inserting "the
header field originating from" between "removing" and "all".

Page 23, 4th paragraph:  as the MTA (implied to be an MTA within the ADMD)
is not the end consumer of the information and the MUA might understand a
later version of the header, shouldn't the decision to remove (or
essentially ignore) the header be made by the MUA?

Page 31, section 8.4, 2nd sentence: change "need" to "needs".

Page 32, section 8.6, 3rd sentence: regarding keeping the list "current",
how about using a new RRType in the DNS?

Page 39, section C.4: the "Received" header would make it look like the
message is going from example.net to example.com, but the "To" and "From"
headers show the opposite to be the case.

Page 39, section C.4: the same issue strikes the paragraph immediately
following Example 4.  The "sending DNS" name is what appears for the
authserv-id, not the "receiving DNS" name.  A simple swap of the "To" and
"From" header values would rectify the situation.

Page 43, 2nd paragraph, 2nd sentence: change "that" to "whom".

Page 44, item 1, 2nd sentence: delete the "s" in "rejections".

Page 44, item 3, 1st sentence: append a comma after "header".

Page 45, item 5, 3rd sentence: change "vs" to "vs."  and append a comma
after "intertia".

		-Peter Yee


From superuser@gmail.com  Mon Jul  8 00:13:41 2013
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CAC6211E81A0; Mon,  8 Jul 2013 00:13:40 -0700 (PDT)
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=[AWL=0.000,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mkNGWYoQ+h3P; Mon,  8 Jul 2013 00:13:39 -0700 (PDT)
Received: from mail-wi0-x22e.google.com (mail-wi0-x22e.google.com [IPv6:2a00:1450:400c:c05::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 5F26211E8190; Mon,  8 Jul 2013 00:13:25 -0700 (PDT)
Received: by mail-wi0-f174.google.com with SMTP id k10so8693106wiv.1 for <multiple recipients>; Mon, 08 Jul 2013 00:13:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ZcE4bJTzebcoiwEnzGGJbNUKkOpj+7W7H1+EBVJJ6g0=; b=wJGWX9MZe/jq/yRx0sOU6PGTHg/cApHByCbCNKPa6c4rKb2/InqbKluO5rN8WO+0AX L2uVGcXX/Ww+HzLzwZapzU21smF+XSvf740RhypiNncsQvHohVdLAMXdtnH3nhwZl7cq ZyyVnO67Cy7wEbeYAN58t0WBtLZDFRhrI5UrmipeGQHQcmK1SqW3NGovy3jMzLIOGtU6 ltMkNTvCVQiR2LJD07mrsfQuDnf7+1oUkpu24yVR0kjFF56f7xyqjRiUnK30yzcLXl2s V4pZmuZfMoY/77HtEBRK9Ffjh0fd/PWoiVwyV7zA+bV7nWQQt2pd0n1kLQckuHBiE04U 2nHg==
MIME-Version: 1.0
X-Received: by 10.194.239.225 with SMTP id vv1mr11458954wjc.63.1373267603336;  Mon, 08 Jul 2013 00:13:23 -0700 (PDT)
Received: by 10.180.90.16 with HTTP; Mon, 8 Jul 2013 00:13:23 -0700 (PDT)
In-Reply-To: <030301ce7b9d$6f821100$4e863300$@akayla.com>
References: <030301ce7b9d$6f821100$4e863300$@akayla.com>
Date: Mon, 8 Jul 2013 00:13:23 -0700
Message-ID: <CAL0qLwbaGGJ_indZfn4QZjLoRwNyQw4K5DB0QN3L4Ju0L_oAMQ@mail.gmail.com>
Subject: Re: Gen-ART Telechat review of draft-ietf-appsawg-rfc5451bis-09
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Peter Yee <peter@akayla.com>
Content-Type: multipart/alternative; boundary=089e01493384adb7d504e0fac7f3
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-appsawg-rfc5451bis.all@tools.ietf.org, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Jul 2013 07:13:41 -0000

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

Hi Peter, thanks for the review.  Comments inline:

On Sun, Jul 7, 2013 at 10:38 PM, Peter Yee <peter@akayla.com> wrote:

> Page 5, 2nd paragraph after bullet item, 1st sentence: change
> "pre-standards
> DomainKeys defined" to "pre-standard DomainKeys-defined".
>

This doesn't seem to work.  The sentence is basically "SPF defined X and
DomainKeys defined Y."  "defined" is a verb, not an adjective, so I don't
think the hyphen is appropriate.


>
> Page 20, 5th full paragraph, 3rd sentence: regarding whether the field can
> be "trusted": why would the MUA check the field in any other location than
> prior to the top-most trace field?  If the location is the source of
> trustedness, then the MUA shouldn't be checking it anywhere else, right?
>

At the time the work on RFC5451 was originally done, here were some
implementations of a plugin API that were not able to prepend trace header
fields, and could only append them.  Moreover, an MUA or other agent might
be configured to trust A-R fields added in more than one place (e.g., a
trusted filter), so trusting only the top-most one would limit that
possibility.


>
> Page 23, 4th paragraph:  as the MTA (implied to be an MTA within the ADMD)
> is not the end consumer of the information and the MUA might understand a
> later version of the header, shouldn't the decision to remove (or
> essentially ignore) the header be made by the MUA?
>

Good point.  I'll add a note about this.


>
> Page 32, section 8.6, 3rd sentence: regarding keeping the list "current",
> how about using a new RRType in the DNS?
>

That's certainly one option to solve that problem. However, I'd prefer not
to suggest new mechanisms that haven't been deployed yet.

I'll post the rest in a -10 revision after the telechat, or if directed to
do so sooner.

Thanks again,
-MSK

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

<div dir=3D"ltr">Hi Peter, thanks for the review.=A0 Comments inline:<br><d=
iv class=3D"gmail_extra"><br>On Sun, Jul 7, 2013 at 10:38 PM, Peter Yee <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:peter@akayla.com" target=3D"_blank">pe=
ter@akayla.com</a>&gt;</span> wrote:<br>
<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">Page 5, 2nd parag=
raph after bullet item, 1st sentence: change &quot;pre-standards<br>
DomainKeys defined&quot; to &quot;pre-standard DomainKeys-defined&quot;.<br=
></blockquote><div><br></div><div>This doesn&#39;t seem to work.=A0 The sen=
tence is basically &quot;SPF defined X and DomainKeys defined Y.&quot;=A0 &=
quot;defined&quot; is a verb, not an adjective, so I don&#39;t think the hy=
phen is appropriate.<br>
=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex">
<br>
Page 20, 5th full paragraph, 3rd sentence: regarding whether the field can<=
br>
be &quot;trusted&quot;: why would the MUA check the field in any other loca=
tion than<br>
prior to the top-most trace field? =A0If the location is the source of<br>
trustedness, then the MUA shouldn&#39;t be checking it anywhere else, right=
?<br></blockquote><div><br></div><div>At the time the work on RFC5451 was o=
riginally done, here were some implementations of a plugin API that were no=
t able to prepend trace header fields, and could only append them.=A0 Moreo=
ver, an MUA or other agent might be configured to trust A-R fields added in=
 more than one place (e.g., a trusted filter), so trusting only the top-mos=
t one would limit that possibility.<br>
=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex">
<br>
Page 23, 4th paragraph: =A0as the MTA (implied to be an MTA within the ADMD=
)<br>
is not the end consumer of the information and the MUA might understand a<b=
r>
later version of the header, shouldn&#39;t the decision to remove (or<br>
essentially ignore) the header be made by the MUA?<br></blockquote><div><br=
></div><div>Good point.=A0 I&#39;ll add a note about this.<br>=A0<br></div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">

<br>
Page 32, section 8.6, 3rd sentence: regarding keeping the list &quot;curren=
t&quot;,<br>
how about using a new RRType in the DNS?<br></blockquote><div><br></div><di=
v>That&#39;s certainly one option to solve that problem. However, I&#39;d p=
refer not to suggest new mechanisms that haven&#39;t been deployed yet. <br=
>
<br></div><div>I&#39;ll post the rest in a -10 revision after the telechat,=
 or if directed to do so sooner.<br><br></div><div>Thanks again,<br></div><=
div>-MSK<br></div></div></div></div>

--089e01493384adb7d504e0fac7f3--

From peter@akayla.com  Mon Jul  8 00:22:09 2013
Return-Path: <peter@akayla.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 058D811E81A9; Mon,  8 Jul 2013 00:22:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.165
X-Spam-Level: 
X-Spam-Status: No, score=-2.165 tagged_above=-999 required=5 tests=[AWL=0.433,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2ZsZUeR-O73O; Mon,  8 Jul 2013 00:22:03 -0700 (PDT)
Received: from p3plsmtpa11-09.prod.phx3.secureserver.net (p3plsmtpa11-09.prod.phx3.secureserver.net [68.178.252.110]) by ietfa.amsl.com (Postfix) with ESMTP id E7DC611E81AB; Mon,  8 Jul 2013 00:21:49 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by p3plsmtpa11-09.prod.phx3.secureserver.net with  id xjMi1l0081huGat01jMiqJ; Mon, 08 Jul 2013 00:21:44 -0700
From: "Peter Yee" <peter@akayla.com>
To: "'Murray S. Kucherawy'" <superuser@gmail.com>
References: <030301ce7b9d$6f821100$4e863300$@akayla.com> <CAL0qLwbaGGJ_indZfn4QZjLoRwNyQw4K5DB0QN3L4Ju0L_oAMQ@mail.gmail.com>
In-Reply-To: <CAL0qLwbaGGJ_indZfn4QZjLoRwNyQw4K5DB0QN3L4Ju0L_oAMQ@mail.gmail.com>
Subject: RE: Gen-ART Telechat review of draft-ietf-appsawg-rfc5451bis-09
Date: Mon, 8 Jul 2013 00:21:42 -0700
Message-ID: <030801ce7bab$cca088e0$65e19aa0$@akayla.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0309_01CE7B71.2042C250"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFQvfcxhikEpypLQc81LDoJCpyLfwHKw+5rmkeDluA=
Content-Language: en-us
Cc: 'General Area Review Team' <gen-art@ietf.org>, draft-ietf-appsawg-rfc5451bis.all@tools.ietf.org, 'ietf' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Jul 2013 07:22:09 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0309_01CE7B71.2042C250
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Murray,

                Quick response!  My replies are found below.

 

                Thanks.

 

                                -Peter

 

From: Murray S. Kucherawy [mailto:superuser@gmail.com] 
Sent: Monday, July 08, 2013 12:13 AM
To: Peter Yee
Cc: draft-ietf-appsawg-rfc5451bis.all@tools.ietf.org; General Area Review
Team; ietf
Subject: Re: Gen-ART Telechat review of draft-ietf-appsawg-rfc5451bis-09

 

Hi Peter, thanks for the review.  Comments inline:


On Sun, Jul 7, 2013 at 10:38 PM, Peter Yee <peter@akayla.com> wrote:

Page 5, 2nd paragraph after bullet item, 1st sentence: change "pre-standards
DomainKeys defined" to "pre-standard DomainKeys-defined".

 

This doesn't seem to work.  The sentence is basically "SPF defined X and
DomainKeys defined Y."  "defined" is a verb, not an adjective, so I don't
think the hyphen is appropriate.

 

Hmm.  Yup, I misread that.  Just ignore the hyphen part of the comment.
 

Page 20, 5th full paragraph, 3rd sentence: regarding whether the field can
be "trusted": why would the MUA check the field in any other location than
prior to the top-most trace field?  If the location is the source of
trustedness, then the MUA shouldn't be checking it anywhere else, right?

 

Page 32, section 8.6, 3rd sentence: regarding keeping the list "current",
how about using a new RRType in the DNS?

 

That's certainly one option to solve that problem. However, I'd prefer not
to suggest new mechanisms that haven't been deployed yet. 

Fair enough.

I'll post the rest in a -10 revision after the telechat, or if directed to
do so sooner.

Thanks again,

-MSK


------=_NextPart_000_0309_01CE7B71.2042C250
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 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=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Murray,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; Quick response! &nbsp;My replies are found =
below.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; Thanks.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
-Peter<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Murray S. Kucherawy [mailto:superuser@gmail.com] <br><b>Sent:</b> =
Monday, July 08, 2013 12:13 AM<br><b>To:</b> Peter Yee<br><b>Cc:</b> =
draft-ietf-appsawg-rfc5451bis.all@tools.ietf.org; General Area Review =
Team; ietf<br><b>Subject:</b> Re: Gen-ART Telechat review of =
draft-ietf-appsawg-rfc5451bis-09<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>Hi =
Peter, thanks for the review.&nbsp; Comments =
inline:<o:p></o:p></p><div><p class=3DMsoNormal><br>On Sun, Jul 7, 2013 =
at 10:38 PM, Peter Yee &lt;<a href=3D"mailto:peter@akayla.com" =
target=3D"_blank">peter@akayla.com</a>&gt; =
wrote:<o:p></o:p></p><div><blockquote =
style=3D'border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in =
6.0pt;margin-left:4.8pt;margin-right:0in'><p class=3DMsoNormal>Page 5, =
2nd paragraph after bullet item, 1st sentence: change =
&quot;pre-standards<br>DomainKeys defined&quot; to &quot;pre-standard =
DomainKeys-defined&quot;.<o:p></o:p></p></blockquote><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>This doesn't seem to work.&nbsp; The sentence is =
basically &quot;SPF defined X and DomainKeys defined Y.&quot;&nbsp; =
&quot;defined&quot; is a verb, not an adjective, so I don't think the =
hyphen is appropriate.<span =
style=3D'color:#1F497D'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Hmm.&nbsp; Yup, I misread that.&nbsp; Just ignore the hyphen part of =
the comment.</span><br>&nbsp;<o:p></o:p></p></div><blockquote =
style=3D'border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in =
6.0pt;margin-left:4.8pt;margin-right:0in'><p class=3DMsoNormal>Page 20, =
5th full paragraph, 3rd sentence: regarding whether the field can<br>be =
&quot;trusted&quot;: why would the MUA check the field in any other =
location than<br>prior to the top-most trace field? &nbsp;If the =
location is the source of<br>trustedness, then the MUA shouldn't be =
checking it anywhere else, right?<o:p></o:p></p></blockquote><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><blockquote =
style=3D'border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in =
6.0pt;margin-left:4.8pt;margin-right:0in'><p class=3DMsoNormal>Page 32, =
section 8.6, 3rd sentence: regarding keeping the list =
&quot;current&quot;,<br>how about using a new RRType in the =
DNS?<o:p></o:p></p></blockquote><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'>That's certainly one option to solve that =
problem. However, I'd prefer not to suggest new mechanisms that haven't =
been deployed yet. <o:p></o:p></p><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Fair enough.<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'>I'll post the rest in a -10 revision =
after the telechat, or if directed to do so =
sooner.<o:p></o:p></p></div><div><p class=3DMsoNormal>Thanks =
again,<o:p></o:p></p></div><div><p =
class=3DMsoNormal>-MSK<o:p></o:p></p></div></div></div></div></div></body=
></html>
------=_NextPart_000_0309_01CE7B71.2042C250--


From l.wood@surrey.ac.uk  Mon Jul  8 00:39:43 2013
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7EFD321F8BC0 for <ietf@ietfa.amsl.com>; Mon,  8 Jul 2013 00:39:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.66
X-Spam-Level: 
X-Spam-Status: No, score=-2.66 tagged_above=-999 required=5 tests=[AWL=-1.230,  BAYES_00=-2.599, J_CHICKENPOX_21=0.6, J_CHICKENPOX_32=0.6, J_CHICKENPOX_45=0.6, RCVD_IN_DNSWL_LOW=-1, UNPARSEABLE_RELAY=0.001, URI_HEX=0.368]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DdWlNbm7Ynq7 for <ietf@ietfa.amsl.com>; Mon,  8 Jul 2013 00:39:37 -0700 (PDT)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.161]) by ietfa.amsl.com (Postfix) with ESMTP id 8C92D21F8C4C for <ietf@ietf.org>; Mon,  8 Jul 2013 00:39:35 -0700 (PDT)
Received: from [195.245.230.131:40796] by server-1.bemta-3.messagelabs.com id 07/DA-01921-5BC6AD15; Mon, 08 Jul 2013 07:39:33 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-9.tower-78.messagelabs.com!1373269172!23899893!1
X-Originating-IP: [131.227.200.35]
X-StarScan-Received: 
X-StarScan-Version: 6.9.9; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 604 invoked from network); 8 Jul 2013 07:39:33 -0000
Received: from exht021p.surrey.ac.uk (HELO EXHT021P.surrey.ac.uk) (131.227.200.35) by server-9.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 8 Jul 2013 07:39:33 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT021P.surrey.ac.uk ([131.227.200.35]) with mapi; Mon, 8 Jul 2013 08:39:32 +0100
From: <l.wood@surrey.ac.uk>
To: <ietf@ietf.org>, <noncom-chair-2013@ietf.org>
Date: Mon, 8 Jul 2013 08:38:16 +0100
Subject: RE: Final Announcement of Qualified Volunteers
Thread-Topic: Final Announcement of Qualified Volunteers
Thread-Index: Ac56k3eMACmjfPaISkGziW3QAHNMiwBGqSto
Message-ID: <290E20B455C66743BE178C5C84F12408223F494EE8@EXMB01CMS.surrey.ac.uk>
References: <20130706215330.8850.38261.idtracker@ietfa.amsl.com>
In-Reply-To: <20130706215330.8850.38261.idtracker@ietfa.amsl.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="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Jul 2013 07:39:43 -0000

RW1haWwgdG8gbm9uY29tLWNoYWlyLTIwMTNAaWV0Zi5vcmcgYXBwZWFycyB0byBmYWlsIC0gYm91
bmNlIGJlbG93Lg0KDQpJZiBBbGxpc29uIGhhc24ndCByZWNlaXZlZCBhbnkgZmVlZGJhY2ssIHRo
YXQncyB3aHkuDQoNCkxsb3lkIFdvb2QNCmh0dHA6Ly9zYXQtbmV0LmNvbS9MLldvb2QvDQoNCg0K
DQpEZWxpdmVyeSBoYXMgZmFpbGVkIHRvIHRoZXNlIHJlY2lwaWVudHMgb3IgZGlzdHJpYnV0aW9u
IGxpc3RzOg0KDQpub25jb20tY2hhaXItMjAxM0BpZXRmLm9yZw0KVGhlIHJlY2lwaWVudCdzIGUt
bWFpbCBhZGRyZXNzIHdhcyBub3QgZm91bmQgaW4gdGhlIHJlY2lwaWVudCdzIGUtbWFpbCBzeXN0
ZW0uIE1pY3Jvc29mdCBFeGNoYW5nZSB3aWxsIG5vdCB0cnkgdG8gcmVkZWxpdmVyIHRoaXMgbWVz
c2FnZSBmb3IgeW91LiBQbGVhc2UgY2hlY2sgdGhlIGUtbWFpbCBhZGRyZXNzIGFuZCB0cnkgcmVz
ZW5kaW5nIHRoaXMgbWVzc2FnZSwgb3IgcHJvdmlkZSB0aGUgZm9sbG93aW5nIGRpYWdub3N0aWMg
dGV4dCB0byB5b3VyIHN5c3RlbSBhZG1pbmlzdHJhdG9yLg0KDQpUaGUgZm9sbG93aW5nIG9yZ2Fu
aXphdGlvbiByZWplY3RlZCB5b3VyIG1lc3NhZ2U6IG1haWwuaWV0Zi5vcmcuDQoNCg0KDQoNCg0K
DQpEaWFnbm9zdGljIGluZm9ybWF0aW9uIGZvciBhZG1pbmlzdHJhdG9yczoNCg0KR2VuZXJhdGlu
ZyBzZXJ2ZXI6IHNlcnZlci03LmJlbXRhLTUubWVzc2FnZWxhYnMuY29tDQoNCm5vbmNvbS1jaGFp
ci0yMDEzQGlldGYub3JnDQptYWlsLmlldGYub3JnICM8bWFpbC5pZXRmLm9yZyAjNS4xLjEgc210
cDsgNTUwIDUuMS4xIDxub25jb20tY2hhaXItMjAxM0BpZXRmLm9yZz46IFJlY2lwaWVudCBhZGRy
ZXNzIHJlamVjdGVkOiBVc2VyIHVua25vd24gaW4gdmlydHVhbCBhbGlhcyB0YWJsZT4gI1NNVFAj
DQoNCk9yaWdpbmFsIG1lc3NhZ2UgaGVhZGVyczoNCg0KUmV0dXJuLVBhdGg6IDxsLndvb2RAc3Vy
cmV5LmFjLnVrPg0KUmVjZWl2ZWQ6IGZyb20gWzg1LjE1OC4xMzYuNTE6Mzg5MjZdIGJ5IHNlcnZl
ci03LmJlbXRhLTUubWVzc2FnZWxhYnMuY29tIGlkIEQ1LzhCLTIxMDAyLTY5NDk4RDE1OyBTYXQs
IDA2IEp1bCAyMDEzIDIyOjA1OjEwICswMDAwDQpYLUVudi1TZW5kZXI6IGwud29vZEBzdXJyZXku
YWMudWsNClgtTXNnLVJlZjogc2VydmVyLTYudG93ZXItNDkubWVzc2FnZWxhYnMuY29tITEzNzMx
NDgzMDkhMjM2MDk2NDQhMg0KWC1PcmlnaW5hdGluZy1JUDogWzEzMS4yMjcuMjAwLjQzXQ0KWC1T
dGFyU2Nhbi1SZWNlaXZlZDoNClgtU3RhclNjYW4tVmVyc2lvbjogNi45Ljk7IGJhbm5lcnM9LSwt
LC0NClgtVmlydXNDaGVja2VkOiBDaGVja2VkDQpSZWNlaXZlZDogKHFtYWlsIDIyODcgaW52b2tl
ZCBmcm9tIG5ldHdvcmspOyA2IEp1bCAyMDEzIDIyOjA1OjEwIC0wMDAwDQpSZWNlaXZlZDogZnJv
bSBleGh0MDIycC5zdXJyZXkuYWMudWsgKEhFTE8gRVhIVDAyMlAuc3VycmV5LmFjLnVrKSAoMTMx
LjIyNy4yMDAuNDMpDQogIGJ5IHNlcnZlci02LnRvd2VyLTQ5Lm1lc3NhZ2VsYWJzLmNvbSB3aXRo
IEFFUzEyOC1TSEEgZW5jcnlwdGVkIFNNVFA7IDYgSnVsIDIwMTMgMjI6MDU6MTAgLTAwMDANClJl
Y2VpdmVkOiBmcm9tIEVYTUIwMUNNUy5zdXJyZXkuYWMudWsgKFsxNjkuMjU0LjEuMTgwXSkgYnkN
CiBFWEhUMDIyUC5zdXJyZXkuYWMudWsgKFsxMzEuMjI3LjIwMC40M10pIHdpdGggbWFwaTsgU2F0
LCA2IEp1bCAyMDEzIDIzOjA1OjEwDQogKzAxMDANCkZyb206IDxsLndvb2RAc3VycmV5LmFjLnVr
Pg0KVG86IDxub25jb20tY2hhaXItMjAxM0BpZXRmLm9yZz4NCkRhdGU6IFNhdCwgNiBKdWwgMjAx
MyAyMzowNTowOCArMDEwMA0KU3ViamVjdDogUkU6IEZpbmFsIEFubm91bmNlbWVudCBvZiBRdWFs
aWZpZWQgVm9sdW50ZWVycw0KVGhyZWFkLVRvcGljOiBGaW5hbCBBbm5vdW5jZW1lbnQgb2YgUXVh
bGlmaWVkIFZvbHVudGVlcnMNClRocmVhZC1JbmRleDogQWM1NmszZU1BQ21qZlBhSVNrR3ppVzNR
QUhOTWl3QUFIUkdRDQpNZXNzYWdlLUlEOiA8MjkwRTIwQjQ1NUM2Njc0M0JFMTc4QzVDODRGMTI0
MDgyMjNGNDk0RUUyQEVYTUIwMUNNUy5zdXJyZXkuYWMudWs+DQpSZWZlcmVuY2VzOiA8MjAxMzA3
MDYyMTUzMzAuODg1MC4zODI2MS5pZHRyYWNrZXJAaWV0ZmEuYW1zbC5jb20+DQpJbi1SZXBseS1U
bzogPDIwMTMwNzA2MjE1MzMwLjg4NTAuMzgyNjEuaWR0cmFja2VyQGlldGZhLmFtc2wuY29tPg0K
QWNjZXB0LUxhbmd1YWdlOiBlbi1VUywgZW4tR0INCkNvbnRlbnQtTGFuZ3VhZ2U6IGVuLUdCDQpY
LU1TLUhhcy1BdHRhY2g6DQpYLU1TLVRORUYtQ29ycmVsYXRvcjoNCmFjY2VwdGxhbmd1YWdlOiBl
bi1VUywgZW4tR0INCkNvbnRlbnQtVHlwZTogdGV4dC9wbGFpbjsgY2hhcnNldD0idXRmLTgiDQpD
b250ZW50LVRyYW5zZmVyLUVuY29kaW5nOiBiYXNlNjQNCk1JTUUtVmVyc2lvbjogMS4wDQoNCg0K
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KRnJvbTogaWV0Zi1hbm5v
dW5jZS1ib3VuY2VzQGlldGYub3JnIFtpZXRmLWFubm91bmNlLWJvdW5jZXNAaWV0Zi5vcmddIE9u
IEJlaGFsZiBPZiBOb21Db20gQ2hhaXIgMjAxMyBbbm9tY29tLWNoYWlyLTIwMTNAaWV0Zi5vcmdd
DQpTZW50OiAwNiBKdWx5IDIwMTMgMjI6NTMNClRvOiBJRVRGIEFubm91bmNlbWVudCBMaXN0DQpT
dWJqZWN0OiBGaW5hbCBBbm5vdW5jZW1lbnQgb2YgUXVhbGlmaWVkIFZvbHVudGVlcnMNCg0KSSBh
bSBwbGVhc2VkIHRvIGFubm91bmNlIHRoYXQgd2UgaGF2ZSAxNDAgcXVhbGlmaWVkIGluZGl2aWR1
YWxzIHdobw0KaGF2ZSBnZW5lcm91c2x5IHZvbHVudGVlcmVkIHRvIHNlcnZlIGFzIHZvdGluZyBt
ZW1iZXJzIG9mIHRoaXMgeWVhcidzDQpOb21jb20uDQoNClBsZWFzZSB0YWtlIGEgbG9vayBhbmQg
Z2V0IGluIHRvdWNoIGJlZm9yZSBKdWx5IDEzIGlmIHlvdSB0aGluayB5b3VyDQpuYW1lIHNob3Vs
ZCBiZSBoZXJlIGFuZCBpdCBpc24ndCAob3IgcG9zc2libHkgSSd2ZSBtaXMtdHlwZWQgaXQuLi4p
LCBvcg0KaWYgeW91IGhhdmUgYW55IG90aGVyIHF1ZXN0aW9ucy4NCg0KQWxsaXNvbiBNYW5raW4N
CjIwMTMtMTQgTm9tY29tIENoYWlyDQpub21jb20tY2hhaXItMjAxM0BpZXRmLm9yZw0KDQotLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQowMDEgSm9obiBTY3VkZGVyLCBK
dW5pcGVyDQowMDIgU3RlcGhlbiBIYW5uYSwgSnVuaXBlcg0KMDAzIFdhc3NpbSBIYWRkYWQsIEVy
aWNzc29uDQowMDQgUnVzcyBXaGl0ZSwgVlRFDQowMDUgU3RlcGhhbiBXZW5nZXIsIFZpZHlvDQow
MDYgWkhBTyBZaSwgSHVhd2VpDQowMDcgRXJpYyBHcmF5LCBFcmljc3Nvbg0KMDA4IFN0ZXZlIEtl
bnQsIEJCTg0KMDA5IFRvZXJsZXNzIEVja2VydCwgQ2lzY28NCjAxMCBBbGlhIEF0bGFzLCBKdW5p
cGVyDQowMTEgVmljdG9yIEt1YXJzaW5naCwgUm9nZXJzDQowMTIgWWl6aG91IExJLCBIdWF3ZWkN
CjAxMyBHb256YWxvIFNhbGd1ZWlybywgQ2lzY28NCjAxNCBHYW5nIENIRU4sIENoaW5hIE1vYmls
ZQ0KMDE1IE5pbmcgS09ORyxDTk5JQw0KMDE2IE1hcmNlbG8gQmFnbnVsbywgVUMzTQ0KMDE3IFNI
RU4gU2h1byDmsojng4EgKFNlYW4pLCBDTk5JQw0KMDE4IEZlcm5hbmRvIEdvbnQsIFNJNiBOZXR3
b3Jrcw0KMDE5IEdsZW4gWm9ybiwgTmV0d29yayBaZW4NCjAyMCBSZWluYWxkbyBQZW5ubywgQ2lz
Y28NCjAyMSBLbGFhcyBXaWVyZW5nYSwgQ2lzY28NCjAyMiBQYXNjYWwgVGh1YmVydCwgQ2lzY28N
CjAyMyBNZWhtZXQgRXJzdWUsIE5va2lhIFNpZW1lbnMNCjAyNCBPbGUgVHJvYW4sIENpc2NvDQow
MjUgSm91bmkgS29yaG9uZW4sIFJlbmVzYXMgTW9iaWxlDQowMjYgR2lsZXMgSGVyb24sIENpc2Nv
DQowMjcgR3VudGVyIFZhbiBkZSBWZWxkZSwgQ2lzY28NCjAyOCBBcnR1cm8gU2VydmluLCBMQUNO
SUMNCjAyOSBFcmljIFZ5bmNrZSwgQ2lzY28NCjAzMCBDdWxsZW4gSmVubmluZ3MsIENpc2NvDQow
MzEgVGluYSBUc291LCBIdWF3ZWkNCjAzMiBEaHJ1diBEaG9keSwgSHVhd2VpDQowMzMgSG9uZ3l1
IExJIChKdWxpbyksIEh1YXdlaQ0KMDM0IFNjb3R0IE1hbnNmaWVsZCwgRXJpY3Nzb24NCjAzNSBK
b2huIERyYWtlLCBKdW5pcGVyDQowMzYgQW5kcmV3IE1jTGFjaGxhbiwgQ2lzY28NCjAzNyBEZXJl
ayBBdGtpbnMsIE1vY2FuYQ0KMDM4IFN1aGFzIE5hbmRha3VtYXIsIENpc2NvDQowMzkgRXJpYyBS
ZXNjb3JsYSwgUlRGTQ0KMDQwIEthcmVuIFNlbywgQkJODQowNDEgU3RpZyBWZW5hYXMsIENpc2Nv
DQowNDIgU3RhbiBSYXRsaWZmLCBDaXNjbw0KMDQzIElnbmFzIEJhZ2RvbmFzLCBDaXNjbw0KMDQ0
IFBldGVyIFllZSwgQUtBWUxBDQowNDUgRG9uYWxkIEVhc3RsYWtlLCBIdWF3ZWkNCjA0NiBaSE9V
IFFpYW4gKENhdGh5KSwgSHVhd2VpDQowNDcgU2FtIEhhcnRtYW4sIFBhaW5sZXNzIFNlY3VyaXR5
DQowNDggTGl4aWEgWmhhbmcsIFVDTEENCjA0OSBUZWVtdSBTYXZvbGFpbmVuLCBOb2tpYQ0KMDUw
IEFsdmFybyBSZXRhbmEsIENpc2NvDQowNTEgVGVycnkgTWFuZGVyc29uLCBJQ0FOTg0KMDUyIEJp
bGwgVmVyU3RlZWcsIENpc2NvDQowNTMgTWVsaW5kYSBTaG9yZSwgTm8gTW91bnRhaW4NCjA1NCBJ
SnNicmFuZCBXaWpuYW5kcywgQ2lzY28NCjA1NSBLYXJlbiBPJ0Rvbm9naHVlLCBJU09DDQowNTYg
QmVuc29uIFNjaGxpZXNzZXIsIEp1bmlwZXINCjA1NyBBcmkgS2Vyw6RuZW4sIEVyaWNzc29uDQow
NTggRmFuZ3dlaSBIVSwgWlRFDQowNTkgTWFjaCBDSEVOLCBIdWF3ZWkNCjA2MCBIdWkgRGVuZywg
Q2hpbmEgTW9iaWxlDQowNjEgTElVIERhcGVuZywgQ2hpbmEgTW9iaWxlDQowNjIgSmFhcCBBa2tl
cmh1aXMsIE5MTkVUIExhYnMNCjA2MyBNYWdudXMgV2VzdGVybHVuZCwgRXJpY3Nzb24NCjA2NCBa
ZWhuIENBTywgQ2hpbmEgTW9iaWxlDQowNjUgWmFoZWR1enphbWFuIFNhcmtlciwgRXJpY3Nzb24N
CjA2NiBCaHVtaXAgS2hhc25hYmlzaCwgWlRFIFVTQQ0KMDY3IEFuZHJldyBDaGksIEJCTg0KMDY4
IFRob21hcyBOYWRlYXUsIEp1bmlwZXINCjA2OSBTdGV2ZW4gQyAoQ3JhaWcpIFdoaXRlLCBBbGNh
dGVsLUx1Y2VudA0KMDcwIE9yaXQgTGV2aW4sIE1pY3Jvc29mdA0KMDcxIFNhbSBBbGRyaW4sIEh1
YXdlaQ0KMDcyIFBhdWwgRWJlcnNtYW4sIEluZm9ibG94DQowNzMgQ2hyaXN0b3BoZXIgTGlsamVu
c3RvbHBlLCBCaWdTd2l0Y2gNCjA3NCBVbWEgQ2h1bmR1cmksIEVyaWNzc29uDQowNzUgU3VyZXNo
IEtyaXNobmFuLCBFcmljc3Nvbg0KMDc2IFZhcnVuIFNpbmdoLCBBYWx0byBVbml2ZXJzaXR5DQow
NzcgUm9uIEJvbmljYSwgSnVuaXBlcg0KMDc4IEJpbGwgKFdpbGxpYW0pIE1hbm5pbmcsIElTSQ0K
MDc5IFJhZGlhIFBlcmxtYW4sIEludGVsDQowODAgRGFuaWVsZSBDZWNjYXJlbGxpLCBFcmljc3Nv
bg0KMDgxIERlYm9yYWggQnJ1bmdhcmQsIEFUJlQNCjA4MiBLb3N0YXMgUGVudGlrb3VzaXMsIEh1
YXdlaQ0KMDgzIEdyZWdvcnkgTWlyc2t5LCBFcmljc3Nvbg0KMDg0IERhdmUgU2luaWNyb3BlLCBF
cmljc3Nvbg0KMDg1IFRob21hcyBXYWxzaCwgSnVuaXBlcg0KMDg2IFpoYW9odWkgKEplZmZyZXkp
IFpIQU5HLCBKdW5pcGVyDQowODcgWGlhbiBaSEFORywgSHVhd2VpDQowODggTWFyayBUb3duc2xl
eSwgQ2lzY28NCjA4OSBIYW5uZXMgR3JlZGxlciwgSnVuaXBlcg0KMDkwIEJyaWFuIFRyYW1tZWxs
LCBFVEhaDQowOTEgQ2FybG9zIE1hcnRpbmV6LCBMQUNOSUMNCjA5MiBQZXRlciBLb2NoLCBERU5J
QyBlRw0KMDkzIERhbmllbCBNaWdhdWx0LCBGcmFuY2UgVGVsZWNvbSAtIE9yYW5nZQ0KMDk0IFlp
IChBYXJvbikgRGluZywgVW5pdmVyc2l0eSBvZiBIZWxzaW5raQ0KMDk1IE1pY2hhZWwgUmljaGFy
ZHNvbiwgU2FuZGVsbWFuDQowOTYgU29oZWwgS2hhbiwgS2VsbG9nZyBTY2hvb2wgb2YgTWd0DQow
OTcgSm9obiBCcmFkbGV5LCBQaW5nIElkZW50aXR5DQowOTggSHVhaW1vIENoZW4sIEh1YXdlaQ0K
MDk5IE1hdHRoZXcgQ2FtcGFnbmEsIEJsYWNrYmVycnkvUklNL0NlcnRpY29tDQoxMDAgS2VpdGgg
RHJhZ2UsIEFsY2F0ZWwtTHVjZW50DQoxMDEgQ2hyaXMgQm93ZXJzLCBKdW5pcGVyDQoxMDIgSmFr
b2IgSGVpdHosIEVyaWNzc29uDQoxMDMgVG9tb2Z1bWkgT2t1Ym8sIElDQU5ODQoxMDQgRW1pbCBJ
dm92LCBqaXRzaS5vcmcNCjEwNSBUaW1vdGh5IEIuIFRlcnJpYmVycnksIE1vemlsbGENCjEwNiBK
SUFORyBZdWFubG9uZywgSHVhd2VpDQoxMDcgTHVpZ2kgSWFubm9uZSwgVGVsZWNvbSBQYXJpcyBU
ZWNoDQoxMDggRGFtaWVuIFNhdWNleiwgSU5SSUENCjEwOSBMb3UgQmVyZ2VyLCBMYWJOIENvbnN1
bHRpbmcsIExMQw0KMTEwIFlhbmEgU3RhbWNoZXZhLCBqaXRzaS5vcmcNCjExMSBPbmTFmWVqIFN1
csO9LCBOSUMuQ1oNCjExMiBNYXJjaW4gUGlsYXJza2ksIFdhcnNhdyBVbml2IFRlY2hub2xvZ3kg
LyBPcmFuZ2UgUG9sc2thDQoxMTMgTWljaGFlbCBTdEpvaG5zLCBDb25zdWx0YW50L1NpbHZlciBT
cHJpbmcgTmV0d29ya3MNCjExNCBXZXMgR2VvcmdlLCBUaW1lIFdhcm5lciBDYWJsZQ0KMTE1IENo
cmlzdGlhbiBPJ0ZsYWhlcnR5LCBJU09DDQoxMTYgVXdlIFJhdXNjaGVuYmFjaCwgTm9raWEgU2ll
bWVucw0KMTE3IE9sYWZ1ciBHdWRtdW5kc3NvbiwgU2hpbmt1cm8NCjExOCBTaHdldGhhIFN1YnJh
eSBCaGFuZGFyaSwgQ2lzY28NCjExOSBUb2JpYXMgR29uZHJvbSwgT3dhc3ANCjEyMCBDaHJpc3Rl
ciBIb2xtYmVyZywgRXJpY3Nzb24NCjEyMSBTdXNhbiBIYXJlcywgQURBUkENCjEyMiBLaXJhbiBL
dW1hciBDaGl0dGltYW5lbmksIEdvb2dsZQ0KMTIzIERvbmFsZCBGZWR5aywgQWxjYXRlbC1MdWNl
bnQNCjEyNCBTdGVwaGVuIEJvdHprbywgUG9seWNvbQ0KMTI1IExpIFh1ZSwgSHVhd2VpDQoxMjYg
Sm9obiBTYXVlciwgVGVsbGFicw0KMTI3IEpvbiBIdWRzb24sIEJyb2NhZGUNCjEyOCBDaGFybGVz
IEVja2VsLCBDaXNjbw0KMTI5IExpIEtlcGVuZywgSHVhd2VpDQoxMzAgSmFzb24gV2VpbCwgVGlt
ZSBXYXJuZXIgQ2FibGUNCjEzMSBEb3JvdGh5IEdlbGxlcnQsIFNpbHZlciBTcHJpbmcgTmV0d29y
a3MNCjEzMiBGcmVkIEJha2VyLCBDaXNjbw0KMTMzIE1pY2hhZWwgTydSZWlyZGFuLCBDb21jYXN0
DQoxMzQgSmVhbi1NaWNoZWwgQ29tYmVzLCBGcmFuY2UgVGVsZWNvbSAtIE9yYW5nZQ0KMTM1IEpp
bSBHZXR0eXMsIEJlbGwgTGFicyAoQWxjYXRlbC1MdWNlbnQpDQoxMzYgSm9obiBCcnpvem93c2tp
LCBDb21jYXN0DQoxMzcgUmF5IEJlbGxpcywgTm9taW5ldCBVSw0KMTM4IEFkYW0gTW9udHZpbGxl
LCBDZW50ZXIgZm9yIEludGVybmV0IFNlY3VyaXR5DQoxMzkgQmluZyBMaXUsIEh1YXdlaQ0KMTQw
IE1pY2hhbCBLcnNlaywgQ29tcHJpbWF0byBTeXN0ZW1zDQoNCg0K

From l.wood@surrey.ac.uk  Mon Jul  8 00:55:59 2013
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDCE111E81A5 for <ietf@ietfa.amsl.com>; Mon,  8 Jul 2013 00:55:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.121
X-Spam-Level: 
X-Spam-Status: No, score=-3.121 tagged_above=-999 required=5 tests=[AWL=-0.523, BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dc5yt5LCVPW0 for <ietf@ietfa.amsl.com>; Mon,  8 Jul 2013 00:55:55 -0700 (PDT)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.141]) by ietfa.amsl.com (Postfix) with ESMTP id CBE9821F9B90 for <ietf@ietf.org>; Mon,  8 Jul 2013 00:55:50 -0700 (PDT)
Received: from [85.158.136.51:25953] by server-5.bemta-5.messagelabs.com id FF/DD-27868-4807AD15; Mon, 08 Jul 2013 07:55:48 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-15.tower-49.messagelabs.com!1373270148!18914636!1
X-Originating-IP: [131.227.200.43]
X-StarScan-Received: 
X-StarScan-Version: 6.9.9; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 4440 invoked from network); 8 Jul 2013 07:55:48 -0000
Received: from exht022p.surrey.ac.uk (HELO EXHT022P.surrey.ac.uk) (131.227.200.43) by server-15.tower-49.messagelabs.com with AES128-SHA encrypted SMTP; 8 Jul 2013 07:55:48 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT022P.surrey.ac.uk ([131.227.200.43]) with mapi; Mon, 8 Jul 2013 08:55:47 +0100
From: <l.wood@surrey.ac.uk>
To: <l.wood@surrey.ac.uk>, <ietf@ietf.org>, <noncom-chair-2013@ietf.org>
Date: Mon, 8 Jul 2013 08:55:08 +0100
Subject: RE: Final Announcement of Qualified Volunteers
Thread-Topic: Final Announcement of Qualified Volunteers
Thread-Index: Ac56k3eMACmjfPaISkGziW3QAHNMiwBGqStoAACWuDI=
Message-ID: <290E20B455C66743BE178C5C84F12408223F494EE9@EXMB01CMS.surrey.ac.uk>
References: <20130706215330.8850.38261.idtracker@ietfa.amsl.com>, <290E20B455C66743BE178C5C84F12408223F494EE8@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F12408223F494EE8@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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Jul 2013 07:56:00 -0000

Gah. Am idiot misspelling it, sorry.

Lloyd Wood
http://sat-net.com/L.Wood/


________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of l.wood@sur=
rey.ac.uk [l.wood@surrey.ac.uk]
Sent: 08 July 2013 08:38
To: ietf@ietf.org; noncom-chair-2013@ietf.org
Subject: RE: Final Announcement of Qualified Volunteers

Email to noncom-chair-2013@ietf.org appears to fail - bounce below.

From jari.arkko@piuha.net  Mon Jul  8 05:34:56 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EFCC11E81E9 for <ietf@ietfa.amsl.com>; Mon,  8 Jul 2013 05:34:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 51lDvO1hB6Y3 for <ietf@ietfa.amsl.com>; Mon,  8 Jul 2013 05:34:51 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 23F7411E81E3 for <ietf@ietf.org>; Mon,  8 Jul 2013 05:34:51 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 458102CC53; Mon,  8 Jul 2013 15:34:46 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V4z_2AMOsexB; Mon,  8 Jul 2013 15:34:45 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 6AED62CC48; Mon,  8 Jul 2013 15:34:45 +0300 (EEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Appeal Response to Abdussalam Baryun regarding	draft-ietf-manet-nhdp-sec-threats
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <20130703165426.GA6039@cisco.com>
Date: Mon, 8 Jul 2013 14:34:45 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <CBA479E8-B97C-4019-BBE3-E43DC8E15E44@piuha.net>
References: <20130702222442.2467.13086.idtracker@ietfa.amsl.com> <290E20B455C66743BE178C5C84F12408223F494ECC@EXMB01CMS.surrey.ac.uk> <m2mwq4o5pr.wl%randy@psg.com> <95D1F4E7-E98D-4188-A54F-2E705EED6FF9@piuha.net> <20130703165426.GA6039@cisco.com>
To: Toerless Eckert <eckert@cisco.com>
X-Mailer: Apple Mail (2.1508)
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Jul 2013 12:34:56 -0000

Toerless, SM, and others who commented on the importance of recognising =
people who made contributions: I fully agree, of course. Giving credit =
for contributions, be it about being the developer of a major protocol, =
having your name on the author list, or being mentioned in the =
acknowledgments is one of the currencies that help draw people into =
doing work at the IETF. Along with people's need to get an =
internetworking problem solved, of course. And the needs for their =
software to interwork with others. And the needs of their users being =
met=85

Anyway, back to acknowledgments. We should, of course, give credit for =
contributions. I hope we all think about this long and hard when we =
write our documents, and do the right thing. Erring on the side of being =
inclusive is probably a better strategy for most cases.

The issue in this case though was where to draw the line. As an example, =
for my documents, I've mostly used a strategy where I acknowledge the =
significant contributions. I've occasionally used another approach, =
essentially listing everyone who had done any work relating to the =
document, no matter how small. I think either model is defensible, but =
there will always be a question of what contributions meet the criteria =
for being included. Should I acknowledge someone if they post a review =
that said everything is OK? A comment on the mailing list that they =
support this document? A suggestion that did not result in a change in =
the document? A minor editorial fix? A question? An argument? We do not =
have a definition of what kinds of things should result in your name =
being listed in the acknowledgments. And I don't think we should =
formalise that either. It is a better model to have the authors make =
common sense decisions about these matters. And, as with any topic, if =
there is a mistake there are several opportunities to rectify the =
situation if after analysis it seems that a mistake was made. But only =
if it were a clear mistake - I think it would be a bad model if the IESG =
or someone else were to micromanage this. The documents are WG's =
documents and author's documents.

Jari


From communication@edox.com  Mon Jul  8 04:03:27 2013
Return-Path: <communication@edox.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF49E21F9EB3 for <ietf@ietfa.amsl.com>; Mon,  8 Jul 2013 04:03:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.643
X-Spam-Level: ***
X-Spam-Status: No, score=3.643 tagged_above=-999 required=5 tests=[AWL=-0.113,  BAYES_99=3.5, GB_I_LETTER=-2, HTML_IMAGE_RATIO_02=0.383, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, SARE_GIF_ATTACH=1.42, SARE_SUB_ENC_UTF8=0.152]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9Lm0t8lJ2OZ7 for <ietf@ietfa.amsl.com>; Mon,  8 Jul 2013 04:03:23 -0700 (PDT)
Received: from edox.com (mailer2.edox.com [212.94.214.1]) by ietfa.amsl.com (Postfix) with SMTP id 7D6B321F9E78 for <ietf@ietf.org>; Mon,  8 Jul 2013 04:03:21 -0700 (PDT)
From: "EDOX" <communication@edox.com>
To: ietf@ietf.org
Subject: =?utf-8?Q?EDOX=3A_D=C3=A9couvrez_les_nouveaut=C3=A9s_BROTHER?=
Date: Mon, 8 Jul 2013 12:12:43 +0200
Mime-Version: 1.0
Message-ID: <20130708101243.0191EC7F12@MAILER2.edox.com>
Content-Type: multipart/mixed; boundary="----=_Part_97_930046966.1373278363403"
X-Mailman-Approved-At: Mon, 08 Jul 2013 07:53:08 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: NO_REPLY <communication@edox.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, 08 Jul 2013 11:03:28 -0000

This is a multipart message in MIME format

------=_Part_97_930046966.1373278363403
Content-Type: multipart/related;   boundary="----=_Part_55_708591777.1373278363128"

------=_Part_55_708591777.1373278363128
Content-Type: multipart/alternative;   boundary="----=_Part_13_178828098.1373278363479"

------=_Part_13_178828098.1373278363479
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Si vous ne visualisez pas correctement ce message, cliquez ici ( "http://pu=
blic.edox.com/COM/Emailing_2013/07-juillet/08-07-13/nletter.html" )




Conform=C3=A9ment =C3=A0 la loi n=C2=B0 2004-801 du 6 ao=C3=BBt 2004 relati=
ve =C3=A0 la protection des personnes physiques =C3=A0 l'=C3=A9gard des tra=
itements de donn=C3=A9es =C3=A0 
caract=C3=A8re personnel et modifiant la loi n=C2=B0 78-17 du 6 janvier 197=
8 relative =C3=A0 l'informatique, aux fichiers et aux libert=C3=A9s, vous d=
isposez d'un droit d'acc=C3=A8s, 
de modification, de rectification et de suppression des donn=C3=A9es vous c=
oncernant. 



Vous recevez ce message car vous =C3=AAtes inscrit sur la liste Edox.
Si vous ne souhaitez plus recevoir d=E2=80=99information de la part de Edox=
, cliquez ici ( "mailto:communication@edox.com?subject=3DDESINSCRIPTION MAI=
LING" ).
Si le lien de d=C3=A9sinscription ne fonctionne pas, merci d'envoyer un mai=
l =C3=A0 communication@edox.com avec comme objet "DESINSCRIPTION" .




------=_Part_13_178828098.1373278363479
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: Quoted-Printable

<html xmlns=3D"http://www.w3.org/1999/xhtml">
<head>
<title>S.28: Nouveaut=C3=A9s impression Brother</title>
<style type=3D"text/css">
a:link {
=09color: #000;
}
a:visited {
=09color: #000;
}
a:hover {
=09color: #FFF;
}
a:active {
=09color: #FFF;
}
</style>
</head>

<body bgcolor=3D"#FFFFFF" link=3D"#FFFFFF" alink=3D"#FFFFFF">
<p align=3D"center" class=3D"Style1">Si vous ne visualisez pas correctement=
 ce message, cliquez 
<A href=3D"http://public.edox.com/COM/Emailing_2013/07-juillet/08-07-13/nle=
tter.html">ici</a></p>
<table width=3D"794" border=3D"0" align=3D"center" bordercolor=3D"#FFFFFF" =
bgcolor=3D"#000000">
  <tr>
    <th height=3D"110" colspan=3D"3" bordercolor=3D"0" bgcolor=3D"#000000" =
scope=3D"col"><IMG src=3D"cid:D719A1E13533B5D9C0E84327605A6975@edox.com" wi=
dth=3D"780" height=3D"150" usemap=3D"#Map5" border=3D"0" /=3D""></th>
  </tr>
  <tr align=3D"center">
    <th height=3D"74" colspan=3D"3" bordercolor=3D"#FFFFFF" bgcolor=3D"#FFF=
FFF" scope=3D"col"><IMG src=3D"http://public.edox.com/COM/Emailing_2013/07-=
juillet/08-07-13/1.jpg" width=3D"780" height=3D"1357" usemap=3D"#Map7" bord=
er=3D"0" /=3D""></th>
  </tr>
  <tr bgcolor=3D"#FFFFFF">
    <th scope=3D"col"><IMG src=3D"cid:CC05ED65922EF3D704DEAD1EA7127AA0@edox=
=2Ecom" alt=3D"v" width=3D"240" height=3D"35" /=3D""></th>
    <th scope=3D"col"><IMG src=3D"cid:00EA6CB003E305B5DE6907925BD50058@edox=
=2Ecom" alt=3D"v" width=3D"240" height=3D"35" border=3D"0" /=3D""></th>
    <th scope=3D"col"><IMG src=3D"cid:A329FF1E03AC315071306B2F3E639856@edox=
=2Ecom" alt=3D"v" width=3D"240" height=3D"35" /=3D""></th>
  </tr>
</table>
<map name=3D"Map6" id=3D"Map6"><AREA shape=3D"rect" coords=3D"245,239,486,4=
69" href=3D"http://www.edox.com/Webshop/products/10002488/NVR810" target=3D=
"_blank" /=3D""><AREA shape=3D"rect" coords=3D"2,236,241,466" href=3D"http:=
//www.edox.com/Webshop/products/10002488/NVR401" target=3D"_blank" /=3D""><=
AREA shape=3D"rect" coords=3D"246,6,487,236" href=3D"http://www.edox.com/We=
bshop/products/10002536/ICAM220W" target=3D"_blank" /=3D""><AREA shape=3D"r=
ect" coords=3D"5,476,244,706" href=3D"http://www.edox.com/Webshop/products/=
10002124/VC202A" target=3D"_blank" /=3D""><AREA shape=3D"rect" coords=3D"24=
6,476,487,706" href=3D"http://www.edox.com/Webshop/products/10002099/WNAP11=
10" target=3D"_blank" /=3D""><AREA shape=3D"rect" coords=3D"491,239,739,472=
" href=3D"http://www.edox.com/Webshop/products/10002488/NVR1610" target=3D"=
_blank" /=3D""><AREA shape=3D"rect" coords=3D"4,7,243,237" href=3D"http://w=
ww.edox.com/Webshop/advancedSearchResults.aspx?id=3D0&amp;keyword2=3Dicam10=
1&amp;searchType=3DALL%20Keywords&amp;SearchSpecificField=3D0&amp;SearchCon=
tent=3D0" target=3D"_blank" /=3D""><AREA shape=3D"rect" coords=3D"492,5,740=
,238" href=3D"http://www.edox.com/Webshop/products/10002536/ICAM227W" targe=
t=3D"_blank" /=3D"">
</map>
<p align=3D"center"><span class=3D"Style6"><span class=3D"Style4">Conform=
=C3=A9ment =C3=A0 la loi n=C2=B0 2004-801 du 6 ao=C3=BBt 2004 relative =C3=
=A0 la protection des   personnes physiques =C3=A0 l'=C3=A9gard des traitem=
ents de donn=C3=A9es =C3=A0 <br />
caract=C3=A8re personnel   
  et modifiant 
  la loi n=C2=B0 78-17 du 6 janvier 1978 relative =C3=A0 l'informatique, au=
x   fichiers et aux libert=C3=A9s, vous disposez d'un droit d'acc=C3=A8s, <=
br />
de modification, de   rectification et de suppression des donn=C3=A9es vous=
 concernant</span></span><span class=3D"Style6">. <br />
<br />
</span></p>
<p align=3D"center"><span class=3D"Style6">Vous recevez   ce message car vo=
us =C3=AAtes inscrit sur la liste Edox.</span><span class=3D"Style6"><br />=

  Si vous ne   souhaitez plus recevoir d=E2=80=99information de la part de =
Edox<span class=3D"Style8">, <A href=3D"mailto:communication@edox.com?subje=
ct=3DDESINSCRIPTION MAILING" target=3D"_blank" class=3D"Style6">cliquez   i=
ci</a></span><span class=3D"Style7">.</span></span><br />
  <span class=3D"Style6">Si le lien de d=C3=A9sinscription ne fonctionne pa=
s, merci d'envoyer un mail =C3=A0 communication@edox.com avec comme objet "=
DESINSCRIPTION" </span>.<br />
</p>
<map name=3D"Map4" id=3D"Map4"><AREA shape=3D"rect" coords=3D"1,1,124,61" h=
ref=3D"http://www.edox.com/Webshop/default.aspx" target=3D"new" /=3D""><ARE=
A shape=3D"rect" coords=3D"132,4,255,60" href=3D"http://www.edox.com/Websho=
p/Login.aspx?tab=3Dnewacct" target=3D"new" /=3D""><AREA shape=3D"rect" coor=
ds=3D"391,5,517,61" href=3D"http://www.edox.com/Webshop/advancedSearchResul=
ts.aspx?id=3D0&amp;SearchSpecificField=3D1&amp;catfilter=3D%24FILTER%24.%24=
NEW_ONLY%24%3d%401%7c" target=3D"new" /=3D""><AREA shape=3D"rect" coords=3D=
"265,6,385,62" href=3D"http://www.edox.com/Webshop/advancedSearchResults.as=
px?id=3D0&amp;SearchSpecificField=3D1&amp;catfilter=3D%24FILTER%24.%24PROMO=
_ONLY%24%3d%401%7c" target=3D"new" /=3D""><AREA shape=3D"rect" coords=3D"53=
0,7,642,59" href=3D"http://www.edox.com/Webshop/advancedSearchResults.aspx?=
id=3D0&amp;SearchSpecificField=3D1&amp;catfilter=3D%24FILTER%24.%24DESTOCK_=
ONLY%24%3d%401%7c" target=3D"new" /=3D""><AREA shape=3D"rect" coords=3D"654=
,9,773,56" href=3D"http://www.edox.com/Webshop/advancedSearchResults.aspx?i=
d=3D0&amp;SearchSpecificField=3D1&amp;catfilter=3D%24FILTER%24.%24DEMO_ONLY=
%24%3d%401%7c&amp;showall=3Dyes" target=3D"new" /=3D"">
</map>

<map name=3D"Map5" id=3D"Map5"><AREA shape=3D"rect" coords=3D"-2,7,314,139"=
 href=3D"http://www.edox.com/Webshop/default.aspx" target=3D"new" /=3D"">
</map>

<map name=3D"Map" id=3D"Map"><AREA shape=3D"rect" coords=3D"522,175,780,339=
" href=3D"http://www.edox.com/Webshop/products/10002628/3227U" target=3D"_b=
lank" /=3D""><AREA shape=3D"rect" coords=3D"524,3,778,172" href=3D"http://w=
ww.edox.com/Webshop/products/10002582/2925E" target=3D"_blank" /=3D""><AREA=
 shape=3D"rect" coords=3D"396,374,779,508" href=3D"http://www.edox.com/Webs=
hop/products/10002463/GSW2404SF" target=3D"_blank" /=3D""><AREA shape=3D"re=
ct" coords=3D"3,541,386,678" href=3D"http://www.edox.com/Webshop/products/1=
0002120/IGSW2840" target=3D"_blank" /=3D""><AREA shape=3D"rect" coords=3D"3=
97,543,778,676" href=3D"http://www.edox.com/Webshop/products/10002120/IGSW2=
4040T" target=3D"_blank" /=3D""><AREA shape=3D"rect" coords=3D"2,4,252,167"=
 href=3D"http://www.edox.com/Webshop/products/10002130/26191" target=3D"_bl=
ank" /=3D""><AREA shape=3D"rect" coords=3D"263,2,517,171" href=3D"http://ww=
w.edox.com/Webshop/advancedSearchResults.aspx?id=3D0&amp;keyword2=3DAliment=
ation%20multifontion%20Notebook%20&amp;searchType=3DALL%20Keywords&amp;Sear=
chSpecificField=3D0&amp;SearchContent=3D0" target=3D"_blank" /=3D""><AREA s=
hape=3D"rect" coords=3D"2,173,256,337" href=3D"http://www.edox.com/Webshop/=
advancedSearchResults.aspx?id=3D0&amp;keyword2=3DC%c3%a2ble%20de%20s%c3%a9c=
urit%c3%a9%20pour%20encoche%20180cm%20&amp;searchType=3DALL%20Keywords&amp;=
SearchSpecificField=3D0&amp;SearchContent=3D0" target=3D"_blank" /=3D""><AR=
EA shape=3D"rect" coords=3D"262,174,520,338" href=3D"http://www.edox.com/We=
bshop/products/10002604/669183" target=3D"_blank" /=3D""><AREA shape=3D"rec=
t" coords=3D"2,372,388,507" href=3D"http://www.edox.com/Webshop/products/10=
002463/GSW1602SF" target=3D"_blank" /=3D""><AREA shape=3D"rect" coords=3D"3=
96,374,779,508" href=3D"http://www.edox.com/Webshop/advancedSearchResults.a=
spx?id=3D0&amp;keyword2=3D2619-90qp&amp;searchType=3DALL%20Keywords&amp;Sea=
rchSpecificField=3D0&amp;SearchContent=3D0" target=3D"_blank" /=3D"">
</map>
<map name=3D"Map7" id=3D"Map7"><AREA shape=3D"rect" coords=3D"2,215,738,433=
" href=3D"http://www.edox.com/Webshop/products/10002381/BRO3140CW" target=
=3D"_blank" /=3D""><AREA shape=3D"rect" coords=3D"2,438,362,688" href=3D"ht=
tp://www.edox.com/Webshop/products/10002381/BRO3150CDW" target=3D"_blank" /=
=3D""><AREA shape=3D"rect" coords=3D"374,436,734,686" href=3D"http://www.ed=
ox.com/Webshop/products/10002381/BRO3170CDW" target=3D"_blank" /=3D""><AREA=
 shape=3D"rect" coords=3D"4,793,736,1039" href=3D"http://www.edox.com/Websh=
op/products/10002380/BRODCP9020CDW" target=3D"_blank" /=3D""><AREA shape=3D=
"rect" coords=3D"4,1045,364,1295" href=3D"http://www.edox.com/Webshop/produ=
cts/10002380/BROMFC9140CDN" target=3D"_blank" /=3D""><AREA shape=3D"rect" c=
oords=3D"-1,2,778,207" href=3D"http://www.edox.com/Webshop/products/1000166=
9/PE6108G" target=3D"_blank" /=3D""><AREA shape=3D"rect" coords=3D"370,1045=
,730,1295" href=3D"http://www.edox.com/Webshop/products/10002382/BROMFC9340=
CDW" target=3D"_blank" /=3D"">
</map>
</body>
</html>

------=_Part_13_178828098.1373278363479--


------=_Part_55_708591777.1373278363128
Content-Type: image/gif;   name="nvle-en-tete2.gif"
Content-Transfer-Encoding: Base64
Content-ID: <D719A1E13533B5D9C0E84327605A6975@edox.com>
Content-Location: http://public.edox.com/COM/Emailing_2013/01-Janvier/02-01-13/nvle-en-tete2.gif

R0lGODlhDAOWAPcAAKmpqaQYgM0ukf3EAAgKDJHR7rm5ucnbivq6Af3XUACV2nyyHXLI7X19fdBE
mcsWh06Bmgmj5QrU/yYmJTs7OgFMc1hYWNHR0dhlpwBlnACDurfUhZvDS8TExBKo593d3fiuAaLH
VvT09AAxTLvUdwGk1wB6slK76Gtra0JCQqtbi/zaZABqo42NjdVWorkJfnN6iZhIenEoV/7rp4C1
JgGd4je47Il/agCXy+np6QGLwgBzqHJyc5ycnFgSP0ZILmNjYgBWiIi5MTuLtVNTUsQDf4CBgeLi
4ymz664QgN5xrkxMS45zGYCyTfvIOmuLNf7li6Py/9rlpmxxS2yqzpOTlCubzNHglUBZEgGO1PzT
Pk6ty8rKyv3TJwAkOLS0tCaq46uIK/rEEfr6+jl1kfvIJbfRbDEqCQau3yek26rLYMqxS+CCvfq7
ImtSAMLXf5eyHP7hd8unKkNDCrHOZaa8c6cKevm3EpwWewC++om91DJLV0eawYgzaAAVIbnc8LSa
SP7QF6iYkZyjdpKuXoONXjQ0MhOb2wB8wa4xhtv0/m1tbzMKI8KXLVFRUJd+NSx+qm2Iu5OUj+/v
74+9O3R0allzK11dXWi843V1di5VZ0C/8sqcBOmrFhUUE+SOxA656xqayvOqCtqjHTNle7XDfoiJ
hJmOZX9qNUYlOvDVeUpnGKzPcuKuBGFTJbwchO76/YBLa1ZoPBmOw56FfrDQdb1upWlpZkhIRx0e
HHp6ekJYYf7LAx2Mz4+Pj7uoWDQdK4aGh2ZmZn6oMduxIiI6RQBur1paWgBBYgCt5/v1+paWlk5O
Tjew5B1znio0FHBwcP/dLoiJiuy/FqSkpI6DgJ+goGhoalZWVVczSQpXcZsgbo+RkpmZmXd4emBg
YM3NzkVFRNfX1x9ffy4uLABflrCwr7e3trOPGF1CUxyt6SSGtXe8Z7DPb6ytrXZdC5TAQ+HFZktU
MEpKSUtGRRDA9MzcnO7mp207WcfHx1tUSuPAMOnITdDQ0P///wAAACH/C1hNUCBEYXRhWE1QPD94
cGFja2V0IGJlZ2luPSLvu78iIGlkPSJXNU0wTXBDZWhpSHpyZVN6TlRjemtjOWQiPz4gPHg6eG1w
bWV0YSB4bWxuczp4PSJhZG9iZTpuczptZXRhLyIgeDp4bXB0az0iQWRvYmUgWE1QIENvcmUgNS4z
LWMwMTEgNjYuMTQ1NjYxLCAyMDEyLzAyLzA2LTE0OjU2OjI3ICAgICAgICAiPiA8cmRmOlJERiB4
bWxuczpyZGY9Imh0dHA6Ly93d3cudzMub3JnLzE5OTkvMDIvMjItcmRmLXN5bnRheC1ucyMiPiA8
cmRmOkRlc2NyaXB0aW9uIHJkZjphYm91dD0iIiB4bWxuczp4bXBNTT0iaHR0cDovL25zLmFkb2Jl
LmNvbS94YXAvMS4wL21tLyIgeG1sbnM6c3RSZWY9Imh0dHA6Ly9ucy5hZG9iZS5jb20veGFwLzEu
MC9zVHlwZS9SZXNvdXJjZVJlZiMiIHhtbG5zOnhtcD0iaHR0cDovL25zLmFkb2JlLmNvbS94YXAv
MS4wLyIgeG1wTU06T3JpZ2luYWxEb2N1bWVudElEPSJ4bXAuZGlkOjk2MkJCODI1QjBCMURGMTFC
RDhFRjM5REQ4OTBFREE1IiB4bXBNTTpEb2N1bWVudElEPSJ4bXAuZGlkOkYwMkI1MDBEMUU3MzEx
RTJBODUxOEY1M0FFNThERDgwIiB4bXBNTTpJbnN0YW5jZUlEPSJ4bXAuaWlkOkYwMkI1MDBDMUU3
MzExRTJBODUxOEY1M0FFNThERDgwIiB4bXA6Q3JlYXRvclRvb2w9IkFkb2JlIFBob3Rvc2hvcCBD
UzYgKFdpbmRvd3MpIj4gPHhtcE1NOkRlcml2ZWRGcm9tIHN0UmVmOmluc3RhbmNlSUQ9InhtcC5p
aWQ6Qzk1MTczN0I3MzFFRTIxMTk5QTlEMzg5QzEwN0ZBRTEiIHN0UmVmOmRvY3VtZW50SUQ9Inht
cC5kaWQ6OTYyQkI4MjVCMEIxREYxMUJEOEVGMzlERDg5MEVEQTUiLz4gPC9yZGY6RGVzY3JpcHRp
b24+IDwvcmRmOlJERj4gPC94OnhtcG1ldGE+IDw/eHBhY2tldCBlbmQ9InIiPz4B//79/Pv6+fj3
9vX08/Lx8O/u7ezr6uno5+bl5OPi4eDf3t3c29rZ2NfW1dTT0tHQz87NzMvKycjHxsXEw8LBwL++
vby7urm4t7a1tLOysbCvrq2sq6qpqKempaSjoqGgn56dnJuamZiXlpWUk5KRkI+OjYyLiomIh4aF
hIOCgYB/fn18e3p5eHd2dXRzcnFwb25tbGtqaWhnZmVkY2JhYF9eXVxbWllYV1ZVVFNSUVBPTk1M
S0pJSEdGRURDQkFAPz49PDs6OTg3NjU0MzIxMC8uLSwrKikoJyYlJCMiISAfHh0cGxoZGBcWFRQT
EhEQDw4NDAsKCQgHBgUEAwIBAAAh+QQAAAAAACwAAAAADAOWAAAI/wD/CRxIsKDBgwgTKlzIsKHD
hxAjSpxIsaLFixgzatzIsaPHjyBDihxJsqTJkyhTqlzJsqXLlzBjypxJs6bNmzhz6tzJs6fPn0CD
Ch1KtKjRo0iTKl3KtKnTp1CjSp1KtarVq1izat3KtavXr2DDih1LtqzZs2jTql3Ltq3bt3Djyp1L
t67du3jz6t3Lt6/fv4ADCx5MuLDhw4gTK17MuLHjx5AjS55MubLly5gza97MubPnz6BDix5NurTp
06hTq17NurXr17Bjy55Nu7bt27hz6979MwUKC7yDC3/6bNWTBQto0FjwZNUzhylySM8h4oMB4AVT
9OiB08IF6QpRiP8w4LCDPxEAhqtfT5SAJeU0hMgXEp/+k1wMU5zf3sO8PxQDpXCBP//h9IE/LQCY
EAD+5NBQDwiyJ+GEPBHwBDwYZqghhpQMg59C+jk4EAr+fDBQCx20kEJOB06w0AQtYLdQixvl0IFH
NlKoY3CWhOAjBxtiyIGPITyxUIgEIflTA/6QpxF4NYrIEZQ7VnkbIbWwwsGWXHbJgRqssHJkg0mS
KRAKF4iQwwUKptDBdDk0IFAKBkzXgYx1SnfnQDk4KVCf/wAgAncCfefiQQfKmRCgf8K55z8N5ECg
dBbAmcOhedooI5pqxomCpA3mYEF005n4D6N/+smpdAB8OqmoqJ7/6iSp0pn6z6psWqlrZnWwQuSv
wIbAygZjSjkBhBec6Q+bFpgH3IEANCCtiymo2YAFaPqDnQXStiApdlSeKuKBwBlQ4EHmiiDCoQdR
SV23kgKYQgPqSnuqPw14qyi3+X77J4LTzluvnPqJ0EAPIgAXLpQk5tCCtCkIbLCcC4tY8MEJ37rs
b87u6jFlhYAJJisikxymyIQU+4+3k674z4EuT9DkPyJoW5B5iv6jn58DWbBsowRBWW2cMx/E5I0X
JIuQu1KSqLS4fPqz4gQ59/yzzP6wC/ScZvoGNZ/j2lwQ00Fb3DWAMAskM8+B5fLDFDecMsggNwDx
w4cOEZDLBLkQ//BxblgQEubghBNehyUq35uzzBNLW12gBBrgsuLSOm4rv/SKsPXmLRBoq0E0VtvC
0lJSifWh7kptEObqCmReDgpuriTYZf/DeLulS/n17LafVzm9n/tFwA+0lDLDDPdIofzypRSCi98g
FjJIHaXUMcgUFBhFgCcEQP+3WlisguUG5JdvPiGWYJG40wG+Op3SkRKY3r2WrvlPpaFKKmLFBNVM
KO4nEkEKtLa5hanua/ea3P30Jx0z/QNhRUMg7xAItQkWUHdCc6DO3Cedp/nFEIO4x/FGuLwSSsEe
gzAEQjxRiA284YVvIIEMa1EIcgAlF4ZgxjeAAARhCOMYuCCHJ/++d5ZnYAELTyBEHTZwgPLVgRDN
wcIcEvcP8xBKZrozSPxuJCkCCoRctKNZ1sIIOeooMGiaG8gFPmCdseUuaAdMnQLBuDnbDehGEtSg
GNkFntsZhEo146PZdIdFw0xBFSNMpAlLeAV7TMEgBCjEGw5ASRiS4A1mMEMdsscTcmBjEZngAQqu
cQ0UoAAa3vDGIojgRSJ6hQBHjKUsZ4mFIYLIgROoGXboiJBcOsg8o/sjBkU0oNgxrEkkCp4az2W7
muGRjAZ0mRxrR8aBqOlP6+JaFosZRl7yKZv/4ObWJuhNwNwgDlCAQiKPl7xFKq+RN/DeP/QxyQNY
MoYkyCQd6tD/yplM4BKZgIYwekhKHxpUGCjwRgMu0U9XasUTc6AlLfGWEN51zlQNe9i1BII5cyWr
Wk2qHHasaIGSXlNjDnOcgyYAJQixTVno2c6A/PHMC8JRmqU7oOv80YOSWuCkKJAWsnZqgAZETI8Z
VamyUmpUoho1qfQaZEGgKiO+TGEF6EynOkfYThNeQQpXCGshoBdJGL5QhjLUJx1CMFaczCMTixAG
D0K5CBQsggepXMQ1hEHKayiUCPJ0KFcI8IyI0nIOzwgsQkhVkO8Qqlml+mKpDHAoOn0gsrYDQP1G
lCY4/cMAGSuUCGJHEMhSh02aJS3ZwIZT1hJkApq1VDOnQ1m1/+WpB4ydamenw9lOzW8Ct73VboUW
Lo6+qVZw8cQZcnEGWx6EHPHAala3SsKughWs9rgCJQsxRE8MwqxozaRa1UAIisqEAJdQpTeuMQ8K
8M0TnpiAIeZxjQZ4Y5SjXIQReGBewWqle88o7BER61z/psUTrniEHIixD2LI4RE/UOwjErAC6U73
eFBo4vLCyuGwbnd7pbgkWvOpVjqoIQQcUCFNPAGEBvDgG4YocEEIQI5L6EIXdjWlLoygYgP7+GOu
kIMYBkBkXhiZF2IIwxleyw8KVzgOUM6qE0QBhwUIgQTY9TAlK1kIChxgxCQ2Ax1MfOIQEKKhKyGA
MIxwDU42ZP8CQDBCJnKciWCc8cd4lhABUHEHBBR5AEc+MjHYNQUtRCMBTpYuFNogCiojZwHtAKt2
t2zPGJYiu2YI85jJfGJ4EEKxLgGCNIgg44ZQQFqLgAYopXHnPLs6OKhAgJ+JXORAGxkQfvPEGrqg
BUQj+skruAMIQAAH5SAn0pQ2awzf0Egxb1oNZUZxCB45E0eoqCK5gEYwoMEDaGSiBW5+tbh1Qw5i
yHoAs6a1rXnxg3/IIxC8jsahfx2HKQ+72MZeQC20O0lLppUEYcVktH0EbXi0WyaG4Ea4J6JmafDg
4bpoAZrHTXHXxFrW56b1n4+Min8AghddCLkWev3rNgyb2PD/WY6+r3DPtIr3AI2k5IjbAY9hgHol
npDGPDRyjRZk4udGCEapK0501hAgDBhPusZrzYtHTGAavIC3yOWdAC2cHOUpT86+RexyZ9PBDC+0
JwnaEQJ4CKEQuXiGIZ5BAQoEmHspEcY3OAINaWTCG98mbdH3rpqjgyDpStc4LwbQiEcYORCIF3mv
y3B1fGedBiT4cpidDe1ob0lDQhhG5uVDg2F4/gmySGxJyKELhvvBD15IvR+8VwlppNIbywgH32ev
GlT8/e+AR/fSiQH1IyNe6loQ9skd//hLivfZ0P5RlzhEifksR+WPHsYTIjwSaExcIAQYATIyoAEc
lAANoKiH//hBgQYTlEMbxaiGEW5sBG70tyLMaMCN50//+tv//viffwOAYJD45///9BdQKHAJjjBA
NxcS5OAIi2AK1GAA+QAO4hCBEngB/dABBmANbLYE1ycQfuAM2vCBIBiC2lAByDACHUEB34BK+FcF
l9AUlVI/0xE72kEo0TE/AbIdDhErGiEeL8UQ3lFcDsGDS/NSM6gTHTBaOpMD6VGDLMGEtEId1lFV
HfEDnYB7gIdxRCYGfQZogfZ7XcB4jZccKWdskPcGyPcrXJIhlLCGzjeG8PFoT2BDIEEB2LAQflAB
O1ACySABeZAH9RB+oBCIgfiHOqAAO7AHtGAE8scN0LAR/v9BIJAYiZI4iZRYiZCYRgTxiJa4iZY4
CeJgAMHAUCAxLwZwBJx4ih9gDjzQYwfhB6EgAbAYi7IYi3lQAhWQEQ1giqfYakYxg9vhP/xBLTPV
Jg4kIASid4uSRRnBIMrIEAeSIBPBjKSTJMOoE5KyhGRiQSaBJAXDH/6BjBpBAIBwdUp3bmJgcggw
eOsGbyY3bKLQCZ6HHG5oZTJUeZaXhmvIhpznhmOIHMMgDyBxCUP3DwSADCaABn2IBiWwkGjQkA1J
fg4JCjiwAzpQDkAgCQ2giMuwBxpBDaf4kSDpD/1gEB4ZkiYpieLQDbwoETByICf5kRfgDQP5D84g
AfWgDg7/2ZAM+X15IAE7cBHmcoqTMJMt4QfIUA4aoAA1oAA6wALI4AcSISlnhCLXpk0nkiIrKUwe
ASNS2BA0MhFcOY1XWZU5YQESt0EOoo0lwY0alEwhUQkJ0AbCN2wI8Hdl4AToKHi2FgjCJwpKlgu5
IA/DIIZZd2UkgIZpCA/52Ib8yI/IIQsHSBHkgAutqA04kAzJUAI44H0L2Znfx5A5iQYasAOIoAk3
IA1GYATVwA0aUAGR2RAl+ZKyKZIkOZuzKQ4NQJQLQQ4MYpsgKQK+8H40KQGhiQaZqZCd6ZMVcQ4f
CU40UQGzEAGHIJ3UOZ2HoA1Q+RBSmR96FBFA2BJM0oMY//GdQMGWzbiW2ahBapkR5KAKK6AFThCf
8pkAeDlsS8d0SCYKwxYGBWYIg8mPQtAOb6AGXsJ8zbePjdmYj9kR4SBjBGCZmbmZm6mZWeB9aIAE
m5ChGVoPSBCIeVB+JpABuyAIqWkEtMAHeaADyGARsembITmSBdGiLhqSIiANr3kQnTOjNNqIB7ED
xKmQyImcnpkHPykRQcmJznlezgAGTNqkTtqk65CdDbGdPdNZF6Aos4MrxjQdInABMsJAmpIkmdIB
CmQpjyIrBKGlCcFS+JIQl0VaPQArfmIBmaI/AXKEOfABVUMndjI5qxInqRI0TmIpE/CmBBGnwOEm
aqKnfP8yK+kpImNaVWZaVX86P3yqJ11pnq/VnRtBAL+AaCM3cvTZBlh4bunGhXzpjgdHED/wn2Mo
HxzgQgSqjwj6aLZ6q/24AE2wBSfAkRrhCQuHDDqQDDigAxKqA8ZqAwUQBYrQrAVQAHqACVuwBVYQ
CqHgfaOpA0FwA90QdOqnAzWQDBpgghMhozq6iZNQm+d6kkfADA8xATO1riB5DqDmo0LqmfhKpBHx
BR85BnJIE9pwAs1gA81QsE5asARrA6SgnTqVTL9hLvJiJk7DMWLzLv1SsRPDMm2iJg/jLQL0TfBy
LlQysc0iNgWROefRT0OlNiXyNT4zKJVzUtXyAQ97LkP/07Fm9C8ahTrD9C/9cjA/w7ImMrM1qyAZ
lJZmwi8s86UZGy9LpVErMjTXki1SqKlqwyA15RFTgGjREAjoJmtWmHuCVwb6KQqj8H4/II8pNx+U
EALkQwIndnkGSgmKSbd2SwnP93y7qqFbsIENQQ7s4gcsUAJMaaw6oAE60Ax/AAv+AAt/QAVkMA7I
UIKp5wUjoH0VEAQssAMmwAIjGgygSwtDgKwKUAJBcKPqeooV2AGs27qu+7qwy7r5YA2py4niELsd
wAUXcARjIJtG0BCGUDMhmQPm0ADfQARLwAxLQARxZgCTYJIfMHQmIAH42pneN6H66hD8+pH/ShN8
gAkn/yCwBTu+5HsC4Muwk5M2f/JRZqK+a7M5PoNHIxu05hE7JPJM86s0VOK+ETQiNBVOQWsQuXRA
EEIxIgJM1FS/fKI0CqwsN3I6bkRN20k1A+wyBVxFzGQ/u/OoqxPA+ftFJrtTObMz2cHBb0IgF5CV
GPED/FAGc0mXYetnGUdkZdCOotBxCJG2hMm2awgPIUAHtUACGyDEQqxs9URpGwAPycEOW6ChGgoB
GkEO0DMCOlACh4usiHsCf6AIjzsOIyCldugFyBAEFVAN1hAM0vCtV1wCGuAFEWGulSicGAHHlCh7
CuEJ4WAEmviRwZQQniC8HwkO3/CangANLvmRyiQQGv9Qi555vY6MA3nAAg3Rm6e4cDOBCeBrA+Gr
yZp8Ap1svgyAvizbOJGiOUjCOL/zOBR0UqZDIC5CHeziS2QEwVCCyjGrTKFTM31cEBAyP1Dyy2MU
RpLyO9SBTbF8Uq+jWj2bQIfqD768P/hSOcW8wUgrJayDia2cNX4ER78DPCVczZDSA031EcqFCmEw
Cvp5dSdXlzGMhXeZzqKwqgchD2pbHz0sJEMCbV+XSTIEQ1vWYVLAxE7sxH2LEfElEMhQA4eLuIi7
Bc8aCdjZipgbBGRcASPgBfLkB7jwBWgsDbQwCwudlDpArg5Bx5PYvRxh0pLorg5BDhASkpmgEPF6
ijH/DRHcEJLmgBCLrJkT2tMSCskZsBDWAJJ2fBMQAL7hG75IrdRJTQWivEH5g1xsGdUazD8UtJ3F
tVr/siIZRNUexDnnMUACrCYTQCKEAsxlCs2WYipZLSUQ5CdWTaVqQ9Zm/S9rPU4cjD/T4UDRZEFg
+j7fjJYjcQao0AjqfNjrXJdXiADvfHKNoJuyII88DA9cQiRqMGb83M9h98+NNLAD7cSagBF98w/a
UAMacNqnbQWYALkjoFgjEAQUmQWHiwgmYALGYNvlUAFuPBA9QA3S4Au0AAGyfdomUIgrWtIgyYop
DZJEEBEUoIsfqdwDoQshydIRsQgh2dwHoQO1+Mg//y2hkZwQ3QCSO5cTAcsADIAJ6K3e6J3e6z0O
T11IBnHKnLrK+4NBqgPLAyHLdYTVIiLfCjHNhVIiH+BF5tIAacKzWy3BOoVGx0xIdyQQgSTMDf5Z
+JLgC66Vgo0kvKTVCbTNUTNxVvsRhD0KiH3i6xy2dwCfc3nDDEEAkW3PPVzZIaDP+4xW/szZepAF
GGoDNrAJP56hNgABqHvHpF0Dta0BxW0FW+AMu00QfqANGkC4OlDbtb0DxsACLJAB5VAOWe6aAnEJ
HRAMviAJplDcC20CSXncDKHSkSjdHcncEuEJ0M2JiUwAISkMFVEFIJmuCMHd3/3dyHqZkmwQfP6R
1v+NE8gwDlTQ3o7u6JjgDGzOEHJdToL9MiFMRvHb36oDsf4L1/jN1VJi6Y3FTAOctVwDLWGEwKve
pgbh6cryUiclTl8j16nuzAOBMwC04WRi1VetOuXE6hXFwR/hCuiM4sh+dXfgBPSpn+zcCSidEO8R
H/koJJZ92Td+STkOc2FlBTwO5D7u4+A+BEWeEARQAQpg5YhrBZBA0gPhB+UQrllQ3LNgBbOgAYiw
AzuwuVjOAkHg5eUAlZ5gDtbQAr4gCJpQDmmu5gow6Qnh5pAI5xkB8QSi3RGRCyHZlUYAkvlwEaBy
inP358Qa6IOOrMNa6AMhDXK+E5gLAY3+rDDPAFT/MATaMLlPjVIaRYwiQlUgKy10FE06w7H5oi6T
A/Tzy1RdqTEx1QMzheo7pVNQ4jPOHLMWoy7i3AAyKPQtQPRnIlRBC1WsXOEYrFPVArNYH0aaSlIm
9UZRsyJQFbU1U1TSkqnE3hGo0GjJjux30AZOsAJOIGxgO2yNUOTuoRzVTuP6LF44vtncrgcK4AHh
Hvk/bgN8oJsMUQHznuQ6MAunaxDaoIfIugWYoAdbAAnjYNGVa7ljrOWaWw4CIQ1jzg0AoA8EEASH
a+UmkAVP/vDJDRIU7w8WHxEq/5EwShB1vomWfN0crxCXuZkmb7jPf/IDEQwrvxNGObnYn/3aD8YL
/yEdCmRa+p1b93NceRo10tGlXzpMLnOpfZLWZSPqpUX+iTz+549asHMQlcIzVEKnmwUQ//6lMJDD
oIgJAgcWNGgghcAJIgzmMJBQIIoLEicKNPhQoUALFD8unIiQYw6BKQwOXDkBwMSNJz92vJjRIICU
Bj5M/DCSJUqVKH0OJTqUwCNRIJQuZdqUqag7bfglSOCkDQgEWbEqRVWUqCwhQijBg8eBQwi0atTQ
MdOWBIk3cQ/MPXDlSrMSSGzY0LvXL5IhBLwO/udFh4kdJkzo0DDCpxcceRTgYPCnAJVxI/x49YKM
RQZjyP7RA9eiirVgApFp0KB4B+vNXqn5o13btv9tQ4R1D5192zdtIrt9Ehjz+3euj+SM+z4ivCjx
5bc9PceRTAeO6zq0b9euIVkQAjei277k3Px5wn6QrWffnr0X9PGHrpRf3/59/Pn17+fPH1VSpwJc
SpQ2nHCiqjLayGpBBkEYxSLnDHmCkrHMOiuEtehgy4y34JJrrjj0qEEdvpDQ68S9kICgPgJMQGSH
xHTYAb6RtMkjDx0YUOSPSJARbDcvgjDGmM0McIebKqixaAQTWoNRhwwG6208f3Lr758pxwsuvnOo
pO2aj67x0p8q8OtgTGy8IgCHCLhzUwPGtINkTCCutFMgAkZgr4L1+ERGszt3oy9QQgs19FBE7/z/
AUABn4rKQCfKEEMMBAZg8FKlHvnRPAJ+eKIJC9NSa8O34vqwri3QMHHVEktEYpf6KpDxSRZi+8gE
CfJSBBY+HDuPACFFq6IfaapwZwmFvGgSRmN0EK2oLKOzsr9ol9sSvUXG7OGjKsYs775gxmxgsDVL
eDNO1ljTgQ8qhUl0Pz+8GEHPeb2w9d2RBsV3X3779be/XBphVECo2ijj4EB4GWBhSxeu9NKsRJk2
vlx+kGWKKZ7AeGN5Ov7h44+nKGUDddRZ9WQTbVCHj+niM8wYGDWodSQCSshVRz18lI8AFoz5R58P
WlgGAGg+8sNFGHdA5N6RqjVu4v2c/u3a85YY/zOfjwwY0yP7gBiTmvR0qAFOddM1W2Y+ijMOhX/b
tlNft+OWe+5//2tUKYMD0ZsXhftmmOGHL+1qX0O2MNlklE/eo75yEGFBaROYrjmPEgr4wxmm0Rth
aU/EoWYZa6QZyQtEEGNBgwqgHXNT/qT2jWrzDBlTnI/AGZMc/IgY0wDd/MChBLLPTtfFDIYwThe6
k5cPbuWbd/75nRu5G4Qyutibb+wHUPhvhy1dUNN+yfCgZPKRQBwJDyBg3TzSWXhcAxoVmhwNBvSo
YP34CEBENAM68KUbayDnIyPQgTF6FjmiuO42LVgENBz4QAhG8IGLwF/TxgQ750xgTD1RyAXGJP9A
+8zjarvxnQKE1yTFpLB4vjEC9Fz4QhjGUIa7IccNTgEIQDRCDqPoBIDu0AXrXQ97fuOew7ICPn5N
IBTkY2LJ0McHCKEnCI4zhgae9ZHIlIABW/BVfoKQOmt8QBrLcAcFfBIEmbFgfwkcUxt90zLVeQmD
wtGgl5rTwQ/iBxdj4oJw/HAdFLamNSlMYTmMV5vUzFCRi2RkI9sWDm/AQJIwMEIDqmHDU+wjGkDU
mxCHWMSsEMMVFTwUAYYQgSY20QOwko8fduA+E0RpJCagnA2G0MX8VCAI/+BBDoRmDmYMB0Y9Y0EF
FehG44wBjmyUo3xyMaY7CsSDXoqifPbopT7/+jELOFDMIAlJyHKsgzYtcGQ5zXlOdOLHAt5oQDsr
OUlJrmGTnPRk9gAnhlEw4Qz/IkUEPDC+8TUxAoGpDzIQkQEWmCB+AilHHnAAhnUsND/I2OUSctAN
MrLNJ5v7DCIkKpBjItM3ylgmby4onzpSKZr/mCaVQFifa1Ipm37UzjdTmBhmlcMKi0hnT336U6D+
wwK6aCdR29kAXXgjE7+IxjyDWE/tIUAOYXDFS5MYCn/+U6vqAGgazFiYPZCCFJoohlWLIqQMIGKX
A0xGCUowC1zqpwKpI8cRAJAk5A2lHDvIgAlS55OQitQ2IigpYE9KMWh+pKXjqWZ8YjqemdL0/5s4
TVpiytELVgZVs5vl7PMskAldhFa0SdVFJrwhT6d2cojTaAQT5mDW8NXgn1nV6mxX5AUyWIGr5LMC
GYpBLoQm9F7lws4Vd0MAL8jLXkXh0z8IcAEDcAM1RNkcQsthUsG2sbAWbGZ8UjqelS42OrA9z2Oj
E1kgebOylTVGOZwBC38UrbO7mUAPbMK8uXVABBotlAUugF/doEAEvFNIB1rQWEKJZCQp6MG28qNg
rzDYwW1bAjSS6g0Ml9a0SvXGKfgxz06KYaquOAMp+zWBQ0RAxbOtbQSskItiWIG2u/VABNJAhu0K
xAvGyMAO1qqQIFgHBz/WzQjKwZrS8fh+Q/+pAI06AA5p9IAbpEQoQjMXWH8c4QNb5nKXvdzlC+RY
IVie426eaUfFjgnB5eWjeUagANfACDHrDcJ7a8PfRjLCB9sIwCsCsA0ZMMLEPplADvxxgQb3YFzO
MzRODPUBf7QAz84BgD+EIpBKDzhR+krBNCddHwCnxNNxowA0MnFqVKc6EzxYhC6Y2oV9tPYHnhi0
v/qpYlz7U9cR2EUusPpPGpOvxkMg7wjaawJc+qEG1ynmbiqQBgYUQA964IMzMgCaDEgOPAL5gjiC
sYwekBcZsTTGR7GMuyuR2ZmJxaOXyGse8y4HvYMZQRY0sN71GqPO8LWNuxjpiW0IQOADH/j/Nhix
G605Wnk56MBHLHDgQ0F6zbqZQAssMBIU2Pfih9JXCwzMNY40PD6h/ofHWwDyf3niFqY+NQ9W3XIe
uHwRKDjFFN4tt1ykoQa55nkNhuAJSMi2tsAm+kC3iwwez0whGTAX/Iociigo4gh/0AMV+LAOvpZD
36O7IjU+EIzTrHnHWo8rltRsJ3V7l93SzON94m2ceRflzXPG9yt9bGfffGORPnBA3/3+d7/LgDAR
8QfK50ZyQjXAHwR2JOJlMvJLx5AIK4955WMuwWt8gwK1bhsZIlAD0H+e5xGgwB5WTNuhazUCZMBf
BQxIZD/YWwd/HUw5GACLSVim6nyYxb0z/1COILBgociI3zI+YITToFuvPSs7lqGmn7SjRzle4qBA
+tF2+1jNSyInDDKyQPf1uk/fkOD3bzYeQ2C4QP3rZ3/7UzGYFPhDBEQhyEQ6wDWYNAT/+XfIRzAi
kQvgLwvoAPtDAUOztBy4OAgbwPxDCQjjCMb7vxwIwKIoNH9YNKJowA44vwW0iQvAQAY0CO6TQAoc
CAKcCAz0v/uyNIWoPxG8OAOkDYO4OIZguPP7BwnMAZwwNPu7QRe0wRbUrxz4AAzMwRTcj1xAAWGQ
ICacuUW4BOVLnlzYgs8DPSsMvRqABHKwgp3LtRpLPa36rZGogJ4xrgowIRPgvB2IAn/YEf9po4It
6IXDeKXfM4YuIgDjCgZvk67nUwjXCw3D8pI+xI/oOw8KGJML+AguuB11GpNzKLLvwzf3cR8fgwQR
GA9kiaEYUAIlaD8HaD9OdIHBsAAW9IkUkIgWaIAWyAER8AhWPCqtaUWOEAFYlD+PQIFDQ4EB9IeL
I0URSMUGsIAUaAARoMVFow9cFAFFaycWhBtkzMVdvEGFIMZLNIkMNMYGAIBL3Lhn/ABd1Bq28UVg
3DhcDMBo/AdIA4CjaizFI8J2koiUkIhgxAheHMZibCeQaKdV5MWLsDRgfIhXVEVD06hTzIF59KCL
O0VvtABw5IhIa6eJu495QIGVc6BFuEj/jMzIi7wFFHAEMbM19LFC0ds50CMDCKixLhw9Fvsnn/MJ
MrTDj3gNZyGMNfSHP7CMAsCELQgFxjCdcigHFrii5PoII7gAI+DDokC6oAxEKhnE+yhE8yBFL2G8
f3CHrcEPXPSSMqG373ucpJnESSwH8vMSXIghJWADDMCA9mM/tWQDNhjFUhyJM+EvXBQ5fekBf7DL
yMNLkYM0j9Ag3jmTI/wHfaEPSOOv+HPAyCNMofBLiFg8n6hLljq0otAXyWRMgXBMjkhEwfQJzQTM
f9hGr4A0DhSKzkwJyMTMoSDFRERHfpyJSytHgTjNgYDMuVSICfyHOorI/CCATIAGYUCB/5lDAeIs
TuMkzmsQBs3jvETxBD4wnyuMzhpIA/MZydE7PV0LBZfsmfgxDMXInJEohygYg5ssgAJgAExIA+xw
ks8ASl/JE9ZpAHAwghawBqc0tqXkrqZEu8NCjxYYE24gSm/Bj24YE/mSu64cJrAES2dwI8NrHltQ
AgyQUE6cUAqlUAx4S68gxcWcRQiJCKHgtFIUUZTQIGwkxp4wtMYqzBKVPwhJTNXEzRY9URGoPoWQ
uIG4RHKaj8gDUZkw0aNqAFYkTH+oJiA9qhr9h0pbvAc1Udh0yCBF0cdTCAtA0vlz0ny5tN0k0ihN
UkML0iH9hzPJgU/rD3IIhgYQhuAszv9ruIZbaFM3pcg2VVML4M1E0YRVkU6SBD0SqUKSFL3rjIBD
8AnPULp/QAbGoD2iQIZNUAacPM/0LIH1NJ3fEz4dY5oG4AL67AGn9ALmY8rxiMKo6c/zgDQv0TuF
0B0vCdD7EIcx+SrqOgyvXFD3SasK8ARBcCNYfR58YANO9NWz/FVhVYIYgL+4fFJkJdEprU2gkEGY
SERDMzwWZdaPgFFnbFYEnIjWRNaSs8UVXUz6WIn4y1aDSNHCWzBn1VaBEFLaULgWPNZwJVeDaM1B
CYlsZUEYzdKZOFcezD9oldfq64FLpEo7wQaw4wEgEIZbWNjkVFOHfVggiNgHxRcC4AP/xPFTPY2A
6rzCKgRUniPU9rKVKUKEsjOaQyjPaWOAE8CL9WTP3ysHwUAunzCCfGiAKBPVj/BUmNTP8XBK+4BK
4ThE7PsHT9ig+zgzKpkEr6g3E6DVSbw2tRozXXUhH4gBt7xarMVaFfCBwdjSfLFG3YTHGKXWsYVR
DepQIv3WJ8VS1ESJS4yiljjWa0yzLasmffFRzDzb+SjSkdDbomBX7nvM+ZNRh1yzQSFNwmVbwsVN
fuVbn4jWCvSgwL0STwACXegGU1DOh91cNU3YzgWCeWDOQCEHMFgVMNDTKzwckcTCjiXJQR0J/LSV
ckAM8AQyTPiAacMETGiGNJDUSR0m/617FvCUhg6w2WXA2WRxn4/CSy/Z1VHtrvOwHS/BmpHQmua1
j//0kgnbKBlx2lpNq+v6CKtsI591Gx/wgT6whU9YX/ZlX2I9X8I4kx3NGn+gy9RU1rItRcSVywt8
XLA1zPp9V5TwoBQEYGn0CQ/iL8Kb3LG9TAP2Cdq80dckCrz9iP1VTfm9RouYVteUxsI81wyG4P71
CrENFApQ2DHKhEtI2IhtYRd24W+4BFwQXTvB0/I5BAVA3Z1Th2bwANT108+bhcdQXjzpq/AlCsOY
NiqAQyvw3ZalVCvzihYwByMolokztnLInOylElSlFlIVDiNoo2BCVy/ZVvSADmqKVf8DWtAqg1oi
U4gl9ZIxQF650bPz7QMVsAU2+AQ2sAUV6IPz9YGDg79L7IBEG5eCTMUWKEZXjLx8xV9c9KV22jhx
nOTZXLwGAEihiORlVDyU8EV1fMdN9kdLjkz5A4AGmyYGDsgGENjXfEZJbgCNquRg7MdYpuRaNON1
JWViFIpTxORSFlNMToEz6QELOGaxjeR/HFvI/WUDOKqNO0VlbCe6bCe81GU7WWEg4AFuyFxthuFv
AIJvGOdxvoRjmNhDGQdhQ4LT1eEdtoF2/mHQyyyF8AOyw5PGUVSX7IXds4JZwAHs6A4noUNAlGIA
qGJpEDOke2OBEBMvecR0+2LdULz/2SGKRfSS+T2PM/ESdx2gAmLjz7i2tGJohTCHNlIGOo4bOw5k
lm5p5nSJD9AIX67B/lvWoLDpej3BIaRSnRa5CWCIbclpmCjFEIQJnuYJoghBEQjAl5i0fn3BxRUq
nbbGoua+ouagnSjXihiKHBwUgsjqnYYIoHaJBlSIHNzByKOJhQDr6vtBkwDRhrBT/FC5iL2ETGgB
HriESyBnvibnvf6GY7CAmyMUdS6Zf2qGQ6iBHM5h6fwnG0BsHVYAgnJJksXnNSIKAginSOADOWSM
4Bkkgj7iogC3Km4AE6uAyx4J2UGTiIZe3TAE6z27ofiu8djKDMqHMRGBChoBDUi6/zYW6WszAZKm
39yW635Z6ZYO5EGeLwHGF8dj7nOaABQYZ2y4hHYShmPQa+3e7u3GhjHeF3VWPQ9ohsVWbPM2b11D
gpUFA4xVMQjIsc2hvSkyrpHwg55Zh3UQpECKs8/omdpViFwIHfrkAa8Qko9yyDE53tYZk/IViFwQ
hi5xI38jCmFoow+4BebMhS32kgfl7aQLaeD+PeHWjY32kkkY7LZhBOQWZEGD7mqVW0N5bhdfJALI
BUOYB+yOYe++BG94wuzW7mMIciG/BGw4BhS3kz1oMY1Ng/Iub/NGyfE+ASlvhsdOg/cuCvvOgB9B
bX3O2fairMS4qWFCqHIjDHKwBv8jOMoJ9wk/aC9S0gVk+oAOMIceqIIWCAY8z3M93/NgkAarwjJ3
qGI+Bztq6ABXFam88opwaSMdXIQlIIdc8ARJt3FH0IXYppOh2BwDCvFrKwcRH+6hkF47+sgZd6F8
3TS0LfVGIgBDwAYLCOzs/nELmAdc2GYgeHUhF/JjPmYiQGdCyYUUqzFcQ2wFKHbzXuwcRskaOIRD
AIM0OIReYL3BQG0aMTZQ99SfDC67+8rPGJIDN0VrIKoqKLN/2Bz6HokjyC7BykSpVXd394cx+BbC
yITsGoNivETBGoM52hy+4vSXzWfneC4LJ3VVb55TRxQZL3joyYV5sAAiwHVdx/X/JaCAWr/1Xb/4
XWcGdn8XAgg6XAM9Zy92kRd5xVYAFbvCYs8CaR8MP0CEvyIA0Khde/7JbAdL4Oax/x4JbOgBdqoC
5/0Irct5C3z3q/wILCN63zAH406JQ0f6MekABOOoEPd0mp/dLicMAmh6KvkAGlZ4t7npd0l4r1ce
cjgGZnh1jE97XDAEQ3AEIscGuI/7uGcGIiB4JMfYnSN2ZC/58/bTYh8H0UXt2DCoc/dDfQuCqhdp
oDSGJdsNFKgCb9AFaRC71C4KT/gCpx8PlDv6zDeHcIgPXTjAzDcOcehi2HUc4Kb6qmf8+PAEU/US
cej6sZ992ochcrCAJThmud/9/7jvdUMgh7MnAuEf/uF3BGZYev7whHXYU9BLAyYfeehnbNBTgEMg
BRpu+WfhGSIhCj8ADcT//p/smXL4dsz2hmBgJ10gJSER3XA4B7UZfdvYfPiPDqNEfqPgAfEa/Q44
BrkDCEQsymUgWO4gwnLGKvxr6PAhxIj/POXwZ/EixowXJHLs6PEjyJAiR5IsafIkypQqV7Js6fIl
R0/HcGEjgu0mkZw6d2LDZYhcipyOhhIlmiIFzJJ7ajBtWgPMIQVSp1JV0PTQOJPIEPlp6AVRuY5+
ghgzxoKF2QwVRpicEEyXt2DCOH5lSzLXpSr5jmTs6/cvxnkQOwAubPjimCMdfP99m5CUgq4Okw5T
PmKABzmPyLIgKuv5M1oTDFdOmEzZXw7HSVezbu36NezYsme/XILL0U7cRHAXHUpknqEJFIgwK27c
uCMKSGlD9LTOqtNDabJUrV5j1h6UBR1+zdCV7ghkyEaM+G6SgjRvmVrg4mgsyMpcQYVlMsLNGjVz
X84Z6O//P4D+ZfaQNwEaeKB/55hDTQ/S6HILNhTkIhsBFAARjDv5iHOECMr4pcwkR4jTAQANXGJI
SH6UUwEyFbjYIowssujSBPwh+J84DTC3I489+vgjkEGKNIEjuOzWmyPHHedIOEdRwMwSUUopJTMp
UODJj0sxZZVUaRxCXXVSZUH/xoQoEYCIXf/4kYExyBDw2jHBZJJJMKpBVIExQurZIwGe5DLBn4F6
8uaehRrqUAo5KJqDCB8YYEFEKfTQg0cdiIACSDkYAJKklHaEggib/mjBBYoeihKoop66WgrhLFEc
lVPKGmU4E0ywRArz6KorLrjoimtwPxLwHJc1KHBIVGBWl8UQhKL0lXn/jBBEEOP54QcB2TqrEgE8
6OItNNt6xdWq5Zp7LrorpeCPCJP2QJg/mDaUwgUWyctRRQBkmoNH9NrrEQCoAfmBPy3cmy7AAiPM
UpVQzrorxBB78mQ4vVp8MS4pkDOgj3tIZexUyFKnLFVZZKfSCMaI6wd5I3hx/y22LRliBA/QBMNM
RH4Y48XCPfv886rr8usQCv584FALHbSwXEcWtGBnR6Z2lPTSH03QAqQ/Egw10A9dnXXXJVW5K8Zl
XxxOLrlUHA7bbbsdzk9AEgBJmMkqMLKYd5PBEjLliOsaEUZAYzPXfrCQZtiJK7641ylgI8wtkd9y
TDjk/C2R0A9l3prUjDfgj6qMiz4Srhi/zTYubuMiYS4UpN7kUbHHTgGKK/UJTDb46J4NMIOCtAfJ
d3+JN953r4PlStNenpQnPGSyiDcHq1kOz6Nbf/25njhSCffde1/JMWX2q3BDEyicgqU5fKDjP4ku
evQ/mjq0KKMXgF3Roh2A3f++AflnTX9q4qcqC3QAgDlAivzmp6oU9E9R+msIqejHvogQbIIcaWAO
HugQAuYPggV04LwwqMEILkpHJFQU+xiYP6Yl0H2Kgt8/UHABEeTgAvJCnwQRxgzXne50rToKLsiR
NuXIrohOooBKPJGNPjigiU50gQtUEAN89K4jcyPZyLKgReJpsRccU4kXKhAt1qSgAYtAQTCQyJ0K
VA971stFuNyoJwKgoAFGsKMR8qjHPDagEuLjyOb+MYGAdaB9jUKBBQwQr/axqwE9EAGkOseoBjSg
BRX5nwgoaclFGjIHDbCADP0RSX9U0pPxG5oFLFIiSorAHwgcWkOklgIafjL/lKPsASUbwLWGKFIE
ItjlQyygyUtCkF0toCSkUimCY36yk7Ws1y1z6ZiK4JKSjpllDo5pSREsR5aNfCSkimZDAoryHwRb
pS4RtgRDwM6I7jxK2lrnpHlSQDn2ZFpJPCGDRAhAAE5sogscEFAoRjEW2fAdRIDHxS0yNItZKIZL
/ICMNq6GAIt4nvOcFZ7lfYQCX8hHPs7xRdbMowofIQIQepSLTDwkE7WLYTBsZwCTikQYFuwIOXhA
tJh6BAU4OwlmGkKEBQHAGnoigi8kYYql3rEBN8ijKVrgC1/c4iOZK6BFLoAUwtyrhowcWgowJUlY
prKQpySaPzbyD8JMcF2b/6oIUiagI6kRpgUPgetZ5zc0tiIKdOZzpUc+V8gLqBUkqVQrXx+SWIcs
1q1/xedjB8PJGPrDrN4EK6YIthzzbaqV+0OYIerpTiLekwLA8ZNwrFTP1bK2VWosSSr42U8HzPaf
AhUoQV1giymmAnn/IMAQsni3hhI3C5qAics4qpIyouAaRghHQ1hGUZJAo2BNWgYpX5MCI3xEGvri
EQVg+I8LQLch32DpStozEgssIiQWEIdDzvuRDtx0JOLIGjm+IYIvfNZHLbCGJFqw1AET2BSS6IFR
x8cvRzaAhaTMJaO+CpGxPoSGsYTlX6f54Fw2Kn6A1WssPxziV951aBXJJf8rj0YYEQAAnw/ZmiHt
2jQOiyDEXKvIjTec4rWyq8WM7TELf+mQCVg4r4EUZCM5fLSAgc7F5yIAM8hhT9auVrWmTUHaPCEc
KnM5VyMFCQFk8IoH9LPM/vTnPweaWxdgAAMqMCgwBIm3XgS3uAw92Uv88DLmQYMH14CGN96k5zGO
xHzlNa87HEKACaDgGA/hwRfMgQ2IUOAc1tjWMgyg3n+0jkDnuAbRLvAB9CLaHNz1CDt74I4l/OMS
7nAH1BzxUiIgzxCqsmQH1EuOl/6jBQYgwpApQA53fEHGXrPGMqzxx9/64gvu4PWuH+KJZXzBGhPA
ckPmoapoI80AjnCILo7/0I/98cAd5pBeRAwgGIeYA9h6WkYPJCHvedN73t34bkeOfFfU0O9o+qYw
iPM6Yg8bcCN4DfjBB965vOIPgGrtQUX8ge8SI42bu7RAw/E38H27OOOLenjE8Q1xVV54wiYGK/kY
ye+PN6QBIe/ZBOYhZS6v1hCGKFI8tcza0IaWdrRLQZRJwog+PKDoAiCzmWmL5jTjNrdt3i0+INAL
OttCCZGw8xbx3JI+qSlbLyGCN64hDCMg8VoqMYc5PiKCSbj7H1+4AA8aMAme/oMcR1jEB/LhEGLr
wh8DwrtDjPABHvjjEg2R4eAdUoUcQAMF/TArvvyRxwvkwwCODGBDxHFq/3OqkRwGIJQlNd0Qa0Ce
9N7whxrXdQRpQKMDH3BWCsbQAmH0QBkv9cQRzLGIFvhDFw5ZxjmGPAl3QMMXk1GNth1CeodQowOn
V2MDxA22t6MAGjmghkfU/RADgFpPtHcX+MM/qfpCRN/zE3FfYVny9TekyAvHK44lknCG+wNqeG2l
naQW/6lVBPLzq7FDiJqjQATB3I+J1d+EIeC+ARPS9N9DbFIhMYqdENnJzUvKmY/6RYTLVRbMEYHN
2Rzt2Nyu4cI3zEM8pc2WfeAHhqAhBAWvfQQwbEMRFB0NHp2ZnZlt3ZbTsVmbtZkSVJ0SBGEk9IKd
9QJEwYSfJIUhhJ0w+P+ZS/QDqFXIauUCoRDAEXAMNADgRPhD7aRSQ7zWGOhU2jTEJUAeOGwKAXAM
DxjbLN3V5kVEDqAXLviDQ1SbQxgANNzhgNjaQ3zBS7UAvi3TRKiGIaCeQ3xAgv3DEXyDQ0gDfDVE
B3yBQzBDNwReInIBvgGBP5RJ8jUEIDqECEjDICpf9/3DIqjfGLRduq0bL5VikJCDKQAANcgiLc6i
LQKAJDhZ+aWcYmXXLmYgwP1DWbGfh21Vwcgf+tHVMZ4fUtRLV+3VMnYEBUaEMw5ZK/mfwOXVYkGi
L/6YsXHENHqNhSnSvRSNqFwWAZaTNBbZwkzALfyGz7nOMSyCMFCArZz/4ASooD6KYApYwAt2RDa8
wgzSIEHa4A3SVg6uGQ/2YBA25A8SIXGtw7K1xBi6RC7wAD1eQwNMJEqAg47kgn+4Qw6cGgF0gPjk
g+/tXSU2RA98AN39AzNkkPh8g6pMwAX0w2v9gzR4yj80wAe0QDf0QBVgYkd0gBoZAvY1RDAk5T8Y
QHvxUu14nmK13SfOyxHkg50Q0EOEwxE0hCdMQgtMSjd0wxG8iRUyoBEkGO5tSz6oUSf2Gr6lwFVC
jakpXz9ww6S0gDh8I0Ro3x26IpAIhzcAANoVpmG6gylojFXxIqL4UjXdEC9KUiZRUgESI17NEujk
0v8kIyqxSzU1QCsh/0XRZBMrgVUrWR4yHV4uKVJhoRWLTUq9cGAv9oAF1GaRKRMzJZMxpSZmomYz
xdBqphVwUhJrdpI2+VI3oVwGjmZuQlBwtibC5AIoZYIu2FEDoMA6bcw9ouA+7tpP/EQKHENOckSY
FYF5midB1iDSHeTSAVTTsdlCYkAQyucP1tkWIQIZKFdKBAtLEMA18AAQAEGDvUT0RYQ6EgAXcEwH
iKJDnMM3cmXoEAB2DUgZQkQmFJ5DBEMiegM4UMBN1AoDrtW6UUCiNYQvJGIHpBRUNgQf3uGkeeLE
6aQh/gMRcMFDMAP84F5N1AS3KeI/NkRaemUO+NY/iEPtvGVVIs2M/v9DXY6eAThOhAhRR/hlK+5J
LmzMElSCJADAOXSpOSyDLhCBdlrVwpUfBgmZ+5jc+SmKCNhPwF3YcjDQB7wPnFKcB9GPRSyHDNHQ
oiCKAczpCwkSn6qPAQATB9UPCgBADhzMIBnQBn1QBt0pCPEPoKqPoL5PoVLgCxVqCC3KkwZcmkLE
oVqqOWFqiJqLJ1gAERzDMTBJzWknoGiZCO7axtTqxqTAJYxnROSCDJ6nrw5kehpkmSGkbakZQfWg
Dzrk1d2Za6TAqYYEAZxXgHqD4cHEJEzciChaP3AMNvgD8oTDJjZEFfhC3dGhINnoP4jAqX0D5HGB
Y3SA3nliIpaGnXT/wJc5BBew2j94lOIxpQF8VyGWiSH4nwb1WonmAroewUqSgz+oaLoa22L8Xkr+
AzXAUDCoylLWITgonrc2xBLc2sGiaw7QlNtt3jxMgkN4QgcQaV/+FC+hm48smq3O7Mzqp2uU6Y7M
nxztbMweg8Okjmr9hBB5QjgQwQTQrK1OQDh8g64+RCoEwK/66gMAa0GuZ9K153tCEQbEp7ISISJI
pGsQwDw0rUh4AhBkAhB8g5/ZbEnkwgdwQVCKQ4R+wBdVwQf4QjdMQrX+wxwugziQ62+BQwf0gDiU
yTX0A/ONbA681jKUKBnmwDJwwxHEKESIw7e1T+mlXfkgIjd8gAjU/9rGBuDedoOqGMAFdMMHqAYF
iBo1+MIFhI4niIM5cMOfQg0X5IMvuMMk6Guvae5vjYgvmMMHHIFqEEHo/gPpMhY4oG69fmO4ccMy
TAKDcgQ4XG5DgINO7YnMIm2tTgDbck4G5iz68Sz57giUwQrQ0g452IoheIIJHu36xu/R2gou1CNA
JkHU5i96pmcNXm0OvufWImuy2gIR7kJsLIEFfK/XoAAPfMN5oQDLvoQFcIM0OJkhiAsuVIE0cA05
VIHDAmkV+JYnfJEwVAHU/AlETIA0VMGhcQQ5II+WDRnUeMIKS0gVftELy/BD6EIIO8QxAAABGMEy
OFpEQEMV5GFEfP9DFRjBtqDwQ6BAFXgDp8Ewx9jKDvewQ0jpQ1CAVP3oQ+RwFnMkkGgZ/HbvBERw
zoYvc+hs+bbxbAxHkQQtBdTKb0mIrczv+t7xtaGALhJAH7xAEbwAIAOy/s7gDDpAmwVUPxkdeyak
0yFrQ9oCBKAxq6AA2UoEAYQDRjqwNwABJbsxwghDV4IyKScFzq7x+JayKjMPOeAClKwOFTYEAWCZ
HtfyHX+Dk/GqIO9yIBeyeQoABjjAK7yCPxFUmVktsTLdmgmwC9xra0zAGVmOR0zMNWSCMFzCNYSp
Aq/ynkzAi3IzOJvEKdOGouhiOJ+zmfxNJpOxLf8JoAgbRDztLs//cy8T8q8KgAu8wjwL8is0ndL5
b7Hu4NaqgBe/BjMIDi6csbYQwJXOQzVfwzcIgzcswiWjs0VfNEZntEaDVzwBynZ6dC54giH0jicA
gwzYwQug9D7Tsz0XgUC1NHqapyAXc0D987A6MkGpQJz1iPY0QDCEnQMLAwPzgDAIA/SgAC588kYv
NVM3tVM/tUSwDqCcIFXngg8kQQBsQxKgdBK8QFd39T7XcyA3EUyfJw3K9AxibdIVq0DFglLLxsSA
kjfAhXrwgJ9FyFtDtV7vNV/3dfnaip9UNVXjwVbbQRIc9mF7tWKvNCD3swD4slmLdVoX8//WtApk
g6H4ya6p7xn7/7VnfzZohzbjTExgC3ZI+0AAYLVqIzZiL/Y+97NADjJkF53+MjJCHt0ryEBeizZv
97Zv/zZGh0NpmzZhB0BqpzZrJ7dr9/PUBnJZQzZ0F0EipAJwV7d1s8YgVWoO9FenwESqcMqkNE2p
qDHCfDcZhXf75ADluoR5l69ID/cJekIqvIJxGzdWI3dyJ3ZK+5N56jM9Q3dz+3Ju7/Z1F7iBe0S9
fAD4QY2/TFZLBAx5z0tswmxDEIzBhA2Es8qEW2CEr0SGu3EKeAJ8xxMe1LeJ33d+I3Y/mWcsJAJL
C7IvP0Af9MGY/eoDbIMMMMKB77hve8IcMAEntAICtAInMIEbEP/4umihRFCNOafE18QSNvaa0jS5
OSngbERqSmC5IGHNajB5+qGElkvEk7txJjM0VXsCapu4mq82Yhv2ir9ANpCDSq90L+svZpd0NsiA
DOBDKgDDNvM4oG+0G3CCGAyAGBz6oRt6K7yDza5LKqcxSnxO6MTGOItEpWsXY1p6h69y65h5R5c4
qKv5iae2HQSAA0xtEvjAP8SCa9P5cyfCnwe6rDc1E5SBrd86rt86OuQ1wSwq5ogQ2OypouhLAsXS
OdKPamgKCkScomQNqdDQBZBf+ZyYRxiQBgGQaqiQA+kps283//hPqPEpACy7RTR7sX/7tusVuHPE
s9dQCpGPsNv/0KPmD7nzG8Yhu7GHO/0g0KQXe7xT+J7smqdbtaiXuKhjdamfunTHmSfEgCCDNWPX
ua++wE7PusV/titogRNofK7behdsvBMwAacQjMSVHy2BEjRRFmkO6PsdYCmxTzmD5mQentEgEjlK
hMyzS4hOEiUBgGd52MsbZylxU/vIPCU5E8qXE3NS0lEY/VzBEjZpE6N002RuEswWzQfY/CJtjjgh
EmHo5jIhUxn50tGfmCXB/NB8zsqHZjbmVdeTU38ZipX4iZYZvHEbvN3Xtx3gAT9N7TaUSTYIgGF/
NWPDeEu/AHVfvOL39RokgBZoQRlAvhN0QRlM/sZrQQLwg0gw/5mvc2NbgU6Vf1bLD5xcrd/Cadb8
QCdlDZZw4ov6FU0EAlbpcxVaQV7nNBboV6aash/t07xlwZI4SQTqx9JGbM7wcxaP1ZckyT7aV7g6
FmPbS83xg/65EAHaoLmJ4/3d332J930R9IFvtbhyQ7yry3RFLz76Y3Q8rMDjt7/7a/zjJ0AcrBfJ
w7yOgWbqsgscqp/+AYS/FP8IEsyRwyBCghP8iWjwsEEOEQULfvA34V8KEf5aUKR4kOIEEQhzCPwo
AuPCkQVBGvQH8aGIDwwnevzX8qbCmygLilSIk+FFjzRhSszoDyFRiDJvCvWIs+TAj0kbfjSJM+E/
pTE/2PT6Ff9sWLFgHeEyhCdA2rRoA7DFgzaRAAEPHvQhUJCACgd2kvT16/dFYMGDX6QaexhxYsWL
GTd2/BhyZMmTKVe2fFkxoASbOXf2vGaxgYYYSx40neNCCqQ2sbaM+vSnTtVIT3eFXbBFwxQpp95+
zVJnVuFNTx9MvZq1TqjBcw5vKrXg7OJdVSOUfvrC8+QsTfaubnUg1ubXTWfHjBlXOjyv3rZ3nzau
3AevstlU4QLP378vkvAn/KKIJIA5j8ACDTwQwQQVXJBBzN7hZ4UVEohQQgorXOERxjayoCneeqrK
o414c6074IZjiDmvjCroAn8+mOm2nlb6zSCeVFJOOadCAjH/xuZq5M0n52hcCDmPvkNRRR1NdAm6
rGgC7x8Re0OyQcoMyeaV+V4JIJEAXkkkPvkeSMQwj/JyIRG+9AOsv/+28aTKOOWck8467bzzMTeY
iGeFOCj08894wnBjsdkw6oAjryzikKIWUVhySB8l4m1RsRyV0Z8OtisIhUy1K0i0Rwnq1ACWbES0
I5sqfcpGnELl1J9SfWRSVX8Ypei7f1alCNEGWGu1ROF2fa1FX5fcFc/EPElHrlfkevbZBwRIBB84
vYoFAwfyC2BNNgnDJ9lwxR2X3HLN/WoON94BJB5VoIgDXihUiWcNJtwgNKwJeti3BwA20jSjjQyA
iNFOc2jh/6GBDEa4gZU+XRLRgRVGimFRPepUBAD2bdFTViHqYcOHAz64gRZEEAG6iBtIQaNYCR6V
4oQJUjkFnDQi2WSUhQwWZpIbEDXXhR9i1IKGGGaU5khbasDFpUwqOuOlFBK6gVvP9QgYfMKENpEY
srH2K3pcQNMObrnttr82AzDk6rbdfhvuuBfz5B11mWC33Xl/eaRuN84Qy4LiLkiVoBQM+MA02/5B
4YKRcgBg1MZPS6hJHycw4KAeCLKgA9Ns9Ijzg0S4AAUAcrDYpdM6YPSgyg03zYAmL888o8MT51Ty
xxfCPIcesHr9oNiXpNyr0EXHqGadjM9B8eUBnr331ntk3P9xf7pb3rSClldcbgKASSUbfLLJJpVc
DptgbAfaMhvtvl6wIxa55Z+f/vrFPePe/PXX/2/7LRPPf/KLVAALFAsHuEB9ZVNLt94XA7AREIIR
lOAExeKJdO1Pf564CwUdA0AOmmuAH5RMLvTiAAckAg9lS0Ja/mIHO8TAfCKU4Qxp2DYCeOIMF0zX
GR5Yw8N40Id3CmEQF5MKB8jFhChMYQpdaAdq9ZCIUZTiFKkoxBRVMU5DxGJYshEXaR0QTGF0QAzY
tkUznhGNaezgFdV4IOm1USzASMQrilCEB5jQhCpIBxTh2Ec//hGQgRRkZQiQChls4y3b6EM6/DBI
Rz4SkpF6lOQkKVlJS14Sk5nU5CY52UlPfhKUoRTlKElZSlOeEpWpVOUqWdlKV74SlrGU5SxpWUtb
3hKXudTlLnnZS1/+EpjBFOYwiVlMYx4TmclU5jKZ2UxnPhOa0ZTmNKlZTWteE5vZ1OY2udlNb34T
nOEU5zjJWU5znpOAAQEAOw==

------=_Part_55_708591777.1373278363128
Content-Type: image/gif;   name="info-HT.gif"
Content-Transfer-Encoding: Base64
Content-ID: <A329FF1E03AC315071306B2F3E639856@edox.com>
Content-Location: http://public.edox.com/COM/Emailing_2013/03-Mars/07-03-13/info-HT.gif

R0lGODlh8AAjALMAAKrV6hGKxO73+0Sj0YjF4t3u98zm8jObzVWs1Xe83Wa02bve7pnN5iKTyACC
wP///yH5BAAAAAAALAAAAADwACMAAAT/8MlJq7046827/2AojmRpnmiqrmzrvnAsz3Rt33iu73zv
/8CgcEgsshaBQorQCDIljAPBBWhKHAsJwcHlHlaNqRGFcIgfAcNjYeWkHwYGjb2JPwoOQYo+YTgm
DnIUgRp8HwxqN28zAg4KVmUBTA4NC1UNDQUAlAEHBZEEAF8FA5hym6YXBAENCgKllQIHrAkSAg2U
CwyYAA+bAQOit5SzDV+2xbW7DQNKDqwNDMOVUH9XgoDYEpcNBrjUa1ZJqJ3Oaqu4AHx03AULlMyY
tb68vvByoDNMeFkPWGt/BAToxWCAHwkIvvw7OEABwAIH3ymhwA/hgHCbJk54R+GdgIME/yL+MVMh
owQ8ahRcJCSRY58uXLT50yaQ4ACXElxiOfgg4UwDDtQEculx4IOCHFHiKdBogbejfyT66yfjQK0D
CK5k4bhJDx6eBxeOFOQAAM+yFXiiIXtLUkdrgOJYE/lAgQMEemw1cLup2swr6uBCzVaB0ISud7AI
1qlr7tizDIiWzZNYpxwsff19tIb2nwygMPX84+gHkynHUwcbLgs5LdxnpgUIWJU1pzUEmHaidlkl
QN4HswMgyByWbGTBag0Tfmm60mLOjf0Ggiy5tGnLU6032HwttYwExxrJCZAFqACgiQYPJj+44cPW
FD03mEchM5w8QLWCjQq3aUkHKNW1kv9x5r1EGAH9KHdfegXaElR2qAWC3kz+vTOhbd1hIZVff7En
QzQTDHDRKg4NEAADTJiSWV8k9kVKPZmVZcgD6ChgwAGYIGjaGQ+YWBArmFnTF0c4NlBbODnSw4wz
vfjTi4/bvNZLGIBVkCKIUEIBpCVCjtRLioQsE8AfVx5X5T8pThHjlwE4NMYJBFz05pwWKEinEQD8
dieddu7p559CoAXooIQWauihiCY6gmf1tUHPDYyOMWMMBSjA4wqRakBlDH2qpV4NfRKBU1WuvBDq
BYhM+oFbPU6xTC9h1mOdJwe9gokBtxgzCDRy2LokH+M8I+dfl/SSAC0U1OhrM+9gAkv/Lc3Gg0kW
r9qzlydw4DgmcLDgiskxV/AKx7dKHDtfrscUy+20siArgbkJrNPEMwB21w4yyAb1jSWmaaTBI/f9
5pFyHvGkwAEHIZBVQX7o+ZdHA9SGwE3QgZRNU0+RFF8/EVuUVFBLfazGLhvlwZNPBzjEkcJHGUTZ
IHJ4NIFK/ojRsINONTExRvUOIoZkPyUojVEFRanRUAERPawG/CRw5BVAaRPUfgedmNgt2C6nmCB+
MObpTDEKYBd9nxrWNWeXLYDdqFNHGPMfVuOBtb+rUYVEXQ7UMrc9VwjE1l48jg0QhgoGghgeerGK
tD1eCaZBQx7ihss7+OQWHVRhQdOE/wAI+KY15dV47fh08GznCzAGdgcVdhqiPbjkukn3tj+aA9f5
b3WnuO3pF3Hum3aNaC4bbfUBA3ThDGjXRnBZLa68B6hIkN9UElZszcEHzVeBf91BLPEAjQh1eTYb
HgZXRT1+z7rarltovV8pD649Bdw/nMdocGXWVPnz1+d4V/j7SzYuZIG+VO88DwrBpnq0JbSYaHKo
MIYm/nAjU7ABdYAQ17L0wIAt2adKaXqAtsimLFiATyewYl+VOPLAIEUpW3uhYJEis5elwQZE6NjW
CC8opxBWMAxsSJIERngUTGxLUCA0jSCCSCUHnqhMYziVokggxSm+qYpWBAEWs0gEJBxysQRe/KIY
x0jGMprxjGhMoxrXyMY2uvGNOIgAADs=

------=_Part_55_708591777.1373278363128
Content-Type: image/gif;   name="mail.gif"
Content-Transfer-Encoding: Base64
Content-ID: <00EA6CB003E305B5DE6907925BD50058@edox.com>
Content-Location: http://public.edox.com/COM/Emailing_2013/03-Mars/07-03-13/mail.gif

R0lGODlh8AAjAPcAALW6vaaprMHFxbm8vtjc39zg4pGSlcnMzdXV1q+xs8XIys7S1d3d3qqusNTW
2eLl5/3+/+vs7bW4utTY2tre4NPX2aqsrvLy8tna29HS1IWJi9jZ2vr6/NDU12dpa73Awp2ho93i
5KOmqfr6+s7T1vb29rCytMDBwvDw8Li6vdba3JWZnZyeoJOWmZ+ipd3f4eXn6fj5+bG0t/T19Pv8
/srO0tbc3+Dg4OXn58jJydHV2K2vsXZ5fMXGxszQ0/n6+tDR08nKzNLX2vHy9O/w8czNzsXIzMXH
yOrr7Ozs7q2urvz9/q6ztuPl5PDw86eoqc7R0szQ1NXZ3NHW2aKlpo2Pkc3S1MvP0ISGiff3+MLG
yvLy8fDy8cDFyO7v8Ojo6Ly9vubo6H1+f6Kio5iamtLV18nN0HR2ecfKzOjp6+Hk572/wbu+wbO2
usvP0vb4+PT29+zt7+Hj4uDh4rS2t8zO0sHCxLq+w7K0uK6wtPX19vPz9Orr6+fr69re3tPW19LU
1cXKzr3CxayxtKGjpX6Bhbve7ojF4v7+/iKTyBGKxO73+/v9/Ga02d3u9zObzfz+/arV6kSj0ZnN
5lWs1czm8ne83fz9/fz8/Pz9/Pv9/f3+/f7///79/fv8/f/+/v7//sbLztba2////tfb3s/T17/D
xr/CxP38/Pv+/cnO0djc3fz+/LzBxMPIy66ytObo6v/+/7O3urq9v+Li4ZugosTHyObo58jMz7vA
w7/Exvz8/f38/dXX17m5uba2uHJ1d/7+/dvc2/r6+fr8/fv8/NLV2ODj5uPk4/T29eTj5dvg48vQ
1IiMj8vN0Pv7+9HT1ejn59HW17KztO3t6/39/Nzd3oKFhri9wNPX2tbZ2NfY2eHk5e/w79Xc2+Pn
6NjZ3MXJzfr7/ejq6mttcOnq6W9wcsTJzL3Bxr3Cxr7BxMTDxMHFyMLHy+Dg38PFyKyytM3Rz+To
6u3t7u7u7e7v7/n6/MzS07K1uLC1urm9wLm+wbm+wv39/QCCwP///yH5BAAAAAAALAAAAADwACMA
AAj/AP8JHEhQIKNM/RIqXLgQkUNECRHF+geRocWCGDNq3Mixo8ePIEOKHEmypEmBlyxe/PesxIxk
ey50Q4FiSxZEFFVi6neyp8+fQIMKHYqRUUJIKj/9mxEBSZw4fb7Jg5UmDYw5wqLxVMmTqNevYMOK
9YiwH1KG/0ogmxPHS5pjBHRMIUXghRoYMKDlSPNP5di/gAMLHrnTIk4c2sZ5+Uaqw4IoRsIx05FN
xwIpakit2ZBz4eDPoEP/LewZAoYyEcaR8nEuBT5Z+BIkMCEBzZRSVgj4wQOtr2fRwIMLL0kaE6Z/
xRRciaBGRzoLDY7cqLdlC70b655YeFenDoFsLhj4/044vLz58wRJ93N4hN23EFEGUUEQQ2O/G0p2
AOlAgE2VPRV1hd6ABH6m3j9F0BFCAVCwkEAJFD2EiFKf4MQSGEqA44AoLZgwXoEghijWJWf988AO
0BBQCgu+CDQKIjERQQQXXGwxxB6oCETHNCpMwEYhRPgm4pBEAgUJUpvE0MAaolQgwi8ULWWNXQSo
oAIpc3BDxx4C6UHGARNYUcgRQhZp5pkhlfgHCNJUIAEZ632iRxEUhGADKXQRMIEOT9zEUw8NkJJN
Cyz8E4yAaJIUySEcGeIPJQVVYok/lPrTSCQj+ZPIIokSlJJZAcDjzT0GiNdJP4DUucAHpwgwyx/Z
4P8yDSKn/vMFCFJMIAIWI/TVaUmUGrKRo/4Q1IgilnAqkCWKNCJSsL8KhNQ/32jQxSoAPBElH2U8
UEoDCFxQwgZFEBDOB0LGQIUDUrwixha+RivSI4o4MiylA0nyiLIEOZIIoyBBG20ml/xzQjMLTAAC
Bn1BAEgBx0iAwEDIlFHBB0GMx8kTzgjRxhnRxCtvUMQKdMim/0TyiD+PUKLIP5O8HLA/wg58CSci
sDAFMy7chMgWCoQgRAqoQITgAmWckoFvnTDyBBQVAGCOOyKTtMixlE7yz9WKaAowsZRSMgmligD8
T6X+IDspssouYkkimjbCKdoAc5312ShXUikllQj/VPI///6jN6SH+CPJ1jRv/Xbcyp6Mds2ON7tI
4fsusnLNBDluqckre+032mKHba9Jm0DwhgENEGDGDr7KEQoFrhzgGyI5iLLAAAyTd4EFqyzABDm0
VD3SypIccoi9kjx6yMqMEnsIJZQa3zXAlDayvNdwA5x8I4Y0snn1lCQiEPHG2yuw8dCL/0/JjiIv
s96MLuIPptt3v/mk/xaeOOXPG/4P9I2AntkGgj/jCatwZTvE9NYXPej54xDJO5xJMgGKemgAAAUw
BRh81QsSFCAX2+gLImJwBFJYQRY4EBItEkABXLiAHNQQXkj05g9+OYJSnIqEphhYrLP5o29jUx+0
/3T4siAKjlKRMETJoHWIRdCQXz6s2SKUSKm+lSwSMlOEBMemtfbRMIkl65rWogi4+SHOH45YBNz8
h5GuYWogcBujDsX3tyreEI0muRkOeCALAgzADr6Khw8oMIs5+GoeaOiAKvDxBSEFQQATMEUzxDCM
USBKJH/7XA/Zhy8y1jFxnCwW2NBGRk0WhIloAyW+YoY4SP3De/ZqxCN4mMpSQktg0Bpb4jAiMIEI
LJS+TFwvR7KJfzThDIOYwB99JYBwrEIdyvCVNaDggyng4wYifMYJGAQAcoyhTCR54kDumMMdflJY
5+ShOu84uoH0UpzuTFzX5qZKUeIxEbMk4j+YZf8vdhZEjMEUFtwwJT80LqJraeNXJezlRoLEUSBG
TOcwRVLMW/CgAdloxwar8Y8BmGIZtrCGQMIAjQmoghmnkABPMIEBB4SAHS7wgHjIYxLyHe8fyaOE
45rXSWilE5g49Vr5Sjk+ww0VWm4kFjo7+QhLpKxrj9CfJPomkOTl76ZrMx4qoxrBoB7CexLU28sK
eIgDpk16D1QnGScakoJxgQcB0IEV8sABnNhCAhRwwwEu8IUFdMANC3ADCdgABSTMoQBqqEEKgFGo
ipzEbv7Qmt0Cp1af9rSear3aGtM6TMhqbYibxSwD31gQR7RTs5UCmObOBzfJTcpZltucIxQxy3//
aM5ZMOvcI8Yo0V2SJBOIgIQGVtCBKewgZP/YgAt0IAUfGOMPVvABCFiwp1J0IBsUmEIgtGAAMaDA
N8cZGViwSAnSRsJ7AxTvR1gBiX88AQuh0MEsckARPbBAHVKQQgesYIUUjAEB6yBBKLrQjlYAgAkt
MEDIfqPer1iic5qyRDsb/BFGpOIfQDjDPm5jghLgBAGEQIMQ3CAAE+yAS+XowRoSYIEABIAQA5jB
eGhK4RqfhxGMAEUMrlELM/jgAz34RzGbYAc7SGAHRehVwfoxDwZkAAjW4NKMaWzjKgcHx4wwGA/0
IdgUAOEfEKDIBVDwjM5cohMYUciRSmTlNosG/8eQgEAMWgACM3RABwPYwEQQwQlOQGQTDEEEKBay
kyMB+pJuTvRfPMGII/0DGVXARxSYQeIMeAHNfpYQKF6kCQhY5FP9CK+iRz0WcdCg0TzphQFkYAYz
4CIUaOgFH2YQgx/8gAM/gEMSYDGBHjhkIZC4BIkyQepih8XUmijLP3pBhgawwxXnCIUPFqCDVRDg
O6WoAS5qMIgqLIREFmaFJmhg7HITRRya0ASqeWErQoBgAK4IRSDO0Y4uoOMOuRAEPwCQjxVgYRcQ
uQSWGTFucZj74EARBzGwjBBi/wAQ07AANnTRCmzIggkNYALGXbCCFuShdAInuLppQAODI/zkJk+x
hzgYfZCQt/cHcyiCLQYggwaIIABMkEAKFACOOEBgCZ7wxLhJXnJxmBzlSA+J0dE9cEjA2SBZIEJT
nJAFcYT5H5xYAtFJvvSlJ/3r/wgIADs=

------=_Part_55_708591777.1373278363128
Content-Type: image/gif;   name="tel.gif"
Content-Transfer-Encoding: Base64
Content-ID: <CC05ED65922EF3D704DEAD1EA7127AA0@edox.com>
Content-Location: http://public.edox.com/COM/Emailing_2013/03-Mars/07-03-13/tel.gif

R0lGODlh8AAjAPcAAL3P5Mna7RpZsilcnv78/Pj+//L+/yVkver5/l2Gudvt+vH6/y1rvKHE5vb6
/hZTnixuwxVSp///+P3++vz9/8DN3tTo+Z652GSQzPb///T+/+79/+Pu80ZpkhtWqRpZrvT2+ZOp
vBFUqRRVqRdVpkp8woeduBpdr0d2tixjrRdZrhlPqbve7ojF4v7+/hGKxDObzczm8v///lWs1e73
+0Sj0arV6v/+//7//yKTyGa02Xe83d3u9//+/v///ZnN5v7//v3///7//fz//////P7+///9//7/
/P//+/7+/P7+/f39/f/9/v/+/f//+v/+/Pr///3//vz//v/++/3+//7/+/3//P3//fz+///8//7+
+v79/h9ftPv///3+/v7/+vv+/rHR5xVYqtvl7IyguRpPm3KQqxhQo/v//TdxsuHr+Zmvy1GExN3v
+DReklaJtWmHsBdXsYmevzJ2yvD4+ytu0M/d8hBPqoqqw5q83R5Yr5bB7FCBxFV3pLbGzf/7/mOT
0TJmqv3+/W2Go1N8u2iWwsTT4qW0yrrU587h79no9XmXw/j9/LzX8vn9/tvm+fv8/K/Czl+OzCBb
prPG2er19Orv9DhywKGzwQ9SpqW6zff5+uv8/u/4/tHg7bTM4LPN6Hiat4yx2Pz8/ISZr0Vwr5Wy
2GeHu2WOv+jy+m2Mvujz/uj2/FV1nzRwwqm5yDp6zxdaseb1+hlbtBxbtS5Zj7/X7w9NnF+SyOHq
8uft9EB+ztrg6JKuzpquxmqOzNvv/eLz++H0+uTz/dPj9tDk9Nbl8XaInoiftxJSozdvvRVSoCZq
xitmwH2n1nmn3X2o1VCCwBdZpFSHx19/rUGD3fv//uHp7kV3u0l6vXKRu+33+6/F1qnE3BpZq8rl
+RRKov7/9t7w99rx/BJTrB5gsJa0zZ+1yoyuy2uZ0R1kvz9rrfz//eP4/snd8maGnWeKqd3u9hBY
r4mv2BBJlhVKmEeB1xZWrlF9si9kpmuTwzN10WiTxdjk7wCCwP///yH5BAAAAAAALAAAAADwACMA
AAj/AF38G0iwoMCCCBMqJHiQYcOFECNKnEixosWLGDNq3AjxIUIXHjUqUYIDigVg7Tb868GxpcuX
MGPKjBnS4UsfLoZcYDMNFyp3MFv4G0p0KAuF/nLQqNgix1AYNizGmEG0RoyBTZ9G3WgDxtAcLWB2
/Rp2JsWaA0G+LPIv0QBY+7iQ4KfhJYsWLXQMxRuWx48ZPwgapbjDHwy8L/zZYEH0xYyrCWv4m9GC
ao1/Qg/vSLyVoNCvOpZK9veCxz8bpPF63aEwK+mBjIc6hoz6hWp/rM1KRPsPJO+KN/71otesTqxM
2ILJjF0wR40dSwcOnpgYstAZd/FSfRG94FDB/v45/zWNeTLCH3y9XsY7mGrZGK8RFj7cIvC/GHy3
L3U/EP4L3bt19FtFQQShzS0MMKNCBNm0sdx3EU0XEXzhwRYfeEchBOE/323I2H8LMSedP0clliGH
/kAGnopIkfiPiSsC2JGALsmAxhCLcFGNOip8wEc8D1b4Dw06vPBCaCOeOBAMpRUk4j9P3jcUi0v6
Yxp8l3m4YUJC5YAhiidKCOWWCfEwJZhfyqgQb2q5JMU/AERzyR33CICCOEES5BV7MySJUHVOallh
YUSRV9Bnsl1FFWV5kVnlUJ0NJqGYsVXV2UBUeYmmn2omhJZvLxnBRAHFNAIIOCuUIkyeUpIoopj/
8P9A5ZMiokfoZQXppQMLLOh12VRFOYpZZf7giuakLhIUG16FcefZdMgq2WlaNLrEBBNs/TNPPSsQ
ggCrlRLFaUS0kumVkJxGaSG6CNGwoaTJbrpumj8MZZ+8sE77aZscyQBEFFCwswA+y5CDQQasmulP
d37KOpDDGqY4UGHGPhpxhur+QzFE7go5mGRlocZux6Z1fJXIuQ0E8kAiT+vpQr4NSBAOQvxzgww+
9CCDEz5g4QgOiAzgjQjQzPSkZIySNxiggBY0H2KKZdeoebkadpsOA6HXwmaKnccX0l/WdlvKBEl2
mGX3JWYbXkeJ3cJqLn8EM78S4YyEDMH5IAMOPfT/DUQGhSQjgAcNGL0hkUSVNRiTpjHOpVOGRaUX
UTlA126Rsln+IlFQJQQ5aUhyOlZSZV2uNpJUBZvh6GDFLfeadEfUtwz/4GC77VH08MQ/xKQQhwCB
fAOE68QXb7zL+8o80A1G3IDDEUcM//wVSfxjSgS0jJAAJzgc7/334G+UfEV43yBEOBL0cPM/QQBh
wBvLnCBNHkFkG/79+OdPLeyxL4QzEF+QABOywIQq1OwfFsgHCeSRBgUQYQq0058EJ0i85CmvdlY4
Qg+yYAQpdEEWBvjHBcqghxGIAgdP8AEFV8hCGVmQIj4QQs1uoAUrQKEbv0jHHkoQAQ+gYBj/KEL3
/1pIxCK2hE39U4gP9HaDHkggCp9Yhz0OcIIDzGISoOhN+4zIxS5W5IU4W2IEI0iQG5iRCERAQAKU
MYdyiAECrnAGFGQgCBfc7SXBKpZYztW6igBrKFbxjNo0p5E/FotKXnydp9RCM+jd8R97K4gZzeeD
AJRgFwf4gAgY8AwEyKAHOABCE2AyFB3w5VJcSc3bcFMe0DBMZZMhFq6EUoNVko0gNhgN1TgHS8qg
LSE2eIFSkkKD0TQJK5ADkfcsiIMi3IyMyxvIEaqwtyD8QxGSgMCCzoCBceCgCUS4QhCCg8d4wYQ/
UvqP1lZZsRGBZyDjSScwSbMDtg1pau7MZ0FoAP8jo7AnWU+rD/iS5wUgyMAIzZukGfvWRCQ44QZD
sMY/bJGCEzxAHwr4RxZ64IQvSGGILslXS2A0IhZl7F0VQimVVpaQV3mMXf/QS582BS2J3Q8tMnCB
ErwQSt0NRAYRFGMokdCDLkThH6+gRgPCoJI/GAEHQBXC8MqpJAqRjgaZoQENvHIUHrwABhdLE1aS
khCuSgmsKBLruAJVIbPCB63KIk10anqUjC3Tfy7YwhZqJwUrFCiUQADCEYA6hCHoDAqsMMQxrjEQ
HDDhCeJkHlBJWZSy8MUprKGKDtDpn7By6lysPE+wtrKof0orWI4hT61GixDJ3IuuYypKDVBZQQH/
CcR2YCgsDpIwAS0kAQcusAJbKoGJEPgiF/9gwhSa0AQnCCEInzQjZU3ZAvLQgFdC+Q8NIFexGBhq
XNPRjlz3mZgW3GW8hoRVKfEiGVwxh5/+MG92GZYY6n4mQ4NZ1tbGezy0LGETILBEJ+jAiCGAgSBE
UCFBHGCHUERiCAOhABNu5oQmNE8ISECCgkNqTkSJ6x/1MmeLwmTOjinpSflSb7JExBwUm/MHnyMK
fl3kYmm5riZFgAQIeFEBOawBGdzwQwUeMQYObCMVauCAJtBRCzf04x8EUAIUqjC8gwaHZl8gAjQ3
IiZAvTcx/L3Pd//B0pbtk1IolRaFyuoP+9Rm/141jlCyBkOyIZ3peEuAGQVAoAtDHIIMg4BHH05h
hnfgAQ6qaEUHOmAOTzhACWbEQhKG14MYCgGNQIAwVQvCmfOGB2S+6s+FWKZKuK1TMsokSGJ8Sdas
XY1LqnRKWUS0amJpCiKwJbPVfoln2w4ECgswRgAocY4QkMIEJjgHAFZRgJ8OxH7/0JsMtMw+yipp
dEQpDNa26g+seRWuuORjWT43m4QYcgaGAvMLCHmocx0mrhU695gTkmsine6VxFuCBV0AVDLioAAF
MkgiB07wjOh7bg8hQl6pgIXCDoEKBY+4xClycP4RRAZJgGAQqcAWUE384yD/xyjGNxAgJIEITQ0A
yRJwlgQlhPzlEg8IADs=

------=_Part_55_708591777.1373278363128--


------=_Part_97_930046966.1373278363403--


From skareem@science.alquds.edu  Sun Jul  7 09:50:16 2013
Return-Path: <skareem@science.alquds.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57B2321F9A38 for <ietf@ietfa.amsl.com>; Sun,  7 Jul 2013 09:50:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.799
X-Spam-Level: 
X-Spam-Status: No, score=-0.799 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_21=0.6, J_CHICKENPOX_32=0.6, J_CHICKENPOX_45=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ci6xbUud6SM6 for <ietf@ietfa.amsl.com>; Sun,  7 Jul 2013 09:50:12 -0700 (PDT)
Received: from mail.alquds.edu (mail.alquds.edu [195.114.29.131]) by ietfa.amsl.com (Postfix) with ESMTP id 048D221F9A50 for <ietf@ietf.org>; Sun,  7 Jul 2013 09:50:11 -0700 (PDT)
Received: from alquds.edu (localhost.localdomain [127.0.0.1]) by mail.alquds.edu (8.14.4/8.14.4) with ESMTP id r67Go7GM023947; Sun, 7 Jul 2013 19:50:07 +0300
From: "0" <skareem@science.alquds.edu>
To: ietf@ietf.org, noncom-chair-2013@ietf.org
Subject: Re: Final Announcement of Qualified Volunteers
Date: Sun, 7 Jul 2013 19:50:07 +0300
Message-Id: <20130707164630.M18401@science.alquds.edu>
In-Reply-To: <20130706215330.8850.38261.idtracker@ietfa.amsl.com>
References: <20130706215330.8850.38261.idtracker@ietfa.amsl.com>
X-Mailer: OpenWebMail 2.53 
X-OriginatingIP: 85.113.99.74 (s0913088)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
X-yoursite-MailScanner-Information: Please contact the ISP for more information
X-yoursite-MailScanner-ID: r67Go7GM023947
X-yoursite-MailScanner: Found to be clean
X-yoursite-MailScanner-From: skareem@science.alquds.edu
X-Mailman-Approved-At: Mon, 08 Jul 2013 07:56:31 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Jul 2013 16:50:16 -0000

Dears;
I am just wondered why there is any names from Arab world, no volunteers or no 
acceptance for Arab people.

Thanks for giving chance to ask.

Sama Kareem

On Sat, 06 Jul 2013 14:53:30 -0700, NomCom Chair 2013 wrote
> I am pleased to announce that we have 140 qualified individuals who 
> have generously volunteered to serve as voting members of this year's 
> Nomcom.
> 
> Please take a look and get in touch before July 13 if you think your 
> name should be here and it isn't (or possibly I've mis-typed it...), or
> if you have any other questions.
> 
> Allison Mankin
> 2013-14 Nomcom Chair
> nomcom-chair-2013@ietf.org
> 
> ----------------------------------------
> 001 John Scudder, Juniper
> 002 Stephen Hanna, Juniper
> 003 Wassim Haddad, Ericsson
> 004 Russ White, VTE
> 005 Stephan Wenger, Vidyo
> 006 ZHAO Yi, Huawei
> 007 Eric Gray, Ericsson
> 008 Steve Kent, BBN
> 009 Toerless Eckert, Cisco
> 010 Alia Atlas, Juniper
> 011 Victor Kuarsingh, Rogers
> 012 Yizhou LI, Huawei
> 013 Gonzalo Salgueiro, Cisco
> 014 Gang CHEN, China Mobile
> 015 Ning KONG,CNNIC
> 016 Marcelo Bagnulo, UC3M
> 017 SHEN Shuo 娌堢儊 (Sean), CNNIC
> 018 Fernando Gont, SI6 Networks
> 019 Glen Zorn, Network Zen
> 020 Reinaldo Penno, Cisco
> 021 Klaas Wierenga, Cisco
> 022 Pascal Thubert, Cisco
> 023 Mehmet Ersue, Nokia Siemens
> 024 Ole Troan, Cisco
> 025 Jouni Korhonen, Renesas Mobile
> 026 Giles Heron, Cisco
> 027 Gunter Van de Velde, Cisco
> 028 Arturo Servin, LACNIC
> 029 Eric Vyncke, Cisco
> 030 Cullen Jennings, Cisco
> 031 Tina Tsou, Huawei
> 032 Dhruv Dhody, Huawei
> 033 Hongyu LI (Julio), Huawei
> 034 Scott Mansfield, Ericsson
> 035 John Drake, Juniper
> 036 Andrew McLachlan, Cisco
> 037 Derek Atkins, Mocana
> 038 Suhas Nandakumar, Cisco
> 039 Eric Rescorla, RTFM
> 040 Karen Seo, BBN
> 041 Stig Venaas, Cisco
> 042 Stan Ratliff, Cisco
> 043 Ignas Bagdonas, Cisco
> 044 Peter Yee, AKAYLA
> 045 Donald Eastlake, Huawei
> 046 ZHOU Qian (Cathy), Huawei
> 047 Sam Hartman, Painless Security
> 048 Lixia Zhang, UCLA
> 049 Teemu Savolainen, Nokia
> 050 Alvaro Retana, Cisco
> 051 Terry Manderson, ICANN
> 052 Bill VerSteeg, Cisco
> 053 Melinda Shore, No Mountain
> 054 IJsbrand Wijnands, Cisco
> 055 Karen O'Donoghue, ISOC
> 056 Benson Schliesser, Juniper
> 057 Ari Ker盲nen, Ericsson
> 058 Fangwei HU, ZTE
> 059 Mach CHEN, Huawei
> 060 Hui Deng, China Mobile
> 061 LIU Dapeng, China Mobile
> 062 Jaap Akkerhuis, NLNET Labs
> 063 Magnus Westerlund, Ericsson
> 064 Zehn CAO, China Mobile
> 065 Zaheduzzaman Sarker, Ericsson
> 066 Bhumip Khasnabish, ZTE USA
> 067 Andrew Chi, BBN
> 068 Thomas Nadeau, Juniper
> 069 Steven C (Craig) White, Alcatel-Lucent
> 070 Orit Levin, Microsoft
> 071 Sam Aldrin, Huawei
> 072 Paul Ebersman, Infoblox
> 073 Christopher Liljenstolpe, BigSwitch
> 074 Uma Chunduri, Ericsson
> 075 Suresh Krishnan, Ericsson
> 076 Varun Singh, Aalto University
> 077 Ron Bonica, Juniper
> 078 Bill (William) Manning, ISI
> 079 Radia Perlman, Intel
> 080 Daniele Ceccarelli, Ericsson
> 081 Deborah Brungard, AT&T
> 082 Kostas Pentikousis, Huawei
> 083 Gregory Mirsky, Ericsson
> 084 Dave Sinicrope, Ericsson
> 085 Thomas Walsh, Juniper
> 086 Zhaohui (Jeffrey) ZHANG, Juniper
> 087 Xian ZHANG, Huawei
> 088 Mark Townsley, Cisco
> 089 Hannes Gredler, Juniper
> 090 Brian Trammell, ETHZ
> 091 Carlos Martinez, LACNIC
> 092 Peter Koch, DENIC eG
> 093 Daniel Migault, France Telecom - Orange
> 094 Yi (Aaron) Ding, University of Helsinki
> 095 Michael Richardson, Sandelman
> 096 Sohel Khan, Kellogg School of Mgt
> 097 John Bradley, Ping Identity
> 098 Huaimo Chen, Huawei
> 099 Matthew Campagna, Blackberry/RIM/Certicom
> 100 Keith Drage, Alcatel-Lucent
> 101 Chris Bowers, Juniper
> 102 Jakob Heitz, Ericsson
> 103 Tomofumi Okubo, ICANN
> 104 Emil Ivov, jitsi.org
> 105 Timothy B. Terriberry, Mozilla
> 106 JIANG Yuanlong, Huawei
> 107 Luigi Iannone, Telecom Paris Tech
> 108 Damien Saucez, INRIA
> 109 Lou Berger, LabN Consulting, LLC
> 110 Yana Stamcheva, jitsi.org
> 111 Ond艡ej Sur媒, NIC.CZ
> 112 Marcin Pilarski, Warsaw Univ Technology / Orange Polska
> 113 Michael StJohns, Consultant/Silver Spring Networks
> 114 Wes George, Time Warner Cable
> 115 Christian O'Flaherty, ISOC
> 116 Uwe Rauschenbach, Nokia Siemens
> 117 Olafur Gudmundsson, Shinkuro
> 118 Shwetha Subray Bhandari, Cisco
> 119 Tobias Gondrom, Owasp
> 120 Christer Holmberg, Ericsson
> 121 Susan Hares, ADARA
> 122 Kiran Kumar Chittimaneni, Google
> 123 Donald Fedyk, Alcatel-Lucent
> 124 Stephen Botzko, Polycom
> 125 Li Xue, Huawei
> 126 John Sauer, Tellabs
> 127 Jon Hudson, Brocade
> 128 Charles Eckel, Cisco
> 129 Li Kepeng, Huawei
> 130 Jason Weil, Time Warner Cable
> 131 Dorothy Gellert, Silver Spring Networks
> 132 Fred Baker, Cisco
> 133 Michael O'Reirdan, Comcast
> 134 Jean-Michel Combes, France Telecom - Orange
> 135 Jim Gettys, Bell Labs (Alcatel-Lucent)
> 136 John Brzozowski, Comcast
> 137 Ray Bellis, Nominet UK
> 138 Adam Montville, Center for Internet Security
> 139 Bing Liu, Huawei
> 140 Michal Krsek, Comprimato Systems
> 
> -- 
> This message has been scanned for viruses and
> dangerous content by SKITCE MailScanner, and is
> believed to be clean.


--
Open WebMail Project (http://openwebmail.org)

-- 
This message has been scanned for viruses and
dangerous content by SKITCE MailScanner, and is
believed to be clean.


From allison.mankin@gmail.com  Mon Jul  8 08:24:06 2013
Return-Path: <allison.mankin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F38021F9BFB for <ietf@ietfa.amsl.com>; Mon,  8 Jul 2013 08:24:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level: 
X-Spam-Status: No, score=-1.699 tagged_above=-999 required=5 tests=[AWL=-0.900, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_21=0.6, J_CHICKENPOX_32=0.6, J_CHICKENPOX_45=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KgMPbUdkBnuo for <ietf@ietfa.amsl.com>; Mon,  8 Jul 2013 08:24:04 -0700 (PDT)
Received: from mail-bk0-x230.google.com (mail-bk0-x230.google.com [IPv6:2a00:1450:4008:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id 0817921F9A3B for <ietf@ietf.org>; Mon,  8 Jul 2013 08:24:03 -0700 (PDT)
Received: by mail-bk0-f48.google.com with SMTP id jf17so1896379bkc.21 for <multiple recipients>; Mon, 08 Jul 2013 08:24:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=M4HL5ng/0VP5Xz0MT+J5DKPxok+PuBEJc/p4MCKqyP0=; b=A3jJn6Ua4Ug/pmKr4x05rp7q/KU+V/E8zGqnxfdxhKSxDZE/NrcxEuExWrbtKLqjDh rTGDxRKXhdfHGNecBbgZB8sTnq64UZjhDov2G/LpVFMCfBwkx0XOOV9dJi81m74G/Lov dq4tbaAGUYwc3kyhCauUXHMbHLLTNnKRQZBf/WoerdIzkKef3aYPhx45EmRZcCwVB6vI cIqdekEBTxlesPX8iPAe6k+pdNOC6NYOp+pqttGluLx2Zgly8hm2YwASr4a5KUh+H1EU sQnTMwK22r3+ogwmrJZFxlw49tFC4HPhqLN6veI2t7uP9TbN5+93CjTazNUl+uoqL26x l7qQ==
MIME-Version: 1.0
X-Received: by 10.204.240.79 with SMTP id kz15mr3456204bkb.112.1373297042730;  Mon, 08 Jul 2013 08:24:02 -0700 (PDT)
Received: by 10.204.36.138 with HTTP; Mon, 8 Jul 2013 08:24:02 -0700 (PDT)
In-Reply-To: <20130707164630.M18401@science.alquds.edu>
References: <20130706215330.8850.38261.idtracker@ietfa.amsl.com> <20130707164630.M18401@science.alquds.edu>
Date: Mon, 8 Jul 2013 11:24:02 -0400
Message-ID: <CAP8yD=t3-eWVm5Bv9LKk8enW_tHbRd57=tozrmZ7HKxYvKqWmw@mail.gmail.com>
Subject: Re: Final Announcement of Qualified Volunteers
From: Allison Mankin <allison.mankin@gmail.com>
To: 0 <skareem@science.alquds.edu>
Content-Type: multipart/alternative; boundary=90e6ba613990676d3504e101a2e3
Cc: IETF Discussion <ietf@ietf.org>, noncom-chair-2013@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Jul 2013 15:24:06 -0000

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

Dear Sama Kareem,

Anybody who has attended three out of the past five IETFs is eligible and
has been encouraged (a lot) to volunteer for the nomcom.  While there are a
number of IETF participants who rarely attend in-person meetings, the
present consensus (and one that I'd tend to support) is that there are many
aspects of searching for/selecting the leadership of the IETF where an
"in-the-meeting-rooms, in-the-hallways" familiarity with the IETF is
important.

Also, I would hesitate to characterize the volunteer list as having "no
acceptance for Arab people" because I don't know peoples' national origins.

There is room for more discussion on the topics of diversity in the nomcom
and in other aspects of the IETF, and that is why there is a current
mailing list on the subject.  Find out more and join the list at:

https://www.ietf.org/mailman/listinfo/diversity

Best regards,
Allison Mankin
Nomcom 2013-14 Chair
nomcom-chair-2013@ietf.org




On Sun, Jul 7, 2013 at 12:50 PM, 0 <skareem@science.alquds.edu> wrote:

>
> Dears;
> I am just wondered why there is any names from Arab world, no volunteers
> or no
> acceptance for Arab people.
>
> Thanks for giving chance to ask.
>
> Sama Kareem
>
> On Sat, 06 Jul 2013 14:53:30 -0700, NomCom Chair 2013 wrote
> > I am pleased to announce that we have 140 qualified individuals who
> > have generously volunteered to serve as voting members of this year's
> > Nomcom.
> >
> > Please take a look and get in touch before July 13 if you think your
> > name should be here and it isn't (or possibly I've mis-typed it...), or
> > if you have any other questions.
> >
> > Allison Mankin
> > 2013-14 Nomcom Chair
> > nomcom-chair-2013@ietf.org
> >
> > ----------------------------------------
> > 001 John Scudder, Juniper
> > 002 Stephen Hanna, Juniper
> > 003 Wassim Haddad, Ericsson
> > 004 Russ White, VTE
> > 005 Stephan Wenger, Vidyo
> > 006 ZHAO Yi, Huawei
> > 007 Eric Gray, Ericsson
> > 008 Steve Kent, BBN
> > 009 Toerless Eckert, Cisco
> > 010 Alia Atlas, Juniper
> > 011 Victor Kuarsingh, Rogers
> > 012 Yizhou LI, Huawei
> > 013 Gonzalo Salgueiro, Cisco
> > 014 Gang CHEN, China Mobile
> > 015 Ning KONG,CNNIC
> > 016 Marcelo Bagnulo, UC3M
> > 017 SHEN Shuo =E6=B2=88=E7=83=81 (Sean), CNNIC
> > 018 Fernando Gont, SI6 Networks
> > 019 Glen Zorn, Network Zen
> > 020 Reinaldo Penno, Cisco
> > 021 Klaas Wierenga, Cisco
> > 022 Pascal Thubert, Cisco
> > 023 Mehmet Ersue, Nokia Siemens
> > 024 Ole Troan, Cisco
> > 025 Jouni Korhonen, Renesas Mobile
> > 026 Giles Heron, Cisco
> > 027 Gunter Van de Velde, Cisco
> > 028 Arturo Servin, LACNIC
> > 029 Eric Vyncke, Cisco
> > 030 Cullen Jennings, Cisco
> > 031 Tina Tsou, Huawei
> > 032 Dhruv Dhody, Huawei
> > 033 Hongyu LI (Julio), Huawei
> > 034 Scott Mansfield, Ericsson
> > 035 John Drake, Juniper
> > 036 Andrew McLachlan, Cisco
> > 037 Derek Atkins, Mocana
> > 038 Suhas Nandakumar, Cisco
> > 039 Eric Rescorla, RTFM
> > 040 Karen Seo, BBN
> > 041 Stig Venaas, Cisco
> > 042 Stan Ratliff, Cisco
> > 043 Ignas Bagdonas, Cisco
> > 044 Peter Yee, AKAYLA
> > 045 Donald Eastlake, Huawei
> > 046 ZHOU Qian (Cathy), Huawei
> > 047 Sam Hartman, Painless Security
> > 048 Lixia Zhang, UCLA
> > 049 Teemu Savolainen, Nokia
> > 050 Alvaro Retana, Cisco
> > 051 Terry Manderson, ICANN
> > 052 Bill VerSteeg, Cisco
> > 053 Melinda Shore, No Mountain
> > 054 IJsbrand Wijnands, Cisco
> > 055 Karen O'Donoghue, ISOC
> > 056 Benson Schliesser, Juniper
> > 057 Ari Ker=C3=A4nen, Ericsson
> > 058 Fangwei HU, ZTE
> > 059 Mach CHEN, Huawei
> > 060 Hui Deng, China Mobile
> > 061 LIU Dapeng, China Mobile
> > 062 Jaap Akkerhuis, NLNET Labs
> > 063 Magnus Westerlund, Ericsson
> > 064 Zehn CAO, China Mobile
> > 065 Zaheduzzaman Sarker, Ericsson
> > 066 Bhumip Khasnabish, ZTE USA
> > 067 Andrew Chi, BBN
> > 068 Thomas Nadeau, Juniper
> > 069 Steven C (Craig) White, Alcatel-Lucent
> > 070 Orit Levin, Microsoft
> > 071 Sam Aldrin, Huawei
> > 072 Paul Ebersman, Infoblox
> > 073 Christopher Liljenstolpe, BigSwitch
> > 074 Uma Chunduri, Ericsson
> > 075 Suresh Krishnan, Ericsson
> > 076 Varun Singh, Aalto University
> > 077 Ron Bonica, Juniper
> > 078 Bill (William) Manning, ISI
> > 079 Radia Perlman, Intel
> > 080 Daniele Ceccarelli, Ericsson
> > 081 Deborah Brungard, AT&T
> > 082 Kostas Pentikousis, Huawei
> > 083 Gregory Mirsky, Ericsson
> > 084 Dave Sinicrope, Ericsson
> > 085 Thomas Walsh, Juniper
> > 086 Zhaohui (Jeffrey) ZHANG, Juniper
> > 087 Xian ZHANG, Huawei
> > 088 Mark Townsley, Cisco
> > 089 Hannes Gredler, Juniper
> > 090 Brian Trammell, ETHZ
> > 091 Carlos Martinez, LACNIC
> > 092 Peter Koch, DENIC eG
> > 093 Daniel Migault, France Telecom - Orange
> > 094 Yi (Aaron) Ding, University of Helsinki
> > 095 Michael Richardson, Sandelman
> > 096 Sohel Khan, Kellogg School of Mgt
> > 097 John Bradley, Ping Identity
> > 098 Huaimo Chen, Huawei
> > 099 Matthew Campagna, Blackberry/RIM/Certicom
> > 100 Keith Drage, Alcatel-Lucent
> > 101 Chris Bowers, Juniper
> > 102 Jakob Heitz, Ericsson
> > 103 Tomofumi Okubo, ICANN
> > 104 Emil Ivov, jitsi.org
> > 105 Timothy B. Terriberry, Mozilla
> > 106 JIANG Yuanlong, Huawei
> > 107 Luigi Iannone, Telecom Paris Tech
> > 108 Damien Saucez, INRIA
> > 109 Lou Berger, LabN Consulting, LLC
> > 110 Yana Stamcheva, jitsi.org
> > 111 Ond=C5=99ej Sur=C3=BD, NIC.CZ
> > 112 Marcin Pilarski, Warsaw Univ Technology / Orange Polska
> > 113 Michael StJohns, Consultant/Silver Spring Networks
> > 114 Wes George, Time Warner Cable
> > 115 Christian O'Flaherty, ISOC
> > 116 Uwe Rauschenbach, Nokia Siemens
> > 117 Olafur Gudmundsson, Shinkuro
> > 118 Shwetha Subray Bhandari, Cisco
> > 119 Tobias Gondrom, Owasp
> > 120 Christer Holmberg, Ericsson
> > 121 Susan Hares, ADARA
> > 122 Kiran Kumar Chittimaneni, Google
> > 123 Donald Fedyk, Alcatel-Lucent
> > 124 Stephen Botzko, Polycom
> > 125 Li Xue, Huawei
> > 126 John Sauer, Tellabs
> > 127 Jon Hudson, Brocade
> > 128 Charles Eckel, Cisco
> > 129 Li Kepeng, Huawei
> > 130 Jason Weil, Time Warner Cable
> > 131 Dorothy Gellert, Silver Spring Networks
> > 132 Fred Baker, Cisco
> > 133 Michael O'Reirdan, Comcast
> > 134 Jean-Michel Combes, France Telecom - Orange
> > 135 Jim Gettys, Bell Labs (Alcatel-Lucent)
> > 136 John Brzozowski, Comcast
> > 137 Ray Bellis, Nominet UK
> > 138 Adam Montville, Center for Internet Security
> > 139 Bing Liu, Huawei
> > 140 Michal Krsek, Comprimato Systems
> >
> > --
> > This message has been scanned for viruses and
> > dangerous content by SKITCE MailScanner, and is
> > believed to be clean.
>
>
> --
> Open WebMail Project (http://openwebmail.org)
>
> --
> This message has been scanned for viruses and
> dangerous content by SKITCE MailScanner, and is
> believed to be clean.
>
>

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

<div dir=3D"ltr"><div><div><div><div><div>Dear Sama Kareem,<br><br></div>An=
ybody who has attended three out of the past five IETFs is eligible and has=
 been encouraged (a lot) to volunteer for the nomcom.=C2=A0 While there are=
 a number of IETF participants who rarely attend in-person meetings, the pr=
esent consensus (and one that I&#39;d tend to support) is that there are ma=
ny aspects of searching for/selecting the leadership of the IETF where an &=
quot;in-the-meeting-rooms, in-the-hallways&quot; familiarity with the IETF =
is important.<br>
<br></div>Also, I would hesitate to characterize the volunteer list as havi=
ng &quot;no acceptance for Arab people&quot; because I don&#39;t know peopl=
es&#39; national origins.<br><br></div>There is room for more discussion on=
 the topics of diversity in the nomcom and in other aspects of the IETF, an=
d that is why there is a current mailing list on the subject.=C2=A0 Find ou=
t more and join the list at:<br>
<br><a href=3D"https://www.ietf.org/mailman/listinfo/diversity">https://www=
.ietf.org/mailman/listinfo/diversity</a><br><br></div>Best regards,<br>Alli=
son Mankin<br>Nomcom 2013-14 Chair<br></div><a href=3D"mailto:nomcom-chair-=
2013@ietf.org">nomcom-chair-2013@ietf.org</a><br>
<div><div><br><br></div></div></div><div class=3D"gmail_extra"><br><br><div=
 class=3D"gmail_quote">On Sun, Jul 7, 2013 at 12:50 PM, 0 <span dir=3D"ltr"=
>&lt;<a href=3D"mailto:skareem@science.alquds.edu" target=3D"_blank">skaree=
m@science.alquds.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>
Dears;<br>
I am just wondered why there is any names from Arab world, no volunteers or=
 no<br>
acceptance for Arab people.<br>
<br>
Thanks for giving chance to ask.<br>
<br>
Sama Kareem<br>
<br>
On Sat, 06 Jul 2013 14:53:30 -0700, NomCom Chair 2013 wrote<br>
<div><div class=3D"h5">&gt; I am pleased to announce that we have 140 quali=
fied individuals who<br>
&gt; have generously volunteered to serve as voting members of this year&#3=
9;s<br>
&gt; Nomcom.<br>
&gt;<br>
&gt; Please take a look and get in touch before July 13 if you think your<b=
r>
&gt; name should be here and it isn&#39;t (or possibly I&#39;ve mis-typed i=
t...), or<br>
&gt; if you have any other questions.<br>
&gt;<br>
&gt; Allison Mankin<br>
&gt; 2013-14 Nomcom Chair<br>
&gt; <a href=3D"mailto:nomcom-chair-2013@ietf.org">nomcom-chair-2013@ietf.o=
rg</a><br>
&gt;<br>
&gt; ----------------------------------------<br>
&gt; 001 John Scudder, Juniper<br>
&gt; 002 Stephen Hanna, Juniper<br>
&gt; 003 Wassim Haddad, Ericsson<br>
&gt; 004 Russ White, VTE<br>
&gt; 005 Stephan Wenger, Vidyo<br>
&gt; 006 ZHAO Yi, Huawei<br>
&gt; 007 Eric Gray, Ericsson<br>
&gt; 008 Steve Kent, BBN<br>
&gt; 009 Toerless Eckert, Cisco<br>
&gt; 010 Alia Atlas, Juniper<br>
&gt; 011 Victor Kuarsingh, Rogers<br>
&gt; 012 Yizhou LI, Huawei<br>
&gt; 013 Gonzalo Salgueiro, Cisco<br>
&gt; 014 Gang CHEN, China Mobile<br>
&gt; 015 Ning KONG,CNNIC<br>
&gt; 016 Marcelo Bagnulo, UC3M<br>
&gt; 017 SHEN Shuo =E6=B2=88=E7=83=81 (Sean), CNNIC<br>
&gt; 018 Fernando Gont, SI6 Networks<br>
&gt; 019 Glen Zorn, Network Zen<br>
&gt; 020 Reinaldo Penno, Cisco<br>
&gt; 021 Klaas Wierenga, Cisco<br>
&gt; 022 Pascal Thubert, Cisco<br>
&gt; 023 Mehmet Ersue, Nokia Siemens<br>
&gt; 024 Ole Troan, Cisco<br>
&gt; 025 Jouni Korhonen, Renesas Mobile<br>
&gt; 026 Giles Heron, Cisco<br>
&gt; 027 Gunter Van de Velde, Cisco<br>
&gt; 028 Arturo Servin, LACNIC<br>
&gt; 029 Eric Vyncke, Cisco<br>
&gt; 030 Cullen Jennings, Cisco<br>
&gt; 031 Tina Tsou, Huawei<br>
&gt; 032 Dhruv Dhody, Huawei<br>
&gt; 033 Hongyu LI (Julio), Huawei<br>
&gt; 034 Scott Mansfield, Ericsson<br>
&gt; 035 John Drake, Juniper<br>
&gt; 036 Andrew McLachlan, Cisco<br>
&gt; 037 Derek Atkins, Mocana<br>
&gt; 038 Suhas Nandakumar, Cisco<br>
&gt; 039 Eric Rescorla, RTFM<br>
&gt; 040 Karen Seo, BBN<br>
&gt; 041 Stig Venaas, Cisco<br>
&gt; 042 Stan Ratliff, Cisco<br>
&gt; 043 Ignas Bagdonas, Cisco<br>
&gt; 044 Peter Yee, AKAYLA<br>
&gt; 045 Donald Eastlake, Huawei<br>
&gt; 046 ZHOU Qian (Cathy), Huawei<br>
&gt; 047 Sam Hartman, Painless Security<br>
&gt; 048 Lixia Zhang, UCLA<br>
&gt; 049 Teemu Savolainen, Nokia<br>
&gt; 050 Alvaro Retana, Cisco<br>
&gt; 051 Terry Manderson, ICANN<br>
&gt; 052 Bill VerSteeg, Cisco<br>
&gt; 053 Melinda Shore, No Mountain<br>
&gt; 054 IJsbrand Wijnands, Cisco<br>
&gt; 055 Karen O&#39;Donoghue, ISOC<br>
&gt; 056 Benson Schliesser, Juniper<br>
&gt; 057 Ari Ker=C3=A4nen, Ericsson<br>
&gt; 058 Fangwei HU, ZTE<br>
&gt; 059 Mach CHEN, Huawei<br>
&gt; 060 Hui Deng, China Mobile<br>
&gt; 061 LIU Dapeng, China Mobile<br>
&gt; 062 Jaap Akkerhuis, NLNET Labs<br>
&gt; 063 Magnus Westerlund, Ericsson<br>
&gt; 064 Zehn CAO, China Mobile<br>
&gt; 065 Zaheduzzaman Sarker, Ericsson<br>
&gt; 066 Bhumip Khasnabish, ZTE USA<br>
&gt; 067 Andrew Chi, BBN<br>
&gt; 068 Thomas Nadeau, Juniper<br>
&gt; 069 Steven C (Craig) White, Alcatel-Lucent<br>
&gt; 070 Orit Levin, Microsoft<br>
&gt; 071 Sam Aldrin, Huawei<br>
&gt; 072 Paul Ebersman, Infoblox<br>
&gt; 073 Christopher Liljenstolpe, BigSwitch<br>
&gt; 074 Uma Chunduri, Ericsson<br>
&gt; 075 Suresh Krishnan, Ericsson<br>
&gt; 076 Varun Singh, Aalto University<br>
&gt; 077 Ron Bonica, Juniper<br>
&gt; 078 Bill (William) Manning, ISI<br>
&gt; 079 Radia Perlman, Intel<br>
&gt; 080 Daniele Ceccarelli, Ericsson<br>
&gt; 081 Deborah Brungard, AT&amp;T<br>
&gt; 082 Kostas Pentikousis, Huawei<br>
&gt; 083 Gregory Mirsky, Ericsson<br>
&gt; 084 Dave Sinicrope, Ericsson<br>
&gt; 085 Thomas Walsh, Juniper<br>
&gt; 086 Zhaohui (Jeffrey) ZHANG, Juniper<br>
&gt; 087 Xian ZHANG, Huawei<br>
&gt; 088 Mark Townsley, Cisco<br>
&gt; 089 Hannes Gredler, Juniper<br>
&gt; 090 Brian Trammell, ETHZ<br>
&gt; 091 Carlos Martinez, LACNIC<br>
&gt; 092 Peter Koch, DENIC eG<br>
&gt; 093 Daniel Migault, France Telecom - Orange<br>
&gt; 094 Yi (Aaron) Ding, University of Helsinki<br>
&gt; 095 Michael Richardson, Sandelman<br>
&gt; 096 Sohel Khan, Kellogg School of Mgt<br>
&gt; 097 John Bradley, Ping Identity<br>
&gt; 098 Huaimo Chen, Huawei<br>
&gt; 099 Matthew Campagna, Blackberry/RIM/Certicom<br>
&gt; 100 Keith Drage, Alcatel-Lucent<br>
&gt; 101 Chris Bowers, Juniper<br>
&gt; 102 Jakob Heitz, Ericsson<br>
&gt; 103 Tomofumi Okubo, ICANN<br>
&gt; 104 Emil Ivov, <a href=3D"http://jitsi.org" target=3D"_blank">jitsi.or=
g</a><br>
&gt; 105 Timothy B. Terriberry, Mozilla<br>
&gt; 106 JIANG Yuanlong, Huawei<br>
&gt; 107 Luigi Iannone, Telecom Paris Tech<br>
&gt; 108 Damien Saucez, INRIA<br>
&gt; 109 Lou Berger, LabN Consulting, LLC<br>
&gt; 110 Yana Stamcheva, <a href=3D"http://jitsi.org" target=3D"_blank">jit=
si.org</a><br>
&gt; 111 Ond=C5=99ej Sur=C3=BD, <a href=3D"http://NIC.CZ" target=3D"_blank"=
>NIC.CZ</a><br>
&gt; 112 Marcin Pilarski, Warsaw Univ Technology / Orange Polska<br>
&gt; 113 Michael StJohns, Consultant/Silver Spring Networks<br>
&gt; 114 Wes George, Time Warner Cable<br>
&gt; 115 Christian O&#39;Flaherty, ISOC<br>
&gt; 116 Uwe Rauschenbach, Nokia Siemens<br>
&gt; 117 Olafur Gudmundsson, Shinkuro<br>
&gt; 118 Shwetha Subray Bhandari, Cisco<br>
&gt; 119 Tobias Gondrom, Owasp<br>
&gt; 120 Christer Holmberg, Ericsson<br>
&gt; 121 Susan Hares, ADARA<br>
&gt; 122 Kiran Kumar Chittimaneni, Google<br>
&gt; 123 Donald Fedyk, Alcatel-Lucent<br>
&gt; 124 Stephen Botzko, Polycom<br>
&gt; 125 Li Xue, Huawei<br>
&gt; 126 John Sauer, Tellabs<br>
&gt; 127 Jon Hudson, Brocade<br>
&gt; 128 Charles Eckel, Cisco<br>
&gt; 129 Li Kepeng, Huawei<br>
&gt; 130 Jason Weil, Time Warner Cable<br>
&gt; 131 Dorothy Gellert, Silver Spring Networks<br>
&gt; 132 Fred Baker, Cisco<br>
&gt; 133 Michael O&#39;Reirdan, Comcast<br>
&gt; 134 Jean-Michel Combes, France Telecom - Orange<br>
&gt; 135 Jim Gettys, Bell Labs (Alcatel-Lucent)<br>
&gt; 136 John Brzozowski, Comcast<br>
&gt; 137 Ray Bellis, Nominet UK<br>
&gt; 138 Adam Montville, Center for Internet Security<br>
&gt; 139 Bing Liu, Huawei<br>
&gt; 140 Michal Krsek, Comprimato Systems<br>
&gt;<br>
</div></div>&gt; --<br>
&gt; This message has been scanned for viruses and<br>
&gt; dangerous content by SKITCE MailScanner, and is<br>
&gt; believed to be clean.<br>
<br>
<br>
--<br>
Open WebMail Project (<a href=3D"http://openwebmail.org" target=3D"_blank">=
http://openwebmail.org</a>)<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
--<br>
This message has been scanned for viruses and<br>
dangerous content by SKITCE MailScanner, and is<br>
believed to be clean.<br>
<br>
</font></span></blockquote></div><br></div>

--90e6ba613990676d3504e101a2e3--

From john-ietf@jck.com  Mon Jul  8 09:00:07 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 551C421F934C for <ietf@ietfa.amsl.com>; Mon,  8 Jul 2013 09:00:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.539
X-Spam-Level: 
X-Spam-Status: No, score=-102.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wPEbjCWE2l6q for <ietf@ietfa.amsl.com>; Mon,  8 Jul 2013 09:00:01 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id EFEEB21F8994 for <ietf@ietf.org>; Mon,  8 Jul 2013 09:00:00 -0700 (PDT)
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 1UwDr5-000EwH-Ub; Mon, 08 Jul 2013 11:59:59 -0400
Date: Mon, 08 Jul 2013 11:59:54 -0400
From: John C Klensin <john-ietf@jck.com>
To: Sama Kareem <skareem@science.alquds.edu>, ietf@ietf.org, noncom-chair-2013@ietf.org
Subject: Re: Final Announcement of Qualified Volunteers
Message-ID: <1785B7A677F1CDD1F63758A2@JcK-HP8200.jck.com>
In-Reply-To: <20130707164630.M18401@science.alquds.edu>
References: <20130706215330.8850.38261.idtracker@ietfa.amsl.com> <20130707164630.M18401@science.alquds.edu>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Jul 2013 16:00:07 -0000

--On Sunday, July 07, 2013 19:50 +0300 0
<skareem@science.alquds.edu> wrote:

> I am just wondered why there is any names from Arab world, no
> volunteers or no  acceptance for Arab people.
> 
> Thanks for giving chance to ask.

Keeping in mind that people have to volunteer their own names
(no one else can do it for them) and that volunteers for the
Nomcom need to meet various requirements (of which the most
restrictive are face to face attendance at three of the last
IETF meetings and a commitment to attend up to a year or 18
months of upcoming IETF meetings face to face), I think your
question turns into three or maybe four others:

(1) Assuming that there are "Arab people" (quotes because I'm
not certain everyone in the IETF community would identify that
group the same way you do) who can satisfy those requirements to
volunteer, why didn't any of them volumteer?

(2) If more "Arab people" don't participate sufficiently in IETF
to meet those requirements, and hence to be eligible to
volunteer, why not?

(3) Are there "Arab people" participating actively in the IETF
who would volunteer for the Nomcom if the requirements were
different but still met the IETF community's reasonable needs?
Note that there is a draft on that subject floating around
(draft-moonesamy-nomcom-eligibility).  Speaking quite personally
and with the understanding that I may be in the minority, I
believe that the current "3 of 5" rules try to provide a single
measure that captures two entirely reasonable requirements: that
a nomcom volunteer understand the IETF community and how it
functions and that the volunteer understand the current
situation in the IETF well enough to meaningfully participate
and contribute to the Nomcom's work.    It may be that the
formula is wrong or that, as I now believe, we should be
separating those concerns into two separate requirements, or
not, but I think that it will be a very long time before the f2f
prerequisite is eliminated entirely and perhaps longer before
the community agrees that the Nomcom doesn't need to meet f2f.

(3) If you meet the 3 of 5 requirement and assuming you are an
instance of "Arab people", why didn't you volunteer?  And,
especially if you don't meet that requirement, does the IETF
expect to see you in Berlin as a first step to qualifying for
future Nomcoms?

  best,
   john




From chair@ietf.org  Mon Jul  8 09:04:21 2013
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05AA821F9DAC; Mon,  8 Jul 2013 09:04:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.099
X-Spam-Level: 
X-Spam-Status: No, score=-103.099 tagged_above=-999 required=5 tests=[AWL=-0.501, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id he2DCxdTzr7L; Mon,  8 Jul 2013 09:04:18 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:15]) by ietfa.amsl.com (Postfix) with ESMTP id BBD1F21F9C81; Mon,  8 Jul 2013 09:04:15 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id E9984A8A73; Mon,  8 Jul 2013 09:04:10 -0700 (PDT)
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 gguOG7PV0hS2; Mon,  8 Jul 2013 09:04:10 -0700 (PDT)
Received: from n238.nomadiclab.com (gw.nomadiclab.com [193.234.218.122]) by c9a.amsl.com (Postfix) with ESMTPSA id 5E3F8A8A6C; Mon,  8 Jul 2013 09:04:08 -0700 (PDT)
From: IETF Chair <chair@ietf.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_253F281E-350B-43A6-8F69-EE9E7C038E9E"
Message-Id: <DBC5838F-40CB-42B4-990C-C9DB045114C8@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: ISOC CEO Search
Date: Mon, 8 Jul 2013 18:04:10 +0200
References: <51DAD446.8030302@frobbit.se>
To: "ietf-announce@ietf.org" <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1508)
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Jul 2013 16:04:21 -0000

--Apple-Mail=_253F281E-350B-43A6-8F69-EE9E7C038E9E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


This announcement is of interest to the IETF community. If you have =
candidates or other feedback in mind, please work with Eva or Odgers =
Berndtson.

Jari Arkko
IETF Chair

Begin forwarded message:

> From: Eva Fr=F6lich <eva@frobbit.se>
> Subject: ISOC CEO Search
> Date: July 8, 2013 5:01:26 PM GMT+02:00
> To: jari.arkko@piuha.net
> Reply-To: eva@frobbit.se
>=20
> Dear Jari,
> The Internet Society Board of Trustees has retained the Executive =
Search firm of Odgers Berndtson to help us identify qualified candidates =
for the Internet Society's President &       CEO position. As announced =
earlier this year, Lynn St.Amour plans to step down as President & CEO =
in February 2014 at the conclusion of her contract.
>=20
> Founded in 1965, Odgers Berndtson provides an extensive range of high =
level recruitment services and has more than 53 offices worldwide. We =
are extremely confident that Odgers Berndtson offers the breadth of =
experience and resources to help us find the absolute right candidate =
for the Internet Society and the broader Internet community.
>=20
> Working with Odgers Berndtson, the Board's CEO Search Committee has =
finalized the position description, below. The position is being =
announced on the homepage of the Internet Society website and in =
messages to all ISOC member and stakeholder email lists and appropriate =
Internet community lists. Additionally, in the next two weeks, Odgers =
Berndtson will place an advertisement in The Economist magazine and =
publicize the opportunity through its global network.
>=20
> We will continue to keep you updated on a very regular basis on our =
recruitment plans and the ongoing search. If you have any questions or =
referrals for this position, please contact Odgers Berndtson: =
ceo-isoc@odgersberndtson.be
> =20
> Eva Fr=F6lich
> Chair, ISOC Board of Trustees
>=20
> _______________________
>=20
> Chief Executive Officer
> The Internet Society (ISOC)
>=20
> =93The Internet is for everyone=94
>=20
> www.internetsociety.org
>=20
> ISOC invites candidates for this exceptional role who will demonstrate =
top level global service in the public and/or business sector, =
leadership in a multi-stakeholder environment, and familiarity with =
civil regulatory and business issues related to the Internet.
>=20
> ISOC's mission is to promote the open development, evolution and use =
of the Internet for the benefit of everyone in the world. Through its =
65,000 individual members and supporters, 90 Chapters, and 145+ =
organizational members, ISOC plays a unique global role in championing =
policies, promoting open standards and implementing a plethora of =
actions to realize its mission. ISOC is also the organizational home of =
the Internet Engineering Task Force, the Internet=92s premier technical =
standards body.
>=20
> With offices in Virginia (USA) and Geneva (CH) and staff around the =
globe, ISOC collaborates with a variety of partners from all societal =
and activity sectors to ensure their engagement in the continued =
evolution of one of the greatest tools of our time.
>=20
> ISOC is a not-for-profit organization for whom transparency, =
consensus, creative thinking and inclusiveness are key, and whose policy =
is developed by the Board of Trustees with input from staff, members, =
chapters and the broader community.
>=20
> The CEO reports to, and is a member of, the Board of Trustees.
>=20
> The Role
> =95 Lead the design, agreement and implementation of actions and =
programmes in support of the strategic policy set with the Board of =
Trustees and Community
> =95 Provide inspired leadership and motivation to staff, members, and =
ISOC partners around the world
> =95 Ensure effective long-term financial and organizational =
stewardship of ISOC, upholding its unique mission and reputation
> =95 Deliver a significant personal impact as ISOC's primary =
representative in the Internet space and beyond
> =95 Be unswerving in driving for the open development and use of the =
Internet, by and for all
>=20
> The Candidate
> =95 Track record of excellence in global leadership and coaching =
within major organizations, at the intersection of public and private =
interests, with strong relevance to the Internet
> =95 Familiarity and comfort with a multi-stakeholder universe, where =
consensus prevails over hierarchy
> =95 Enthusiasm for and commitment to ISOC=92s mission and operating =
values
> =95 An outstanding communicator and advocate, who engenders trust and =
who shows integrity and courage
> =95 Strategic and integrative thinker, open to innovation, who sees =
the big and the small picture, and is streetwise and politically astute
> =95 Genuinely multicultural, connects effectively with different =
cultures, value systems and business models
>=20
> ISOC is an Equal Employment Opportunity Employer and does not =
discriminate based on race, color, religion, national origin, ancestry, =
citizenship, marital status, veteran status, physical or mental =
disability, sex, sexual orientation, age or other protected =
characteristics and complies with all applicable laws and regulations.=20=

>=20
> For further information and to apply, please contact:=20
> Bernard Tobin, Partner, at ceo-isoc@odgersberndtson.be.
> --=20
> -----------------------------
> Eva Fr=F6lich
> Frobbit AB
>=20
> Mail: eva@frobbit.se
> www.frobbit.se
>=20
>=20


--Apple-Mail=_253F281E-350B-43A6-8F69-EE9E7C038E9E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div>This announcement is of interest to the IETF community. If =
you have candidates or other feedback in mind, please work with Eva =
or&nbsp;Odgers Berndtson.</div><div><br></div><div>Jari =
Arkko</div><div>IETF Chair</div><div><br><div>Begin forwarded =
message:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px;"><span =
style=3D"font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, =
1.0);"><b>From: </b></span><span style=3D"font-family:'Helvetica'; =
font-size:medium;">Eva Fr=F6lich &lt;<a =
href=3D"mailto:eva@frobbit.se">eva@frobbit.se</a>&gt;<br></span></div><div=
 style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(0, 0, 0, 1.0);"><b>Subject: =
</b></span><span style=3D"font-family:'Helvetica'; =
font-size:medium;"><b>ISOC CEO Search</b><br></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(0, 0, 0, 1.0);"><b>Date: </b></span><span =
style=3D"font-family:'Helvetica'; font-size:medium;">July 8, 2013 =
5:01:26 PM GMT+02:00<br></span></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span =
style=3D"font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, =
1.0);"><b>To: </b></span><span style=3D"font-family:'Helvetica'; =
font-size:medium;"><a =
href=3D"mailto:jari.arkko@piuha.net">jari.arkko@piuha.net</a><br></span></=
div><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(0, 0, 0, 1.0);"><b>Reply-To: =
</b></span><span style=3D"font-family:'Helvetica'; font-size:medium;"><a =
href=3D"mailto:eva@frobbit.se">eva@frobbit.se</a><br></span></div><br>
 =20

    <meta http-equiv=3D"content-type" content=3D"text/html; =
charset=3DISO-8859-1">
 =20
  <div text=3D"#000000" bgcolor=3D"#FFFFFF">
    <div>Dear Jari,</div>
    <div>The Internet Society Board of Trustees has retained the
      Executive Search firm of Odgers Berndtson to help us identify
      qualified candidates for the Internet Society's President &amp;
      CEO position. As announced earlier this year, Lynn St.Amour plans
      to step down as President &amp; CEO in February 2014 at the
      conclusion of her contract.</div>
    <div><br>
    </div>
    <div>Founded in 1965, Odgers Berndtson provides an extensive range
      of high level recruitment services and has more than 53 offices
      worldwide. We are extremely confident that Odgers Berndtson offers
      the breadth of experience and resources to help us find the
      absolute right candidate for the Internet Society and the broader
      Internet community.</div>
    <div><br>
    </div>
    <div>Working with Odgers Berndtson, the Board's CEO Search Committee
      has finalized the position description, below. The position is
      being announced on the homepage of the Internet Society website
      and in messages to all ISOC member and stakeholder email lists and
      appropriate Internet community lists. Additionally, in the next
      two weeks, Odgers Berndtson will place an advertisement in The
      Economist magazine and publicize the opportunity through its
      global network.</div>
    <div><br>
    </div>
    <div>We will continue to keep you updated on a very regular basis on
      our recruitment plans and the ongoing search. If you have any
      questions or referrals for this position, please contact Odgers
      Berndtson:
      <a =
href=3D"mailto:ceo-isoc@odgersberndtson.be">ceo-isoc@odgersberndtson.be</a=
></div>
    <div>&nbsp;</div>
    <div>Eva Fr=F6lich</div>
    <div>Chair, ISOC Board of Trustees</div>
    <div><br>
    </div>
    <div>_______________________</div>
    <div><br>
    </div>
    <div>Chief Executive Officer</div>
    <div>The Internet Society (ISOC)</div>
    <div><br>
    </div>
    <div>=93The Internet is for everyone=94</div>
    <div><br>
    </div>
    <div><a =
href=3D"http://www.internetsociety.org/">www.internetsociety.org</a></div>=

    <div><br>
    </div>
    <div>ISOC invites candidates for this exceptional role who will
      demonstrate top level global service in the public and/or business
      sector, leadership in a multi-stakeholder environment, and
      familiarity with civil regulatory and business issues related to
      the Internet.</div>
    <div><br>
    </div>
    <div>ISOC's mission is to promote the open development, evolution
      and use of the Internet for the benefit of everyone in the world.
      Through its 65,000 individual members and supporters, 90 Chapters,
      and 145+ organizational members, ISOC plays a unique global role
      in championing policies, promoting open standards and implementing
      a plethora of actions to realize its mission. ISOC is also the
      organizational home of the Internet Engineering Task Force, the
      Internet=92s premier technical standards body.</div>
    <div><br>
    </div>
    <div>With offices in Virginia (USA) and Geneva (CH) and staff around
      the globe, ISOC collaborates with a variety of partners from all
      societal and activity sectors to ensure their engagement in the
      continued evolution of one of the greatest tools of our =
time.</div>
    <div><br>
    </div>
    <div>ISOC is a not-for-profit organization for whom transparency,
      consensus, creative thinking and inclusiveness are key, and whose
      policy is developed by the Board of Trustees with input from
      staff, members, chapters and the broader community.</div>
    <div><br>
    </div>
    <div>The CEO reports to, and is a member of, the Board of =
Trustees.</div>
    <div><br>
    </div>
    <div>The Role</div>
    <div>=95<span class=3D"Apple-tab-span" style=3D"white-space:pre"> =
</span>Lead
      the design, agreement and implementation of actions and programmes
      in support of the strategic policy set with the Board of Trustees
      and Community</div>
    <div>=95<span class=3D"Apple-tab-span" style=3D"white-space:pre"> =
</span>Provide
      inspired leadership and motivation to staff, members, and ISOC
      partners around the world</div>
    <div>=95<span class=3D"Apple-tab-span" style=3D"white-space:pre"> =
</span>Ensure
      effective long-term financial and organizational stewardship of
      ISOC, upholding its unique mission and reputation</div>
    <div>=95<span class=3D"Apple-tab-span" style=3D"white-space:pre"> =
</span>Deliver
      a significant personal impact as ISOC's primary representative in
      the Internet space and beyond</div>
    <div>=95<span class=3D"Apple-tab-span" style=3D"white-space:pre"> =
</span>Be
      unswerving in driving for the open development and use of the
      Internet, by and for all</div>
    <div><br>
    </div>
    <div>The Candidate</div>
    <div>=95<span class=3D"Apple-tab-span" style=3D"white-space:pre"> =
</span>Track

      record of excellence in global leadership and coaching within
      major organizations, at the intersection of public and private
      interests, with strong relevance to the Internet</div>
    <div>=95<span class=3D"Apple-tab-span" style=3D"white-space:pre"> =
</span>Familiarity
      and comfort with a multi-stakeholder universe, where consensus
      prevails over hierarchy</div>
    <div>=95<span class=3D"Apple-tab-span" style=3D"white-space:pre"> =
</span>Enthusiasm
      for and commitment to ISOC=92s mission and operating values</div>
    <div>=95<span class=3D"Apple-tab-span" style=3D"white-space:pre"> =
</span>An
      outstanding communicator and advocate, who engenders trust and who
      shows integrity and courage</div>
    <div>=95<span class=3D"Apple-tab-span" style=3D"white-space:pre"> =
</span>Strategic

      and integrative thinker, open to innovation, who sees the big and
      the small picture, and is streetwise and politically astute</div>
    <div>=95<span class=3D"Apple-tab-span" style=3D"white-space:pre"> =
</span>Genuinely
      multicultural, connects effectively with different cultures, value
      systems and business models</div>
    <div><br>
    </div>
    <div>ISOC is an Equal Employment Opportunity Employer and does not
      discriminate based on race, color, religion, national origin,
      ancestry, citizenship, marital status, veteran status, physical or
      mental disability, sex, sexual orientation, age or other protected
      characteristics and complies with all applicable laws and
      regulations.&nbsp;</div>
    <div><br>
    </div>
    <div>For further information and to apply, please =
contact:&nbsp;</div>
    <div>Bernard Tobin, Partner, at <a =
href=3D"mailto:ceo-isoc@odgersberndtson.be">ceo-isoc@odgersberndtson.be</a=
>.</div>
    <pre class=3D"moz-signature" cols=3D"72">--=20
-----------------------------
Eva Fr=F6lich
Frobbit AB

Mail: <a class=3D"moz-txt-link-abbreviated" =
href=3D"mailto:eva@frobbit.se">eva@frobbit.se</a>
<a class=3D"moz-txt-link-abbreviated" =
href=3D"http://www.frobbit.se/">www.frobbit.se</a>


</pre>
  </div>

</blockquote></div><br></body></html>=

--Apple-Mail=_253F281E-350B-43A6-8F69-EE9E7C038E9E--

From john-ietf@jck.com  Tue Jul  9 06:32:07 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59CFA21F9D7A for <ietf@ietfa.amsl.com>; Tue,  9 Jul 2013 06:32:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.549
X-Spam-Level: 
X-Spam-Status: No, score=-102.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J-A38zTDhiaV for <ietf@ietfa.amsl.com>; Tue,  9 Jul 2013 06:32:01 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 7D8C021F9CDD for <ietf@ietf.org>; Tue,  9 Jul 2013 06:32:01 -0700 (PDT)
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 1UwY1Q-000Koe-HK; Tue, 09 Jul 2013 09:32:00 -0400
Date: Tue, 09 Jul 2013 09:31:55 -0400
From: John C Klensin <john-ietf@jck.com>
To: noncom-chair-2013@ietf.org
Subject: Re: Final Announcement of Qualified Volunteers
Message-ID: <4F42151A549CD62F5BC9CB01@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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Jul 2013 13:32:07 -0000

--On Saturday, July 06, 2013 14:53 -0700 NomCom Chair 2013
<nomcom-chair-2013@ietf.org> wrote:

> I am pleased to announce that we have 140 qualified
> individuals who  have generously volunteered to serve as
> voting members of this year's  Nomcom.

Allison,

Given my previous comment about statistical assertions, a quick
look at this list sheds some additional light on cross-sections
of the community.  

(1) While you have 140 people from whom to do a random draw, the
"no more than two volunteers with the same primary affiliation"
(RFC 3777, Section 4, Bullet17) rule means that the actual nomcom
pool is only 81 even though some of the people are indeterminate
(I've made some assumptions about company boundaries -- other
assumptions would yield very slightly different results).  That
number is obtained by listing the companies and then counting
any company with more that two volunteers as having only two.  

Neither the 140 number nor the 81 number is incorrect, they just
measure different things.

(2) Four companies account for 44.3% of the volunteers.  As
others have pointed out, while having a very large number of
volunteers cannot produce more than two Nomcom voting seats due
to that restriction, it can virtually guarantee (statistical
randomness notwithstanding) that one will end up with one or two
seats.  Specifically, if the people selected constitute a
cross-section of the volunteers, then more than 10% of the pool
(14 volunteers) would predict to at least one seat.  Two
companies exceed that number and a third is very close.
Randomness could make the actual numbers either better or worse,
but, if an organization's goal were to assure at least one seat,
that seems easily accomplished.  Of course, having lots of
volunteers doesn't imply that an organization was trying to
accomplish any such thing -- it could just have a lot of
public-spirited IETF participants and policies that allow people
to commit the time.

(3) It is probably too late to even discuss it for this year
(see below) but it occurs to me that, if one wanted to minimize
the odds of organizations trying to game the nomcom selection
process, it would be rational to do a two step draw, first
randomly selecting two volunteers from any organization offering
more than two and then including only those two in the final
selection process.    On the other hand, that would give you
around 81 candidates for the final selection this year.  If
running the final selection against order 140 people rather than
order 81 causes the community to believe that it has a better
sample, then that option probably would not be appropriate.  I
am not, however, convinced that we would actually have consensus
for minimizing those odds, nor about whether a company's ability
to nearly guarantee that at least one of its employees will be
on the Nomcom by providing a large fraction of the volunteers
violates the provision of Section 4, bullet 16, of RFC 3777
requiring "...unbiased if no one can influence its outcome in
favor of a specific outcome".

Actually, if I read Bullet 16 correctly, the choice of methods
is up to you, with RFC 2777 (and 3797) being just examples. So,
in theory, you could make that change.  I wouldn't personally
recommend it, but you are the one who has personal
responsibility for things being fair and unbiased while this is
just a statistical exercise for me.

best,
   john


From Ted.Lemon@nominum.com  Tue Jul  9 06:50:03 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8995921F9FE1 for <ietf@ietfa.amsl.com>; Tue,  9 Jul 2013 06:50:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DxroQ9x1qSA3 for <ietf@ietfa.amsl.com>; Tue,  9 Jul 2013 06:49:56 -0700 (PDT)
Received: from exprod7og105.obsmtp.com (exprod7og105.obsmtp.com [64.18.2.163]) by ietfa.amsl.com (Postfix) with ESMTP id BD99921F9A98 for <ietf@ietf.org>; Tue,  9 Jul 2013 06:49:56 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob105.postini.com ([64.18.6.12]) with SMTP ID DSNKUdwVBHAY41qLcr6a3u/uTRNXUMw/oj6y@postini.com; Tue, 09 Jul 2013 06:49:56 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 299DA1B806D; Tue,  9 Jul 2013 06:49:56 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 0F181190052; Tue,  9 Jul 2013 06:49:56 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Tue, 9 Jul 2013 06:49:56 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Final Announcement of Qualified Volunteers
Thread-Topic: Final Announcement of Qualified Volunteers
Thread-Index: AQHOfKitACmjfPaISkGziW3QAHNMi5lc0mqA
Date: Tue, 9 Jul 2013 13:49:55 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775205FFB@mbx-01.win.nominum.com>
References: <4F42151A549CD62F5BC9CB01@JcK-HP8200.jck.com>
In-Reply-To: <4F42151A549CD62F5BC9CB01@JcK-HP8200.jck.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <B32308C91856D846BDD006EF6AFDAD62@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>, "<noncom-chair-2013@ietf.org>" <noncom-chair-2013@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Jul 2013 13:50:03 -0000

I find the presumption that IETF attendees employed by companies that send =
large number of attendees are robots to be somewhat distasteful.   It also =
doesn't match my experience.   I am sure that _some_ attendees from large c=
ompanies are just as partisan as you fear, but some are not.   So I am not =
convinced that your proposal would have a good outcome.


From scott.brim@gmail.com  Tue Jul  9 07:00:03 2013
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C26AF21F9FEA for <ietf@ietfa.amsl.com>; Tue,  9 Jul 2013 07:00:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3oSFUpf9ZWbW for <ietf@ietfa.amsl.com>; Tue,  9 Jul 2013 07:00:02 -0700 (PDT)
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 D461F21F9F9D for <ietf@ietf.org>; Tue,  9 Jul 2013 07:00:02 -0700 (PDT)
Received: by mail-oa0-f50.google.com with SMTP id k7so7941474oag.23 for <multiple recipients>; Tue, 09 Jul 2013 07:00:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=1vPRU6ffi9HAw4pzxJx28I45vYXh4HXRiCpnHlgJ/qA=; b=pH8kPEQbHr7x7QJYGoi0tjI0m1eSxI/979ga8uT5ieQOku7sOBhAkjO6PqlZ+Qxd9f 2FeNrHL867jXxwWvBeL8gXXO9wuUXAfUOSId8Sm79cYEr0LP5toBNA7JASQuQopIzM11 yoUZyYZ2YzCt261LhlS39Dxox7Rq7hplc3KxG1o5idI08ZBML/OYfMDa1dsquIDJK6cZ NpxyvmIeQUgyNge5quKChLsPIcv0eBi/PirPT+kIM7AJ3tHhT+PXNzlEHQngNTkotomx H6lSsFmRDbdpbBizhybSIv7qV/fjko0mKr8QXVxvEf3OEtHDVhShzfFLFKtDKZjDDy03 p9YQ==
X-Received: by 10.60.92.165 with SMTP id cn5mr24219019oeb.53.1373378402211; Tue, 09 Jul 2013 07:00:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.97.37 with HTTP; Tue, 9 Jul 2013 06:59:42 -0700 (PDT)
In-Reply-To: <4F42151A549CD62F5BC9CB01@JcK-HP8200.jck.com>
References: <4F42151A549CD62F5BC9CB01@JcK-HP8200.jck.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Tue, 9 Jul 2013 09:59:42 -0400
Message-ID: <CAPv4CP-9Fwi_OAzBS-STMTrie7H8R5KEqiL0uFE8+k-Eum5F3g@mail.gmail.com>
Subject: Re: Final Announcement of Qualified Volunteers
To: John C Klensin <john-ietf@jck.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org, noncom-chair-2013@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Jul 2013 14:00:04 -0000

On Tue, Jul 9, 2013 at 9:31 AM, John C Klensin <john-ietf@jck.com> wrote:
> if one wanted to minimize
> the odds of organizations trying to game the nomcom selection
> process, it would be rational to do a two step draw, first
> randomly selecting two volunteers from any organization offering
> more than two and then including only those two in the final
> selection process.    On the other hand, that would give you
> around 81 candidates for the final selection this year.  If
> running the final selection against order 140 people rather than
> order 81 causes the community to believe that it has a better
> sample, then that option probably would not be appropriate.

The sample is better at 140 if individuals represent themselves, but
not if they are swayed by their organizational affiliation, and
organization is now a significant factor in what we can expect from
volunteers -- not all, but even some of those from organizations where
the volunteers are long time participants.  I support this idea.  I
think the gain is greater than the loss, and it even fosters
diversity.

From david.black@emc.com  Mon Jul  8 13:44:31 2013
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B91621F9E18; Mon,  8 Jul 2013 13:44:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SYiHA9L0gMKd; Mon,  8 Jul 2013 13:44:26 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 798DA21F9E0D; Mon,  8 Jul 2013 13:44:24 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r68KhwW7016168 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 8 Jul 2013 16:44:07 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd03.lss.emc.com [10.254.221.145]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Mon, 8 Jul 2013 16:43:43 -0400
Received: from mxhub12.corp.emc.com (mxhub12.corp.emc.com [10.254.92.107]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r68Khg2q012722; Mon, 8 Jul 2013 16:43:43 -0400
Received: from mxhub40.corp.emc.com (128.222.70.107) by mxhub12.corp.emc.com (10.254.92.107) with Microsoft SMTP Server (TLS) id 8.3.297.1; Mon, 8 Jul 2013 16:43:42 -0400
Received: from mx15a.corp.emc.com ([169.254.1.184]) by mxhub40.corp.emc.com ([128.222.70.107]) with mapi; Mon, 8 Jul 2013 16:43:42 -0400
From: "Black, David" <david.black@emc.com>
To: "Black, David" <david.black@emc.com>, "stefan.winter@restena.lu" <stefan.winter@restena.lu>, "jsalowey@cisco.com" <jsalowey@cisco.com>, General Area Review Team <gen-art@ietf.org>
Date: Mon, 8 Jul 2013 16:43:41 -0400
Subject: Gen-ART review of draft-ietf-abfab-eapapplicability-04
Thread-Topic: Gen-ART review of draft-ietf-abfab-eapapplicability-04
Thread-Index: Ac5rzQ3h5Vr98eb9RParuraCHgwUcgQTfgIg
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712983F2C87@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE71298265158@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71298265158@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-EMM-MHVC: 1
X-Mailman-Approved-At: Tue, 09 Jul 2013 08:21:40 -0700
Cc: "abfab@ietf.org" <abfab@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Jul 2013 20:44:31 -0000

The -04 version of this draft resolves the minor issue noted in
the Gen-ART review of the -03 version.

There is a remaining editorial nit, in that the one use of
"non-network" in the -04 version would benefit from clarification.
I suggest the following text change to the start of the paragraph
that's split across pages 3 and 4 (change is to last line of excerpt):

OLD
   Operators need to carefully consider the security implications before
   relaxing these requirements.  One potentially serious attack exists
   when channel binding is not required and EAP authentication is
   introduced into an existing non-network service.

NEW
   Operators need to carefully consider the security implications before
   relaxing these requirements.  One potentially serious attack exists
   when channel binding is not required and EAP authentication is
   introduced into an existing service other than network access.
=09
Thanks,
--David

> -----Original Message-----
> From: Black, David
> Sent: Monday, June 17, 2013 10:39 PM
> To: stefan.winter@restena.lu; jsalowey@cisco.com; General Area Review Tea=
m
> Cc: ietf@ietf.org; abfab@ietf.org; Black, David
> Subject: Gen-ART review of draft-ietf-abfab-eapapplicability-03
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-ietf-abfab-eapapplicability-03
> Reviewer: David L. Black
> Review Date: June 17, 2003
> IETF LC End Date: June 17, 2003
>=20
> Summary:
> This draft is on the right track but has open issues, described in the re=
view.
>=20
> This draft updates the applicability statement for EAP to include usage
> for application layer access via EAP over GSSAPI.  Additional security
> requirements are introduced for environments in which EAP is used for
> that purpose.
>=20
> I found one open issue, which is minor, and may be editorial
>=20
> Major issues: None
>=20
> Minor issues: One
>=20
> The next to last paragraph on p.3 begins with this sentence:
>=20
>    For these reasons, channel binding MUST be implemented by peers, EAP
>    servers and AAA servers in environments where EAP authentication is
>    used to access application layer services.
>=20
> It appear that this "MUST" requirement applies to all uses of EAP,
> including network access authentication, not just application layer acces=
s
> authentication.  If so, that's not immediately obvious from the text, and
> an additional sentence should be added to make this clearer.  If not,
> the above sentence needs to exclude network access authentication from
> that requirement.
>=20
> Nits/editorial comments:
>=20
> The same paragraph (p.3) continues with:
>=20
>    In addition, channel
>    binding MUST default to being required by peers for non-network
>    authentication.  If the EAP server is aware that authentication is
>    for something other than a network service, it too MUST default to
>    requiring channel binding.
>=20
> What is meant by "non-network authentication" and "other than a network
> service"?  If those mean "other than for network access authentication"
> as the term "network access authentication" is used in section 1 and
> RFC 3748, that meaning should be clarified.
>=20
> idnits 2.12.17 generated this comment:
>=20
>   -- The document seems to lack a disclaimer for pre-RFC5378 work, but ma=
y
>      have content which was first submitted before 10 November 2008.  If =
you
>      have contacted all the original authors and they are all willing to =
grant
>      the BCP78 rights to the IETF Trust, then this is fine, and you can i=
gnore
>      this comment.  If not, you may need to add the pre-RFC5378 disclaime=
r.
>      (See the Legal Provisions document at
>      http://trustee.ietf.org/license-info for more information.)
>=20
> idnits appears to be confused ;-).  The -00 version of this draft is from
> 2012,
> and this draft does not contain sufficient material from RFC 3748 that wo=
uld
> raise that concern, so this comment should be ok to ignore.
>=20
> Thanks,
> --David
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
> +1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-7=
786
> david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> ----------------------------------------------------


From john-ietf@jck.com  Tue Jul  9 09:11:08 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61E8321F9D5E; Tue,  9 Jul 2013 09:11:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.556
X-Spam-Level: 
X-Spam-Status: No, score=-102.556 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cu0hlKJZci6l; Tue,  9 Jul 2013 09:11:02 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 812ED21F9C68; Tue,  9 Jul 2013 09:11:02 -0700 (PDT)
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 1UwaVH-000Lqv-OH; Tue, 09 Jul 2013 12:10:59 -0400
Date: Tue, 09 Jul 2013 12:10:54 -0400
From: John C Klensin <john-ietf@jck.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: Final Announcement of Qualified Volunteers
Message-ID: <F3F8EB0538136F450DE4B889@JcK-HP8200.jck.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775205FFB@mbx-01.win.nominum.com>
References: <4F42151A549CD62F5BC9CB01@JcK-HP8200.jck.com> <8D23D4052ABE7A4490E77B1A012B630775205FFB@mbx-01.win.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
Cc: nomcom-chair-2013@ietf.org, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Jul 2013 16:11:08 -0000

--On Tuesday, July 09, 2013 13:49 +0000 Ted Lemon
<Ted.Lemon@nominum.com> wrote:

> I find the presumption that IETF attendees employed by
> companies that send large number of attendees are robots to be
> somewhat distasteful.   It also doesn't match my experience.
> I am sure that _some_ attendees from large companies are just
> as partisan as you fear, but some are not.   So I am not
> convinced that your proposal would have a good outcome.

It was _not_ a proposal, merely an analysis of the numbers and
an exploration of alternatives.

I also didn't say "robots" or anything that could be reasonably
construed as robots.  I don't even have any experience that
would lead to expect that a company would expect any selected
Nomcom members to march in lockstep.

I do note that the "no more than two people with the same
primary affiliation" rule is part of RFC 3777 (BCP 10) and take
that as an indication that the community was unhappy with at
least the appearances of one company having more than 1/5 of
Nomcom voting membership.  That limit is not part of any
proposal I or, to my knowledge, others have made recently.  With
regard to that limit, my analysis is merely an exploration of
how the intent of that rule might best be satisfied.

I'd welcome a discussion of whether the analysis is correct or
not. You might reasonably believe that it is irrelevant.  But,
as far as disagreeing with a proposal or not, please wait until
someone makes one (fwiw, it won't be me).

    john




From arturo.servin@gmail.com  Tue Jul  9 12:53:27 2013
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 580CF11E8153; Tue,  9 Jul 2013 12:53:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d6fMXFFynC6F; Tue,  9 Jul 2013 12:53:24 -0700 (PDT)
Received: from mail-ye0-x22a.google.com (mail-ye0-x22a.google.com [IPv6:2607:f8b0:4002:c04::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 58DFE11E8143; Tue,  9 Jul 2013 12:53:23 -0700 (PDT)
Received: by mail-ye0-f170.google.com with SMTP id q3so2122311yen.29 for <multiple recipients>; Tue, 09 Jul 2013 12:53:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=yuNRKXbbp7iuaGaqdq+3+Il2mbzueUC6/kl8kgrMdh4=; b=z52Z6SPDGubf7daFuyxLQz8+XhQymMOf/mlnE7QgN9C+SSpbh/hs5wOH6dgXdCI4im OcHCBkwOR3+ORSGMev7vh17EsjL2OnaX7bLTfwlcldWnubLl4A0nFDZss2fp3hHzb1Ig wFhwyw1IEDcIgUitp6rQC7IfPQoaw2CdSRM9taghUNrXI0n/Tf7SH8aWoBXsIHCaafSw H7ASBM2UxbkKG+TV8p7sFmAnA+J9VoARHdIVZpQX8eRtCbzAoo8FxYCjIpO/xnY61uhg 8xg2BJGPmx+ldKTWp48OsD3hs48/51JkqxnrlVOAqpds5bdI4mjVlSCYYakVSTUjRLNX vtLQ==
X-Received: by 10.236.164.9 with SMTP id b9mr16044783yhl.151.1373399600328; Tue, 09 Jul 2013 12:53:20 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local ([2001:13c7:7001:7000:41a1:bbe0:a49:944b]) by mx.google.com with ESMTPSA id g66sm46958418yhd.11.2013.07.09.12.53.18 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 09 Jul 2013 12:53:19 -0700 (PDT)
Message-ID: <51DC6A2B.3090105@gmail.com>
Date: Tue, 09 Jul 2013 16:53:15 -0300
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org, chair@ietf.org
Subject: Re: Draft submission deadlines change
References: <20130703051701.22549.85585.idtracker@ietfa.amsl.com>
In-Reply-To: <20130703051701.22549.85585.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Jul 2013 19:53:27 -0000

Hello,

    I was checking the deadlines for submitting drafts. Clear it is
Monday 15th July but it does not say the time.

   
Thanks,
as

On 7/3/13 2:17 AM, IETF Chair wrote:
> Please note that for IETF 87, there is only one deadline for draft submission: Monday 15th July. Previously, there had been two different deadlines, one for -00 and another one for other versions. The IESG has decided to experiment with just one deadline for now to simplify the set of deadlines and enable easier submission of new drafts. While we realise that the change comes near the deadline, we hope that you find the extra time useful.
>
> But please do note that working group chairs will continue to make smart decisions about what topics are worthwhile for discussing in a session in the upcoming meeting, and will also set their agendas in a timely manner and create deadlines for their working groups that must be adhered to. The earlier new drafts are submitted, the more time there is to talk about them on the mailing lists and consider them for the session agendas. This is particularly important for BoFs.
>
> Jari Arkko for the IESG


From amorris@amsl.com  Tue Jul  9 12:56:52 2013
Return-Path: <amorris@amsl.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C118E21F9CAD; Tue,  9 Jul 2013 12:56:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.682
X-Spam-Level: 
X-Spam-Status: No, score=-2.682 tagged_above=-999 required=5 tests=[AWL=-0.083, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mgADqrEpn4Ww; Tue,  9 Jul 2013 12:56:48 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.21]) by ietfa.amsl.com (Postfix) with ESMTP id 6502921F9CA7; Tue,  9 Jul 2013 12:56:48 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id BAB80A8AC5; Tue,  9 Jul 2013 12:56:38 -0700 (PDT)
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 BHHzgUVpUzJ3; Tue,  9 Jul 2013 12:56:38 -0700 (PDT)
Received: from [64.170.98.186] (unknown [64.170.98.186]) by c9a.amsl.com (Postfix) with ESMTPSA id A0E51A8926; Tue,  9 Jul 2013 12:56:38 -0700 (PDT)
Subject: Re: Draft submission deadlines change
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Alexa Morris <amorris@amsl.com>
In-Reply-To: <51DC6A2B.3090105@gmail.com>
Date: Tue, 9 Jul 2013 12:59:34 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <C5009353-A854-4060-8793-4EA2D0DFF0CF@amsl.com>
References: <20130703051701.22549.85585.idtracker@ietfa.amsl.com> <51DC6A2B.3090105@gmail.com>
To: Arturo Servin <arturo.servin@gmail.com>
X-Mailer: Apple Mail (2.1085)
Cc: chair@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Jul 2013 19:56:53 -0000

Arturo,

The time is the same as usual (UTC 24:00) and it's posted online in the =
Important Dates section here: =
http://www.ietf.org/meeting/cutoff-dates-2013.html#IETF87.=20

Regards,
Alexa

On Jul 9, 2013, at 12:53 PM, Arturo Servin wrote:

> Hello,
>=20
>    I was checking the deadlines for submitting drafts. Clear it is
> Monday 15th July but it does not say the time.
>=20
>=20
> Thanks,
> as
>=20
> On 7/3/13 2:17 AM, IETF Chair wrote:
>> Please note that for IETF 87, there is only one deadline for draft =
submission: Monday 15th July. Previously, there had been two different =
deadlines, one for -00 and another one for other versions. The IESG has =
decided to experiment with just one deadline for now to simplify the set =
of deadlines and enable easier submission of new drafts. While we =
realise that the change comes near the deadline, we hope that you find =
the extra time useful.
>>=20
>> But please do note that working group chairs will continue to make =
smart decisions about what topics are worthwhile for discussing in a =
session in the upcoming meeting, and will also set their agendas in a =
timely manner and create deadlines for their working groups that must be =
adhered to. The earlier new drafts are submitted, the more time there is =
to talk about them on the mailing lists and consider them for the =
session agendas. This is particularly important for BoFs.
>>=20
>> Jari Arkko for the IESG
>=20

----------
Alexa Morris / Executive Director / IETF
48377 Fremont Blvd., Suite 117, Fremont, CA  94538
Phone: +1.510.492.4089 / Fax: +1.510.492.4001
Email: amorris@amsl.com

Managed by Association Management Solutions (AMS)
Forum Management, Meeting and Event Planning
www.amsl.com <http://www.amsl.com/>


From arturo.servin@gmail.com  Tue Jul  9 12:58:02 2013
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E9A721F9D82; Tue,  9 Jul 2013 12:58:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZObCamUzlsIy; Tue,  9 Jul 2013 12:58:02 -0700 (PDT)
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 D8B3221F9D71; Tue,  9 Jul 2013 12:58:01 -0700 (PDT)
Received: by mail-qc0-f170.google.com with SMTP id s1so3266760qcw.1 for <multiple recipients>; Tue, 09 Jul 2013 12:58:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=O6GvgSIiIeJ+yKjgR4xqbvUbzZP3j+UKAJvotn3A24s=; b=XUuudYhf3Bjw9TQtHu6pdUuT/vEOZavyIBx9a3AJU8j1flpeLtdVPAiOlhIY80u7RA 4vPE99SGiPCO0vPbpShStnDi7OcPQZeRca1cN7msjL4LB2mK0QNRvZdP3niXJLXmuYnY AReI7RLeTFXsmZcNGMAEgLMykLY+c0Bd+6XRVuuWt3LLj42//dKw48tfbYlXvXjUA+Id TtikAv80Q8Qn/lxyDo9CzNZPLAsNUgD9nz3H2EYfxA3EnA+Q7+9+ByPI+cppLNC3x/0l BToUCwguWrXlD9pxG0dYJujTjeAVJ35llwok8R7Yeg6wETju1Ybpsi5boC8WtntrE9zN oTAQ==
X-Received: by 10.49.26.35 with SMTP id i3mr22515989qeg.75.1373399881337; Tue, 09 Jul 2013 12:58:01 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local ([2001:13c7:7001:7000:41a1:bbe0:a49:944b]) by mx.google.com with ESMTPSA id w9sm16842230qas.8.2013.07.09.12.57.58 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 09 Jul 2013 12:58:00 -0700 (PDT)
Message-ID: <51DC6B45.1040501@gmail.com>
Date: Tue, 09 Jul 2013 16:57:57 -0300
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Alexa Morris <amorris@amsl.com>
Subject: Re: Draft submission deadlines change
References: <20130703051701.22549.85585.idtracker@ietfa.amsl.com> <51DC6A2B.3090105@gmail.com> <C5009353-A854-4060-8793-4EA2D0DFF0CF@amsl.com>
In-Reply-To: <C5009353-A854-4060-8793-4EA2D0DFF0CF@amsl.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: chair@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Jul 2013 19:58:02 -0000

    Thanks Alexa.

   
Best regards,
as
On 7/9/13 4:59 PM, Alexa Morris wrote:
> Arturo,
>
> The time is the same as usual (UTC 24:00) and it's posted online in the Important Dates section here: http://www.ietf.org/meeting/cutoff-dates-2013.html#IETF87. 
>
> Regards,
> Alexa
>
> On Jul 9, 2013, at 12:53 PM, Arturo Servin wrote:
>
>> Hello,
>>
>>    I was checking the deadlines for submitting drafts. Clear it is
>> Monday 15th July but it does not say the time.
>>
>>
>> Thanks,
>> as
>>
>> On 7/3/13 2:17 AM, IETF Chair wrote:
>>> Please note that for IETF 87, there is only one deadline for draft submission: Monday 15th July. Previously, there had been two different deadlines, one for -00 and another one for other versions. The IESG has decided to experiment with just one deadline for now to simplify the set of deadlines and enable easier submission of new drafts. While we realise that the change comes near the deadline, we hope that you find the extra time useful.
>>>
>>> But please do note that working group chairs will continue to make smart decisions about what topics are worthwhile for discussing in a session in the upcoming meeting, and will also set their agendas in a timely manner and create deadlines for their working groups that must be adhered to. The earlier new drafts are submitted, the more time there is to talk about them on the mailing lists and consider them for the session agendas. This is particularly important for BoFs.
>>>
>>> Jari Arkko for the IESG
> ----------
> Alexa Morris / Executive Director / IETF
> 48377 Fremont Blvd., Suite 117, Fremont, CA  94538
> Phone: +1.510.492.4089 / Fax: +1.510.492.4001
> Email: amorris@amsl.com
>
> Managed by Association Management Solutions (AMS)
> Forum Management, Meeting and Event Planning
> www.amsl.com <http://www.amsl.com/>
>


From ben@nostrum.com  Tue Jul  9 12:58:55 2013
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 207D321F9D80; Tue,  9 Jul 2013 12:58:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ezttndz4pXIg; Tue,  9 Jul 2013 12:58:54 -0700 (PDT)
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 C17D521F9CAD; Tue,  9 Jul 2013 12:58:53 -0700 (PDT)
Received: from [10.0.1.12] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r69JwpgG051378 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 9 Jul 2013 14:58:52 -0500 (CDT) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Gen-ART Telechat Review of draft-thornburgh-adobe-rtmfp-09
Date: Tue, 9 Jul 2013 14:58:51 -0500
Message-Id: <AE51780A-646A-4C82-9DAD-8557B06C75A5@nostrum.com>
To: "draft-thornburgh-adobe-rtmfp.all@tools.ietf.org" <draft-thornburgh-adobe-rtmfp.all@tools.ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
Received-SPF: pass (shaman.nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Jul 2013 19:58:55 -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>.
=20
Please wait for direction from your document shepherd or AD before =
posting a new version of the draft.
=20
Document: draft-thornburgh-adobe-rtmfp-09
Reviewer: Ben Campbell
Review Date: 2013-07-09
IESG Telechat date: 2013-07-11
=20
Summary: This draft is essentially ready for publication as an =
informational RFC. There is one issue from my previous review and =
related discussion that I think is almost, but not completely handled. =
All other concerns from my previous review have been addressed in this =
version.
=20
Major issues:
=20
There has been a fair amount of discussion about how this protocol =
requires a crypto profile to interoperate, and no such profiles are =
included, or otherwise widely published. If this were a standards track =
draft, I would argue for at least one mandatory-to-implement profile to =
be included or referenced. But since this is intended as an =
informational RFC that simply describes what certain products are doing, =
that's probably okay.  Furthermore, the author added a paragraph to the =
introduction specifically calling out the issue, which I applaud.=20

But I'd like to see that paragraph go a bit further, and explicitly =
mention any such profile needed to interoperate with the commercial =
products mentioned in the 2nd paragraph of section 1 has not been made =
available at the time of RFC publication, and that implementors should =
investigate the availability of such a profile prior to implementing =
this protocol for the purposes of interoperating with those products.

Minor issues:

None.

Nits/editorial comments:

None.=

From brian.e.carpenter@gmail.com  Tue Jul  9 13:40:50 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 414B321F9D09 for <ietf@ietfa.amsl.com>; Tue,  9 Jul 2013 13:40:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.422
X-Spam-Level: 
X-Spam-Status: No, score=-102.422 tagged_above=-999 required=5 tests=[AWL=0.177, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZvrLkcDeug14 for <ietf@ietfa.amsl.com>; Tue,  9 Jul 2013 13:40:49 -0700 (PDT)
Received: from mail-pa0-x234.google.com (mail-pa0-x234.google.com [IPv6:2607:f8b0:400e:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id DB35521F9CFB for <ietf@ietf.org>; Tue,  9 Jul 2013 13:40:49 -0700 (PDT)
Received: by mail-pa0-f52.google.com with SMTP id kq13so5873253pab.39 for <multiple recipients>; Tue, 09 Jul 2013 13:40:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=uYFFvCJjsRVqMsW8v5eyJ296AlRteNu9gh3vMgNRgxs=; b=rWqNx1R3iDsgoXNLvaVG/2nMEMdH0L8n8Pg9A9z/oTE5nRey14EwRDeVg7/wkhqRR/ zjO3lWyj9fGzzEg1kC+Y4d1tDmJ5DXiugt+y9HkG778X9IsLUiAejPCBVi3qYhI7kPaW UzqJpr58bwu4Izbzn5V21tWgW4zL3x2bz2pwtrJLe3pbwPAT2vOoCPjdegkx+hjq4Xem /gvAoQXwbp7RdPFghIqETPc5zjt37xbGMno3pw9Po/Cn80x0RdTE+Y4u3F2Tfn172gEZ cPhyuxIkOlyoNYP6zjMYiwEUk8ROpHORyvZMEe1ttAI8Hg8ulpvduj2qVZswzbhYESye dONA==
X-Received: by 10.68.96.229 with SMTP id dv5mr7669487pbb.89.1373402449639; Tue, 09 Jul 2013 13:40:49 -0700 (PDT)
Received: from [192.168.178.23] (211.192.69.111.dynamic.snap.net.nz. [111.69.192.211]) by mx.google.com with ESMTPSA id vb8sm29956804pbc.11.2013.07.09.13.40.47 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 09 Jul 2013 13:40:49 -0700 (PDT)
Message-ID: <51DC7552.5040900@gmail.com>
Date: Wed, 10 Jul 2013 08:40:50 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Final Announcement of Qualified Volunteers
References: <4F42151A549CD62F5BC9CB01@JcK-HP8200.jck.com>
In-Reply-To: <4F42151A549CD62F5BC9CB01@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, noncom-chair-2013@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Jul 2013 20:40:50 -0000

> (2) Four companies account for 44.3% of the volunteers.

OK, but what would X be in "Four companies account for X% of
people eligible to volunteer"?

That said, the "not more than two from the same employer" rule
was written in anticipation of a theoretical problem; it seems
that it was a good idea, but it does allow the following to become
true: "Four companies account for 67% of the NomCom members."

Should we consider changing it to "not more than one" in view
of today's data?

Regards
   Brian

From dhc@dcrocker.net  Tue Jul  9 13:54:30 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A772711E813A; Tue,  9 Jul 2013 13:54:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.591
X-Spam-Level: 
X-Spam-Status: No, score=-6.591 tagged_above=-999 required=5 tests=[AWL=0.008,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bzbxMwAEh5uI; Tue,  9 Jul 2013 13:54:25 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id F31FD21F9D8C; Tue,  9 Jul 2013 13:54:24 -0700 (PDT)
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 r69KsL5w009777 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 9 Jul 2013 13:54:24 -0700
Message-ID: <51DC7866.90106@dcrocker.net>
Date: Tue, 09 Jul 2013 13:53:58 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Final Announcement of Qualified Volunteers
References: <4F42151A549CD62F5BC9CB01@JcK-HP8200.jck.com> <51DC7552.5040900@gmail.com>
In-Reply-To: <51DC7552.5040900@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Tue, 09 Jul 2013 13:54:24 -0700 (PDT)
Cc: nomcom-chair-2013@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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, 09 Jul 2013 20:54:30 -0000

> Should we consider changing it to "not more than one" in view
> of today's data?


On it's face, that sounds like an absolutely Draconian rule.

However stepping back a bit, it should prompt a simple question:  Is the 
IETF so reliant on a tiny number of companies that we cannot produce 
viable committees if we require each member of a committee to be 
affiliated with a different company?

In other words, are we really incapable of requiring extensive corporate 
diversity?


d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From scott.brim@gmail.com  Tue Jul  9 13:59:01 2013
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E548B21F9D69; Tue,  9 Jul 2013 13:59:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SVzdSieDzEcc; Tue,  9 Jul 2013 13:59:01 -0700 (PDT)
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 6000521F9D58; Tue,  9 Jul 2013 13:59:01 -0700 (PDT)
Received: by mail-oa0-f42.google.com with SMTP id j6so8725091oag.29 for <multiple recipients>; Tue, 09 Jul 2013 13:59:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=lGCBZpTc7oVJxT8Q5jI9cSfd41jQTQr1UUH7xT8zRFs=; b=os6nOs0Z4eoZsbRuD8ZMAZxlRyybiKKKwCztS7qyuNrnPZXHewogsuNfdxXs8un4Ik 3yDtJvWTfGnHnnQMyUJK0gJ0dhUzcQhnonTZVg7eDlkTCMuCuMah+xEJNPzUxMiGuTFk 9HCMJBMrru/4b0QzWYnNbuEZYKPSZS7V0n4rso+y2XVcvM5Y1svjo7XpOy6+w8O88xZ3 9hKlZBU3B+NKCvEiHE414Ry+ImiX2agD7Mwu34/bDlDv5wbx7NmuHepwTvPNqYg1bH1K VuFuqInhKtwkutAvZyRB9p9dA7fAZ2MLb7/kok2oxO5dkuM2AIfvVbLgPDLYtAGNkwb6 Tviw==
X-Received: by 10.60.92.165 with SMTP id cn5mr25623304oeb.53.1373403540936; Tue, 09 Jul 2013 13:59:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.97.37 with HTTP; Tue, 9 Jul 2013 13:58:40 -0700 (PDT)
In-Reply-To: <51DC7866.90106@dcrocker.net>
References: <4F42151A549CD62F5BC9CB01@JcK-HP8200.jck.com> <51DC7552.5040900@gmail.com> <51DC7866.90106@dcrocker.net>
From: Scott Brim <scott.brim@gmail.com>
Date: Tue, 9 Jul 2013 16:58:40 -0400
Message-ID: <CAPv4CP_Avv9nuxKrjH1XxXPHGhhnGjCaAE58jpfd9noELKZyKQ@mail.gmail.com>
Subject: Re: Final Announcement of Qualified Volunteers
To: dcrocker@bbiw.net
Content-Type: text/plain; charset=ISO-8859-1
Cc: nomcom-chair-2013@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Jul 2013 20:59:02 -0000

On Tue, Jul 9, 2013 at 4:53 PM, Dave Crocker <dhc@dcrocker.net> wrote:
>
>> Should we consider changing it to "not more than one" in view
>> of today's data?
>
>
>
> On it's face, that sounds like an absolutely Draconian rule.
>
> However stepping back a bit, it should prompt a simple question:  Is the
> IETF so reliant on a tiny number of companies that we cannot produce viable
> committees if we require each member of a committee to be affiliated with a
> different company?
>
> In other words, are we really incapable of requiring extensive corporate
> diversity?

Is the great majority of the wisdom in the IETF incorporated into a
few megacorporations?

(That might reflect market share, in which case, is it a problem?)

From Ted.Lemon@nominum.com  Tue Jul  9 14:07:37 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B22C421F9A65; Tue,  9 Jul 2013 14:07:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XJ0zxVi2nGTW; Tue,  9 Jul 2013 14:07:31 -0700 (PDT)
Received: from exprod7og107.obsmtp.com (exprod7og107.obsmtp.com [64.18.2.167]) by ietfa.amsl.com (Postfix) with ESMTP id B976711E813A; Tue,  9 Jul 2013 14:07:30 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob107.postini.com ([64.18.6.12]) with SMTP ID DSNKUdx7kmHsYbPveoRpBn6GmByF8fFqu3Tx@postini.com; Tue, 09 Jul 2013 14:07:30 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 530991B823E; Tue,  9 Jul 2013 14:07:30 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 44569190052; Tue,  9 Jul 2013 14:07:30 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Tue, 9 Jul 2013 14:07:23 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: Final Announcement of Qualified Volunteers
Thread-Topic: Final Announcement of Qualified Volunteers
Thread-Index: AQHOfKitACmjfPaISkGziW3QAHNMi5ldRTkAgAADqwCAAAFQAIAAAm8A
Date: Tue, 9 Jul 2013 21:07:23 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775206ED4@mbx-01.win.nominum.com>
References: <4F42151A549CD62F5BC9CB01@JcK-HP8200.jck.com> <51DC7552.5040900@gmail.com> <51DC7866.90106@dcrocker.net> <CAPv4CP_Avv9nuxKrjH1XxXPHGhhnGjCaAE58jpfd9noELKZyKQ@mail.gmail.com>
In-Reply-To: <CAPv4CP_Avv9nuxKrjH1XxXPHGhhnGjCaAE58jpfd9noELKZyKQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <56F59877F3184B4FA4B1284747A70ACE@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<nomcom-chair-2013@ietf.org>" <nomcom-chair-2013@ietf.org>, "<dcrocker@bbiw.net>" <dcrocker@bbiw.net>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Jul 2013 21:07:37 -0000

On Jul 9, 2013, at 4:58 PM, Scott Brim <scott.brim@gmail.com> wrote:
> Is the great majority of the wisdom in the IETF incorporated into a
> few megacorporations?
>=20
> (That might reflect market share, in which case, is it a problem?)

I don't know the answer to that question, but it's an interesting question.=
   But the reason I reacted to John Klensin's message earlier the way I did=
 is that I think that the question of how biased toward the company's goals=
 a nomcom participant will be has a lot to do with the individual candidate=
.   And large companies do seem to tend to snap up long-time influential IE=
TF participants, so indeed it is likely that over time IETF knowledge will =
tend to concentrate in one large company or another.

That being the case, the current two-person rule could as easily be argued =
to be damaging to the process as beneficial to it.   I'm not making a claim=
 either way, but I think that absent statistically valid data, this discuss=
ion is completely theoretical.


From ynir@checkpoint.com  Tue Jul  9 14:37:25 2013
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0721B11E8173; Tue,  9 Jul 2013 14:37:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.546
X-Spam-Level: 
X-Spam-Status: No, score=-10.546 tagged_above=-999 required=5 tests=[AWL=0.053, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8MQZUcgVxrpD; Tue,  9 Jul 2013 14:37:19 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 3AE6F11E8179; Tue,  9 Jul 2013 14:37:11 -0700 (PDT)
Received: from IL-EX10.ad.checkpoint.com ([194.29.34.147]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r69Lb88J029586; Wed, 10 Jul 2013 00:37:09 +0300
X-CheckPoint: {51DC8284-1F-1B221DC2-1FFFF}
Received: from DAG-EX10.ad.checkpoint.com ([169.254.3.48]) by IL-EX10.ad.checkpoint.com ([169.254.2.91]) with mapi id 14.02.0342.003; Wed, 10 Jul 2013 00:37:08 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: Final Announcement of Qualified Volunteers
Thread-Topic: Final Announcement of Qualified Volunteers
Thread-Index: AQHOfKitACmjfPaISkGziW3QAHNMi5lcnZUAgAADrACAAAFQAIAAAm+AgAAIUYA=
Date: Tue, 9 Jul 2013 21:37:07 +0000
Message-ID: <2D9F6CF3-7947-4F60-948E-62E4D2ABCC3E@checkpoint.com>
References: <4F42151A549CD62F5BC9CB01@JcK-HP8200.jck.com> <51DC7552.5040900@gmail.com> <51DC7866.90106@dcrocker.net> <CAPv4CP_Avv9nuxKrjH1XxXPHGhhnGjCaAE58jpfd9noELKZyKQ@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B630775206ED4@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775206ED4@mbx-01.win.nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.20.63]
x-kse-antivirus-interceptor-info: protection disabled
x-cpdlp: 112940efe94c175e04b2e8a3873ca68aa50d7cf7ca
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <7ED2C0C697D80147B40ED41F0D240ECB@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "nomcom-chair-2013@ietf.org" <nomcom-chair-2013@ietf.org>, ietf Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Jul 2013 21:37:25 -0000

On Jul 10, 2013, at 12:07 AM, Ted Lemon <Ted.Lemon@nominum.com>
 wrote:

> On Jul 9, 2013, at 4:58 PM, Scott Brim <scott.brim@gmail.com> wrote:
>> Is the great majority of the wisdom in the IETF incorporated into a
>> few megacorporations?
>>=20
>> (That might reflect market share, in which case, is it a problem?)
>=20
> I don't know the answer to that question, but it's an interesting questio=
n.   But the reason I reacted to John Klensin's message earlier the way I d=
id is that I think that the question of how biased toward the company's goa=
ls a nomcom participant will be has a lot to do with the individual candida=
te. =20

I think that before we discuss the extent of the bias, we should explore th=
e question of whether such bias matters. Phrased as a question, how much ca=
n a nomcom member (or a pair of them) do to advance a company's goals? I've=
 heard that nomcom members recuse themselves from discussions of candidates=
 from their own company, so company X can't hope to get its employees appoi=
nted as ADs by stuffing the nomcom with other employees. Well, unless there=
's a huge back-room conspiracy among several such companies.=20

Company X might have a bunch of technologies that they want to bring to the=
 IETF to get them rubber-stamped as standards track RFCs, and they might wa=
nt to see to it that ADs that will be trouble-makers don't get elected. Tha=
t might even work (a single member is much more able to prevent someone bei=
ng appointed than to cause someone to be appointed) But such proposals coul=
d be defeated in working groups and at IETF last call long before they even=
 reach the IESG. I just don't see the benefit justifying the effort.

Yoav=

From sm@elandsys.com  Tue Jul  9 14:48:08 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 521C711E8164; Tue,  9 Jul 2013 14:48:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.597
X-Spam-Level: 
X-Spam-Status: No, score=-102.597 tagged_above=-999 required=5 tests=[AWL=0.002, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9eN+z-loUV-7; Tue,  9 Jul 2013 14:48:07 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id C71B111E8156; Tue,  9 Jul 2013 14:48:07 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.140.33]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r69LlqUr025104 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Jul 2013 14:48:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1373406485; bh=VnL53uccuga/8yI0GgGoAXekZT29l581MqyphCjPvPg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=aIXjKNktHk2HREzTw8+mx1yEhT9OxCNOjlv8aBCvql16NDf5I0WG3sEcpTsu6xKCr DE5IxJSICarhC0O4DcCD2fQd62yerqBfJef3sq67ALD5CK+6cPcZy44KTiPWOHAPLY XJ3PgoNbrrCOSb3VHA+A4FjEl/2yf6LDEqO6DNlg=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1373406485; i=@elandsys.com; bh=VnL53uccuga/8yI0GgGoAXekZT29l581MqyphCjPvPg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=CuHbWy5Ju/gY0dHi7hzv25+6vIimbj4md9Hq198kVT6gwVZHw9KSwqR8vq+sQLNAA 7edgYtAC+BLzPAC1K8DqkjOGY+4ooesIRwFEYr/ZqNsBtULTyrYIfpfuqZtrShsqVk CZEH+HZGCwddtBLrqmBw8k0EKZWYzNTHEYWyUUpY=
Message-Id: <6.2.5.6.2.20130709113355.0b7677a8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 09 Jul 2013 14:41:12 -0700
To: Ted Lemon <Ted.Lemon@nominum.com>, John C Klensin <john-ietf@jck.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Final Announcement of Qualified Volunteers
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775205FFB@mbx-01.win.nominu m.com>
References: <4F42151A549CD62F5BC9CB01@JcK-HP8200.jck.com> <8D23D4052ABE7A4490E77B1A012B630775205FFB@mbx-01.win.nominum.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: nomcom-chair-2013@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Jul 2013 21:48:08 -0000

At 06:49 09-07-2013, Ted Lemon wrote:
>I find the presumption that IETF attendees employed by companies 
>that send large number of attendees are robots to be somewhat 
>distasteful.   It also doesn't match my experience.   I am sure that 
>_some_ attendees from large companies are just as partisan as you 
>fear, but some are not.   So I am not convinced that your proposal 
>would have a good outcome.

I fixed the nomcom-chair-2013 email address as it does not make sense 
to send an email to an invalid address.

When designing a random selection a person has to ensure that the 
selection is such that the unbiased nature is publicly 
verifiable.  As John Klensin mentioned "four companies account for 
44.3% of the volunteers".  A similar question was raised by Sam 
Hartman previously.  When I looked at the affiliations over the years 
I noticed that two companies can easily get 40% of the vote.

The IETF works on the presumption of good faith.  Would a significant 
number of attendees from large companies adopt a partisan 
approach?  It's difficult for the public to determine that.  I'll 
change the question: does anyone believe that the average attendee 
from a large company will take a decision which is in the interest of 
the IETF Community even though that decision conflicts with what 
would be in the interest of the company?

That's not the better question though.  What is NomCom about?  The 
possible answers are not in the RFCs.

Anyway, the initial message was about having a broad pool and doing 
an unbiased selection from it.  The pool may have less people but it 
is broader in the sense that there would be people from all walks of 
the IETF.  I think that's what Jari Arkko might be referring to when 
he writes the word "inclusive".

Regards,
S. Moonesamy  


From doug.mtview@gmail.com  Tue Jul  9 14:53:00 2013
Return-Path: <doug.mtview@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26A5A11E816F; Tue,  9 Jul 2013 14:53:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id daU94zT7TQeE; Tue,  9 Jul 2013 14:52:59 -0700 (PDT)
Received: from mail-pa0-x234.google.com (mail-pa0-x234.google.com [IPv6:2607:f8b0:400e:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id 48A0711E8171; Tue,  9 Jul 2013 14:52:58 -0700 (PDT)
Received: by mail-pa0-f52.google.com with SMTP id kq13so5962150pab.25 for <multiple recipients>; Tue, 09 Jul 2013 14:52:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=DgSCyx1arzwE6Hse+E2rerEzm13ZGJET74+BhhLaMs4=; b=Tyx8BH4LfCUCpnFjhONwujMY4KsVY2Nl9BkjuyWa/dkYXZ2GfSRlf/+W83HZqwF21i Yq/4afyKYDzQlydWvbu0zc35XvgKg5xJ9rsS7UBrMrK3gCg0besVHmVbfTOXvpma4fHx bOJZlQFEvV1dROMiCJay8w2fDOo23uIL6phteA/AGaZx3sFtp15LAs39r6Kb/fiand+f KTX+QOMfYpia+xPvh01U3Ge6ljqE65xyOsQ30LOJAQDEN2J6kG5j2Pq9bU7JvbgfDi6a vgKUX4ZN7yx4UEzC6rl9qJnfox7My3RBET2kqCsGgWpkb4jSCUOExZi+n7Nc6eCsyIDV p6Fw==
X-Received: by 10.68.97.229 with SMTP id ed5mr28534297pbb.37.1373406777628; Tue, 09 Jul 2013 14:52:57 -0700 (PDT)
Received: from ?IPv6:2601:9:3180:3e:5434:9108:2a08:6ebf? ([2601:9:3180:3e:5434:9108:2a08:6ebf]) by mx.google.com with ESMTPSA id ep4sm2596568pbd.35.2013.07.09.14.52.55 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 09 Jul 2013 14:52:56 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Final Announcement of Qualified Volunteers
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775206ED4@mbx-01.win.nominum.com>
Date: Tue, 9 Jul 2013 14:52:55 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <34CDC0AC-1BE1-4A42-8432-1B59CFBB7AFD@gmail.com>
References: <4F42151A549CD62F5BC9CB01@JcK-HP8200.jck.com> <51DC7552.5040900@gmail.com> <51DC7866.90106@dcrocker.net> <CAPv4CP_Avv9nuxKrjH1XxXPHGhhnGjCaAE58jpfd9noELKZyKQ@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B630775206ED4@mbx-01.win.nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1508)
Cc: "<nomcom-chair-2013@ietf.org>" <nomcom-chair-2013@ietf.org>, "<dcrocker@bbiw.net>" <dcrocker@bbiw.net>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Jul 2013 21:53:00 -0000

On Jul 9, 2013, at 2:07 PM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> On Jul 9, 2013, at 4:58 PM, Scott Brim <scott.brim@gmail.com> wrote:
>> Is the great majority of the wisdom in the IETF incorporated into a
>> few megacorporations?
>>=20
>> (That might reflect market share, in which case, is it a problem?)
>=20
> I don't know the answer to that question, but it's an interesting =
question.   But the reason I reacted to John Klensin's message earlier =
the way I did is that I think that the question of how biased toward the =
company's goals a nomcom participant will be has a lot to do with the =
individual candidate.   And large companies do seem to tend to snap up =
long-time influential IETF participants, so indeed it is likely that =
over time IETF knowledge will tend to concentrate in one large company =
or another.
>=20
> That being the case, the current two-person rule could as easily be =
argued to be damaging to the process as beneficial to it.   I'm not =
making a claim either way, but I think that absent statistically valid =
data, this discussion is completely theoretical.

Dear Ted,

=46rom my experience, some projects have been thwarted through actions =
of a few companies.  The direction taken ended up being doomed which may =
have been the ultimate goal and potentially represents a real fairness =
issue IMHO.

Regards,
Douglas Otis =20


From mthornbu@adobe.com  Tue Jul  9 15:09:44 2013
Return-Path: <mthornbu@adobe.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 911E211E817C; Tue,  9 Jul 2013 15:09:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vU+9n1ttO6uJ; Tue,  9 Jul 2013 15:09:37 -0700 (PDT)
Received: from exprod6og111.obsmtp.com (exprod6og111.obsmtp.com [64.18.1.27]) by ietfa.amsl.com (Postfix) with ESMTP id 6CB9D11E8175; Tue,  9 Jul 2013 15:09:35 -0700 (PDT)
Received: from outbound-smtp-2.corp.adobe.com ([193.104.215.16]) by exprod6ob111.postini.com ([64.18.5.12]) with SMTP ID DSNKUdyKFSXa5o+m18yy7oGztmueyi6/2Sjt@postini.com; Tue, 09 Jul 2013 15:09:36 PDT
Received: from inner-relay-1.corp.adobe.com (inner-relay-1.corp.adobe.com [153.32.1.51]) by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id r69M9NAI008831; Tue, 9 Jul 2013 15:09:23 -0700 (PDT)
Received: from nahub02.corp.adobe.com (nahub02.corp.adobe.com [10.8.189.98]) by inner-relay-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id r69M2g6I018016; Tue, 9 Jul 2013 15:09:21 -0700 (PDT)
Received: from nambx08.corp.adobe.com ([10.8.189.94]) by nahub02.corp.adobe.com ([10.8.189.98]) with mapi; Tue, 9 Jul 2013 15:03:24 -0700
From: Michael Thornburgh <mthornbu@adobe.com>
To: Ben Campbell <ben@nostrum.com>, "draft-thornburgh-adobe-rtmfp.all@tools.ietf.org" <draft-thornburgh-adobe-rtmfp.all@tools.ietf.org>
Date: Tue, 9 Jul 2013 15:03:23 -0700
Subject: RE: Gen-ART Telechat Review of draft-thornburgh-adobe-rtmfp-09
Thread-Topic: Gen-ART Telechat Review of draft-thornburgh-adobe-rtmfp-09
Thread-Index: Ac583sYXYAi/c8CwRiingf+U1YZ89QADR/hA
Message-ID: <D9D602D39A98E34D9C43E965BEC74398261AB600@nambx08.corp.adobe.com>
References: <AE51780A-646A-4C82-9DAD-8557B06C75A5@nostrum.com>
In-Reply-To: <AE51780A-646A-4C82-9DAD-8557B06C75A5@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Jul 2013 22:09:44 -0000

hi Ben.

your "like to see" is entirely reasonable, and the following text will be i=
n the next revision once my AD or Document Shepherd directs me to post it:

   Note to implementers: at the time of writing, the Cryptography
   Profile used by the above mentioned Adobe products is not publicly
   described by Adobe.  Implementers should investigate the availability
   of documentation of that Cryptography Profile prior to implementing
   RTMFP for the purpose of interoperation with the above mentioned
   Adobe products.

thank you.

-michael thornburgh


> From: Ben Campbell [mailto:ben@nostrum.com]
> Sent: Tuesday, July 09, 2013 12:59 PM
>=20
> 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>.
>=20
> Please wait for direction from your document shepherd or AD before postin=
g a new version of the draft.
>=20
> Document: draft-thornburgh-adobe-rtmfp-09
> Reviewer: Ben Campbell
> Review Date: 2013-07-09
> IESG Telechat date: 2013-07-11
>=20
> Summary: This draft is essentially ready for publication as an informatio=
nal RFC. There is one issue
> from my previous review and related discussion that I think is almost, bu=
t not completely handled. All
> other concerns from my previous review have been addressed in this versio=
n.
>=20
> Major issues:
>=20
> There has been a fair amount of discussion about how this protocol requir=
es a crypto profile to
> interoperate, and no such profiles are included, or otherwise widely publ=
ished. If this were a
> standards track draft, I would argue for at least one mandatory-to-implem=
ent profile to be included or
> referenced. But since this is intended as an informational RFC that simpl=
y describes what certain
> products are doing, that's probably okay.  Furthermore, the author added =
a paragraph to the
> introduction specifically calling out the issue, which I applaud.
>=20
> But I'd like to see that paragraph go a bit further, and explicitly menti=
on any such profile needed to
> interoperate with the commercial products mentioned in the 2nd paragraph =
of section 1 has not been
> made available at the time of RFC publication, and that implementors shou=
ld investigate the
> availability of such a profile prior to implementing this protocol for th=
e purposes of interoperating
> with those products.
>=20
> Minor issues:
>=20
> None.
>=20
> Nits/editorial comments:
>=20
> None.

From ben@nostrum.com  Tue Jul  9 15:12:19 2013
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E302B21E804D; Tue,  9 Jul 2013 15:12:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.373
X-Spam-Level: 
X-Spam-Status: No, score=-101.373 tagged_above=-999 required=5 tests=[AWL=-1.228, BAYES_00=-2.599, FRT_ADOBE2=2.455, SPF_PASS=-0.001,  USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hF4kldosMtVO; Tue,  9 Jul 2013 15:12:19 -0700 (PDT)
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 2F75E21F9C8D; Tue,  9 Jul 2013 15:12:19 -0700 (PDT)
Received: from [10.0.1.12] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r69MCAAT065769 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 9 Jul 2013 17:12:10 -0500 (CDT) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Gen-ART Telechat Review of draft-thornburgh-adobe-rtmfp-09
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <D9D602D39A98E34D9C43E965BEC74398261AB600@nambx08.corp.adobe.com>
Date: Tue, 9 Jul 2013 17:12:09 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <579008D9-8C34-439B-BEE0-BF73EF25636B@nostrum.com>
References: <AE51780A-646A-4C82-9DAD-8557B06C75A5@nostrum.com> <D9D602D39A98E34D9C43E965BEC74398261AB600@nambx08.corp.adobe.com>
To: Michael Thornburgh <mthornbu@adobe.com>
X-Mailer: Apple Mail (2.1508)
Received-SPF: pass (shaman.nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>, "draft-thornburgh-adobe-rtmfp.all@tools.ietf.org" <draft-thornburgh-adobe-rtmfp.all@tools.ietf.org>, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Jul 2013 22:12:20 -0000

Thanks Michael, that note would completely resolve my concern, and =
change my review summary to "ready for publication".

Ben.

On Jul 9, 2013, at 5:03 PM, Michael Thornburgh <mthornbu@adobe.com> =
wrote:

> hi Ben.
>=20
> your "like to see" is entirely reasonable, and the following text will =
be in the next revision once my AD or Document Shepherd directs me to =
post it:
>=20
>   Note to implementers: at the time of writing, the Cryptography
>   Profile used by the above mentioned Adobe products is not publicly
>   described by Adobe.  Implementers should investigate the =
availability
>   of documentation of that Cryptography Profile prior to implementing
>   RTMFP for the purpose of interoperation with the above mentioned
>   Adobe products.
>=20
> thank you.
>=20
> -michael thornburgh
>=20
>=20
>> From: Ben Campbell [mailto:ben@nostrum.com]
>> Sent: Tuesday, July 09, 2013 12:59 PM
>>=20
>> 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>.
>>=20
>> Please wait for direction from your document shepherd or AD before =
posting a new version of the draft.
>>=20
>> Document: draft-thornburgh-adobe-rtmfp-09
>> Reviewer: Ben Campbell
>> Review Date: 2013-07-09
>> IESG Telechat date: 2013-07-11
>>=20
>> Summary: This draft is essentially ready for publication as an =
informational RFC. There is one issue
>> from my previous review and related discussion that I think is =
almost, but not completely handled. All
>> other concerns from my previous review have been addressed in this =
version.
>>=20
>> Major issues:
>>=20
>> There has been a fair amount of discussion about how this protocol =
requires a crypto profile to
>> interoperate, and no such profiles are included, or otherwise widely =
published. If this were a
>> standards track draft, I would argue for at least one =
mandatory-to-implement profile to be included or
>> referenced. But since this is intended as an informational RFC that =
simply describes what certain
>> products are doing, that's probably okay.  Furthermore, the author =
added a paragraph to the
>> introduction specifically calling out the issue, which I applaud.
>>=20
>> But I'd like to see that paragraph go a bit further, and explicitly =
mention any such profile needed to
>> interoperate with the commercial products mentioned in the 2nd =
paragraph of section 1 has not been
>> made available at the time of RFC publication, and that implementors =
should investigate the
>> availability of such a profile prior to implementing this protocol =
for the purposes of interoperating
>> with those products.
>>=20
>> Minor issues:
>>=20
>> None.
>>=20
>> Nits/editorial comments:
>>=20
>> None.


From l.wood@surrey.ac.uk  Tue Jul  9 15:13:31 2013
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48ABD21F9C8F for <ietf@ietfa.amsl.com>; Tue,  9 Jul 2013 15:13:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.124
X-Spam-Level: 
X-Spam-Status: No, score=-3.124 tagged_above=-999 required=5 tests=[AWL=-0.526, BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HX6VkIkCYe4D for <ietf@ietfa.amsl.com>; Tue,  9 Jul 2013 15:13:26 -0700 (PDT)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.139]) by ietfa.amsl.com (Postfix) with ESMTP id 307FF21F9C8C for <ietf@ietf.org>; Tue,  9 Jul 2013 15:13:21 -0700 (PDT)
Received: from [195.245.231.67:17156] by server-3.bemta-5.messagelabs.com id 14/DB-09186-00B8CD15; Tue, 09 Jul 2013 22:13:20 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-7.tower-82.messagelabs.com!1373407999!25889650!1
X-Originating-IP: [131.227.200.35]
X-StarScan-Received: 
X-StarScan-Version: 6.9.9; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 18265 invoked from network); 9 Jul 2013 22:13:19 -0000
Received: from exht021p.surrey.ac.uk (HELO EXHT021P.surrey.ac.uk) (131.227.200.35) by server-7.tower-82.messagelabs.com with AES128-SHA encrypted SMTP; 9 Jul 2013 22:13:19 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT021P.surrey.ac.uk ([131.227.200.35]) with mapi; Tue, 9 Jul 2013 23:13:19 +0100
From: <l.wood@surrey.ac.uk>
To: <l.wood@surrey.ac.uk>, <ietf@ietf.org>
Date: Tue, 9 Jul 2013 23:08:37 +0100
Subject: RE: Final Announcement of Qualified Volunteers
Thread-Topic: Final Announcement of Qualified Volunteers
Thread-Index: Ac56k3eMACmjfPaISkGziW3QAHNMiwBGqStoAACWuDIAUBlQWg==
Message-ID: <290E20B455C66743BE178C5C84F12408223F494EF5@EXMB01CMS.surrey.ac.uk>
References: <20130706215330.8850.38261.idtracker@ietfa.amsl.com>, <290E20B455C66743BE178C5C84F12408223F494EE8@EXMB01CMS.surrey.ac.uk>, <290E20B455C66743BE178C5C84F12408223F494EE9@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F12408223F494EE9@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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Jul 2013 22:13:31 -0000

Ah, Allison actually misspelled it in setting her reply-to. So all replies =
would bounce.

Seriously guys, nom-com is the way to go to reduce this confusion. Needs a =
minus.

Lloyd Wood
http://sat-net.com/L.Wood/

On plus side, I didn't make the typo, only copied it and couldn't spot it. =
Go me!


________________________________________
From: Wood L  Dr (Electronic Eng)
Sent: 08 July 2013 08:55
To: l.wood@surrey.ac.uk; ietf@ietf.org; noncom-chair-2013@ietf.org
Subject: RE: Final Announcement of Qualified Volunteers

Gah. Am idiot misspelling it, sorry.

Lloyd Wood
http://sat-net.com/L.Wood/


________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of l.wood@sur=
rey.ac.uk [l.wood@surrey.ac.uk]
Sent: 08 July 2013 08:38
To: ietf@ietf.org; noncom-chair-2013@ietf.org
Subject: RE: Final Announcement of Qualified Volunteers

Email to noncom-chair-2013@ietf.org appears to fail - bounce below.

From spencerdawkins.ietf@gmail.com  Tue Jul  9 15:59:15 2013
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7119B11E8195; Tue,  9 Jul 2013 15:59:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.543
X-Spam-Level: 
X-Spam-Status: No, score=-2.543 tagged_above=-999 required=5 tests=[AWL=0.056,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xNk5ncTaDOge; Tue,  9 Jul 2013 15:59:15 -0700 (PDT)
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 B7B4911E818D; Tue,  9 Jul 2013 15:59:14 -0700 (PDT)
Received: by mail-ob0-f180.google.com with SMTP id eh20so7570093obb.25 for <multiple recipients>; Tue, 09 Jul 2013 15:59:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=BrPQ7wVpx8WwJjRYpqclmzp4oV32S7a+0PlimKDJQDU=; b=liV6sqhEd1gpW5lakKvNDhFc01ZZRGn8iTm3UO9IRqhk8okezogsu+WemIjsulsb1V wdXmBPi5sz5yTOj/YvyJHrm96sqfw9UN3HDRRLrkULR+PKxTn24o03Fu5jSF1tnXi1CO vtOTkYu7qvuQBbbw5vRW2fgfZTqoQ/GtWOUCFvWRnCdVVfCLXAlLwyhuOdORGak2VOCl 8xkeo0m8uGuMZvKc+gwMCK4WxE6DUEaJuPcrFcydIu/JYvojOZwe0VQMZteVdyMwvqh6 R75DPKJLl+ZZ8x1AvMCUbpx2FjEFVFsr2lWpiGbLy85LxIqp/K5by6w9T37ZZ1I2JF0C cMlQ==
X-Received: by 10.60.99.42 with SMTP id en10mr25845823oeb.85.1373410754316; Tue, 09 Jul 2013 15:59:14 -0700 (PDT)
Received: from [192.168.1.77] (99-108-174-213.lightspeed.rcsntx.sbcglobal.net. [99.108.174.213]) by mx.google.com with ESMTPSA id rs1sm40526220obb.12.2013.07.09.15.59.12 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 09 Jul 2013 15:59:13 -0700 (PDT)
Message-ID: <51DC9582.60100@gmail.com>
Date: Tue, 09 Jul 2013 17:58:10 -0500
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: Final Announcement of Qualified Volunteers
References: <4F42151A549CD62F5BC9CB01@JcK-HP8200.jck.com> <CAPv4CP-9Fwi_OAzBS-STMTrie7H8R5KEqiL0uFE8+k-Eum5F3g@mail.gmail.com>
In-Reply-To: <CAPv4CP-9Fwi_OAzBS-STMTrie7H8R5KEqiL0uFE8+k-Eum5F3g@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: John C Klensin <john-ietf@jck.com>, nomcom-chair-2013@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Jul 2013 22:59:15 -0000

On 7/9/2013 8:59 AM, Scott Brim wrote:
> The sample is better at 140 if individuals represent themselves, but 
> not if they are swayed by their organizational affiliation, and 
> organization is now a significant factor in what we can expect from 
> volunteers -- not all, but even some of those from organizations where 
> the volunteers are long time participants. I support this idea. I 
> think the gain is greater than the loss, and it even fosters diversity. 

I don't have a lot of time to chat about this, but

- I agree with Scott that it matters what voting members are guided by 
(organization, personal experience, intuition, flipping coins ...)
- I suspect that it's not possible to predict what any 10 voting members 
chosen at random will be guided by
- I'm not sure we can even know what the 10 voting members *were* guided 
by, unless the behavior is so bad that the advisor freaks out or the 
chair tells us in the plenary Nomcom report

If people want to think about the Nomcom volunteer pool, it may be 
useful to wonder about whether the perspective of voting members from 
more organizations would help the Nomcom make better choices.

Of course, I'm not sure we can predict that, either :-)

Spencer

From randy@psg.com  Tue Jul  9 16:23:18 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69F7111E80CC for <ietf@ietfa.amsl.com>; Tue,  9 Jul 2013 16:23:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.584
X-Spam-Level: 
X-Spam-Status: No, score=-2.584 tagged_above=-999 required=5 tests=[AWL=0.015,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q3H-CAU+wqPx for <ietf@ietfa.amsl.com>; Tue,  9 Jul 2013 16:23:07 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 4E05F11E80C5 for <ietf@ietf.org>; Tue,  9 Jul 2013 16:23:07 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1UwhFQ-0001pw-BI; Tue, 09 Jul 2013 23:23:04 +0000
Date: Tue, 09 Jul 2013 13:23:03 -1000
Message-ID: <m2li5f5ne0.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
Subject: Re: Final Announcement of Qualified Volunteers
In-Reply-To: <51DC9582.60100@gmail.com> <2D9F6CF3-7947-4F60-948E-62E4D2ABCC3E@checkpoint.com>
References: <4F42151A549CD62F5BC9CB01@JcK-HP8200.jck.com> <CAPv4CP-9Fwi_OAzBS-STMTrie7H8R5KEqiL0uFE8+k-Eum5F3g@mail.gmail.com> <51DC9582.60100@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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Jul 2013 23:23:18 -0000

Spencer Dawkins wrote:

> - I'm not sure we can even know what the 10 voting members *were*
>   guided by, unless the behavior is so bad that the advisor freaks out
>   or the chair tells us in the plenary Nomcom report

and Yoav Nir wrote:

> how much can a nomcom member (or a pair of them) do to advance a
> company's goals?

< reality check >

the ietf is no longer a collegiate collection of engineers, computer
scientists, and operators.  sad to say, we need to get past that fantasy
of the good old days.  and i would point out that traditional SDOs are
generally users trying to get multi-vendor interoperability and choice,
not vendors throwing weight proportional to market share.

but physics says we do this in an environment which is dominated by the
vendors being the ones who can afford the cost to have a strong presence
in the ietf, see <http://archive.psg.com/051000.ccr-ivtf.html>.

and i believe that there is a real problem, not just fud and theory.

i *heard* (from reliable sources, plural, but not witnssed) that there
was a nomcom where company X said that an employee of X must be chosen
for the iesg or <very negative financial and political consequences>
would ensue.

randy

From doug.mtview@gmail.com  Tue Jul  9 16:30:57 2013
Return-Path: <doug.mtview@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2730411E80D3; Tue,  9 Jul 2013 16:30:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q2dZ2p6JAsI6; Tue,  9 Jul 2013 16:30:56 -0700 (PDT)
Received: from mail-pb0-x22a.google.com (mail-pb0-x22a.google.com [IPv6:2607:f8b0:400e:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 7F7F611E80C5; Tue,  9 Jul 2013 16:30:51 -0700 (PDT)
Received: by mail-pb0-f42.google.com with SMTP id un1so6065832pbc.15 for <multiple recipients>; Tue, 09 Jul 2013 16:30:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=3wQax1nG/cRhOFWGVkklG6mU+GmedZbKWzmxzkmo248=; b=lcUX9D6ri8eMdvKr8WAbnk03Pksey8DTPoNV44wzcAQko1JvyZT5iYpJWHG2o+kx3q ZKuZLO7HiEldU44SDmzR6TwMyHTjjleyL9iZYJ8XmKGv0QJGIvuX0wSK8eTTyIwrNv/4 Dun7lsbj295JvJt/gDHsmWoRbJS9iyShOZa1Yi2wYcR3Axch6RH++lKiTV8c9BHqoR76 G8qyOY9BLpbXt/VcQP3TDyEBgGI1QwDDr30SL67iEMiFLsnZq5gKBUnuikkbQKZvCn9w RMvimDLUhFWHKJaXvxnGwMa6bf6zoeKhbMPzXNKWWNYogs6Uh/aq4qqUt9X3vZqFru03 ZrDg==
X-Received: by 10.66.25.10 with SMTP id y10mr29942899paf.96.1373412651243; Tue, 09 Jul 2013 16:30:51 -0700 (PDT)
Received: from ?IPv6:2601:9:3180:3e:5434:9108:2a08:6ebf? ([2601:9:3180:3e:5434:9108:2a08:6ebf]) by mx.google.com with ESMTPSA id iq6sm30495382pbc.1.2013.07.09.16.30.49 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 09 Jul 2013 16:30:50 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Final Announcement of Qualified Volunteers
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <51DC9582.60100@gmail.com>
Date: Tue, 9 Jul 2013 16:30:49 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <37832A14-1AA6-4E46-A0EE-5E0690569ECB@gmail.com>
References: <4F42151A549CD62F5BC9CB01@JcK-HP8200.jck.com> <CAPv4CP-9Fwi_OAzBS-STMTrie7H8R5KEqiL0uFE8+k-Eum5F3g@mail.gmail.com> <51DC9582.60100@gmail.com>
To: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
X-Mailer: Apple Mail (2.1508)
Cc: John C Klensin <john-ietf@jck.com>, nomcom-chair-2013@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Jul 2013 23:30:57 -0000

On Jul 9, 2013, at 3:58 PM, Spencer Dawkins =
<spencerdawkins.ietf@gmail.com> wrote:

> On 7/9/2013 8:59 AM, Scott Brim wrote:
>> The sample is better at 140 if individuals represent themselves, but =
not if they are swayed by their organizational affiliation, and =
organization is now a significant factor in what we can expect from =
volunteers -- not all, but even some of those from organizations where =
the volunteers are long time participants. I support this idea. I think =
the gain is greater than the loss, and it even fosters diversity.=20
>=20
> I don't have a lot of time to chat about this, but
>=20
> - I agree with Scott that it matters what voting members are guided by =
(organization, personal experience, intuition, flipping coins ...)
> - I suspect that it's not possible to predict what any 10 voting =
members chosen at random will be guided by
> - I'm not sure we can even know what the 10 voting members *were* =
guided by, unless the behavior is so bad that the advisor freaks out or =
the chair tells us in the plenary Nomcom report
>=20
> If people want to think about the Nomcom volunteer pool, it may be =
useful to wonder about whether the perspective of voting members from =
more organizations would help the Nomcom make better choices.
>=20
> Of course, I'm not sure we can predict that, either :-)

Dear Spencer,

Precisely because it is impossible to judge motivations, the only way to =
ensure fairness is to ensure broad participation.  It seems unfortunate =
an organization dedicated to developing the Internet has not done more =
to ensure those obtaining remote access are not treated as second class =
participants.  This should greatly increase the available talent.  The =
larger pool could be coupled with a meeting subscription to offset the =
loss of fees collected at meeting venues.=20

To improve the experience, a flash based netbook coupled with the =
projector and PA could improve remote access into being much closer to a =
face-to-face experience worthy of fees requested.  Importantly, both =
face-to-face and remote participants should be able to obtain equal =
roles.  If the Internet is down, so is the meeting.  That may make venue =
selection more dependent upon the quality of the Internet availability.

Imagine real time translations made possible actually enhancing regional =
understanding.

Regards,
Douglas Otis=

From d3e3e3@gmail.com  Tue Jul  9 16:43:26 2013
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86CC421F9C84 for <ietf@ietfa.amsl.com>; Tue,  9 Jul 2013 16:43:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LILdItFJT06z for <ietf@ietfa.amsl.com>; Tue,  9 Jul 2013 16:43:26 -0700 (PDT)
Received: from mail-ob0-x22f.google.com (mail-ob0-x22f.google.com [IPv6:2607:f8b0:4003:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id E1E2421F9BF9 for <ietf@ietf.org>; Tue,  9 Jul 2013 16:43:25 -0700 (PDT)
Received: by mail-ob0-f175.google.com with SMTP id xn12so7593450obc.20 for <multiple recipients>; Tue, 09 Jul 2013 16:43:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=zZgMaegfVXy+ol4DvNhX35cWkKjIAUg/m1Ga5jGUQ5E=; b=kr8wjqOsrJDQRmEEi7jcCEoBxo2oqegAVR6dIKN+h5DhLzO/jXFWnwqvp/uxGXVrye 4J6xnDjY6LOZm2YWCWnpj5IkfOmjngp2El61WFY1dZz6/Uc6cq/NyVdDz4hmus3X3Ffq znjuG6Su1YQ1P8OMQjLq81utuXqMJX7gzsj9GcN3DPTYmwEOztSp0X3CjE4tv4fnSynt str/JmaXtb1O2Ir7/a+vTwRE8yAlDR2FUgH5WhC1JuHK9XNtIxj1gNi4gVc2hFEuMYga M6+emvFgBY6v3pk5VaMEkLObAZIljDOuUgtb/mjIecNjicBnVf/kWIY0a1Pal2dXMaDV h1vQ==
X-Received: by 10.60.42.101 with SMTP id n5mr25932178oel.4.1373413404399; Tue, 09 Jul 2013 16:43:24 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.73.106 with HTTP; Tue, 9 Jul 2013 16:43:04 -0700 (PDT)
In-Reply-To: <4F42151A549CD62F5BC9CB01@JcK-HP8200.jck.com>
References: <4F42151A549CD62F5BC9CB01@JcK-HP8200.jck.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 9 Jul 2013 19:43:04 -0400
Message-ID: <CAF4+nEH7N6QC=m4mcE2XOXYHmnefKTNDa7XRqhuDtXT_-v3Vjg@mail.gmail.com>
Subject: Re: Final Announcement of Qualified Volunteers
To: John C Klensin <john-ietf@jck.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org, noncom-chair-2013@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Jul 2013 23:43:26 -0000

Hi John,

Excuse me for replying to just part of your message below:

On Tue, Jul 9, 2013 at 9:31 AM, John C Klensin <john-ietf@jck.com> wrote:
>
>...
>
> (3) It is probably too late to even discuss it for this year
> (see below) but it occurs to me that, if one wanted to minimize
> the odds of organizations trying to game the nomcom selection
> process, it would be rational to do a two step draw, first
> randomly selecting two volunteers from any organization offering
> more than two and then including only those two in the final
> selection process.    On the other hand, that would give you
> around 81 candidates for the final selection this year.  If

The current two nomcom member per sponsor limit is really pretty much
of an honor system by self declaration. The Nomcom chair has no need
to bindingly determine what affiliation every volunteer has. Only as
nomcom members are selected does the Nomcom chair have to even think
about this. I think that, as a result, there are probably at most a
handful of cases where the Nomcom chair has to worry about this at all
including ambiguous cases such as someone working for a subsidiary of
a company that sponsors someone already selected for noncom or
consultations that nominally work for a separate organization but are
X% funded for their IETF work by BigCompany for various values of X.
Any "two step" rule as you suggest will move affiliation from a tail
end check designed to be sure that the nomcom passes the smell test to
the heart of the selection process. I think the result would be a
mess.

However, if such a system were adopted, its not like an upfront
selection to 2 per sponsor is the only alternative to the current
unlimited pool from which the noncom is selected. Just to give an
example of an alternative rule, since you have to classify all
volunteers as to who their sponsor is, you could do initially a select
among the V volunteers from sponsor S limited to the square root of V
rounded up. That would seem like a more moderate intermediate course.

> running the final selection against order 140 people rather than
> order 81 causes the community to believe that it has a better
> sample, then that option probably would not be appropriate.  I
> am not, however, convinced that we would actually have consensus
> for minimizing those odds, nor about whether a company's ability
> to nearly guarantee that at least one of its employees will be
> on the Nomcom by providing a large fraction of the volunteers
> violates the provision of Section 4, bullet 16, of RFC 3777
> requiring "...unbiased if no one can influence its outcome in
> favor of a specific outcome".

In my opinion, those words, in the context of the previous sentence
which speaks of each volunteer being equally likely to be selected,
means influence in favor of a particular volunteer or the like.
(Although all volunteers are equally likely to be selected, the
selections are ordered and after two have been selected with the same
affiliate, subsequent selections with the same affiliation are
discarded and additional selection(s) made.)

> ...

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

> best,
>    john
>

From d3e3e3@gmail.com  Tue Jul  9 17:05:41 2013
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37C1011E8117 for <ietf@ietfa.amsl.com>; Tue,  9 Jul 2013 17:05:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bh8XNff5n3yL for <ietf@ietfa.amsl.com>; Tue,  9 Jul 2013 17:05:40 -0700 (PDT)
Received: from mail-oa0-x236.google.com (mail-oa0-x236.google.com [IPv6:2607:f8b0:4003:c02::236]) by ietfa.amsl.com (Postfix) with ESMTP id B2EE511E80E0 for <ietf@ietf.org>; Tue,  9 Jul 2013 17:05:40 -0700 (PDT)
Received: by mail-oa0-f54.google.com with SMTP id o6so8935302oag.27 for <multiple recipients>; Tue, 09 Jul 2013 17:05:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=67GxtCH+P9OmpWhcI3VZBUSgvpzjTGNB3diNMpGHBbs=; b=JTIL1bYwxDZ+/f+i/RyUBZAyHNax6IIsZyFLDJTjT8lnyBwM0Zni8Y4/qlW3V6uO4h MkiSmJDpq/E67H5/v8rabVn1z/CxI+uZj5KUb1BNFb/uxE7BYrXJVocDpzERPRHW9Cyx 5gWZ15vKIv/g3CYzTohevG7ZF3fZYd/bhSdDEgFzCeY15X5UYG/dJtfN39vAADeO7lZP BsXblwQxQhX3li1+4Pv23z3qQsT6Q3nAXfjXuR2dgEHUS5QVh3n92CMryjVqYDGMmeXH LE0Nz1Ad78AznxuhTOjHOtxUys69bC23DUbKyfRv1mBMO5XG5erOjsqZTVkO4JAvUiQM /pPg==
X-Received: by 10.182.142.104 with SMTP id rv8mr21351321obb.3.1373414740293; Tue, 09 Jul 2013 17:05:40 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.73.106 with HTTP; Tue, 9 Jul 2013 17:05:20 -0700 (PDT)
In-Reply-To: <51DC7552.5040900@gmail.com>
References: <4F42151A549CD62F5BC9CB01@JcK-HP8200.jck.com> <51DC7552.5040900@gmail.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 9 Jul 2013 20:05:20 -0400
Message-ID: <CAF4+nEHtKxycP-1UfD2LmzKHb37FChy0M8zh+uqagRDVAA25zw@mail.gmail.com>
Subject: Re: Final Announcement of Qualified Volunteers
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: John C Klensin <john-ietf@jck.com>, ietf@ietf.org, noncom-chair-2013@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Jul 2013 00:05:41 -0000

Hi Brian,

On Tue, Jul 9, 2013 at 4:40 PM, Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:
>> (2) Four companies account for 44.3% of the volunteers.
>
> OK, but what would X be in "Four companies account for X% of
> people eligible to volunteer"?
>
> That said, the "not more than two from the same employer" rule
> was written in anticipation of a theoretical problem; it seems

I think not. If I recall correctly, there was at least one noncom with
three voting members with the same affiliation. While there was no
particular evidence that these voting members were acting as other
than individuals, the consensus was that it just smelled bad and so
the limit of two per primary affiliation was adopted. (Also note that,
according to the records, the first two nomcoms had only 7 voting
members.)

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

> that it was a good idea, but it does allow the following to become
> true: "Four companies account for 67% of the NomCom members."
>
> Should we consider changing it to "not more than one" in view
> of today's data?
>
> Regards
>    Brian

From l.wood@surrey.ac.uk  Tue Jul  9 17:27:34 2013
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85E4F11E80BA; Tue,  9 Jul 2013 17:27:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.086
X-Spam-Level: 
X-Spam-Status: No, score=-3.086 tagged_above=-999 required=5 tests=[AWL=-0.488, BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FSz7YLVlE0uk; Tue,  9 Jul 2013 17:27:30 -0700 (PDT)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.151]) by ietfa.amsl.com (Postfix) with ESMTP id 8EB0221F9B0E; Tue,  9 Jul 2013 17:27:22 -0700 (PDT)
Received: from [85.158.136.51:38274] by server-15.bemta-5.messagelabs.com id 9A/30-01226-86AACD15; Wed, 10 Jul 2013 00:27:20 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-2.tower-49.messagelabs.com!1373416040!20072252!1
X-Originating-IP: [131.227.200.35]
X-StarScan-Received: 
X-StarScan-Version: 6.9.9; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 7310 invoked from network); 10 Jul 2013 00:27:20 -0000
Received: from exht021p.surrey.ac.uk (HELO EXHT021P.surrey.ac.uk) (131.227.200.35) by server-2.tower-49.messagelabs.com with AES128-SHA encrypted SMTP; 10 Jul 2013 00:27:20 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT021P.surrey.ac.uk ([131.227.200.35]) with mapi; Wed, 10 Jul 2013 01:27:19 +0100
From: <l.wood@surrey.ac.uk>
To: <dcrocker@bbiw.net>, <ietf@ietf.org>
Date: Wed, 10 Jul 2013 01:23:47 +0100
Subject: RE: Final Announcement of Qualified Volunteers
Thread-Topic: Final Announcement of Qualified Volunteers
Thread-Index: Ac585paUvG/UfgXWSy+S48mzSubmVgAHSgbz
Message-ID: <290E20B455C66743BE178C5C84F12408223F494EF8@EXMB01CMS.surrey.ac.uk>
References: <4F42151A549CD62F5BC9CB01@JcK-HP8200.jck.com> <51DC7552.5040900@gmail.com>,<51DC7866.90106@dcrocker.net>
In-Reply-To: <51DC7866.90106@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
Cc: nomcom-chair-2013@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Jul 2013 00:27:34 -0000

I do recall a case where both chairs of a WG belonged to a Major Organizati=
on.

World domination was thwarted, however, because the chairs couldn't actuall=
y
agree on anything; the organization was big enough that competing views
were widespread within it.

Much to the frustration of other members of the Major Organization.
And the members of the working group.

This suggests that we can't produce viable committees _anyway_.

Lloyd Wood
http://sat-net.com/L.Wood/


________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Dave Crock=
er [dhc@dcrocker.net]
Sent: 09 July 2013 21:53
To: ietf@ietf.org
Cc: nomcom-chair-2013@ietf.org
Subject: Re: Final Announcement of Qualified Volunteers

> Should we consider changing it to "not more than one" in view
> of today's data?


On it's face, that sounds like an absolutely Draconian rule.

However stepping back a bit, it should prompt a simple question:  Is the
IETF so reliant on a tiny number of companies that we cannot produce
viable committees if we require each member of a committee to be
affiliated with a different company?

In other words, are we really incapable of requiring extensive corporate
diversity?


d/


--
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From dhc@dcrocker.net  Tue Jul  9 18:23:36 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2020421F9C10; Tue,  9 Jul 2013 18:23:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.591
X-Spam-Level: 
X-Spam-Status: No, score=-6.591 tagged_above=-999 required=5 tests=[AWL=0.007,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CUXtFVkIMDMC; Tue,  9 Jul 2013 18:23:31 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 2A8EA21F9BD4; Tue,  9 Jul 2013 18:23:31 -0700 (PDT)
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 r6A1NR51014307 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 9 Jul 2013 18:23:30 -0700
Message-ID: <51DCB777.8000602@dcrocker.net>
Date: Tue, 09 Jul 2013 18:23:03 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: l.wood@surrey.ac.uk
Subject: Re: Final Announcement of Qualified Volunteers
References: <4F42151A549CD62F5BC9CB01@JcK-HP8200.jck.com> <51DC7552.5040900@gmail.com>, <51DC7866.90106@dcrocker.net> <290E20B455C66743BE178C5C84F12408223F494EF8@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F12408223F494EF8@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]); Tue, 09 Jul 2013 18:23:31 -0700 (PDT)
Cc: nomcom-chair-2013@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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, 10 Jul 2013 01:23:36 -0000

On 7/9/2013 5:23 PM, l.wood@surrey.ac.uk wrote:
> I do recall a case where both chairs of a WG belonged to a Major Organization.
>
> World domination was thwarted, however, because the chairs couldn't actually
> agree on anything; the organization was big enough that competing views
> were widespread within it.
>
> Much to the frustration of other members of the Major Organization.
> And the members of the working group.
>
> This suggests that we can't produce viable committees _anyway_.


As usual, what it suggests is that we think that individual 
counter-examples somehow refute basic, well-established principles.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From dhc@dcrocker.net  Tue Jul  9 18:35:54 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7606F21F9A18; Tue,  9 Jul 2013 18:35:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.592
X-Spam-Level: 
X-Spam-Status: No, score=-6.592 tagged_above=-999 required=5 tests=[AWL=0.007,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GiKckFeoR4Jr; Tue,  9 Jul 2013 18:35:49 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 8259721F9A05; Tue,  9 Jul 2013 18:35:49 -0700 (PDT)
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 r6A1Zin5014497 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 9 Jul 2013 18:35:47 -0700
Message-ID: <51DCBA58.5020701@dcrocker.net>
Date: Tue, 09 Jul 2013 18:35:20 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: Final Announcement of Qualified Volunteers
References: <4F42151A549CD62F5BC9CB01@JcK-HP8200.jck.com> <51DC7552.5040900@gmail.com> <51DC7866.90106@dcrocker.net> <CAPv4CP_Avv9nuxKrjH1XxXPHGhhnGjCaAE58jpfd9noELKZyKQ@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B630775206ED4@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775206ED4@mbx-01.win.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]); Tue, 09 Jul 2013 18:35:47 -0700 (PDT)
Cc: "<nomcom-chair-2013@ietf.org>" <nomcom-chair-2013@ietf.org>, "<dcrocker@bbiw.net>" <dcrocker@bbiw.net>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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, 10 Jul 2013 01:35:54 -0000

On 7/9/2013 2:07 PM, Ted Lemon wrote:
> On Jul 9, 2013, at 4:58 PM, Scott Brim <scott.brim@gmail.com> wrote:
>> Is the great majority of the wisdom in the IETF incorporated into
>> a few megacorporations?
>>
>> (That might reflect market share, in which case, is it a problem?)
>
> I don't know the answer to that question, but it's an interesting
> question.   But the reason I reacted to John Klensin's message
> earlier the way I did is that I think that the question of how biased
> toward the company's goals a nomcom participant will be has a lot to
> do with the individual candidate.

Yes it does, but unfortunately that is irrelevant.

The concept of conflict of interest is not concerned with whether an 
individual's behavior is problematic, but whether there is an inherent 
tension amongst different interests for the person.  In other words, 
it's about the situational potential, not personal integrity.

There are two ways to deal with conflict of interest.

The first is to prohibit it.  If a person has competing situational 
influences, they are excluded.

In many environments -- and especially ones with industry participants 
doing industry work, like a standards body -- it is not possible to 
create a 'neutral' situation.  So the alternative is to 'balance' things 
through diversity, ensuring that the situational forces pull in many 
different directions.  (Actually, this also means we ought to mean we 
limit the number of router vendors or MTA vendors or... in positions of 
control for individual committees.)


> And large companies do seem to
> tend to snap up long-time influential IETF participants, so indeed it
> is likely that over time IETF knowledge will tend to concentrate in
> one large company or another.

Trends towards industry concentration are a long-standing challenge.  To 
the extent that the IETF wishes to continue to be inclusive, diversity 
pressures means it needs to limit the /ability/ of the giants to dominate.

Again, it has nothing to do with the motives or style of any of the 
giants.  It has to due with a requirement that others are assured equal 
opportunity to participate and influence.

d/



-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From iab-chair@iab.org  Tue Jul  9 20:34:19 2013
Return-Path: <iab-chair@iab.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E4BA11E810E; Tue,  9 Jul 2013 20:34:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.486
X-Spam-Level: 
X-Spam-Status: No, score=-101.486 tagged_above=-999 required=5 tests=[AWL=-0.556, BAYES_00=-2.599, DATE_IN_PAST_06_12=1.069, J_CHICKENPOX_53=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bn+72D-WUtMM; Tue,  9 Jul 2013 20:34:15 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.21]) by ietfa.amsl.com (Postfix) with ESMTP id 2383C11E8199; Tue,  9 Jul 2013 20:34:15 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id 24AE4A8939; Tue,  9 Jul 2013 20:34:04 -0700 (PDT)
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 DoPNmBKlkNaF; Tue,  9 Jul 2013 20:34:04 -0700 (PDT)
Received: from [192.168.2.109] (pool-96-241-156-29.washdc.fios.verizon.net [96.241.156.29]) by c9a.amsl.com (Postfix) with ESMTPSA id 8DD8FA890D; Tue,  9 Jul 2013 20:34:03 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Subject: Second Call for Volunteers to Serve on the ICANN Nominating Committee
Mime-Version: 1.0 (Apple Message framework v1085)
From: IAB Chair <iab-chair@iab.org>
Date: Tue, 9 Jul 2013 16:09:47 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <FC4B2D1A-369E-4045-B854-90450676D660@iab.org>
To: IETF Announce <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1085)
Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 10 Jul 2013 03:34:19 -0000

Please note that the deadline for volunteering is 19 July 2013.  Please =
pass this call for volunteer to anyone that might be interested.

Russ

=3D =3D =3D =3D =3D =3D =3D =3D =3D =3D

Dear Colleagues,

The IAB (on behalf of the IETF) has been asked to supply a member to the =
2014 ICANN Nominating Committee (NomCom) by 15 August 2013. We would =
therefore like to ask the community for volunteers to serve on the ICANN =
NomCom. If you are interested, please send a short e-mail to iab-chair =
at iab.org with a copy to execd at iab.org with your motivation and =
information concerning your familiarity with the IETF and ICANN.  The =
deadline for volunteering is 19 July 2013.

The IAB will select from the available candidates, taking into account =
the familiarity with ICANN and the IETF, their roles, and their =
processes. The selected candidate will serve on the ICANN NomCom on =
personal title; however, we will be looking for a candidate who has an =
understanding of the interests of the technical community.

The ICANN NomCom process itself is governed by the ICANN bylaws; an =
abstract of the relevant articles can be found at =
http://nomcom.icann.org/bylaws.htm.  In addition, each NomCom determines =
a number of its own operational procedures, including the role of the =
NomCom in recruiting and selecting candidates.

The ICANN Nominating Committee typically meets in person at or around =
three consecutive ICANN meetings. The first of these meetings, when the=20=

committee is formally established, will be held  22-23 November 2013 =
following the Buenos Aires ICANN meeting on 17-21 November. The =
committee will next attend the "Spring" ICANN meeting, which in 2014 =
will be in Singapore on 23-27 March 2014. Finally, the committee will =
meet during and after the "Summer" ICANN meeting in London on 22-26 June =
2014 where the final slate of candidates for the ICANN Board, the GNSO, =
ccNSO,and ALAC will be agreed upon.

Candidates should be able to join monthly teleconferences (typically at =
UTC 14:00), with the expectation that these teleconferences will held =
weekly during the candidate assessment process in May-June.

NOTE: ICANN does cover travel and hotel costs for a pre-determined =
number of days at each of the 3 consecutive ICANN meetings.

For more information about the ICANN NomCom see: =
http://nomcom.icann.org/.  If you are willing to be considered or would =
like to nominate someone for the position, please send an email to =
iab-chair at iab.org and execd at iab.org.

On behalf of the IAB,
Russ Housley
IAB Chair=

From john-ietf@jck.com  Tue Jul  9 20:54:25 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C568A11E810C; Tue,  9 Jul 2013 20:54:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.566
X-Spam-Level: 
X-Spam-Status: No, score=-102.566 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jsYLUD-HsTH9; Tue,  9 Jul 2013 20:54:20 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id E972911E8105; Tue,  9 Jul 2013 20:54:19 -0700 (PDT)
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 1UwlTv-000MrV-0W; Tue, 09 Jul 2013 23:54:19 -0400
Date: Tue, 09 Jul 2013 23:54:13 -0400
From: John C Klensin <john-ietf@jck.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Subject: Re: Final Announcement of Qualified Volunteers
Message-ID: <C58909260F10019223103F0D@JcK-HP8200.jck.com>
In-Reply-To: <CAF4+nEH7N6QC=m4mcE2XOXYHmnefKTNDa7XRqhuDtXT_-v3Vjg@mail.gmail.com>
References: <4F42151A549CD62F5BC9CB01@JcK-HP8200.jck.com> <CAF4+nEH7N6QC=m4mcE2XOXYHmnefKTNDa7XRqhuDtXT_-v3Vjg@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: nomcom-chair-2013@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Jul 2013 03:54:25 -0000

--On Tuesday, July 09, 2013 19:43 -0400 Donald Eastlake
<d3e3e3@gmail.com> wrote:

> Hi John,
> 
> Excuse me for replying to just part of your message below:

No problem.
I found your explanation helpful.    Two observations at the
risk of repeating myself....

(1) I did not make a proposal.  I did point out that there were
other possibilities within the general bounds of the "no more
than two" rule.  Beyond that, about as far as I'm willing to go
is to say that different mechanisms (the current ordered list,
selecting a company down to two candidates, your square root of
V alternate suggestion, and maybe some other things) each have
advantages and disadvantages and, probably, each optimizes for
something different or deals with a different marginal case.  I
suspect that, most of the time, the differences in practice are
likely to be trivial (or smaller).   But I haven't even tried to
do the analyses in large part because I think they would be much
too speculative.

(2) In response to Brian, you wrote...

>> That said, the "not more than two from the same employer" rule
>> was written in anticipation of a theoretical problem; it seems
> 
> I think not. If I recall correctly, there was at least one
> noncom with three voting members with the same affiliation.
> While there was no particular evidence that these voting
> members were acting as other than individuals, the consensus
> was that it just smelled bad and so the limit of two ...

The "bad smell" issue is, IMO, far more important than any
discussions of whether people or organizations have misbehaved
or might misbehave in the future.  It is especially important
should we have another round of discussions about antitrust
policies because, for an SDO, the ability, even in principle,
for one organization or set of interests to dominate a body or
its leadership selection process can easily create a lawyer's
playground.  I don't think it would be wise to try to completely
eliminate that risk even if it were possible, but passing a
smell test is nonetheless important for multiple reasons.

best,
   john


From bob.hinden@gmail.com  Wed Jul 10 08:52:20 2013
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62A5421F9C7E; Wed, 10 Jul 2013 08:52:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gBbNTf7EwbAH; Wed, 10 Jul 2013 08:52:19 -0700 (PDT)
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 DB37721F9D45; Wed, 10 Jul 2013 08:52:10 -0700 (PDT)
Received: by mail-ea0-f179.google.com with SMTP id b15so5132310eae.10 for <multiple recipients>; Wed, 10 Jul 2013 08:52:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=C0TQFIUzLKt7sIyyVgimBqzjo6GDq8c+WwyL9PByTXk=; b=mqwOtOxc1HbWrcvMJzdMuZdcd4X/kD3GS5a+o3lgOB+6IyaJCQCCMi2B/grRY3GMGs cL4MQOgg1ygMQ1VV2hTuMJUZjJ+tU8jkyAhMWnzEzAdZBnadkqQn8mgzpNWAgb579ziL 1T88QFY1e8POIj0MPH2za5GmlbcVYtP2sQz1CqFToSwIOos3W/SNDzfq5+yzuBaX22Q5 K751C0l6BbFnB0Xm+4ZgBLHupSxoEK7I/kUxYa8aiuePm9672tzvWjzfcdJGipHR1hse V0uen/N6/KYLe2jYNXxnBH5aZe+fF1Xz+IQXKOom0n3f4UgoK46a8chK7Oda5nvm/jsk RBhg==
X-Received: by 10.15.91.69 with SMTP id r45mr37003233eez.79.1373471529878; Wed, 10 Jul 2013 08:52:09 -0700 (PDT)
Received: from ?IPv6:2601:9:4080:10:a405:8a8a:8864:a035? ([2601:9:4080:10:a405:8a8a:8864:a035]) by mx.google.com with ESMTPSA id cg12sm60936365eeb.7.2013.07.10.08.52.05 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 10 Jul 2013 08:52:07 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Final Announcement of Qualified Volunteers
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <290E20B455C66743BE178C5C84F12408223F494EF8@EXMB01CMS.surrey.ac.uk>
Date: Wed, 10 Jul 2013 08:52:01 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <47F56A59-1CF9-40B3-AAF9-690AD0841F81@gmail.com>
References: <4F42151A549CD62F5BC9CB01@JcK-HP8200.jck.com> <51DC7552.5040900@gmail.com>, <51DC7866.90106@dcrocker.net> <290E20B455C66743BE178C5C84F12408223F494EF8@EXMB01CMS.surrey.ac.uk>
To: l.wood@surrey.ac.uk
X-Mailer: Apple Mail (2.1508)
Cc: nomcom-chair-2013@ietf.org, Bob Hinden <bob.hinden@gmail.com>, dcrocker@bbiw.net, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Jul 2013 15:52:20 -0000

Lloyd,

On Jul 9, 2013, at 5:23 PM, l.wood@surrey.ac.uk wrote:

> I do recall a case where both chairs of a WG belonged to a Major =
Organization.
>=20
> World domination was thwarted, however, because the chairs couldn't =
actually
> agree on anything; the organization was big enough that competing =
views
> were widespread within it.
>=20
> Much to the frustration of other members of the Major Organization.
> And the members of the working group.

I can think of one company who uses to IETF to have internal arguments.  =
But at the same time, I can think of another company who is very aligned =
in how they participate in the IETF.  Many others are somewhere in =
between.  There isn't a single model here.

Bob


From dhc@dcrocker.net  Wed Jul 10 08:59:00 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA6EB21F9EC7; Wed, 10 Jul 2013 08:59:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.592
X-Spam-Level: 
X-Spam-Status: No, score=-6.592 tagged_above=-999 required=5 tests=[AWL=0.007,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N9sIVjhel1rg; Wed, 10 Jul 2013 08:58:42 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 586B611E8124; Wed, 10 Jul 2013 08:58:23 -0700 (PDT)
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 r6AFwIa2030346 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 10 Jul 2013 08:58:22 -0700
Message-ID: <51DD8482.7050502@dcrocker.net>
Date: Wed, 10 Jul 2013 08:57:54 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Bob Hinden <bob.hinden@gmail.com>
Subject: Re: Final Announcement of Qualified Volunteers
References: <4F42151A549CD62F5BC9CB01@JcK-HP8200.jck.com> <51DC7552.5040900@gmail.com>, <51DC7866.90106@dcrocker.net> <290E20B455C66743BE178C5C84F12408223F494EF8@EXMB01CMS.surrey.ac.uk> <47F56A59-1CF9-40B3-AAF9-690AD0841F81@gmail.com>
In-Reply-To: <47F56A59-1CF9-40B3-AAF9-690AD0841F81@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, 10 Jul 2013 08:58:22 -0700 (PDT)
Cc: nomcom-chair-2013@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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, 10 Jul 2013 15:59:01 -0000

On 7/10/2013 8:52 AM, Bob Hinden wrote:
> On Jul 9, 2013, at 5:23 PM, l.wood@surrey.ac.uk wrote:
>> I do recall a case where both chairs of a WG belonged to a Major Organization.
...
> I can think of one company who uses to IETF to have internal arguments.  But at the same time, I can think of another company who is very aligned in how they participate in the IETF.  Many others are somewhere in between.  There isn't a single model here.


Bob,

If one were doing a broad discussion about the role of the IETF within 
various organizations' operations, your point would be interesting.

For the current discussion, I suspect it's not all the relevant, since I 
understand this thread to be about the /potential/ for undue influence 
by an organization.  Anecdotes about the potential being exercised (or 
not) provide some seasoning to the discussion but do not affect the 
essence of the concern.

It doesn't matter whether that potential is exercised.  What matters is 
the exposure of the IETF to that potential and how the IETF can reduce it.

As with all security risks, the requirement is to anticipate them and 
protect against them, rather than wait to fix things afterwards...

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From lojakab@cisco.com  Tue Jul  9 11:45:15 2013
Return-Path: <lojakab@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 880CB21F9732; Tue,  9 Jul 2013 11:45:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tljGcqH6q9nS; Tue,  9 Jul 2013 11:45:10 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 821B721F9638; Tue,  9 Jul 2013 11:45:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1814; q=dns/txt; s=iport; t=1373395511; x=1374605111; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=df2P6mr99iblnNvx9koiqYA0q6ZFpG7b7LdGomNOOSY=; b=RBtNKp/AEgMt6r0suvhA//QGoPdHITYldijQZcLnwjazAPYoT4i5M+6A LKbuA1goSPBt+LzV+X5mDJiDtWXRd3Pio1DH5L3hi3gOhQYkih0ArohV6 MeZQCZ5AkYXu0rkLUaoDaUIsNPdctWbLP0iPBphw2AoyZL+Bx4c/73Gd0 Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApQLAJJZ3FGtJXHA/2dsb2JhbABagwkyTcEUAgGBGRZ0giMBAQEEODYKARALGAkWBAsJAwIBAgE0EQYNAQUCAQGICwy6JY8eTQcWg1wDiG0yjjSBKYR6iyWBWIE8giU
X-IronPort-AV: E=Sophos;i="4.87,1029,1363132800"; d="scan'208";a="229740678"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-9.cisco.com with ESMTP; 09 Jul 2013 18:45:10 +0000
Received: from xhc-rcd-x10.cisco.com (xhc-rcd-x10.cisco.com [173.37.183.84]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r69Ij9TM027272 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 9 Jul 2013 18:45:09 GMT
Received: from [10.21.126.39] (10.21.126.39) by xhc-rcd-x10.cisco.com (173.37.183.84) with Microsoft SMTP Server (TLS) id 14.2.318.4; Tue, 9 Jul 2013 13:45:08 -0500
Message-ID: <51DC5A2E.4040905@cisco.com>
Date: Tue, 9 Jul 2013 21:45:02 +0300
From: Lori Jakab <lojakab@cisco.com>
Organization: Cisco Systems, Inc.
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: Last Call: <draft-ietf-lisp-deployment-08.txt> (LISP Network Element Deployment Considerations) to Informational RFC
References: <20130701160310.22718.49133.idtracker@ietfa.amsl.com>
In-Reply-To: <20130701160310.22718.49133.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.21.126.39]
X-Mailman-Approved-At: Wed, 10 Jul 2013 10:30:58 -0700
Cc: The IESG <iesg-secretary@ietf.org>, lisp@ietf.org, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Jul 2013 18:45:15 -0000

It was pointed out to the document authors privately that a locally 
caching Map Server, as mentioned in the penultimate bullet of Section 
2.3, is not something that we should recommend anymore.

We, the authors agree, and want to note that the concept of a "locally 
caching Map Server" was introduced into the document at the time when 
DDT was still being in design phase, with many of its properties being 
inspired by DNS.  As a result, we removed the sentence that read "To 
lower the impact, the site could use a local caching Map Resolver." in 
revision -09 of the document, which we just posted to the datatracker.

On behalf of the authors,
-Lorand Jakab

On 7/1/13 7:03 PM, The IESG wrote:
>
> The IESG has received a request from the Locator/ID Separation Protocol
> WG (lisp) to consider the following document:
> - 'LISP Network Element Deployment Considerations'
>    <draft-ietf-lisp-deployment-08.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 2013-07-15. 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 discusses the different scenarios for the deployment of
>     the new network elements introduced by the Locator/Identifier
>     Separation Protocol (LISP).
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-lisp-deployment/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-lisp-deployment/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>

From paitken@cisco.com  Wed Jul 10 09:02:12 2013
Return-Path: <paitken@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A590C21F99D9; Wed, 10 Jul 2013 09:02:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jNkSK7KQIrFh; Wed, 10 Jul 2013 09:02:06 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 262B211E81B9; Wed, 10 Jul 2013 09:01:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=354; q=dns/txt; s=iport; t=1373472084; x=1374681684; h=message-id:date:from:mime-version:to:subject: content-transfer-encoding; bh=HFz6hSqNpP/atBzNCPmK2ZBqYUoW9VJCn6dmfwScIxw=; b=dGVjtT0BXVeBk7gtaXwN4hLunD06jl5bI2dDzj1dJmX4xUVbe2/eho36 vxumXARBf5LE5c6Kr8zwAuTj+6zVSGFfwOQB8r10m6nnd+kde8V7RYBUb qOYQJp7yCr41WpWc5k0L3VNW4Emz9dwUsg7n8DdC00S0gFe+EzrAjBduA 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AisFAPWE3VGQ/khL/2dsb2JhbABagwnDJBZ0gmJAPRYYAwIBAgFMDAgBAYgLuU+TXwOXV4YjiyeDEg
X-IronPort-AV: E=Sophos;i="4.87,1036,1363132800"; d="scan'208";a="156449759"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 10 Jul 2013 16:01:22 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r6AG1LtP006076 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 10 Jul 2013 16:01:21 GMT
Received: from [144.254.153.36] (dhcp-144-254-153-36.cisco.com [144.254.153.36]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id r6AG1Kih010704; Wed, 10 Jul 2013 17:01:20 +0100 (BST)
Message-ID: <51DD8551.6090502@cisco.com>
Date: Wed, 10 Jul 2013 17:01:21 +0100
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org, ietf-registrar@ietf.org
Subject: IETF registration fee?
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 10 Jul 2013 10:30:58 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Jul 2013 16:02:12 -0000

Can you help me understand why the One Day Pass rate ($350) is so high 
compared with the full week rate ($650 / $800)?

Registering for two days could cost more than a week!

Surely the day rate should be a little more than (week/5), eg about $175 
- $200, to encourage those who only want/need to contribute on 
particular days?

Thanks,
P.

From bmanning@isi.edu  Wed Jul 10 11:46:29 2013
Return-Path: <bmanning@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33D0B21F9D89; Wed, 10 Jul 2013 11:46:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MOpo9fVrHeWb; Wed, 10 Jul 2013 11:46:23 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 6D03F21F9994; Wed, 10 Jul 2013 11:46:23 -0700 (PDT)
Received: from [192.168.0.4] (cpe-24-24-228-167.socal.res.rr.com [24.24.228.167]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r6AIjkWa014215 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 10 Jul 2013 11:45:56 -0700 (PDT)
Subject: Re: IETF registration fee?
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=iso-8859-1
From: manning bill <bmanning@isi.edu>
In-Reply-To: <51DD8551.6090502@cisco.com>
Date: Wed, 10 Jul 2013 11:45:44 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <9413FAC5-737F-492E-96C0-22F6BDDA608D@isi.edu>
References: <51DD8551.6090502@cisco.com>
To: Paul Aitken <paitken@cisco.com>
X-Mailer: Apple Mail (2.1283)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: bmanning@isi.edu
Cc: ietf@ietf.org, ietf-registrar@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Jul 2013 18:46:29 -0000

you are not allowed to register for two days.

/bill

On 10July2013Wednesday, at 9:01, Paul Aitken wrote:

> Can you help me understand why the One Day Pass rate ($350) is so high =
compared with the full week rate ($650 / $800)?
>=20
> Registering for two days could cost more than a week!
>=20
> Surely the day rate should be a little more than (week/5), eg about =
$175 - $200, to encourage those who only want/need to contribute on =
particular days?
>=20
> Thanks,
> P.


From d3e3e3@gmail.com  Wed Jul 10 11:50:55 2013
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71A6421F9A5E for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2013 11:50:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.381
X-Spam-Level: 
X-Spam-Status: No, score=-102.381 tagged_above=-999 required=5 tests=[AWL=0.219, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pVRCaUx9V0W4 for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2013 11:50:55 -0700 (PDT)
Received: from mail-oa0-x233.google.com (mail-oa0-x233.google.com [IPv6:2607:f8b0:4003:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id C38DB21F9A4B for <ietf@ietf.org>; Wed, 10 Jul 2013 11:50:54 -0700 (PDT)
Received: by mail-oa0-f51.google.com with SMTP id i4so9923964oah.38 for <ietf@ietf.org>; Wed, 10 Jul 2013 11:50:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=OpIHspca0c1EGAFN5UUO2LetOBXCOlD0Zqdi3PahYS0=; b=HWC3G+52n1uEbS3K2o+itvVtx4c6LkEj195Qld3tI90cmcWhwKEzccF2ZuGx7AItsQ ZaMpLfEAmtTZuv0z5K5fbx333U/8XAtOlAxsbsv9w5JqkVQW1sIy+qjPgcDeeGTEP/ej a2t2lZ7Iu0HbH4tJd7dhyNj3g9+EF/6Ps55dOAfWHDW0NTdXI9T1oKuTUfiWbMjeX1lm lkHlPxScGBo0PO9gmGwl4c9npmuIKUIEoYjiAFYVN5jicOy3TOULHKHEbqp16kJNIkGT s8wY8zbcXzo9p1hI742tAE4OKq7j2S7M/Gn176c11s9mFkP3wHMz1mM/rISY8GTMhLxk 51/w==
X-Received: by 10.182.80.5 with SMTP id n5mr27847430obx.88.1373482253315; Wed, 10 Jul 2013 11:50:53 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.73.106 with HTTP; Wed, 10 Jul 2013 11:50:33 -0700 (PDT)
In-Reply-To: <51DD8551.6090502@cisco.com>
References: <51DD8551.6090502@cisco.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Wed, 10 Jul 2013 14:50:33 -0400
Message-ID: <CAF4+nEG7=oAfNvaUJexEA1B0YUx3ySV_575NjO8z_61kq92QOg@mail.gmail.com>
Subject: Re: IETF registration fee?
To: Paul Aitken <paitken@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Jul 2013 18:50:55 -0000

The IETF values cross area interaction at IETF meeting and attendees
have always been encouraged to attend for the week. Allowing one day
passes is a recent phenomenon to which some people, including myself,
are on balance opposed.

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


On Wed, Jul 10, 2013 at 12:01 PM, Paul Aitken <paitken@cisco.com> wrote:
> Can you help me understand why the One Day Pass rate ($350) is so high
> compared with the full week rate ($650 / $800)?
>
> Registering for two days could cost more than a week!
>
> Surely the day rate should be a little more than (week/5), eg about $175 -
> $200, to encourage those who only want/need to contribute on particular
> days?
>
> Thanks,
> P.

From moore@network-heretics.com  Wed Jul 10 12:41:38 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7EC5921F9D8D for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2013 12:41:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LMpyeN2Oqo+b for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2013 12:41:33 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id 5A43221F9D8B for <ietf@ietf.org>; Wed, 10 Jul 2013 12:41:33 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 556AD2096F for <ietf@ietf.org>; Wed, 10 Jul 2013 15:41:32 -0400 (EDT)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute1.internal (MEProxy); Wed, 10 Jul 2013 15:41:32 -0400
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=W4d8Jw5fkw2L5YIkh8471A BhK1A=; b=MGdIinUSoUibd1cpCE49DQaHu4VNPxv5QKMzFA070R7oZ8pkoGq0bE 6VfAORS0mm3a5gOFF4dwA8uoLNiS7cxhaQz2r2NLUvVvItXA3U5k0sVKkqw7y0Z8 DErCXWCM6vA9rU5StuLD7/RMRl2PaQWHRSojDFczGEMktYeZcKaIg=
X-Sasl-enc: IdBadwRJaBHhce5QBpeq0HMiNVZl46A4TTIs5LRzzz1f 1373485292
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id BD87B6801ED; Wed, 10 Jul 2013 15:41:31 -0400 (EDT)
Message-ID: <51DDB8E5.5050406@network-heretics.com>
Date: Wed, 10 Jul 2013 15:41:25 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF registration fee?
References: <51DD8551.6090502@cisco.com> <CAF4+nEG7=oAfNvaUJexEA1B0YUx3ySV_575NjO8z_61kq92QOg@mail.gmail.com>
In-Reply-To: <CAF4+nEG7=oAfNvaUJexEA1B0YUx3ySV_575NjO8z_61kq92QOg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Jul 2013 19:41:38 -0000

On 07/10/2013 02:50 PM, Donald Eastlake wrote:
> The IETF values cross area interaction at IETF meeting and attendees
> have always been encouraged to attend for the week. Allowing one day
> passes is a recent phenomenon to which some people, including myself,
> are on balance opposed.

I'm also of the opinion that the one-day passes were a bad idea. We have 
too little cross-group and cross-area participation, too many groups 
working at cross-purposes, and too little attention paid to the 
implications of any one new protocol on the Internet architecture.   We 
have become very overspecialized and we need to see what we can do to 
discourage this trend.

Keith


From stpeter@stpeter.im  Wed Jul 10 12:44:55 2013
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B8A021F9D8B for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2013 12:44:55 -0700 (PDT)
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=[AWL=0.063, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E5QUUurkPgoX for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2013 12:44:50 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 6AEB521F9F1C for <ietf@ietf.org>; Wed, 10 Jul 2013 12:44:50 -0700 (PDT)
Received: from ergon.local (unknown [128.107.239.235]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 86335413F5; Wed, 10 Jul 2013 13:45:55 -0600 (MDT)
Message-ID: <51DDB9AE.9000109@stpeter.im>
Date: Wed, 10 Jul 2013 13:44:46 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: IETF registration fee?
References: <51DD8551.6090502@cisco.com> <CAF4+nEG7=oAfNvaUJexEA1B0YUx3ySV_575NjO8z_61kq92QOg@mail.gmail.com> <51DDB8E5.5050406@network-heretics.com>
In-Reply-To: <51DDB8E5.5050406@network-heretics.com>
X-Enigmail-Version: 1.5.1
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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Jul 2013 19:44:56 -0000

On 7/10/13 1:41 PM, Keith Moore wrote:
> On 07/10/2013 02:50 PM, Donald Eastlake wrote:
>> The IETF values cross area interaction at IETF meeting and attendees
>> have always been encouraged to attend for the week. Allowing one day
>> passes is a recent phenomenon to which some people, including myself,
>> are on balance opposed.
> 
> I'm also of the opinion that the one-day passes were a bad idea. We have
> too little cross-group and cross-area participation, too many groups
> working at cross-purposes, and too little attention paid to the
> implications of any one new protocol on the Internet architecture.   We
> have become very overspecialized and we need to see what we can do to
> discourage this trend.

I can spend a week at an IETF meeting and never participate in a session
outside a given area. Day passes have nothing to do with it.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From jari.arkko@piuha.net  Wed Jul 10 13:25:04 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22FBC21F9D5A; Wed, 10 Jul 2013 13:25:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.589
X-Spam-Level: 
X-Spam-Status: No, score=-102.589 tagged_above=-999 required=5 tests=[AWL=0.010, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VbZ9H68gVp-8; Wed, 10 Jul 2013 13:24:59 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id AAE3021F9DAA; Wed, 10 Jul 2013 13:24:58 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 04B9F2CC48; Wed, 10 Jul 2013 23:24:41 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lplK58zgVFGC; Wed, 10 Jul 2013 23:24:40 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 6746C2CC3C; Wed, 10 Jul 2013 23:24:40 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [Gen-art] Gen-ART Telechat review of draft-ietf-appsawg-rfc5451bis-09
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <030301ce7b9d$6f821100$4e863300$@akayla.com>
Date: Wed, 10 Jul 2013 23:24:40 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <3D189071-3175-4D21-8B64-7F59FB259EF9@piuha.net>
References: <030301ce7b9d$6f821100$4e863300$@akayla.com>
To: Peter Yee <peter@akayla.com>
X-Mailer: Apple Mail (2.1508)
Cc: gen-art@ietf.org, draft-ietf-appsawg-rfc5451bis.all@tools.ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Jul 2013 20:25:04 -0000

Peter,

Thank you very much for your detailed review. And Murray, thanks for =
taking into account the comments. FWIW, I plan to ballot No-Objection =
for this draft based on the Gen-ART review (and my own far less detailed =
review).

Jari


From brian.e.carpenter@gmail.com  Wed Jul 10 13:46:14 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81A4621F9E50 for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2013 13:46:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.486
X-Spam-Level: 
X-Spam-Status: No, score=-102.486 tagged_above=-999 required=5 tests=[AWL=0.113, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yuvrHmky3INO for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2013 13:46:14 -0700 (PDT)
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 1134521F9E4C for <ietf@ietf.org>; Wed, 10 Jul 2013 13:46:14 -0700 (PDT)
Received: by mail-pd0-f179.google.com with SMTP id q10so6778260pdj.10 for <ietf@ietf.org>; Wed, 10 Jul 2013 13:46:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=AHPzEyMPVfBepeeMv+tVKe1awSjwGq2yVZSW+fJTv9Y=; b=mua/1eKR9qFsR2paiVVvu5bM8uepiVVWZAYQPvdzdY4BFyxtI8wmzwNvfeYJpuRkDc oUIngCr+C7q2AzCi4kotNwLH8IC6RB4CX4UeURPkbdIlVWm2IMMTJe+nuy7h67H6rByD R3RnpUOrdY7f3c7PrrprtorZkY3xZsKfCGk+7vvtW3NKqkKZBUapPEGJ6P3Ci4scqDoF MrY+yYAsS8R0O6UOqGVMw2gDGnBkOkeGRHhie8cNuignVJE9A9L31jl6Hr/qGuM7J0kL kuNb3V0Q9wpXQnwJdjRL+3l6vYnkM49QzO54atz6+SRZWF1J2dXMBRZcJTv0oeMgqjnj wXLw==
X-Received: by 10.66.122.99 with SMTP id lr3mr35188452pab.187.1373489173862; Wed, 10 Jul 2013 13:46:13 -0700 (PDT)
Received: from [192.168.178.23] (150.199.69.111.dynamic.snap.net.nz. [111.69.199.150]) by mx.google.com with ESMTPSA id we2sm38010378pab.0.2013.07.10.13.46.11 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 10 Jul 2013 13:46:13 -0700 (PDT)
Message-ID: <51DDC819.3070506@gmail.com>
Date: Thu, 11 Jul 2013 08:46:17 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: IETF registration fee?
References: <51DD8551.6090502@cisco.com>	<CAF4+nEG7=oAfNvaUJexEA1B0YUx3ySV_575NjO8z_61kq92QOg@mail.gmail.com>	<51DDB8E5.5050406@network-heretics.com> <51DDB9AE.9000109@stpeter.im>
In-Reply-To: <51DDB9AE.9000109@stpeter.im>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Keith Moore <moore@network-heretics.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Jul 2013 20:46:14 -0000

On 11/07/2013 07:44, Peter Saint-Andre wrote:
> On 7/10/13 1:41 PM, Keith Moore wrote:
>> On 07/10/2013 02:50 PM, Donald Eastlake wrote:
>>> The IETF values cross area interaction at IETF meeting and attendees
>>> have always been encouraged to attend for the week. Allowing one day
>>> passes is a recent phenomenon to which some people, including myself,
>>> are on balance opposed.
>> I'm also of the opinion that the one-day passes were a bad idea. We have
>> too little cross-group and cross-area participation, too many groups
>> working at cross-purposes, and too little attention paid to the
>> implications of any one new protocol on the Internet architecture.   We
>> have become very overspecialized and we need to see what we can do to
>> discourage this trend.
> 
> I can spend a week at an IETF meeting and never participate in a session
> outside a given area. 

That's true of course, but you will also have the chance to pick up
corridor gossip from other areas, and to be found by people in other
areas who are concerned about something your area is doing.

> Day passes have nothing to do with it.

I disagree. Day passes encourage the notion that it's normal to
parachute into the IETF to attend a single session. I think that the
IETF's strength is that we don't totally compartmentalise work items.

In that light, it's reasonable that two day passes should cost
more than the whole week. In any case, hotel costs quickly exceed
the meeting fee if you stay for a few days.

Not to mention that people who've paid for a day pass get mighty
upset when a session is moved to a different day at the last
moment.

   Brian

From john-ietf@jck.com  Wed Jul 10 13:51:52 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EC3021F8A85 for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2013 13:51:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.569
X-Spam-Level: 
X-Spam-Status: No, score=-102.569 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zft2khstCjBJ for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2013 13:51:45 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 4FFB721F9E9A for <ietf@ietf.org>; Wed, 10 Jul 2013 13:51:45 -0700 (PDT)
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 1Ux1MV-000P49-U4; Wed, 10 Jul 2013 16:51:43 -0400
Date: Wed, 10 Jul 2013 16:51:39 -0400
From: John C Klensin <john-ietf@jck.com>
To: Donald Eastlake <d3e3e3@gmail.com>, Paul Aitken <paitken@cisco.com>
Subject: Re: IETF registration fee?
Message-ID: <F3BB59B656548FCD695E9482@JcK-HP8200.jck.com>
In-Reply-To: <CAF4+nEG7=oAfNvaUJexEA1B0YUx3ySV_575NjO8z_61kq92QOg@mail.gmail.com>
References: <51DD8551.6090502@cisco.com> <CAF4+nEG7=oAfNvaUJexEA1B0YUx3ySV_575NjO8z_61kq92QOg@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@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Jul 2013 20:51:52 -0000

--On Wednesday, July 10, 2013 14:50 -0400 Donald Eastlake
<d3e3e3@gmail.com> wrote:

> The IETF values cross area interaction at IETF meeting and
> attendees have always been encouraged to attend for the week.
> Allowing one day passes is a recent phenomenon to which some
> people, including myself, are on balance opposed.

I would add that the registration fee covers a number of IETF
expenses that are fixed and independent of the number of
people-days at a meeting.  So, independent of Donald's concern,
even if one were to use a formula similar to the one you suggest
it would be more like
 
   (1/5 * day-cost-part-of-fee) + fixed-expense-part-of-free

or at least a much larger fraction of the latter.

   john




From pthaler@broadcom.com  Wed Jul 10 14:11:16 2013
Return-Path: <pthaler@broadcom.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30AE021F9A92 for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2013 14:11:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 58MZEngGN+iH for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2013 14:11:11 -0700 (PDT)
Received: from mms2.broadcom.com (mms2.broadcom.com [216.31.210.18]) by ietfa.amsl.com (Postfix) with ESMTP id 1C0B921F9644 for <ietf@ietf.org>; Wed, 10 Jul 2013 14:11:11 -0700 (PDT)
Received: from [10.9.208.53] by mms2.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.5)); Wed, 10 Jul 2013 14:05:06 -0700
X-Server-Uuid: 4500596E-606A-40F9-852D-14843D8201B2
Received: from SJEXCHCAS07.corp.ad.broadcom.com (10.16.203.16) by IRVEXCHCAS06.corp.ad.broadcom.com (10.9.208.53) with Microsoft SMTP Server (TLS) id 14.1.438.0; Wed, 10 Jul 2013 14:10:59 -0700
Received: from SJEXCHMB09.corp.ad.broadcom.com ( [fe80::3da7:665e:cc78:181f]) by SJEXCHCAS07.corp.ad.broadcom.com ( [::1]) with mapi id 14.01.0438.000; Wed, 10 Jul 2013 14:10:58 -0700
From: "Pat Thaler" <pthaler@broadcom.com>
To: "Keith Moore" <moore@network-heretics.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: IETF registration fee?
Thread-Topic: IETF registration fee?
Thread-Index: AQHOfZNv+o7r5Sx6JkOFqJkLirsl/5letuiAgAAONoD//532wA==
Date: Wed, 10 Jul 2013 21:10:57 +0000
Message-ID: <EB9B93801780FD4CA165E0FBCB3C3E672AE34B2B@SJEXCHMB09.corp.ad.broadcom.com>
References: <51DD8551.6090502@cisco.com> <CAF4+nEG7=oAfNvaUJexEA1B0YUx3ySV_575NjO8z_61kq92QOg@mail.gmail.com> <51DDB8E5.5050406@network-heretics.com>
In-Reply-To: <51DDB8E5.5050406@network-heretics.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.16.203.100]
MIME-Version: 1.0
X-WSS-ID: 7DC313081R042889884-13-01
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Jul 2013 21:11:16 -0000

As someone who during iSCSI development attended just to attend that group,=
 I didn't find IETF to be single day attendance friendly and I don't think =
that day passes change that substantially.=20

The main problem is that the final agenda isn't published until a little mo=
re than 3 weeks before the meeting so attending for a single day means wait=
ing to make travel reservations late enough that it may be difficult to get=
 a good airfare (and either booking the hotel for more days and reducing th=
e reservation when one knows what day one is interested in or getting a hot=
el after the IETF hotel blocks are full).

While generally IETF is helped by cross pollination and multi-day attendanc=
e is a good thing to encourage, there are times when the work of a particul=
ar group is helped by the attendance of some subject matter experts who are=
 only interested in the topic of that group and who would not be willing or=
 able to attend for the week. A day pass at around 1/2 the full week regist=
ration fee does something for the one day attendee while still encouraging =
full attendance.=20

That seems to be a reasonable compromise to me - though given the choice be=
tween having a stable agenda more than a month before the meeting and a day=
 pass, I think the former would be more helpful for single subject attendee=
s.

Regards,
Pat=20

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Kei=
th Moore
Sent: Wednesday, July 10, 2013 12:41 PM
To: ietf@ietf.org
Subject: Re: IETF registration fee?

On 07/10/2013 02:50 PM, Donald Eastlake wrote:
> The IETF values cross area interaction at IETF meeting and attendees
> have always been encouraged to attend for the week. Allowing one day
> passes is a recent phenomenon to which some people, including myself,
> are on balance opposed.

I'm also of the opinion that the one-day passes were a bad idea. We have=20
too little cross-group and cross-area participation, too many groups=20
working at cross-purposes, and too little attention paid to the=20
implications of any one new protocol on the Internet architecture.   We=20
have become very overspecialized and we need to see what we can do to=20
discourage this trend.

Keith




From Josh.Howlett@ja.net  Wed Jul 10 14:18:15 2013
Return-Path: <Josh.Howlett@ja.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A20A421F9D91 for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2013 14:18:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.099
X-Spam-Level: 
X-Spam-Status: No, score=-102.099 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, GB_AFFORDABLE=1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7kHCN7ChIokh for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2013 14:18:09 -0700 (PDT)
Received: from egw001.ukerna.ac.uk (egw001.ukerna.ac.uk [194.82.140.74]) by ietfa.amsl.com (Postfix) with ESMTP id 5BDB921F9D8F for <ietf@ietf.org>; Wed, 10 Jul 2013 14:18:08 -0700 (PDT)
Received: from egw001.ukerna.ac.uk (localhost.localdomain [127.0.0.1]) by localhost (Email Security Appliance) with SMTP id 4D0813138908_1DDCF8FB; Wed, 10 Jul 2013 21:18:07 +0000 (GMT)
Received: from EXC001.atlas.ukerna.ac.uk (exc001.atlas.ukerna.ac.uk [193.62.83.37]) by egw001.ukerna.ac.uk (Sophos Email Appliance) with ESMTP id 0FD1E31388D7_1DDCF8FF; Wed, 10 Jul 2013 21:18:07 +0000 (GMT)
Received: from EXC001.atlas.ukerna.ac.uk ([193.62.83.37]) by EXC001 ([193.62.83.37]) with mapi id 14.02.0247.003; Wed, 10 Jul 2013 22:18:00 +0100
From: Josh Howlett <Josh.Howlett@ja.net>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: IETF registration fee?
Thread-Topic: IETF registration fee?
Thread-Index: AQHOfZNqd4AVTHa8ZEaWlgNiPYwP2ZleMMyAgAAONoCAAADwAIAAETCAgAAZkQA=
Date: Wed, 10 Jul 2013 21:17:59 +0000
Message-ID: <CE0388EA.21B7F%Josh.Howlett@ja.net>
In-Reply-To: <51DDC819.3070506@gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.5.130515
x-originating-ip: [194.82.140.76]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <0C035B423AEF774D917D52B502BAF0C2@ukerna.ac.uk>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Keith Moore <moore@network-heretics.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Jul 2013 21:18:15 -0000

>> Day passes have nothing to do with it.
>
>I disagree. Day passes encourage the notion that it's normal to
>parachute into the IETF to attend a single session. I think that the
>IETF's strength is that we don't totally compartmentalise work items.

I am perplexed that there is, on the one hand, a (valid, IMHO) concern
about increasing IETF diversity & participation, when there appears to be
an active policy of discouraging potential participants who simply wish to
get work done in some specific sessions. Superficially, it would seem that
making participation more flexible and affordable might help to improve
diversity & participation.

Josh.



Janet(UK) is a trading name of Jisc Collections and Janet Limited, a=20
not-for-profit company which is registered in England under No. 2881024=20
and whose Registered Office is at Lumen House, Library Avenue,
Harwell Oxford, Didcot, Oxfordshire. OX11 0SG. VAT No. 614944238


From moore@network-heretics.com  Wed Jul 10 14:38:09 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5E3A21F9C20 for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2013 14:38:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.099
X-Spam-Level: 
X-Spam-Status: No, score=-3.099 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, GB_AFFORDABLE=1, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1F4wiblkZUsS for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2013 14:38:04 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id 9127B21F9C0C for <ietf@ietf.org>; Wed, 10 Jul 2013 14:38:04 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 23AEB20C47; Wed, 10 Jul 2013 17:38:00 -0400 (EDT)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute6.internal (MEProxy); Wed, 10 Jul 2013 17:38:01 -0400
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 :content-transfer-encoding; s=smtpout; bh=ETxPlJy6VlG5PEQvN7ykAx TY2dg=; b=VcjCqgbwTP7WS1/L3ia27uoPdpLqj/eG22jh4dvsCl8bflW9g/Ep+v uWQ4sywDMbM4KanIzJh+RxWLHu1c8GbW3+t0JudxWZPr1uEK0iNlSDKUYUMwFruJ ZRcF0Q3Et7Ta8fPqLO/pYqEZzKIAP9AvNVFl2hyG/FCzKkjpmXNrA=
X-Sasl-enc: RdWaWvSBqVAnVhQqnwL9qTWom9PvXZ69a4yrhJ+BbG/F 1373492280
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id DAE386804D4; Wed, 10 Jul 2013 17:37:59 -0400 (EDT)
Message-ID: <51DDD430.3090004@network-heretics.com>
Date: Wed, 10 Jul 2013 17:37:52 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: Josh Howlett <Josh.Howlett@ja.net>
Subject: Re: IETF registration fee?
References: <CE0388EA.21B7F%Josh.Howlett@ja.net>
In-Reply-To: <CE0388EA.21B7F%Josh.Howlett@ja.net>
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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Jul 2013 21:38:09 -0000

On 07/10/2013 05:17 PM, Josh Howlett wrote:
>>> Day passes have nothing to do with it.
>> I disagree. Day passes encourage the notion that it's normal to
>> parachute into the IETF to attend a single session. I think that the
>> IETF's strength is that we don't totally compartmentalise work items.
> I am perplexed that there is, on the one hand, a (valid, IMHO) concern
> about increasing IETF diversity & participation, when there appears to be
> an active policy of discouraging potential participants who simply wish to
> get work done in some specific sessions. Superficially, it would seem that
> making participation more flexible and affordable might help to improve
> diversity & participation.

There's more than one kind of diversity.

IETF (and its work) would greatly benefit from participants who work in 
more diverse areas, including areas within IETF and/or outside of IETF.

IETF has a long history of giving too much favor to narrow and/or 
short-term interests.   The long-term viability of the Internet 
continues to suffer because of this bias.

Keith


From dhc@dcrocker.net  Wed Jul 10 14:40:14 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E326721F9CA1 for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2013 14:40:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.593
X-Spam-Level: 
X-Spam-Status: No, score=-6.593 tagged_above=-999 required=5 tests=[AWL=0.006,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ekj10ZQ0GnHz for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2013 14:40:10 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 863F921F9C8C for <ietf@ietf.org>; Wed, 10 Jul 2013 14:40:10 -0700 (PDT)
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 r6ALe7WV005569 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 10 Jul 2013 14:40:10 -0700
Message-ID: <51DDD49E.5090406@dcrocker.net>
Date: Wed, 10 Jul 2013 14:39:42 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IAB Statement on Dotless Domains
References: <1984CBB8-6862-4DBB-AFAE-F8461E694083@vigilsec.com>
In-Reply-To: <1984CBB8-6862-4DBB-AFAE-F8461E694083@vigilsec.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, 10 Jul 2013 14:40:10 -0700 (PDT)
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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, 10 Jul 2013 21:40:15 -0000

On 7/10/2013 11:59 AM, Russ Housley wrote:
> The IAB has made a statement on dotless domains.  You can find this statement here:
> http://www.iab.org/documents/correspondence-reports-documents/2013-2/iab-statement-dotless-domains-considered-harmful/


It's unfortunate that the IAB did not choose to circulate a draft before 
releasing the Statement.  The Statement could have been made a bit 
stronger in the concern it expresses.

There's been a separate discussion on the SMTP mailing list about the 
ICANN SSAC report on the topic of dotless domains.

The report correctly notes that there are also email barriers to the use 
of dotless domains.

The report incorrectly attributes these to the email standards, which do 
not prohibit the use.  (To be fair the format standard RFC 2822, which 
was in force for a number of years, did have the prohibition, but 
neither its predecessor nor its successor -- the current standard 
RFC5322 -- carry the limitation.)

Rather, the SMTP mailing list confirmed common software implementation 
barriers, sometimes due to the DNS-related stricture.

More interesting were other concerns about possible attacks and 
configuration errors.  The example of localhost was cited.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From sob@harvard.edu  Wed Jul 10 16:03:51 2013
Return-Path: <sob@harvard.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B316421F9CAE for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2013 16:03:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rF1USngmjRkk for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2013 16:03:46 -0700 (PDT)
Received: from ackroyd.harvard.edu (ackroyd.harvard.edu [128.103.208.29]) by ietfa.amsl.com (Postfix) with ESMTP id CE39021F9CAD for <ietf@ietf.org>; Wed, 10 Jul 2013 16:03:46 -0700 (PDT)
Received: from exchange.university.harvard.edu (entwedge0000001.university.harvard.edu [10.35.2.152]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ackroyd.harvard.edu (Postfix) with ESMTP id A423DEA153 for <ietf@ietf.org>; Wed, 10 Jul 2013 19:03:45 -0400 (EDT)
Received: from ENTWHUBT0000000.university.harvard.edu (10.32.8.201) by ENTWEDGE0000001.university.harvard.edu (10.35.2.152) with Microsoft SMTP Server (TLS) id 14.2.342.3; Wed, 10 Jul 2013 19:03:30 -0400
Received: from ENTWEXMB0000008.university.harvard.edu ([169.254.1.137]) by ENTWHUBT0000000.university.harvard.edu ([10.32.8.201]) with mapi id 14.02.0342.003; Wed, 10 Jul 2013 19:03:45 -0400
From: "Bradner, Scott" <sob@harvard.edu>
To: "<ietf@ietf.org>" <ietf@ietf.org>
Subject: Re: Last Call: RFC 2050 to historic
Thread-Topic: Last Call: RFC 2050 to historic
Thread-Index: AQHOfcG6HbWKPpNInk29dddkWOADiw==
Date: Wed, 10 Jul 2013 23:03:44 +0000
Message-ID: <0BFC28DF-EAE5-4EEC-B178-D562A4A5C577@harvard.edu>
References: <20130710213959.9266.65720.idtracker@ietfa.amsl.com>
In-Reply-To: <20130710213959.9266.65720.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [136.248.127.162]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <C9B0316542D47D48A9712F04E54D3D9E@Exchange.university.harvard.edu>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Jul 2013 23:03:51 -0000

is there a reason to not disclose who the individual participant is?

Scott

On Jul 10, 2013, at 5:39 PM, The IESG <iesg-secretary@ietf.org> wrote:

>=20
> The IESG has received a request from an individual participant to make
> the following status changes:
>=20
> - RFC2050 from Best Current Practice to Historic
>=20
> The supporting document for this request can be found here:
>=20
> http://datatracker.ietf.org/doc/status-change-2050-to-historic/
>=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 2013-08-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.
>=20
> The affected document can be obtained via
> http://datatracker.ietf.org/doc/rfc2050/
>=20
> IESG discussion of this request can be tracked via
> http://datatracker.ietf.org/doc/status-change-2050-to-historic/ballot/
>=20
>=20


From hsantos@isdg.net  Wed Jul 10 16:09:47 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88F6511E8153 for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2013 16:09:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.275
X-Spam-Level: 
X-Spam-Status: No, score=-102.275 tagged_above=-999 required=5 tests=[AWL=-0.676, BAYES_00=-2.599, GB_AFFORDABLE=1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lzW3apM1lyqo for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2013 16:09:42 -0700 (PDT)
Received: from groups.winserver.com (secure.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 48AE411E814B for <ietf@ietf.org>; Wed, 10 Jul 2013 16:09:41 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1357; t=1373497773; h=Received:Received: Message-ID:Date:From:To:Subject:Organization:List-ID; bh=ACdZ0p5 qmOuemG8aPxYmrh1t/5A=; b=M6d1Z6gSMJhtup6i6A0fT+pQnknq6e6lRz/hgKT g6vsi4ny5iVWNnFHljLeLm9Q9zjZUyvc8hCIiPNvtDiGXXqX8Jeb6T5iR731VkGI lsG/6UQAWoBwu8AeJjZK0OpM3vm24skZSF7zK0kLN8MVBDa9THQFdaJHM0zIC20w ZfRs=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Wed, 10 Jul 2013 19:09:33 -0400
Received: from [208.247.131.8] ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 4255298318.8699.4688; Wed, 10 Jul 2013 19:09:33 -0400
Message-ID: <51DDE8FA.6030607@isdg.net>
Date: Wed, 10 Jul 2013 19:06:34 -0400
From: Hector Santos <hsantos@isdg.net>
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Josh Howlett <Josh.Howlett@ja.net>
Subject: Re: IETF registration fee?
References: <CE0388EA.21B7F%Josh.Howlett@ja.net>
In-Reply-To: <CE0388EA.21B7F%Josh.Howlett@ja.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>, Keith Moore <moore@network-heretics.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Jul 2013 23:09:47 -0000

On 7/10/2013 5:17 PM, Josh Howlett wrote:
>
>>> Day passes have nothing to do with it.
>>
>> I disagree. Day passes encourage the notion that it's normal to
>> parachute into the IETF to attend a single session. I think that the
>> IETF's strength is that we don't totally compartmentalise work items.
>
> I am perplexed that there is, on the one hand, a (valid, IMHO) concern
> about increasing IETF diversity & participation, when there appears to be
> an active policy of discouraging potential participants who simply wish to
> get work done in some specific sessions. Superficially, it would seem that
> making participation more flexible and affordable might help to improve
> diversity & participation.
>
> Josh.


+1 Thank you. Well said. I had very little limited time but I wanted to 
blast by Orlando from Miami (by car) and attend just one day, just to 
meet the folks I often have electronic battles with over the years.  But 
the daily cost was a little too much and I certainly didn't want (nor 
ready) to stay an entire week to make it cost effective.  Perhaps it is 
a minor issue to attract local area interest, since that would be the 
only advantage for a daily attendance cost.

It seems to be too much contradictory discussion about diversity. I 
don't have too much confidence anything will be improved.

--
HLS


From doug.mtview@gmail.com  Wed Jul 10 16:32:20 2013
Return-Path: <doug.mtview@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B41221F9C64 for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2013 16:32:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[AWL=-0.501,  BAYES_00=-2.599, GB_AFFORDABLE=1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qcXH2MJ4rTEb for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2013 16:32:16 -0700 (PDT)
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 0162D21F9C20 for <ietf@ietf.org>; Wed, 10 Jul 2013 16:32:15 -0700 (PDT)
Received: by mail-pd0-f178.google.com with SMTP id w11so6786153pde.23 for <ietf@ietf.org>; Wed, 10 Jul 2013 16:32:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=DvCCaHVXfzxT3koI6T5/mIAuYVzzdF3iZb+/Hl+LeGo=; b=Pzm4DGB9AjVArK4MqjUzr6u5yO0WAhNnwLKm3Y0bZIwPbDiZyQZ9Sxn7zFyu94lU9v IyzMcUzSqyScXG3xPyQA8dbaeB3iiksGnyzkr7BDfxhOzx+BY4ZEHxYIcO5c26H0lKPJ jhDpEQlvd1lJu0McGaFESbPBQs1ez+oc64AOhzVRiYfuLlv38du7LVE3K8TW9AEwmk24 1GpIKgIiRU2MGjRc48pXTTOgw6sMrQ2hpeDFLA5t43glhzwpGs3YCmCqK6xlrvOVP9i+ Od5QA26DvHmR8vFfG6ccrNIkZFVYdaWyk3cb8jIEfVye35zzhM72YT8UJdP2nra9/ihL TsFw==
X-Received: by 10.68.253.227 with SMTP id ad3mr34362863pbd.63.1373499135541; Wed, 10 Jul 2013 16:32:15 -0700 (PDT)
Received: from [192.168.2.240] (c-98-207-206-162.hsd1.ca.comcast.net. [98.207.206.162]) by mx.google.com with ESMTPSA id vb8sm36204552pbc.11.2013.07.10.16.32.13 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 10 Jul 2013 16:32:14 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: IETF registration fee?
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <CE0388EA.21B7F%Josh.Howlett@ja.net>
Date: Wed, 10 Jul 2013 16:32:12 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <803FCD9A-6B8A-45EC-914F-E2114C581EA1@gmail.com>
References: <CE0388EA.21B7F%Josh.Howlett@ja.net>
To: Josh Howlett <Josh.Howlett@ja.net>
X-Mailer: Apple Mail (2.1508)
Cc: "ietf@ietf.org" <ietf@ietf.org>, Keith Moore <moore@network-heretics.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Jul 2013 23:32:20 -0000

On Jul 10, 2013, at 2:17 PM, Josh Howlett <Josh.Howlett@ja.net> wrote:
>>> Day passes have nothing to do with it.
>>=20
>> I disagree. Day passes encourage the notion that it's normal to
>> parachute into the IETF to attend a single session. I think that the
>> IETF's strength is that we don't totally compartmentalise work items.
>=20
> I am perplexed that there is, on the one hand, a (valid, IMHO) concern
> about increasing IETF diversity & participation, when there appears to =
be
> an active policy of discouraging potential participants who simply =
wish to
> get work done in some specific sessions. Superficially, it would seem =
that
> making participation more flexible and affordable might help to =
improve
> diversity & participation.
>=20
> Josh.


Dear Josh,

I agree. A single day fee should also be considered in conjunction with =
the increased status of remote participation underwritten by a much =
smaller remote meeting fee.  It seems there is a general reluctance to =
consider schemes aimed at capturing face-to-face meetings in a realtime =
fashion permitting moderated realtime interaction with selected network =
entities. Experiments with things like WebEx and others involve a fair =
amount of network resources or they offer poor results.  An audio/video =
bridge suitable for many simultaneous participants is difficult to solve =
in a generic manner.  The real question is simultaneous participation in =
conjunction with telephone bridges really necessary?

Setting up a dedicated low cost device to manage video projectors, =
microphones, and PA systems for a single moderated inbound access should =
supplant much of the complexity.  By not permitting multiple video/audio =
sources and requiring presentation being available in the cloud prior to =
the meetings, issues of distribution and audio quality are removed.  =
Such an approach will necessitate greater meeting discipline to ensure =
only those at an active microphone are recognized, and that presenters =
both local and remote are permitted control of their presentation.=20

Developing this approach would offer a number of benefits extending well =
beyond that of the IETF since this is a common problem.  Much of the =
ongoing work related to HTML5 facilitate standardizing the needed APIs.  =
There are many fairly powerful systems using dual core Atom processors =
available well below $300.  These systems should be able to handle audio =
using USB adapters and source video presentations accessed from the =
cloud.  A fallback operation should be able to carry meetings forward =
completely from the cloud "as if" moderators and participants were =
present locally.  In other words, treat loss of the Internet at the =
venue as being equivalent to being denied access to the physical venue =
and include this requirement in venue arrangements.

Those traveling thousands of miles already confront many uncertainties.  =
Those that elect to participate remotely should be afforded greater =
certainty of being able to participate when problems occur at local =
venues or with transportation.  Increasing participation without the =
expense of the brick and mortar and travel should offer long term =
benefits and increased fairness.=20

Regards,
Douglas Otis







From ole@cisco.com  Wed Jul 10 16:33:38 2013
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47D2021F9D58 for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2013 16:33:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.572
X-Spam-Level: 
X-Spam-Status: No, score=-110.572 tagged_above=-999 required=5 tests=[AWL=0.027, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rf18xnDIe2wy for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2013 16:33:33 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id DB25121F9C50 for <ietf@ietf.org>; Wed, 10 Jul 2013 16:33:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=898; q=dns/txt; s=iport; t=1373499213; x=1374708813; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=TMs0szO/SXCZ3dMixuKOLqPvUuJwGDtU5nv8qffawhM=; b=BQ/hdLe01KYoGz/f1exxFWykKNGd2pPebMj9cXhhTcEI9J+6m+rja+ob /1njMiPIj0LTNM9ISICauHyiweOcWU8g1l/LfsINaCsrHj51fWn6U0bWa uQk2vqg7sO7ttAXlzCJk6UuD2fTBdiqKXfEjrBXOv9W2S8g5d+Iu1u9CB k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnMFAAPv3VGrRDoJ/2dsb2JhbABXA4MJMoMPvmWBDhZ0giQBAQQ6PxALDjhXBhOIDrdqjjGBIhAHEYNkA4knilyJeoYEhSODMRyBNQ
X-IronPort-AV: E=Sophos;i="4.87,1039,1363132800"; d="scan'208";a="83148788"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-3.cisco.com with ESMTP; 10 Jul 2013 23:33:32 +0000
Received: from [10.27.1.132] (sjc-ole-8913.cisco.com [10.27.1.132]) by mtv-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r6ANXU2g012581 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 10 Jul 2013 23:33:31 GMT
Date: Wed, 10 Jul 2013 16:33:26 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Hector Santos <hsantos@isdg.net>
Subject: Re: IETF registration fee?
In-Reply-To: <51DDE8FA.6030607@isdg.net>
Message-ID: <alpine.OSX.2.01.1307101623390.84716@173-11-110-132-sfba.hfc.comcastbusiness.net>
References: <CE0388EA.21B7F%Josh.Howlett@ja.net> <51DDE8FA.6030607@isdg.net>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: "ietf@ietf.org" <ietf@ietf.org>, Keith Moore <moore@network-heretics.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@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: Wed, 10 Jul 2013 23:33:38 -0000

When we introduced the day passes, part of the discussion revolved 
around the observation that some number of people (I don't think
this has ever been "measured") attend for a day or less than a day
in order to participate in a specific working group session or even
just meet with other people. This has certainly been the case for
as long as I have been attending, Berlin will be my 80th (!) IETF
meeting.
 
Prior to the day pass program (and since we generally don't check 
badges), there was no "honest" way to attend for just a single day. 
Having Day Passes at least let's people attend for a day without 
feeling guilty (whether they consume cookies or not).

Ole


Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo



From andy@yumaworks.com  Wed Jul 10 16:39:37 2013
Return-Path: <andy@yumaworks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58C1F11E80D1 for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2013 16:39:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.224
X-Spam-Level: 
X-Spam-Status: No, score=-2.224 tagged_above=-999 required=5 tests=[AWL=-0.247, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, GB_AFFORDABLE=1, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fmjIw1dh4ttM for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2013 16:39:32 -0700 (PDT)
Received: from mail-pb0-f42.google.com (mail-pb0-f42.google.com [209.85.160.42]) by ietfa.amsl.com (Postfix) with ESMTP id 55A3711E80A5 for <ietf@ietf.org>; Wed, 10 Jul 2013 16:39:32 -0700 (PDT)
Received: by mail-pb0-f42.google.com with SMTP id un1so7266251pbc.1 for <ietf@ietf.org>; Wed, 10 Jul 2013 16:39:32 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=jh0qH8rkJLNTFCpu8F44kcoWNqKlon55+5JBOx4JVeQ=; b=k3zV9YXnA3nI07O1MLP8JoJF+14K4VjoBMaJRe7tKeCVnnvaUpMYsuSzEOBxm0uOfz QwTGxSf+kgbW0CHMec5ikSyxDPKQZ/Ngx5wGCjPCNOzsIVGLxS8IfQI2mEGpQ99NNDUH aVjXQJnK15S8MYlgP8rDGuWxDcXyguwJFl4Yi+yzuRx1ZJHFJp8rvnznq2WuqprAyjvb ClO+HuDyUzPpJ7txOaAhdg8qermw52T4MIR9QV+deRU08gsdfsrWqjc7K208AqINGcim yfl/DkOyeQ+9lR0XXgp7qAPtFgZKC8skZ7gykENRgwVwrGZwDdPaQ4sfnFT8tSJGq8cf EXLQ==
MIME-Version: 1.0
X-Received: by 10.66.252.194 with SMTP id zu2mr35626811pac.71.1373499571987; Wed, 10 Jul 2013 16:39:31 -0700 (PDT)
Received: by 10.70.12.161 with HTTP; Wed, 10 Jul 2013 16:39:31 -0700 (PDT)
In-Reply-To: <51DDE8FA.6030607@isdg.net>
References: <CE0388EA.21B7F%Josh.Howlett@ja.net> <51DDE8FA.6030607@isdg.net>
Date: Wed, 10 Jul 2013 16:39:31 -0700
Message-ID: <CABCOCHRbiYbyFOn+fm+JOxr6PPpcnAZGmXGV9DsjT=Z-9bi2yA@mail.gmail.com>
Subject: Re: IETF registration fee?
From: Andy Bierman <andy@yumaworks.com>
To: Hector Santos <hsantos@isdg.net>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQlymWYJJeaV9q1CrOgfgxW2GMrgjyc26uUN4E/no7t0sXDNUyHRIwWgRYkCj3tuWdHe1q6d
Cc: "ietf@ietf.org" <ietf@ietf.org>, Keith Moore <moore@network-heretics.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Jul 2013 23:39:37 -0000

On Wed, Jul 10, 2013 at 4:06 PM, Hector Santos <hsantos@isdg.net> wrote:
> On 7/10/2013 5:17 PM, Josh Howlett wrote:
>>
>>
>>>> Day passes have nothing to do with it.
>>>
>>>
>>> I disagree. Day passes encourage the notion that it's normal to
>>> parachute into the IETF to attend a single session. I think that the
>>> IETF's strength is that we don't totally compartmentalise work items.
>>
>>
>> I am perplexed that there is, on the one hand, a (valid, IMHO) concern
>> about increasing IETF diversity & participation, when there appears to be
>> an active policy of discouraging potential participants who simply wish to
>> get work done in some specific sessions. Superficially, it would seem that
>> making participation more flexible and affordable might help to improve
>> diversity & participation.
>>
>> Josh.
>
>
>
> +1 Thank you. Well said. I had very little limited time but I wanted to
> blast by Orlando from Miami (by car) and attend just one day, just to meet
> the folks I often have electronic battles with over the years.  But the
> daily cost was a little too much and I certainly didn't want (nor ready) to
> stay an entire week to make it cost effective.  Perhaps it is a minor issue
> to attract local area interest, since that would be the only advantage for a
> daily attendance cost.
>
> It seems to be too much contradictory discussion about diversity. I don't
> have too much confidence anything will be improved.
>

+1
Just because I want to attend all week doesn't mean everybody
else should also want to do the same, or can afford the time and expense.

Back when I was RMONMIB WG Chair, it was difficult to get developers
to attend the IETF.  They were too busy implementing the RFCs to
spend an entire week at the IETF.  They really didn't want to expand
their horizons and attend extra meetings for WGs they didn't follow.
I think a 1-day pass would have helped a little, since one still has to make
travel plans in advance of the final agenda.

It seems to me that a cheap 1 day pass and ultra-cheap 1 day student pass
would encourage local people to attend their first IETF.


> --
> HLS
>

Andy

From jari.arkko@piuha.net  Wed Jul 10 16:42:48 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32ADF11E8135 for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2013 16:42:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.296
X-Spam-Level: 
X-Spam-Status: No, score=-99.296 tagged_above=-999 required=5 tests=[AWL=-3.285, BAYES_00=-2.599, FB_WORD1_END_DOLLAR=3.294, FB_WORD2_END_DOLLAR=3.294, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1r+xHokJl0iK for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2013 16:42:43 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 9BDE411E80A5 for <ietf@ietf.org>; Wed, 10 Jul 2013 16:42:42 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 4D7B92CC61 for <ietf@ietf.org>; Thu, 11 Jul 2013 02:42:41 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uacBZ6WE1RRr for <ietf@ietf.org>; Thu, 11 Jul 2013 02:42:40 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 92C192CC48 for <ietf@ietf.org>; Thu, 11 Jul 2013 02:42:40 +0300 (EEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: IETF registration fee?
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <51DDE8FA.6030607@isdg.net>
Date: Thu, 11 Jul 2013 02:42:40 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <9C7F0B90-4029-43C7-8FB2-2230F936D6E1@piuha.net>
References: <CE0388EA.21B7F%Josh.Howlett@ja.net> <51DDE8FA.6030607@isdg.net>
To: "ietf@ietf.org list" <ietf@ietf.org>
X-Mailer: Apple Mail (2.1508)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Jul 2013 23:42:48 -0000

First, I wanted to agree with what Pat said:

> While generally IETF is helped by cross pollination and multi-day =
attendance is a good thing to encourage, there are times when the work =
of a particular group is helped by the attendance of some subject matter =
experts who are only interested in the topic of that group and who would =
not be willing or able to attend for the week. A day pass at around 1/2 =
the full week registration fee does something for the one day attendee =
while still encouraging full attendance.=20
>=20
> That seems to be a reasonable compromise to me - though given the =
choice between having a stable agenda more than a month before the =
meeting and a day pass, I think the former would be more helpful for =
single subject attendees.

Secondly, the day pass rates are a combination of a number of partially =
conflicting factors, including:

- the desire to help cross-pollination
- the desire to attract more participants (and more diverse =
participation)
- the desire to make attending easy for everyone
- costs: the combination of fixed costs (e.g., RFC Editor), fixed =
meeting costs (e.g., site selection), and variable meeting costs (e.g., =
size of rooms)
- pricing: what attendees find as a reasonable fee and how it compares =
to their other costs, such as travel; avoiding competing with the full =
week option
- setting up meetings only as a place to do work vs. as a part of =
funding a bigger system (e.g., editor staff, tools development)
- =85

Are we at the right spot? Maybe, maybe not. I personally think the =
current settings are at least in the ballpark. 1/5 price for a day =
ticket would certainly be a bad choice, IMO. Something between 2/5 to =
3/5 is probably the right area, and I think we are there. And don't =
forget that we also have Fellows/Guest programs...

I also tend to agree with Pat that the practical matters are more =
relevant than whether the day pass costs 100$ more or less. I'd rather =
work on those matters than the price.

Jari


From jari.arkko@piuha.net  Wed Jul 10 16:45:15 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00BA511E813D for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2013 16:45:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.548
X-Spam-Level: 
X-Spam-Status: No, score=-102.548 tagged_above=-999 required=5 tests=[AWL=0.051, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fWAPFnOQ6802 for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2013 16:45:07 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 00F7A11E80A5 for <ietf@ietf.org>; Wed, 10 Jul 2013 16:45:07 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id DB0862CC61; Thu, 11 Jul 2013 02:45:04 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d96srJl6pRt1; Thu, 11 Jul 2013 02:45:04 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id E8A792CC48; Thu, 11 Jul 2013 02:45:03 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Last Call: RFC 2050 to historic
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <0BFC28DF-EAE5-4EEC-B178-D562A4A5C577@harvard.edu>
Date: Thu, 11 Jul 2013 02:45:03 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <83562D0A-4059-4B34-900A-C0745BA4F69E@piuha.net>
References: <20130710213959.9266.65720.idtracker@ietfa.amsl.com> <0BFC28DF-EAE5-4EEC-B178-D562A4A5C577@harvard.edu>
To: "Bradner, Scott" <sob@harvard.edu>
X-Mailer: Apple Mail (2.1508)
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Jul 2013 23:45:17 -0000

Scott,

> is there a reason to not disclose who the individual participant is?

No, but actually that text just came from the standard boilerplate for =
the last call text in these cases. In reality has been several people =
asking for this to be done, e.g., SM wrote a document about 2050 and a =
few other RFCs, several IESG members felt that this needs to be done =
after the 2050bis was approved, etc.

Jari


From denghui02@gmail.com  Wed Jul 10 17:04:38 2013
Return-Path: <denghui02@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3A1F11E80E4 for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2013 17:04:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.157
X-Spam-Level: 
X-Spam-Status: No, score=-102.157 tagged_above=-999 required=5 tests=[AWL=-0.442, BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aflKgUMwJoTc for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2013 17:04:38 -0700 (PDT)
Received: from mail-qc0-x22b.google.com (mail-qc0-x22b.google.com [IPv6:2607:f8b0:400d:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 62EF311E80AD for <ietf@ietf.org>; Wed, 10 Jul 2013 17:04:38 -0700 (PDT)
Received: by mail-qc0-f171.google.com with SMTP id n1so3995794qcw.16 for <ietf@ietf.org>; Wed, 10 Jul 2013 17:04:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=e9gxJVV86vsULloBX6EEaeRl72Ft4gECC9yj3cIJgOI=; b=q4E4VzBUuAMMx8a8fowzD0YzK0wkieCaZVw0iIJ78da9zewoEbdRHpBQ45f4BT7C11 8GzqYZKn2jxrlEYCYK0nw7M/hqlAeKknLhOqUgxwZq7nOMzHva3ZZK7HfwBRwDYiJzx9 bt5+AyoaIrLgNkA7i6j1KGj9mKm0rHHs0AzWbF1u11cFHrLDyTHcReuVl9+bQ5ADFbhU g5dxm8BJuFj2af5nV9APXwzvK8UvSLJytw2VhB/WReec+RurGQbSWvDbeOcVFF3uyrB0 03B2a8qOwpuDrA0SVZ2TZQZ81s8Kk4tGHva3bebmmHiLncToA8Vv3Uwky4GGhuZqg/91 xFow==
MIME-Version: 1.0
X-Received: by 10.224.166.135 with SMTP id m7mr23114931qay.55.1373501076784; Wed, 10 Jul 2013 17:04:36 -0700 (PDT)
Received: by 10.49.16.42 with HTTP; Wed, 10 Jul 2013 17:04:36 -0700 (PDT)
Date: Thu, 11 Jul 2013 08:04:36 +0800
Message-ID: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com>
Subject: Regarding call Chinese names
From: Hui Deng <denghui02@gmail.com>
To: IETF Discussion <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=001a11c22b14c7ccef04e131230a
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 00:04:38 -0000

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

Hello all

We submitted two drafts to help people here to correctly call chinese
people names:

http://tools.ietf.org/html/draft-deng-call-chinese-names-00

   http://tools.ietf.org/html/draft-zcao-chinese-pronounce-00



Feel free to let us know if you have any other issues?

Best regards,



-Hui Deng

--001a11c22b14c7ccef04e131230a
Content-Type: text/html; charset=GB2312
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hello all</div><div>&nbsp;</div><div>We submitted two=
 drafts to help people here to correctly call chinese people names:</div><d=
iv><font color=3D"#000000" size=3D"3" face=3D"=CB=CE=CC=E5">

</font><p style=3D"margin:0cm 0cm 0pt"><span lang=3D"EN-US"><a href=3D"http=
://tools.ietf.org/html/draft-deng-call-chinese-names-00" target=3D"_blank">=
<span style=3D"background:white;color:rgb(17,85,204);font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;;font-size:10pt">http://tools.ietf.org/html/d=
raft-deng-call-chinese-names-00</span></a></span><span style=3D"background:=
white;color:rgb(34,34,34);font-family:&quot;Arial&quot;,&quot;sans-serif&qu=
ot;;font-size:10pt" lang=3D"EN-US">&nbsp;</span></p>
<font color=3D"#000000" size=3D"3" face=3D"=CB=CE=CC=E5">

</font><p style=3D"margin:0cm 0cm 0pt"><span style=3D"background:white;colo=
r:rgb(34,34,34);font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;font-s=
ize:10pt" lang=3D"EN-US">&nbsp; &nbsp;</span><span lang=3D"EN-US"><a href=
=3D"http://tools.ietf.org/html/draft-zcao-chinese-pronounce-00" target=3D"_=
blank"><span style=3D"background:white;color:rgb(17,85,204);font-family:&qu=
ot;Arial&quot;,&quot;sans-serif&quot;;font-size:10pt">http://tools.ietf.org=
/html/draft-zcao-chinese-pronounce-00</span></a></span></p>
<p style=3D"margin:0cm 0cm 0pt"><span lang=3D"EN-US"></span>&nbsp;</p><p st=
yle=3D"margin:0cm 0cm 0pt"><span lang=3D"EN-US">Feel free to let us know if=
 you have any other issues?</span></p><p style=3D"margin:0cm 0cm 0pt"><span=
 lang=3D"EN-US">Best regards,</span></p>
<p style=3D"margin:0cm 0cm 0pt"><span lang=3D"EN-US"></span>&nbsp;</p><p st=
yle=3D"margin:0cm 0cm 0pt"><span lang=3D"EN-US">-Hui Deng</span></p><font c=
olor=3D"#000000" size=3D"3" face=3D"=CB=CE=CC=E5">

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

--001a11c22b14c7ccef04e131230a--

From ida_leung@yahoo.com  Wed Jul 10 18:00:39 2013
Return-Path: <ida_leung@yahoo.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9A8F21F99FA for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2013 18:00:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.282
X-Spam-Level: **
X-Spam-Status: No, score=2.282 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dYAKt6ePw0GW for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2013 18:00:34 -0700 (PDT)
Received: from nm5-vm0.bullet.mail.bf1.yahoo.com (nm5-vm0.bullet.mail.bf1.yahoo.com [98.139.213.150]) by ietfa.amsl.com (Postfix) with ESMTP id 6F15C11E80A5 for <ietf@ietf.org>; Wed, 10 Jul 2013 18:00:22 -0700 (PDT)
Received: from [98.139.212.149] by nm5.bullet.mail.bf1.yahoo.com with NNFMP; 11 Jul 2013 01:00:21 -0000
Received: from [68.142.230.65] by tm6.bullet.mail.bf1.yahoo.com with NNFMP; 11 Jul 2013 01:00:20 -0000
Received: from [127.0.0.1] by smtp222.mail.bf1.yahoo.com with NNFMP; 11 Jul 2013 01:00:20 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1373504420; bh=y7BSuE0ZFNqJxTPXdoU322MSKbXgZR9nTjQoxrjH6/Y=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:X-Rocket-Received:References:Mime-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding:Message-Id:Cc:X-Mailer:From:Subject:Date:To; b=zpBQb/I5jOEhKKzEDC1E5OY7stiqp7llIj9EGP3Grp88S91EefEQyiv7oq/3EjpDCUeFed2rTbAV+Z7E0YqeLN3B2pU5JwKn75275b7nk0qW4V3Aei7UsJB2ePuthWafkMccbiwC6B5p5+iAYsxYrgkRNsre9pGvHrFgG3Ut7aM=
X-Yahoo-Newman-Id: 928664.12092.bm@smtp222.mail.bf1.yahoo.com
X-Yahoo-Newman-Property: ymail-3
X-YMail-OSG: 64fVvRkVM1li.u2GTqDtQwdXzDjdwZWDYuQBkHf3RRZ0Npj 62Mt7Y7gamwG4QHGT6IxpdEzYNMqm8twu3SFJZIVb3ILsSmFcHL7Jk1NZjaX c4aQEL7Vr0ducsnB0FbiWe6SJcKIIRKRNivP72ig3n7v_7r1EHi5jMpsjanK dMkVpumRTnja5wEIk2CFpGrnx93S688my8EjrAxLArJJ713LBmjJgycjTgQM js7L2nQoA9.CwTJJuXxpBEHK1NVjKvMnboaUJwY5trd7XP3c4HqSz_yhEJ.9 uXYq2iE.pZXQuxfO9SCy0U1sJX3qxtj1CjepmNrUKhfD5gBmWRCQu6CLE7nw hiZkdkgJ4.2aaPJyNjP.fXVh08x3GT5rJ78CCgbzeNqFYFhb4xuM0nFaTMYY ZkYfb7IfnimO45JS4pAA9_aiT_n1SU9IK6tTzCEeZuOL5Xi0Ho875SmI2PZO XC2728E6OsjBIzPUVH6zx5htQ0Gfz85gaP2WoQmnCNFFO.wpzF75TxKy_KiZ mY4PCMNRXv2l._1UpT.713qJiATQ_GVATJlVCCTB..3_gzM.2WruBAVGgNLO BMBUA_MsGl_hY2Aw7NXB_XB.ePv_iXscmn1wiNYPOCA30zSAxXuSBOyfZVcH gSW3n8v09tsFDrJnPvm0pUvSGdyX33RZP2vs-
X-Yahoo-SMTP: q2miY8yswBCn9p2CkkLMbAZMmk70rw--
X-Rocket-Received: from [10.0.0.4] (ida_leung@24.114.86.114 with ) by smtp222.mail.bf1.yahoo.com with SMTP; 11 Jul 2013 01:00:20 +0000 UTC
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com> <B580C1FC-5794-433F-81CA-FC649CB75943@yahoo.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <B580C1FC-5794-433F-81CA-FC649CB75943@yahoo.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-58FE463B-65CB-4980-BD0D-8E6DC68109AB
Content-Transfer-Encoding: 7bit
Message-Id: <F5D9DB98-4E52-42B0-8707-87781BED6710@yahoo.com>
X-Mailer: iPad Mail (10B329)
From: Ida <ida_leung@yahoo.com>
Subject: Re: Regarding call Chinese names
Date: Wed, 10 Jul 2013 21:00:20 -0400
To: Hui Deng <denghui02@gmail.com>
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 01:00:39 -0000

--Apple-Mail-58FE463B-65CB-4980-BD0D-8E6DC68109AB
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable



Sent from my iPad

On 2013-07-10, at 8:59 PM, Ida <ida_leung@yahoo.com> wrote:

> One comment:  I think most of the Chinese women don't change to our husban=
d's last name. So,  my husband is not Mr Leung.  We love to keep our own las=
t name.  =20
>=20
> ...Ida
>=20
> Sent from my iPad
>=20
> On 2013-07-10, at 8:04 PM, Hui Deng <denghui02@gmail.com> wrote:
>=20
>> Hello all
>> =20
>> We submitted two drafts to help people here to correctly call chinese peo=
ple names:
>> http://tools.ietf.org/html/draft-deng-call-chinese-names-00=20
>>    http://tools.ietf.org/html/draft-zcao-chinese-pronounce-00
>> =20
>> Feel free to let us know if you have any other issues?
>> Best regards,
>> =20
>> -Hui Deng

--Apple-Mail-58FE463B-65CB-4980-BD0D-8E6DC68109AB
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><br><br>Sent from my iPad</div><div><b=
r>On 2013-07-10, at 8:59 PM, Ida &lt;<a href=3D"mailto:ida_leung@yahoo.com">=
ida_leung@yahoo.com</a>&gt; wrote:<br><br></div><blockquote type=3D"cite"><d=
iv><meta http-equiv=3D"content-type" content=3D"text/html; charset=3Dutf-8">=
<div>One comment: &nbsp;I think most of the Chinese women don't change to ou=
r husband's last name. So, &nbsp;my husband is not Mr Leung. &nbsp;We love t=
o keep our own last name. &nbsp;&nbsp;</div><div><br></div><div>...Ida<br><b=
r>Sent from my iPad</div><div><br>On 2013-07-10, at 8:04 PM, Hui Deng &lt;<a=
 href=3D"mailto:denghui02@gmail.com">denghui02@gmail.com</a>&gt; wrote:<br><=
br></div><blockquote type=3D"cite"><div><div dir=3D"ltr"><div>Hello all</div=
><div>&nbsp;</div><div>We submitted two drafts to help people here to correc=
tly call chinese people names:</div><div><font color=3D"#000000" size=3D"3" f=
ace=3D"=E5=AE=8B=E4=BD=93">

</font><p style=3D"margin:0cm 0cm 0pt"><span lang=3D"EN-US"><a href=3D"http:=
//tools.ietf.org/html/draft-deng-call-chinese-names-00" target=3D"_blank"><s=
pan style=3D"background:white;color:rgb(17,85,204);font-family:&quot;Arial&q=
uot;,&quot;sans-serif&quot;;font-size:10pt">http://tools.ietf.org/html/draft=
-deng-call-chinese-names-00</span></a></span><span style=3D"background:white=
;color:rgb(34,34,34);font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;fo=
nt-size:10pt" lang=3D"EN-US">&nbsp;</span></p>
<font color=3D"#000000" size=3D"3" face=3D"=E5=AE=8B=E4=BD=93">

</font><p style=3D"margin:0cm 0cm 0pt"><span style=3D"background:white;color=
:rgb(34,34,34);font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;font-siz=
e:10pt" lang=3D"EN-US">&nbsp; &nbsp;</span><span lang=3D"EN-US"><a href=3D"h=
ttp://tools.ietf.org/html/draft-zcao-chinese-pronounce-00" target=3D"_blank"=
><span style=3D"background:white;color:rgb(17,85,204);font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;;font-size:10pt">http://tools.ietf.org/html/dr=
aft-zcao-chinese-pronounce-00</span></a></span></p>
<p style=3D"margin:0cm 0cm 0pt"><span lang=3D"EN-US"></span>&nbsp;</p><p sty=
le=3D"margin:0cm 0cm 0pt"><span lang=3D"EN-US">Feel free to let us know if y=
ou have any other issues?</span></p><p style=3D"margin:0cm 0cm 0pt"><span la=
ng=3D"EN-US">Best regards,</span></p>
<p style=3D"margin:0cm 0cm 0pt"><span lang=3D"EN-US"></span>&nbsp;</p><p sty=
le=3D"margin:0cm 0cm 0pt"><span lang=3D"EN-US">-Hui Deng</span></p><font col=
or=3D"#000000" size=3D"3" face=3D"=E5=AE=8B=E4=BD=93">

</font></div></div>
</div></blockquote></div></blockquote></body></html>=

--Apple-Mail-58FE463B-65CB-4980-BD0D-8E6DC68109AB--

From sm@elandsys.com  Wed Jul 10 18:03:31 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEB4621F9C22 for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2013 18:03:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.598
X-Spam-Level: 
X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NpR4H67Nr3US for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2013 18:03:31 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EC8021F9983 for <ietf@ietf.org>; Wed, 10 Jul 2013 18:03:29 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.152.167]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r6B139tN007719 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 10 Jul 2013 18:03:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1373504601; bh=y1Xtvlvnd8GmuaVJp2Mh/+NqFIXOtA8jLcO4ivZDRZk=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Jo8FzEjgKuj1EN+ucO0Kq+CeN87ny7z1uk3g5Ze8jo+QaHyVwltz9nYu065yIm9cV wUXD7n3VDiEO6D4FMA6tqEXM6tQGzwiThSpPdfWrSWiFysuutqFgv5JMK7b4C9SQIO NPTtrcMLhXT5nLADrfi0jddSqsn7QPnKROm8AYrY=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1373504601; i=@elandsys.com; bh=y1Xtvlvnd8GmuaVJp2Mh/+NqFIXOtA8jLcO4ivZDRZk=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=PtCxWv+VatkWn1odtettn10maq/XWgyzsa+yHHMWyyb/1EnAx75E/kKSeSnej4qql lq0J9u0KtKJtNpl09qMj5NS7RwrZl2e0EiUOPWen7ZuH/Eyxb/dlBRDijkiwjOk6GP +pK1MaiFs21Ppq/blW5dchteytJoYrtLWR3dtlpM=
Message-Id: <6.2.5.6.2.20130710170747.10088580@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 10 Jul 2013 17:55:24 -0700
To: Hui Deng <denghui02@gmail.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Regarding call Chinese names
In-Reply-To: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.g mail.com>
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com>
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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 01:03:32 -0000

Hi Deng Hui,
At 17:04 10-07-2013, Hui Deng wrote:
>We submitted two drafts to help people here to correctly call 
>chinese people names:
>
>http://tools.ietf.org/html/draft-deng-call-chinese-names-00
>
>    http://tools.ietf.org/html/draft-zcao-chinese-pronounce-00

I would like to thank you and your co-author on taking the initiative 
to write the drafts.  I don't know whether I am western or not. :-)

In Section 3 of draft-deng-call-chinese-names-00:

   'Two generic titles that have similar meanings to "Mr." and
    "Ms./Mrs." are "Xian1sheng1" and "Nv3Shi4".'

   "(1,2,3,4 in this section will be explained in next section)

There are digits in two words in the above.  I suggest making the 
comment about the numbers clearer by mentioning that the digits are 
intentional and they are used to denote the tone.

Regards,
S. Moonesamy 


From hsantos@isdg.net  Wed Jul 10 18:48:54 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F411421F9C4D for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2013 18:48:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.179
X-Spam-Level: 
X-Spam-Status: No, score=-102.179 tagged_above=-999 required=5 tests=[AWL=-0.502, BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, HOST_MISMATCH_COM=0.311, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jnis8eZXT8g8 for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2013 18:48:49 -0700 (PDT)
Received: from catinthebox.net (groups.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 5620321F9C49 for <ietf@ietf.org>; Wed, 10 Jul 2013 18:48:49 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=359; t=1373507320; h=Received:Received: Message-ID:Date:From:To:Subject:Organization:List-ID; bh=QYmzFNh 7VtyZK9nVH6xc9bzXGb4=; b=C1JEV7MzRXcm3+X8aRBGoDW/3BIucQQh/w1Zj0V vTAt2ebg3jxEyofwk+FlQBVEw73EtwM/vVcqNG7DxsB4Dz4HUBNEGkspSsEr1ylo ESJBzdgdL//h6geoSPJWMZTFtJaGWFUc3egyJvmg+pjxsVTzzb1Z+GHpqxSJ9Jvl rKUY=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Wed, 10 Jul 2013 21:48:40 -0400
Received: from [208.247.131.8] ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 4264844861.8699.5508; Wed, 10 Jul 2013 21:48:39 -0400
Message-ID: <51DE0E45.7000603@isdg.net>
Date: Wed, 10 Jul 2013 21:45:41 -0400
From: Hector Santos <hsantos@isdg.net>
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Hui Deng <denghui02@gmail.com>
Subject: Re: Regarding call Chinese names
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com>
In-Reply-To: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com>
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 01:48:54 -0000

On 7/10/2013 8:04 PM, Hui Deng wrote:
> Hello all
> 
> We submitted two drafts to help people here to correctly call chinese
> people names:
> 
>    http://tools.ietf.org/html/draft-deng-call-chinese-names-00
>    http://tools.ietf.org/html/draft-zcao-chinese-pronounce-00
> 

Fantastic. Short and sweet!  Thanks for helping to make us all one.

--
HLS


From zehn.cao@gmail.com  Wed Jul 10 19:17:20 2013
Return-Path: <zehn.cao@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71D3611E80EE for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2013 19:17:20 -0700 (PDT)
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=[AWL=0.000,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w7vwkuh26Hsi for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2013 19:17:20 -0700 (PDT)
Received: from mail-wi0-x22b.google.com (mail-wi0-x22b.google.com [IPv6:2a00:1450:400c:c05::22b]) by ietfa.amsl.com (Postfix) with ESMTP id C0B4611E80A2 for <ietf@ietf.org>; Wed, 10 Jul 2013 19:17:19 -0700 (PDT)
Received: by mail-wi0-f171.google.com with SMTP id hj3so12076885wib.10 for <ietf@ietf.org>; Wed, 10 Jul 2013 19:17:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=0S920AwqFdnrTcG4g2vqEsayjRwNs/xPgpxQ+Ykl8XU=; b=zJ6nUMMidlegj5T6fPooGy9EYWGCstghyjPD3/0KLJc/HmW5yt097jj1K3NVlSQ1/8 1ek9uAfgDenQItbgC/vsaE84B8ZUsoEEj7LD6rK8MfcTWZMHkUE+MwiZde36j8K17tUv ZG3SPW1zgN3zArbPiQwSEfPboXU5azJGllkSIkGti6ktYvgQ0VMgHN5o3QlypxPeGIh/ x2fmZb4pRIQJrScV9elgAkojNkTiL0OOHeNwcWmq1DOEASjUKPykkBKSP3rlj2LOxG8l fGmdsGw/zdjUzu1BfCkQ3uguojtZOAyes3AF9rEeaWSqcyAyk7LYK24glhdTawdbLSG+ +jBA==
MIME-Version: 1.0
X-Received: by 10.194.87.100 with SMTP id w4mr19709473wjz.34.1373509038882; Wed, 10 Jul 2013 19:17:18 -0700 (PDT)
Received: by 10.217.129.136 with HTTP; Wed, 10 Jul 2013 19:17:18 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20130710170747.10088580@resistor.net>
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com> <6.2.5.6.2.20130710170747.10088580@resistor.net>
Date: Thu, 11 Jul 2013 10:17:18 +0800
Message-ID: <CAProHATtW7hXV84v0O+AbpjzMB6n8OBenDLo84a_jS8bRAx_bQ@mail.gmail.com>
Subject: Re: Regarding call Chinese names
From: "Cao,Zhen" <zehn.cao@gmail.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 02:17:20 -0000

On Thu, Jul 11, 2013 at 8:55 AM, S Moonesamy <sm+ietf@elandsys.com> wrote:
> Hi Deng Hui,
>
> At 17:04 10-07-2013, Hui Deng wrote:
>>
>> We submitted two drafts to help people here to correctly call chinese
>> people names:
>>
>> http://tools.ietf.org/html/draft-deng-call-chinese-names-00
>>
>>    http://tools.ietf.org/html/draft-zcao-chinese-pronounce-00
>
>
> I would like to thank you and your co-author on taking the initiative to
> write the drafts.  I don't know whether I am western or not. :-)

:)

>
> In Section 3 of draft-deng-call-chinese-names-00:
>
>   'Two generic titles that have similar meanings to "Mr." and
>    "Ms./Mrs." are "Xian1sheng1" and "Nv3Shi4".'
>
>   "(1,2,3,4 in this section will be explained in next section)
>
> There are digits in two words in the above.  I suggest making the comment
> about the numbers clearer by mentioning that the digits are intentional and
> they are used to denote the tone.

Thanks for the comments, we will revise accordingly.
btw: tones are really difficult to handle, similar for us Chinese to
use the modal words and intonations in English.

>
> Regards,
> S. Moonesamy

From liushucheng@huawei.com  Wed Jul 10 20:44:49 2013
Return-Path: <liushucheng@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 236A821F99A5 for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2013 20:44:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k9xFA2y1fzAV for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2013 20:44:45 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 5A61321F997E for <ietf@ietf.org>; Wed, 10 Jul 2013 20:44:44 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AUX18247; Thu, 11 Jul 2013 03:44:41 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 11 Jul 2013 04:44:17 +0100
Received: from SZXEML401-HUB.china.huawei.com (10.82.67.31) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 11 Jul 2013 04:44:37 +0100
Received: from SZXEML546-MBX.china.huawei.com ([169.254.3.181]) by szxeml401-hub.china.huawei.com ([::1]) with mapi id 14.01.0323.007; Thu, 11 Jul 2013 11:44:30 +0800
From: "Will Liu (Shucheng)" <liushucheng@huawei.com>
To: Hui Deng <denghui02@gmail.com>
Subject: RE: Regarding call Chinese names
Thread-Topic: Regarding call Chinese names
Thread-Index: AQHOfcpEl0pvf3u9ZUKxUqyVS06975le1Z4A
Date: Thu, 11 Jul 2013 03:44:29 +0000
Message-ID: <C9B5F12337F6F841B35C404CF0554ACB4B46B99B@szxeml546-mbx.china.huawei.com>
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com>
In-Reply-To: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.66.78.79]
Content-Type: multipart/alternative; boundary="_000_C9B5F12337F6F841B35C404CF0554ACB4B46B99Bszxeml546mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: Zhamin <zhamin@huawei.com>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 03:44:49 -0000

--_000_C9B5F12337F6F841B35C404CF0554ACB4B46B99Bszxeml546mbxchi_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

A typo in draft-deng-call-chinese-names-00: "Jiao4shao4" should be "Jiao4sh=
ou4".

Cheers,
Shucheng LIU (Will)

From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Hui=
 Deng
Sent: Thursday, July 11, 2013 8:05 AM
To: IETF Discussion
Subject: Regarding call Chinese names

Hello all

We submitted two drafts to help people here to correctly call chinese peopl=
e names:

http://tools.ietf.org/html/draft-deng-call-chinese-names-00

   http://tools.ietf.org/html/draft-zcao-chinese-pronounce-00



Feel free to let us know if you have any other issues?

Best regards,



-Hui Deng

--_000_C9B5F12337F6F841B35C404CF0554ACB4B46B99Bszxeml546mbxchi_
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:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:m=3D"http://schema=
s.microsoft.com/office/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html=
40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:\5B8B\4F53;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@\5B8B\4F53";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@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:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:\5B8B\4F53;}
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
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:\5B8B\4F53;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
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"ZH-CN" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;color=
:#000040">A typo in draft-deng-call-chinese-names-00:
</span><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#000040">&#8220;</span><span lang=
=3D"EN-US" style=3D"font-size:10.0pt;color:#000040">Jiao4shao4</span><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#000040">&#8221;</span><span lang=3D"EN-US" styl=
e=3D"font-size:10.0pt;color:#000040">
 should be </span><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-famil=
y:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#000040">&#8220;</span><=
span lang=3D"EN-US" style=3D"font-size:10.0pt;color:#000040">Jiao4shou4</sp=
an><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Calibri=
&quot;,&quot;sans-serif&quot;;color:#000040">&#8221;</span><span lang=3D"EN=
-US" style=3D"font-size:10.0pt;color:#000040">.</span><span lang=3D"EN-US" =
style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&=
quot;;color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-align:justify;text-justify:inter-ideog=
raph"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Cali=
bri&quot;,&quot;sans-serif&quot;;color:#1F497D">Cheers,<o:p></o:p></span></=
p>
<p class=3D"MsoNormal" style=3D"text-align:justify;text-justify:inter-ideog=
raph"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Cali=
bri&quot;,&quot;sans-serif&quot;;color:#1F497D">Shucheng LIU (Will)<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&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:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<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;"> ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org]
<b>On Behalf Of </b>Hui Deng<br>
<b>Sent:</b> Thursday, July 11, 2013 8:05 AM<br>
<b>To:</b> IETF Discussion<br>
<b>Subject:</b> Regarding call Chinese names<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hello all<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">We submitted two drafts to help=
 people here to correctly call chinese people names:<o:p></o:p></span></p>
</div>
<div>
<p style=3D"margin:0cm;margin-bottom:.0001pt"><span lang=3D"EN-US"><a href=
=3D"http://tools.ietf.org/html/draft-deng-call-chinese-names-00" target=3D"=
_blank"><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot=
;sans-serif&quot;;color:#1155CC;background:white">http://tools.ietf.org/htm=
l/draft-deng-call-chinese-names-00</span></a></span><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot=
;;color:#222222;background:white">&nbsp;</span><span lang=3D"EN-US"><o:p></=
o:p></span></p>
<p style=3D"margin:0cm;margin-bottom:.0001pt"><span lang=3D"EN-US" style=3D=
"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;colo=
r:#222222;background:white">&nbsp; &nbsp;</span><span lang=3D"EN-US"><a hre=
f=3D"http://tools.ietf.org/html/draft-zcao-chinese-pronounce-00" target=3D"=
_blank"><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot=
;sans-serif&quot;;color:#1155CC;background:white">http://tools.ietf.org/htm=
l/draft-zcao-chinese-pronounce-00</span></a><o:p></o:p></span></p>
<p style=3D"margin:0cm;margin-bottom:.0001pt"><span lang=3D"EN-US">&nbsp;<o=
:p></o:p></span></p>
<p style=3D"margin:0cm;margin-bottom:.0001pt"><span lang=3D"EN-US">Feel fre=
e to let us know if you have any other issues?<o:p></o:p></span></p>
<p style=3D"margin:0cm;margin-bottom:.0001pt"><span lang=3D"EN-US">Best reg=
ards,<o:p></o:p></span></p>
<p style=3D"margin:0cm;margin-bottom:.0001pt"><span lang=3D"EN-US">&nbsp;<o=
:p></o:p></span></p>
<p style=3D"margin:0cm;margin-bottom:.0001pt"><span lang=3D"EN-US">-Hui Den=
g<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_C9B5F12337F6F841B35C404CF0554ACB4B46B99Bszxeml546mbxchi_--

From sm@elandsys.com  Wed Jul 10 21:03:07 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65B9611E80FF; Wed, 10 Jul 2013 21:03:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.598
X-Spam-Level: 
X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ENg-smWpBo11; Wed, 10 Jul 2013 21:03:06 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 34E0A11E80EC; Wed, 10 Jul 2013 21:02:56 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.152.167]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r6B42dEM013416 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 10 Jul 2013 21:02:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1373515373; bh=g774JFttB6398QhMkmEdu8oK5Z/Qc3oRs1cAvfWESpQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=aCOKnmnHIdubx3VFNfu1UosuGU0ZIe5xoDuIOIfLSmH+kxWb8WgmsRlUmTOE2bnUP 49ZgPqn5L7UogeVMeXzsDqtdha/TUbPZ+YR8fPOn6TiYIeqEs+KXsoFf3gr3kSLP5L LGSPq5FWqSUj05s9b86BsuquoLTzv+7N12MGmTN8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1373515373; i=@elandsys.com; bh=g774JFttB6398QhMkmEdu8oK5Z/Qc3oRs1cAvfWESpQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=zPg0MW4qusAcFqDJXMIwbjmLtdbLVmZ7488UmJmUyuoi8N2N76svxIt3fjeBlG33b wqMduIARBb0vcnNbkg4hR1HswEpT2LPoQ6f1MeXSyWOZMX+KvKuSlM9cLovQ9QfRC6 T4V9DLgkw0Xx057iQx0fGmaR6GOl1LV0sdlFzPfk=
Message-Id: <6.2.5.6.2.20130710180152.100c7ed0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 10 Jul 2013 20:23:36 -0700
To: iab@iab.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: IAB Statement on Dotless Domains
In-Reply-To: <1984CBB8-6862-4DBB-AFAE-F8461E694083@vigilsec.com>
References: <1984CBB8-6862-4DBB-AFAE-F8461E694083@vigilsec.com>
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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 04:03:07 -0000

Hello,
At 11:59 10-07-2013, Russ Housley wrote:
>The IAB has made a statement on dotless domains.  You can find this 
>statement here:
>http://www.iab.org/documents/correspondence-reports-documents/2013-2/iab-statement-dotless-domains-considered-harmful/

There was a report from the ICANN the Security and Stability Advisory 
Committee in February 2012 on "Dotless domains".  An IAB statement 
about "Dotless Domains Considered Harmful" is issued over a year 
after that.  I am surprised that a draft of the statement was not 
brought to the attention of the IETF participants who have been 
discussing about the use of dotless domains on the SMTP mailing 
list.  To be fair, I should have read the minutes and enquired about 
the matter instead of commenting about the matter after the fact.

ICANN announced in May 2013 that "it has commissioned a study on the 
potential risks related to dotless domain names based on SAC 053 
report".  The announcement mentioned that in June 2012 "the ICANN 
Board directed staff to consult with the relevant communities 
regarding implementation of the recommendations in SAC 053".  One of 
the recommendations in SAC0533 is that:

   "As a result, the SSAC also recommends that the use of DNS 
resource records such
    as A, AAAA, and MX in the apex of a Top-Level Domain (TLD) be contractually
    prohibited where appropriate and strongly discouraged in all cases."

I don't know whether the ICANN Board considers the IETF as a relevant 
community.  I read several IETF Fluff Area mailing lists.  I did not 
see any message about a consultation regarding that recommendation.

The IAB statement mentioned that:

   "The IAB believes that SSAC report SAC053 [SAC053] is a reasonable summary
    of the technical problems that arise from the implementation of dotless
    domains."

I would describe the report as an adequate summary of the technical 
problems for a non-technical audience.

RFC 5321 was published in October 2008.  SAC053 references RFC 2821 
on Page 7.  It is odd that the members of the ICANN Security and 
Stability Advisory Committee were not aware that RFC 2821 was then 
considered as obsolete for over three years.

 From the IAB statement:

   "SAC053 does not, however, discuss the standards compliance aspect."

And from SAC053:

   "Thus standard-compliant mail servers would reject emails to addresses such
    as user@brand."

The report mentions a standards compliance aspect.

 From the IAB statement:

   "The use of SHOULD for [RFC 1123 section 6.1.4.3] (b) is a recommendation
    against doing DNS queries for dotless domains.  RFC 2119 explains 
the meaning
    of SHOULD as follows:"

and the statement quotes text from RFC 2119.  The meaning of the 
"SHOULD" in RFC 1123 is explained in RFC 1123.  RFC 1123 was 
published in October 1989.  RFC 2119 was published in March 1997.  I 
suspect that the IAB may have used time-travel technology for the 
"discussion of standards conformance".

The IAB issued a statement about "The interpretation of rules in the 
ICANN gTLD Applicant Guidebook" in February 2012.  That report also 
refers to "one of the specific TLD requirements set by RFC 1123".  It 
seems to me that the conversations with subject matter specialists 
were mainly about adding a "string" to the Root Zone and that the 
protocol-related issues might not have been conveyed clearly given 
that the IAB issued the statement about "dotless domains" in July 2013.

The IAB previously mentioned that it maintains its chartered 
responsibility about the RFC Series.  The IAB statement refers to 
RFCs from the www.faqs.org website.  It might be better to reference 
the rfc-editor.org links or else there may be a perception that the 
IAB is not aware of the most stable reference available.

Regards,
S. Moonesamy  


From spromano@unina.it  Thu Jul 11 01:38:18 2013
Return-Path: <spromano@unina.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD31221F9ED4 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 01:38:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.718
X-Spam-Level: 
X-Spam-Status: No, score=-100.718 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QX9Fc1+0gqfM for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 01:38:14 -0700 (PDT)
Received: from smtp2.unina.it (smtp2.unina.it [192.132.34.62]) by ietfa.amsl.com (Postfix) with ESMTP id A000621F9EDF for <ietf@ietf.org>; Thu, 11 Jul 2013 01:38:10 -0700 (PDT)
Received: from [143.225.162.130] ([143.225.162.130]) (authenticated bits=0) by smtp2.unina.it (8.14.4/8.14.4) with ESMTP id r6B8c4WZ020539 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 11 Jul 2013 10:38:05 +0200
Subject: Re: IETF registration fee?
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: multipart/alternative; boundary="Apple-Mail=_FB3E45A7-7A07-452C-93CD-FC1D605965A2"
From: Simon Pietro Romano <spromano@unina.it>
In-Reply-To: <803FCD9A-6B8A-45EC-914F-E2114C581EA1@gmail.com>
Date: Thu, 11 Jul 2013 10:38:11 +0200
Message-Id: <C053B4F4-4821-4132-B872-3F8A611B2F5F@unina.it>
References: <CE0388EA.21B7F%Josh.Howlett@ja.net> <803FCD9A-6B8A-45EC-914F-E2114C581EA1@gmail.com>
To: Douglas Otis <doug.mtview@gmail.com>
X-Mailer: Apple Mail (2.1283)
Cc: "ietf@ietf.org" <ietf@ietf.org>, Keith Moore <moore@network-heretics.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 08:38:18 -0000

--Apple-Mail=_FB3E45A7-7A07-452C-93CD-FC1D605965A2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Hello Douglas,

> Dear Josh,
>=20
> I agree. A single day fee should also be considered in conjunction =
with the increased status of remote participation underwritten by a much =
smaller remote meeting fee.  It seems there is a general reluctance to =
consider schemes aimed at capturing face-to-face meetings in a realtime =
fashion permitting moderated realtime interaction with selected network =
entities. Experiments with things like WebEx and others involve a fair =
amount of network resources or they offer poor results.  An audio/video =
bridge suitable for many simultaneous participants is difficult to solve =
in a generic manner.  The real question is simultaneous participation in =
conjunction with telephone bridges really necessary?

As regards remote participation 'experiments', we have been working for =
years on trying and improving remote participants involvement and =
interactivity at IETF meetings (starting with IETF80 in Prague). You can =
have a look at [http://ietf8X.conf.meetecho.com/ (0 <=3D X <=3D 7)] to =
get an idea of such work.

> Setting up a dedicated low cost device to manage video projectors, =
microphones, and PA systems for a single moderated inbound access should =
supplant much of the complexity.  By not permitting multiple video/audio =
sources and requiring presentation being available in the cloud prior to =
the meetings, issues of distribution and audio quality are removed.  =
Such an approach will necessitate greater meeting discipline to ensure =
only those at an active microphone are recognized, and that presenters =
both local and remote are permitted control of their presentation.=20

With respect to this point, we proposed an experiment at IETF83: =
http://ietf83.conf.meetecho.com/index.php/UMPIRE_Project. Discussions =
about this specific topic can be found in the vmeet mailing list, as =
well as in the once-supposed-to-become-official RPS document from Paul =
Hoffman http://tools.ietf.org/html/draft-ietf-genarea-rps-reqs-08.

> Developing this approach would offer a number of benefits extending =
well beyond that of the IETF since this is a common problem.  Much of =
the ongoing wok related to HTML5 facilitate standardizing the needed =
APIs.  There are many fairly powerful systems using dual core Atom =
processors available well below $300.  These systems should be able to =
handle audio using USB adapters and source video presentations accessed =
from the cloud.  A fallback operation should be able to carry meetings =
forward completely from the cloud "as if" moderators and participants =
were present locally.  In other words, treat loss of the Internet at the =
venue as being equivalent to being denied access to the physical venue =
and include this requirement in venue arrangements.
>=20
> Those traveling thousands of miles already confront many =
uncertainties.  Those that elect to participate remotely should be =
afforded greater certainty of being able to participate when problems =
occur at local venues or with transportation.  Increasing participation =
without the expense of the brick and mortar and travel should offer long =
term benefits and increased fairness.=20

Agreed.

Cheers,

Simon

>=20
> Regards,
> Douglas Otis
>=20
>=20
>=20
>=20
>=20
>=20
>=20

                     					       _\\|//_
                           				      ( O-O )
   ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
                    				Simon Pietro Romano
             				 Universita' di Napoli Federico =
II
                		     Computer Engineering Department=20
	             Phone: +39 081 7683823 -- Fax: +39 081 7683816
                                           e-mail: spromano@unina.it

		    <<Molti mi dicono che lo scoraggiamento =CB l'alibi =
degli=20
		    idioti. Ci rifletto un istante; e mi scoraggio>>. =
Magritte.
               			                     oooO
  ~~~~~~~~~~~~~~~~~~~~~~~(   )~~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
					                 \ (            =
(   )
			                                  \_)          ) =
/
                                                                       =
(_/






--Apple-Mail=_FB3E45A7-7A07-452C-93CD-FC1D605965A2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hello =
Douglas,<div><br><div><blockquote type=3D"cite"><div>Dear Josh,<br><br>I =
agree. A single day fee should also be considered in conjunction with =
the increased status of remote participation underwritten by a much =
smaller remote meeting fee. &nbsp;It seems there is a general reluctance =
to consider schemes aimed at capturing face-to-face meetings in a =
realtime fashion permitting moderated realtime interaction with selected =
network entities. Experiments with things like WebEx and others involve =
a fair amount of network resources or they offer poor results. &nbsp;An =
audio/video bridge suitable for many simultaneous participants is =
difficult to solve in a generic manner. &nbsp;The real question is =
simultaneous participation in conjunction with telephone bridges really =
necessary?<br></div></blockquote><div><br></div>As regards remote =
participation 'experiments', we have been working for years on trying =
and improving remote participants involvement and interactivity at IETF =
meetings (starting with IETF80 in Prague). You can have a look at [<a =
href=3D"http://ietf8X.conf.meetecho.com/">http://ietf8X.conf.meetecho.com/=
</a> (0 &lt;=3D X &lt;=3D 7)] to get an idea of such =
work.</div><div><br><blockquote type=3D"cite"><div>Setting up a =
dedicated low cost device to manage video projectors, microphones, and =
PA systems for a single moderated inbound access should supplant much of =
the complexity. &nbsp;By not permitting multiple video/audio sources and =
requiring presentation being available in the cloud prior to the =
meetings, issues of distribution and audio quality are removed. =
&nbsp;Such an approach will necessitate greater meeting discipline to =
ensure only those at an active microphone are recognized, and that =
presenters both local and remote are permitted control of their =
presentation. <br></div></blockquote><div><br></div>With respect to this =
point, we proposed an experiment at IETF83:&nbsp;<a =
href=3D"http://ietf83.conf.meetecho.com/index.php/UMPIRE_Project">http://i=
etf83.conf.meetecho.com/index.php/UMPIRE_Project</a>. Discussions about =
this specific topic can be found in the vmeet mailing list, as well as =
in the once-supposed-to-become-official RPS document from Paul =
Hoffman&nbsp;<a =
href=3D"http://tools.ietf.org/html/draft-ietf-genarea-rps-reqs-08">http://=
tools.ietf.org/html/draft-ietf-genarea-rps-reqs-08</a>.</div><div><br><blo=
ckquote type=3D"cite"><div>Developing this approach would offer a number =
of benefits extending well beyond that of the IETF since this is a =
common problem. &nbsp;Much of the ongoing wok related to HTML5 =
facilitate standardizing the needed APIs. &nbsp;There are many fairly =
powerful systems using dual core Atom processors available well below =
$300. &nbsp;These systems should be able to handle audio using USB =
adapters and source video presentations accessed from the cloud. &nbsp;A =
fallback operation should be able to carry meetings forward completely =
from the cloud "as if" moderators and participants were present locally. =
&nbsp;In other words, treat loss of the Internet at the venue as being =
equivalent to being denied access to the physical venue and include this =
requirement in venue arrangements.<br><br>Those traveling thousands of =
miles already confront many uncertainties. &nbsp;Those that elect to =
participate remotely should be afforded greater certainty of being able =
to participate when problems occur at local venues or with =
transportation. &nbsp;Increasing participation without the expense of =
the brick and mortar and travel should offer long term benefits and =
increased fairness. =
<br></div></blockquote><div><br></div>Agreed.</div><div><br></div><div>Che=
ers,</div><div><br></div><div>Simon</div><div><br><blockquote =
type=3D"cite"><div><br>Regards,<br>Douglas =
Otis<br><br><br><br><br><br><br><br></div></blockquote></div><br><div =
apple-content-edited=3D"true">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">					=
</span><span class=3D"Apple-converted-space">&nbsp;</span>&nbsp; &nbsp; =
&nbsp; _\\|//_</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
</span>&nbsp; &nbsp; &nbsp;&nbsp;( O-O )</div><div>&nbsp; =
&nbsp;~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~</div><di=
v>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;<span class=3D"Apple-converted-space">&nbsp;</span><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
</span>Simon Pietro Romano</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;<span class=3D"Apple-tab-span" style=3D"white-space: pre; =
">				</span><span =
class=3D"Apple-converted-space">&nbsp;</span>Universita' di Napoli =
Federico II</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;&nbsp;<span class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
	</span>&nbsp; &nbsp; &nbsp;Computer Engineering =
Department&nbsp;</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	</span>&nbsp; &nbsp; &nbsp;&nbsp; &nbsp; =
&nbsp; &nbsp; Phone: +39 081 7683823 -- Fax: +39 081 =
7683816</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;e-mail: <a =
href=3D"mailto:spromano@unina.it">spromano@unina.it</a></div><div><br></di=
v><div><span class=3D"Apple-tab-span" style=3D"white-space: pre; ">		=
</span>&nbsp; &nbsp; &lt;&lt;Molti mi dicono che lo scoraggiamento =CB =
l'alibi degli&nbsp;</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">		</span>&nbsp;&nbsp; =
&nbsp;idioti. Ci rifletto un istante; e mi scoraggio&gt;&gt;. =
Magritte.</div><div>&nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; =
&nbsp;<span class=3D"Apple-converted-space">&nbsp;</span><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">			=
</span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;oooO</div><div>&nbsp; ~~~~~~~~~~~~~~~~~~~~~~~( &nbsp; =
)~~~&nbsp;Oooo~~~~~~~~~~~~~~~~~~~~~~~~~</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
	</span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;\ ( &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;( &nbsp; =
)</div><div><span class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
		</span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
\_) &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;) /</div><div>&nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp;(_/</div></div><div><br></div></div><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<br></div></body></html>=

--Apple-Mail=_FB3E45A7-7A07-452C-93CD-FC1D605965A2--

From victor.zhongxin@huawei.com  Thu Jul 11 02:50:18 2013
Return-Path: <victor.zhongxin@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41A9321F9FE6 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 02:50:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.795
X-Spam-Level: 
X-Spam-Status: No, score=-0.795 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, EXTRA_MPART_TYPE=1, HTML_MESSAGE=0.001, J_CHICKENPOX_66=0.6, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QINhKE2eyjDA for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 02:50:14 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 9D73F21F9F8A for <ietf@ietf.org>; Thu, 11 Jul 2013 02:50:13 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ATI51135; Thu, 11 Jul 2013 09:50:12 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 11 Jul 2013 10:49:44 +0100
Received: from LHREML514-MBX.china.huawei.com ([10.201.4.201]) by lhreml406-hub.china.huawei.com ([10.201.5.243]) with mapi id 14.01.0323.007; Thu, 11 Jul 2013 10:50:01 +0100
From: "Zhongxin (Victor)" <victor.zhongxin@huawei.com>
To: Hui Deng <denghui02@gmail.com>, IETF Discussion <ietf@ietf.org>
Subject: RE: Regarding call Chinese names
Thread-Topic: Regarding call Chinese names
Thread-Index: AQHOfcpGCzpMeGeGzkux9Sq9sSjZq5lfJqmA
Date: Thu, 11 Jul 2013 09:50:00 +0000
Message-ID: <0B65E3C66FCF4F459F93A1A5767BB35A034AD02C@lhreml514-mbx>
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com>
In-Reply-To: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.200.218.40]
Content-Type: multipart/related; boundary="_004_0B65E3C66FCF4F459F93A1A5767BB35A034AD02Clhreml514mbx_";  type="multipart/alternative"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 09:50:18 -0000

--_004_0B65E3C66FCF4F459F93A1A5767BB35A034AD02Clhreml514mbx_
Content-Type: multipart/alternative;
	boundary="_000_0B65E3C66FCF4F459F93A1A5767BB35A034AD02Clhreml514mbx_"

--_000_0B65E3C66FCF4F459F93A1A5767BB35A034AD02Clhreml514mbx_
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64

QlJBVk8sIHRlY2hpZXMgbm90IHNwZWFraW5nIENoaW5lc2Ugd291bGQgbm8gbG9uZ2VyIG1pc3By
b25vdW5jZSChsEh1YXdlaaGxIGFzIHRoZSBuYW1lIG9mIHNvbWUgVS5TIHN0YXRlLg0KDQoNCl9f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQpWaWN0b3IgWmhvbmcgWGluICDW0yD2zg0K
RXVyb3BlYW4gUmVnaW9uLEh1YXdlaSBUZWNobm9sb2dpZXMgQ28uLCBMdGQuDQpbaHVhd2VpLWxv
Z29dDQoNCmh0dHA6Ly93d3cuaHVhd2VpLmNvbQ0KX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX18NCg0KDQoNCkZyb206IGlldGYtYm91bmNlc0BpZXRmLm9yZzxtYWlsdG86aWV0Zi1ib3Vu
Y2VzQGlldGYub3JnPiBbbWFpbHRvOmlldGYtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9m
IEh1aSBEZW5nDQpTZW50OiBUaHVyc2RheSwgSnVseSAxMSwgMjAxMyAyOjA1IEFNDQpUbzogSUVU
RiBEaXNjdXNzaW9uDQpTdWJqZWN0OiBSZWdhcmRpbmcgY2FsbCBDaGluZXNlIG5hbWVzDQoNCkhl
bGxvIGFsbA0KDQpXZSBzdWJtaXR0ZWQgdHdvIGRyYWZ0cyB0byBoZWxwIHBlb3BsZSBoZXJlIHRv
IGNvcnJlY3RseSBjYWxsIGNoaW5lc2UgcGVvcGxlIG5hbWVzOg0KDQpodHRwOi8vdG9vbHMuaWV0
Zi5vcmcvaHRtbC9kcmFmdC1kZW5nLWNhbGwtY2hpbmVzZS1uYW1lcy0wMA0KDQogICBodHRwOi8v
dG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC16Y2FvLWNoaW5lc2UtcHJvbm91bmNlLTAwDQoNCg0K
DQpGZWVsIGZyZWUgdG8gbGV0IHVzIGtub3cgaWYgeW91IGhhdmUgYW55IG90aGVyIGlzc3Vlcz8N
Cg0KQmVzdCByZWdhcmRzLA0KDQoNCg0KLUh1aSBEZW5nDQo=

--_000_0B65E3C66FCF4F459F93A1A5767BB35A034AD02Clhreml514mbx_
Content-Type: text/html; charset="gb2312"
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=3Dgb2312">
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:=CB=CE=CC=E5;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@=CB=CE=CC=E5";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:=BB=AA=CE=C4=CF=B8=BA=DA;
	panose-1:2 1 6 0 4 1 1 1 1 1;}
@font-face
	{font-family:"\@=BB=AA=CE=C4=CF=B8=BA=DA";
	panose-1:2 1 6 0 4 1 1 1 1 1;}
@font-face
	{font-family:"Segoe Script";
	panose-1:2 11 5 4 2 0 0 0 0 3;}
@font-face
	{font-family:=BB=AA=CE=C4=D0=D0=BF=AC;
	panose-1:2 1 8 0 4 1 1 1 1 1;}
@font-face
	{font-family:"\@=BB=AA=CE=C4=D0=D0=BF=AC";
	panose-1:2 1 8 0 4 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:=CB=CE=CC=E5;}
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
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:=CB=CE=CC=E5;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"2050" />
</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;;color:#1F497D">BRAVO, techies not speaki=
ng Chinese would no longer mispronounce =A1=B0Huawei=A1=B1 as the name of s=
ome U.S state.<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"><o:p>&nbsp;</o:p></span><=
/p>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span=
 style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:#1F497D">
<hr size=3D"2" width=3D"100%" align=3D"center">
</span></div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Segoe Script&quot;,=
&quot;sans-serif&quot;;color:black">Victor Zhong Xin</span><span style=3D"f=
ont-size:10.0pt;font-family:=BB=AA=CE=C4=CF=B8=BA=DA;color:black">&nbsp;
</span><span lang=3D"ZH-CN" style=3D"font-size:14.0pt;font-family:=BB=AA=CE=
=C4=D0=D0=BF=AC;color:black">=D6=D3 =F6=CE</span><span style=3D"font-size:1=
0.0pt;font-family:=BB=AA=CE=C4=CF=B8=BA=DA;color:black"><br>
</span><span style=3D"font-size:7.5pt;font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;;color:#A6A6A6">European Region,Huawei Technologies Co., Ltd=
.<br>
<img width=3D"45" height=3D"45" id=3D"Picture_x0020_2" src=3D"cid:image001.=
jpg@01CE7E22.80935490" alt=3D"huawei-logo"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:7.5pt;font-family:&quot;Ari=
al&quot;,&quot;sans-serif&quot;;color:#A6A6A6"><br>
</span><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:#1F497D"><a href=3D"http://www.huawei.com"><span s=
tyle=3D"font-size:7.5pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot=
;;color:#A6A6A6">http://www.huawei.com</span></a></span><span style=3D"font=
-size:7.5pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#A6A=
6A6">
<o:p></o:p></span></p>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span=
 style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:#1F497D">
<hr size=3D"2" width=3D"100%" align=3D"center">
</span></div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;<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"><o:p>&nbsp;</o:p></span><=
/p>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<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;">
<a href=3D"mailto:ietf-bounces@ietf.org">ietf-bounces@ietf.org</a> [<a href=
=3D"mailto:ietf-bounces@ietf.org">mailto:ietf-bounces@ietf.org</a>]
<b>On Behalf Of </b>Hui Deng<br>
<b>Sent:</b> Thursday, July 11, 2013 2:05 AM<br>
<b>To:</b> IETF Discussion<br>
<b>Subject:</b> Regarding call Chinese names<o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal">Hello all<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">We submitted two drafts to help people here to corre=
ctly call chinese people names:<o:p></o:p></p>
</div>
<div>
<p style=3D"margin:0cm;margin-bottom:.0001pt"><a href=3D"http://tools.ietf.=
org/html/draft-deng-call-chinese-names-00" target=3D"_blank"><span style=3D=
"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;colo=
r:#1155CC;background:white">http://tools.ietf.org/html/draft-deng-call-chin=
ese-names-00</span></a><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;;color:#222222;background:white">&nbsp;</sp=
an><o:p></o:p></p>
<p style=3D"margin:0cm;margin-bottom:.0001pt"><span style=3D"font-size:10.0=
pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222;backg=
round:white">&nbsp; &nbsp;</span><a href=3D"http://tools.ietf.org/html/draf=
t-zcao-chinese-pronounce-00" target=3D"_blank"><span style=3D"font-size:10.=
0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#1155CC;back=
ground:white">http://tools.ietf.org/html/draft-zcao-chinese-pronounce-00</s=
pan></a><o:p></o:p></p>
<p style=3D"margin:0cm;margin-bottom:.0001pt">&nbsp;<o:p></o:p></p>
<p style=3D"margin:0cm;margin-bottom:.0001pt">Feel free to let us know if y=
ou have any other issues?<o:p></o:p></p>
<p style=3D"margin:0cm;margin-bottom:.0001pt">Best regards,<o:p></o:p></p>
<p style=3D"margin:0cm;margin-bottom:.0001pt">&nbsp;<o:p></o:p></p>
<p style=3D"margin:0cm;margin-bottom:.0001pt">-Hui Deng<o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>

--_000_0B65E3C66FCF4F459F93A1A5767BB35A034AD02Clhreml514mbx_--

--_004_0B65E3C66FCF4F459F93A1A5767BB35A034AD02Clhreml514mbx_
Content-Type: image/jpeg; name="image001.jpg"
Content-Description: image001.jpg
Content-Disposition: inline; filename="image001.jpg"; size=1658;
	creation-date="Thu, 11 Jul 2013 09:50:00 GMT";
	modification-date="Thu, 11 Jul 2013 09:50:00 GMT"
Content-ID: <image001.jpg@01CE7E22.80935490>
Content-Transfer-Encoding: base64

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwgHBgoICAgLCgoLDhgQDg0NDh0VFhEYIx8lJCIf
IiEmKzcvJik0KSEiMEExNDk7Pj4+JS5ESUM8SDc9Pjv/2wBDAQoLCw4NDhwQEBw7KCIoOzs7Ozs7
Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozv/wAARCAAtAC0DASIA
AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA
AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3
ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm
p6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA
AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx
BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK
U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3
uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD1+8vL
bT7V7q7mWGGMZZ26Cuc8eeIJ9I8PRyWEm2S7cIky87Vxkkfh/OsT4tXVwkOn2q5FvIzu2OjMMYH6
mucsNQfXPCs+gTNuuLT/AEiyJ6sF+8n5ZIriq13zOmux9Ll+VxdKni56rm1Xle1/k9/I3vh5qEv9
rvHLM8n2iM7i7Ekkcg8/jW2b8/aZrpJmVy5IweMdq4PwXemLxBbLnn5//QTV2xv5b24itYTmSZgo
/HvXGpvkS8z08ZgE8VOXSy/X/I9RGqW0WmxXt1KkEcgXljgZPargIIyORXj/AIv8RpfTJY2r7rO0
Hlx4/jI4LV6H4IuJrrwfp8twxaTYy5PUgMQP0Ar0KVfnm4dj5/GZZLDYaNeX2nt26r/gnmP/AAms
1/FLo3iy3N1HHIV86MBZoHHGR2P0NU5NNudOdNV0q5W8toXDpcQjmM9g69VP14967f4ieFdBMX9t
3Mk9hKW2yTW8HmKxPQuvH55rhtOk0qxukk0/xHdifovl2By3tjdz9K5a1OXNr/wT38vxlJ0r01a+
6s3F/ctPl80bej6ek3ivTtQtE22l+JHVR0jkCNvT8DyPYisq3STSNGN2dwu7/dDbL3WPo7j6/dH4
16t4Z0uODT1uJbRYZpW8wr5PlfNjG7Zk7CQecflWR4xsl03bf2qvaDyxG11Dbec0Kjoq/MPLHuB+
NXKhaHMYUs2VTEeytdaL1s3ZdX1XTW22unAW+j2un7bjxBK0QxlbKP8A10n1/uD3PPoK14fFHiXV
pHTRE+yWtsqolvAoIjXnGTjk8Vii18Pyyb5vEFySxyxNkST/AOPV694W0Wx0XR447JJP3wEjvKu2
RyemR2+nas6NOUnZOy/E6szxlKlBTqR55vZNNRXeyf8AwX8iJ/FGh3nhldXlYy6bcssXzwk7t7BQ
Cp7ZIrMsB4K0OzutesrFIEt7k2skoiZmWQOEIUHOBuPauHsvD2np8K9O1RVm+1/arf5jcSFP9av8
G7b+lOv9Rmj8R3fw82oYL7VPtRvMHcgaQSldvQ8jGc/hXp2R8OpySaT0Z6hP4n0m317+w3uCb/yD
MIlQnKgE4z03YBOOuKrnxpoDQ6S5u/k1ptlplD856EH05OOe9cBPp95L4Vn8ejVZlu1vTfrbeWhj
BRzGFzjdjYNvXHPSoDpCS3Pi6ISlY9Ht/P09dv8Ax7s7faDj6MoH0pknXSz+BLDVpbldPVr6G6Nu
scNs8jPMFDEIgBBIBGSBxVvVviT4d0MW39qNeWj3UZkSOW0dXChivKkZHIPXtXDavYRWPgLQfFc+
65njeW4uIt7x+e1xyx3IQVxxj2Fcb47vY9Y07w7fQ25tUls5cQmZpduJ5B95jk9M80kkti51Jz+N
t+p//9k=

--_004_0B65E3C66FCF4F459F93A1A5767BB35A034AD02Clhreml514mbx_--

From swmike@swm.pp.se  Thu Jul 11 03:25:29 2013
Return-Path: <swmike@swm.pp.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AB8921F9F59 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 03:25:29 -0700 (PDT)
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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W2qIrI2OUaES for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 03:25:28 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by ietfa.amsl.com (Postfix) with ESMTP id 667F121F9F86 for <ietf@ietf.org>; Thu, 11 Jul 2013 03:25:23 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 80B509C; Thu, 11 Jul 2013 12:25:21 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 7786E9A for <ietf@ietf.org>; Thu, 11 Jul 2013 12:25:21 +0200 (CEST)
Date: Thu, 11 Jul 2013 12:25:21 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: IETF Discussion <ietf@ietf.org>
Subject: RE: Regarding call Chinese names
In-Reply-To: <0B65E3C66FCF4F459F93A1A5767BB35A034AD02C@lhreml514-mbx>
Message-ID: <alpine.DEB.2.00.1307111201190.8891@uplift.swm.pp.se>
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com> <0B65E3C66FCF4F459F93A1A5767BB35A034AD02C@lhreml514-mbx>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="-137064504-1874925368-1373536982=:8891"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 10:25:29 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

---137064504-1874925368-1373536982=:8891
Content-Type: TEXT/PLAIN; CHARSET=UTF-8; FORMAT=flowed
Content-Transfer-Encoding: 8BIT

On Thu, 11 Jul 2013, Zhongxin (Victor) wrote:

> BRAVO, techies not speaking Chinese would no longer mispronounce 
> 鈥淗uawei鈥� as the name of some U.S state.

I have asked Huawei staff how it's pronounced and I think I get it fairly 
right. People who hasn't, might get confused because when I use that 
pronounciation it's not the prevelant pronounciation. About your example, 
there are plenty of places in the US with french origins, and in US 
english, these are pronounced differently than in french. What's correct? 
Perhaps if Huawei would call itself Whow-wei in latin characters more 
people would get it right, if this is a really sensitive issue.

Linux has similar issue, Linus Torvalds native language is swedish, but 
he's also a native finnish speaker:

<http://danielmiessler.com/blog/dont-ever-argue-again-about-the-pronunciation-of-linux>

How many english speakers pronounce Linux correctly? Linus' first name? In 
what language? Do native chinese get it right? Is it really worth spending 
time debating it? My name is pronounced differently in english and in 
swedish, just like Linus' name is. I don't get upset when people get it 
"wrong". Btw, it's pronounced Mii-ka-el in swedish (where the ii is a long 
version of the initial sound in "industry").

So while I read with interest the documents presented in the original post 
in this thread, I don't expect to understand and remember all of what's in 
them.

Are these documents intended to be published as informational RFCs (it 
says "intended status: informational")? Are we intending to have one for 
each 'major' language in the world? Where is the cutoff for 'major' status 
of a language?

Should the IETF really publish documents about human languages that 
doesn't really have anything to do with Internet Engineering?

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se
---137064504-1874925368-1373536982=:8891--

From tom@dropfuse.com  Thu Jul 11 04:05:33 2013
Return-Path: <tom@dropfuse.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F1A811E810E for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 04:05:33 -0700 (PDT)
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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q9PsC93v-S-D for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 04:05:28 -0700 (PDT)
Received: from mail01.dropfuse.com (mail.ams.dropfuse.com [198.211.127.66]) by ietfa.amsl.com (Postfix) with ESMTP id E079311E810B for <ietf@ietf.org>; Thu, 11 Jul 2013 04:05:11 -0700 (PDT)
Received: by mail01.dropfuse.com (Postfix, from userid 1003) id EA00C6EF34; Thu, 11 Jul 2013 11:05:02 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dropfuse.com; s=mail; t=1373540702; bh=Pvv0bzNN8Pur+s0PG8Ooc/81lnKEweCyzxCPzU2qTpM=; h=Date:From:To:Subject:References:In-Reply-To; b=Urnqg+7grKRUzAPEmg1YnILVe26FKbcoBeBFUtVoUw/KSpEwTLy8Z9858x255Yd3j 3gEHu8ciqUwKg3GgYMIurueUVmTdurbfaNC+zmF1lC9haIQD/QIhe4CC0fBlCiqctJ 3PvcnRAbY8wffdscomGQfIo+z/dq+jV41daoBdF4=
Received: from [192.168.1.126] (cpc5-bagu10-2-0-cust364.1-3.cable.virginmedia.com [86.10.189.109]) by mail01.dropfuse.com (Postfix) with ESMTPSA id 3813B6EED7 for <ietf@ietf.org>; Thu, 11 Jul 2013 11:05:02 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dropfuse.com; s=mail; t=1373540702; bh=Pvv0bzNN8Pur+s0PG8Ooc/81lnKEweCyzxCPzU2qTpM=; h=Date:From:To:Subject:References:In-Reply-To; b=Urnqg+7grKRUzAPEmg1YnILVe26FKbcoBeBFUtVoUw/KSpEwTLy8Z9858x255Yd3j 3gEHu8ciqUwKg3GgYMIurueUVmTdurbfaNC+zmF1lC9haIQD/QIhe4CC0fBlCiqctJ 3PvcnRAbY8wffdscomGQfIo+z/dq+jV41daoBdF4=
Message-ID: <51DE915D.3070302@dropfuse.com>
Date: Thu, 11 Jul 2013 12:05:01 +0100
From: Tom McLoughlin <tom@dropfuse.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Regarding call Chinese names
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com> <0B65E3C66FCF4F459F93A1A5767BB35A034AD02C@lhreml514-mbx> <alpine.DEB.2.00.1307111201190.8891@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.00.1307111201190.8891@uplift.swm.pp.se>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 11:05:33 -0000

I've always pronounced Huawei as Hawaii tbh.

On 11/07/2013 11:25, Mikael Abrahamsson wrote:
> On Thu, 11 Jul 2013, Zhongxin (Victor) wrote:
>
>> BRAVO, techies not speaking Chinese would no longer mispronounce
>> 鈥淗uawei鈥� as the name of some U.S state.
>
> I have asked Huawei staff how it's pronounced and I think I get it
> fairly right. People who hasn't, might get confused because when I use
> that pronounciation it's not the prevelant pronounciation. About your
> example, there are plenty of places in the US with french origins, and
> in US english, these are pronounced differently than in french. What's
> correct? Perhaps if Huawei would call itself Whow-wei in latin
> characters more people would get it right, if this is a really
> sensitive issue.
>
> Linux has similar issue, Linus Torvalds native language is swedish,
> but he's also a native finnish speaker:
>
> <http://danielmiessler.com/blog/dont-ever-argue-again-about-the-pronunciation-of-linux>
>
>
> How many english speakers pronounce Linux correctly? Linus' first
> name? In what language? Do native chinese get it right? Is it really
> worth spending time debating it? My name is pronounced differently in
> english and in swedish, just like Linus' name is. I don't get upset
> when people get it "wrong". Btw, it's pronounced Mii-ka-el in swedish
> (where the ii is a long version of the initial sound in "industry").
>
> So while I read with interest the documents presented in the original
> post in this thread, I don't expect to understand and remember all of
> what's in them.
>
> Are these documents intended to be published as informational RFCs (it
> says "intended status: informational")? Are we intending to have one
> for each 'major' language in the world? Where is the cutoff for
> 'major' status of a language?
>
> Should the IETF really publish documents about human languages that
> doesn't really have anything to do with Internet Engineering?
>


From yding@cs.helsinki.fi  Thu Jul 11 04:22:46 2013
Return-Path: <yding@cs.helsinki.fi>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF4A021F9655 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 04:22:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FRPKthIt0HzC for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 04:22:42 -0700 (PDT)
Received: from courier.cs.helsinki.fi (courier.cs.helsinki.fi [128.214.9.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A54D11E80F3 for <ietf@ietf.org>; Thu, 11 Jul 2013 04:22:40 -0700 (PDT)
X-DKIM: Courier DKIM Filter v0.50+pk-2013-06-17 courier.cs.helsinki.fi Thu Jul 11 14:22:18 2013
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cs.helsinki.fi; h=message-id:date:from:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; s= dkim20130528; bh=cMQsLQthcNMS7gTPtDUS+wdr8XhYw/d7cu2QbEwbZ4s=; b= KwrrJx3kmtddohHKEDCracT2hrJVNLGecJ4N/T1rzHeZidC4yX1MioCuX23ek2gv ihQN0iCgEPa+h5fcYPev91R9/1gJ1ik4TA3Qqje/CDDCw5weLEbphSce/1CcH/vU 6qgaPhwWTcR6K+/q9hp3tr8bfJ0aRUZ346Vn3ALtUXI=
Received: from [128.232.100.160] (c0160.aw.cl.cam.ac.uk [128.232.100.160]) (AUTH: PLAIN yding, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by mail.cs.helsinki.fi with esmtp; Thu, 11 Jul 2013 14:22:17 +0300 id 00068AFB.51DE9569.00000CF2
Message-ID: <51DE9563.2090100@cs.helsinki.fi>
Date: Thu, 11 Jul 2013 12:22:11 +0100
From: Aaron Yi DING <yding@cs.helsinki.fi>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: Tom McLoughlin <tom@dropfuse.com>
Subject: Hawaii Huawei. Re: Regarding call Chinese names
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com> <0B65E3C66FCF4F459F93A1A5767BB35A034AD02C@lhreml514-mbx> <alpine.DEB.2.00.1307111201190.8891@uplift.swm.pp.se> <51DE915D.3070302@dropfuse.com>
In-Reply-To: <51DE915D.3070302@dropfuse.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 11:22:46 -0000

On 11/07/13 12:05, Tom McLoughlin wrote:
> I've always pronounced Huawei as Hawaii tbh.


Not a bad idea to get Huawei smartphones under that brand name, which 
sounds quite cute :)

Aaron


> On 11/07/2013 11:25, Mikael Abrahamsson wrote:
>> On Thu, 11 Jul 2013, Zhongxin (Victor) wrote:
>>
>>> BRAVO, techies not speaking Chinese would no longer mispronounce
>>> 鈥淗uawei鈥� as the name of some U.S state.
>> I have asked Huawei staff how it's pronounced and I think I get it
>> fairly right. People who hasn't, might get confused because when I use
>> that pronounciation it's not the prevelant pronounciation. About your
>> example, there are plenty of places in the US with french origins, and
>> in US english, these are pronounced differently than in french. What's
>> correct? Perhaps if Huawei would call itself Whow-wei in latin
>> characters more people would get it right, if this is a really
>> sensitive issue.
>>
>> Linux has similar issue, Linus Torvalds native language is swedish,
>> but he's also a native finnish speaker:
>>
>> <http://danielmiessler.com/blog/dont-ever-argue-again-about-the-pronunciation-of-linux>
>>
>>
>> How many english speakers pronounce Linux correctly? Linus' first
>> name? In what language? Do native chinese get it right? Is it really
>> worth spending time debating it? My name is pronounced differently in
>> english and in swedish, just like Linus' name is. I don't get upset
>> when people get it "wrong". Btw, it's pronounced Mii-ka-el in swedish
>> (where the ii is a long version of the initial sound in "industry").
>>
>> So while I read with interest the documents presented in the original
>> post in this thread, I don't expect to understand and remember all of
>> what's in them.
>>
>> Are these documents intended to be published as informational RFCs (it
>> says "intended status: informational")? Are we intending to have one
>> for each 'major' language in the world? Where is the cutoff for
>> 'major' status of a language?
>>
>> Should the IETF really publish documents about human languages that
>> doesn't really have anything to do with Internet Engineering?
>>


From denghui02@gmail.com  Thu Jul 11 04:57:43 2013
Return-Path: <denghui02@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71ABC21F9FCF for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 04:57:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.378
X-Spam-Level: 
X-Spam-Status: No, score=-102.378 tagged_above=-999 required=5 tests=[AWL=0.221, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2ExEeSUR9zaP for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 04:57:43 -0700 (PDT)
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 CD96C21F9F9B for <ietf@ietf.org>; Thu, 11 Jul 2013 04:57:42 -0700 (PDT)
Received: by mail-qa0-f43.google.com with SMTP id d13so7630464qak.9 for <ietf@ietf.org>; Thu, 11 Jul 2013 04:57:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=TIKsNOwoIE8cvom/SpdWiGIeVxcwmJCL1wXgMoMx9VU=; b=l6rTiZSF+jw3teLRKqb/elZU0dsEugDFL2n7YoCykiQ5TPCe6Tlk9BLJWQLJ2bn+pL tctmGj5ELZdvnbq6rI0dOeGs06FGk32HcCywzbO4hWIfIN9vLx+b/vn6uSvaMI76akiF mbTyKZ+OaGvodL/eGOLCu955fFtZs+ffpZ1THQuq5fMK2TeLUzj/Vyms1cP0SwgN7L5S SyhE4tAjryUCi720qg2avxTZkoU5YVQkPjdsLrX3u2f/5BjhhCWoe8E7c90Oxf1q/lEL iIZCSQLSqzAb8OLnxek6EnNu735h4W6BcvSzl7mNP1S0SiGuE02yQAdSfbdzfzBBmIt/ Wrug==
MIME-Version: 1.0
X-Received: by 10.224.172.198 with SMTP id m6mr32505725qaz.44.1373543862210; Thu, 11 Jul 2013 04:57:42 -0700 (PDT)
Received: by 10.49.16.42 with HTTP; Thu, 11 Jul 2013 04:57:42 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20130710170747.10088580@resistor.net>
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com> <6.2.5.6.2.20130710170747.10088580@resistor.net>
Date: Thu, 11 Jul 2013 19:57:42 +0800
Message-ID: <CANF0JMB2uz73tM88mpZXY71cqWDJ=7_L7_sKx=smTCpWEH-4vQ@mail.gmail.com>
Subject: Re: Regarding call Chinese names
From: Hui Deng <denghui02@gmail.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Content-Type: multipart/alternative; boundary=047d7b5d8c7ffdb25704e13b1912
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 11:57:43 -0000

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

Hi S. Moonesamy,

Thanks a lot, we will add that explaination you suggested in the next
version.

Best regards,

-Hui


2013/7/11 S Moonesamy <sm+ietf@elandsys.com>

> Hi Deng Hui,
>
> At 17:04 10-07-2013, Hui Deng wrote:
>
>> We submitted two drafts to help people here to correctly call chinese
>> people names:
>>
>> http://tools.ietf.org/html/**draft-deng-call-chinese-names-**00<http://tools.ietf.org/html/draft-deng-call-chinese-names-00>
>>
>>    http://tools.ietf.org/html/**draft-zcao-chinese-pronounce-**00<http://tools.ietf.org/html/draft-zcao-chinese-pronounce-00>
>>
>
> I would like to thank you and your co-author on taking the initiative to
> write the drafts.  I don't know whether I am western or not. :-)
>
> In Section 3 of draft-deng-call-chinese-names-**00:
>
>   'Two generic titles that have similar meanings to "Mr." and
>    "Ms./Mrs." are "Xian1sheng1" and "Nv3Shi4".'
>
>   "(1,2,3,4 in this section will be explained in next section)
>
> There are digits in two words in the above.  I suggest making the comment
> about the numbers clearer by mentioning that the digits are intentional and
> they are used to denote the tone.
>
> Regards,
> S. Moonesamy
>

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

<div dir=3D"ltr"><div>Hi S. Moonesamy,</div><div>=A0</div><div>Thanks a lot=
, we will add that explaination you suggested in the next version.</div><di=
v>=A0</div><div>Best regards,</div><div>=A0</div><div>-Hui</div></div><div =
class=3D"gmail_extra">
<br><br><div class=3D"gmail_quote">2013/7/11 S Moonesamy <span dir=3D"ltr">=
&lt;<a href=3D"mailto:sm+ietf@elandsys.com" target=3D"_blank">sm+ietf@eland=
sys.com</a>&gt;</span><br><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Deng Hui,<div class=3D"im"><br>
At 17:04 10-07-2013, Hui Deng wrote:<br>
<blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-=
color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class=
=3D"gmail_quote">
We submitted two drafts to help people here to correctly call chinese peopl=
e names:<br>
<br>
<a href=3D"http://tools.ietf.org/html/draft-deng-call-chinese-names-00" tar=
get=3D"_blank">http://tools.ietf.org/html/<u></u>draft-deng-call-chinese-na=
mes-<u></u>00</a><br>
<br>
=A0 =A0<a href=3D"http://tools.ietf.org/html/draft-zcao-chinese-pronounce-0=
0" target=3D"_blank">http://tools.ietf.org/html/<u></u>draft-zcao-chinese-p=
ronounce-<u></u>00</a><br>
</blockquote>
<br></div>
I would like to thank you and your co-author on taking the initiative to wr=
ite the drafts. =A0I don&#39;t know whether I am western or not. :-)<br>
<br>
In Section 3 of draft-deng-call-chinese-names-<u></u>00:<br>
<br>
=A0 &#39;Two generic titles that have similar meanings to &quot;Mr.&quot; a=
nd<br>
=A0 =A0&quot;Ms./Mrs.&quot; are &quot;Xian1sheng1&quot; and &quot;Nv3Shi4&q=
uot;.&#39;<br>
<br>
=A0 &quot;(1,2,3,4 in this section will be explained in next section)<br>
<br>
There are digits in two words in the above. =A0I suggest making the comment=
 about the numbers clearer by mentioning that the digits are intentional an=
d they are used to denote the tone.<br>
<br>
Regards,<br>
S. Moonesamy <br>
</blockquote></div><br></div>

--047d7b5d8c7ffdb25704e13b1912--

From denghui02@gmail.com  Thu Jul 11 04:58:40 2013
Return-Path: <denghui02@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6946B11E8110 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 04:58:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.452
X-Spam-Level: 
X-Spam-Status: No, score=-102.452 tagged_above=-999 required=5 tests=[AWL=0.147, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PAFxsGfOeYQB for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 04:58:40 -0700 (PDT)
Received: from mail-qe0-x233.google.com (mail-qe0-x233.google.com [IPv6:2607:f8b0:400d:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id BEED321F9F9B for <ietf@ietf.org>; Thu, 11 Jul 2013 04:58:39 -0700 (PDT)
Received: by mail-qe0-f51.google.com with SMTP id a11so4289006qen.24 for <ietf@ietf.org>; Thu, 11 Jul 2013 04:58:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=i21lIhUY/CGrHS2T70s0uK4dxttdImGD9913luneoGY=; b=J830c9yqBynKsZ7dqYupvQfu8dK2GwFdxKBn71UrerdImphzt/5HGosFqlhribn0wq B98aLePnXZIOZmMb4Mrq1VRpLE63oRhZ6aKG6XibX01FEGVwDjY9CGpZIHMnAEnrbUaC 2V/LI5ykS0oNUTt8Q60GHE6uEBGw2/vTszbIkU3ufQxx/5SA0HR4YLh64xdqinkO0pU8 CqZbMLux24JqbdiI15QXy5MRrbu8mloZ8qM8BJeZxwg1zIxRDm3NWxb/LSPX1GK41+ka 0eTJb0sGskN/Nh84gNgia49TUkE+DVOA7dhltuqc4aPAHmQ3e/LVJLHkwma2GIwUm8jm 7GEw==
MIME-Version: 1.0
X-Received: by 10.224.21.6 with SMTP id h6mr17961222qab.14.1373543919250; Thu, 11 Jul 2013 04:58:39 -0700 (PDT)
Received: by 10.49.16.42 with HTTP; Thu, 11 Jul 2013 04:58:39 -0700 (PDT)
In-Reply-To: <C9B5F12337F6F841B35C404CF0554ACB4B46B99B@szxeml546-mbx.china.huawei.com>
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com> <C9B5F12337F6F841B35C404CF0554ACB4B46B99B@szxeml546-mbx.china.huawei.com>
Date: Thu, 11 Jul 2013 19:58:39 +0800
Message-ID: <CANF0JMAyY4KNb2w=8H0VvWM3Ve25mYkJnEMn7eAPMuF4W+vhaQ@mail.gmail.com>
Subject: Re: Regarding call Chinese names
From: Hui Deng <denghui02@gmail.com>
To: "Will Liu (Shucheng)" <liushucheng@huawei.com>
Content-Type: multipart/alternative; boundary=001a11c294ca63f2c204e13b1dc7
Cc: Zhamin <zhamin@huawei.com>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 11:58:40 -0000

--001a11c294ca63f2c204e13b1dc7
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Good catch, thansk a lot

-Hui


2013/7/11 Will Liu (Shucheng) <liushucheng@huawei.com>

>  A typo in draft-deng-call-chinese-names-00: =93Jiao4shao4=94 should be =
=93
> Jiao4shou4=94.****
>
> ** **
>
> Cheers,****
>
> Shucheng LIU (Will)****
>
> ** **
>
> *From:* ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] *On Behalf
> Of *Hui Deng
> *Sent:* Thursday, July 11, 2013 8:05 AM
> *To:* IETF Discussion
> *Subject:* Regarding call Chinese names****
>
> ** **
>
> Hello all****
>
>  ****
>
> We submitted two drafts to help people here to correctly call chinese
> people names:****
>
> http://tools.ietf.org/html/draft-deng-call-chinese-names-00 ****
>
>    http://tools.ietf.org/html/draft-zcao-chinese-pronounce-00****
>
>  ****
>
> Feel free to let us know if you have any other issues?****
>
> Best regards,****
>
>  ****
>
> -Hui Deng****
>

--001a11c294ca63f2c204e13b1dc7
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Good catch, thansk a lot</div><div>=A0</div><div>-Hui=
</div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">2=
013/7/11 Will Liu (Shucheng) <span dir=3D"ltr">&lt;<a href=3D"mailto:liushu=
cheng@huawei.com" target=3D"_blank">liushucheng@huawei.com</a>&gt;</span><b=
r>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">





<div lang=3D"ZH-CN" vlink=3D"purple" link=3D"blue">
<div>
<p class=3D"MsoNormal"><span style=3D"color:rgb(0,0,64);font-size:10pt" lan=
g=3D"EN-US">A typo in draft-deng-call-chinese-names-00:
</span><span style=3D"color:rgb(0,0,64);font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;;font-size:10pt" lang=3D"EN-US">=93</span><span style=3D=
"color:rgb(0,0,64);font-size:10pt" lang=3D"EN-US">Jiao4shao4</span><span st=
yle=3D"color:rgb(0,0,64);font-family:&quot;Calibri&quot;,&quot;sans-serif&q=
uot;;font-size:10pt" lang=3D"EN-US">=94</span><span style=3D"color:rgb(0,0,=
64);font-size:10pt" lang=3D"EN-US">
 should be </span><span style=3D"color:rgb(0,0,64);font-family:&quot;Calibr=
i&quot;,&quot;sans-serif&quot;;font-size:10pt" lang=3D"EN-US">=93</span><sp=
an style=3D"color:rgb(0,0,64);font-size:10pt" lang=3D"EN-US">Jiao4shou4</sp=
an><span style=3D"color:rgb(0,0,64);font-family:&quot;Calibri&quot;,&quot;s=
ans-serif&quot;;font-size:10pt" lang=3D"EN-US">=94</span><span style=3D"col=
or:rgb(0,0,64);font-size:10pt" lang=3D"EN-US">.</span><span style=3D"color:=
rgb(31,73,125);font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;font-=
size:10.5pt" lang=3D"EN-US"><u></u><u></u></span></p>

<p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125);font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;;font-size:10.5pt" lang=3D"EN-US"><u>=
</u>=A0<u></u></span></p>
<p style=3D"text-align:justify;text-justify:inter-ideograph" class=3D"MsoNo=
rmal"><span style=3D"color:rgb(31,73,125);font-family:&quot;Calibri&quot;,&=
quot;sans-serif&quot;;font-size:10.5pt" lang=3D"EN-US">Cheers,<u></u><u></u=
></span></p>

<p style=3D"text-align:justify;text-justify:inter-ideograph" class=3D"MsoNo=
rmal"><span style=3D"color:rgb(31,73,125);font-family:&quot;Calibri&quot;,&=
quot;sans-serif&quot;;font-size:10.5pt" lang=3D"EN-US">Shucheng LIU (Will)<=
u></u><u></u></span></p>

<p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125);font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;;font-size:10.5pt" lang=3D"EN-US"><u>=
</u>=A0<u></u></span></p>
<div style=3D"border-width:medium medium medium 1.5pt;border-style:none non=
e none solid;border-color:currentColor currentColor currentColor blue;paddi=
ng:0cm 0cm 0cm 4pt">
<div>
<div style=3D"border-width:1pt medium medium;border-style:solid none none;b=
order-color:rgb(181,196,223) currentColor currentColor;padding:3pt 0cm 0cm"=
>
<p class=3D"MsoNormal"><b><span style=3D"font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;;font-size:10pt" lang=3D"EN-US">From:</span></b><span st=
yle=3D"font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;font-size:10pt=
" lang=3D"EN-US"> <a href=3D"mailto:ietf-bounces@ietf.org" target=3D"_blank=
">ietf-bounces@ietf.org</a> [mailto:<a href=3D"mailto:ietf-bounces@ietf.org=
" target=3D"_blank">ietf-bounces@ietf.org</a>]
<b>On Behalf Of </b>Hui Deng<br>
<b>Sent:</b> Thursday, July 11, 2013 8:05 AM<br>
<b>To:</b> IETF Discussion<br>
<b>Subject:</b> Regarding call Chinese names<u></u><u></u></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=A0<u></u></span></p>
<div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hello all<u></u><u></u></span><=
/p>
</div><div class=3D"im">
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=A0<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">We submitted two drafts to help=
 people here to correctly call chinese people names:<u></u><u></u></span></=
p>
</div>
</div><div>
<p style=3D"margin:0cm 0cm 0pt"><span lang=3D"EN-US"><a href=3D"http://tool=
s.ietf.org/html/draft-deng-call-chinese-names-00" target=3D"_blank"><span s=
tyle=3D"background:white;color:rgb(17,85,204);font-family:&quot;Arial&quot;=
,&quot;sans-serif&quot;;font-size:10pt">http://tools.ietf.org/html/draft-de=
ng-call-chinese-names-00</span></a></span><span style=3D"background:white;c=
olor:rgb(34,34,34);font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;fon=
t-size:10pt" lang=3D"EN-US">=A0</span><span lang=3D"EN-US"><u></u><u></u></=
span></p>

<p style=3D"margin:0cm 0cm 0pt"><span style=3D"background:white;color:rgb(3=
4,34,34);font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;font-size:10p=
t" lang=3D"EN-US">=A0 =A0</span><span lang=3D"EN-US"><a href=3D"http://tool=
s.ietf.org/html/draft-zcao-chinese-pronounce-00" target=3D"_blank"><span st=
yle=3D"background:white;color:rgb(17,85,204);font-family:&quot;Arial&quot;,=
&quot;sans-serif&quot;;font-size:10pt">http://tools.ietf.org/html/draft-zca=
o-chinese-pronounce-00</span></a><u></u><u></u></span></p>

<p style=3D"margin:0cm 0cm 0pt"><span lang=3D"EN-US">=A0<u></u><u></u></spa=
n></p>
<p style=3D"margin:0cm 0cm 0pt"><span lang=3D"EN-US">Feel free to let us kn=
ow if you have any other issues?<u></u><u></u></span></p>
<p style=3D"margin:0cm 0cm 0pt"><span lang=3D"EN-US">Best regards,<u></u><u=
></u></span></p>
<p style=3D"margin:0cm 0cm 0pt"><span lang=3D"EN-US">=A0<u></u><u></u></spa=
n></p>
<p style=3D"margin:0cm 0cm 0pt"><span lang=3D"EN-US">-Hui Deng<u></u><u></u=
></span></p>
</div>
</div>
</div>
</div>
</div>

</blockquote></div><br></div>

--001a11c294ca63f2c204e13b1dc7--

From denghui02@gmail.com  Thu Jul 11 05:14:49 2013
Return-Path: <denghui02@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C0A311E810A for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 05:14:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.489
X-Spam-Level: 
X-Spam-Status: No, score=-102.489 tagged_above=-999 required=5 tests=[AWL=0.111, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id brXHqKkh4wKo for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 05:14:47 -0700 (PDT)
Received: from mail-qa0-x231.google.com (mail-qa0-x231.google.com [IPv6:2607:f8b0:400d:c00::231]) by ietfa.amsl.com (Postfix) with ESMTP id 969E011E8100 for <ietf@ietf.org>; Thu, 11 Jul 2013 05:14:47 -0700 (PDT)
Received: by mail-qa0-f49.google.com with SMTP id hu16so4152872qab.15 for <ietf@ietf.org>; Thu, 11 Jul 2013 05:14:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=JHrhTmprBy3iIhL6y1Fl4ETDAttbVTDIIxotX/5Dusc=; b=QFOl8vHbpEGG4fuenn9qSi4/fmQHkXW3E6Sy1y/MAyuP2/A+cj7NRPYSZNE+FOGfFT ssYEFdcPzHpG4lRbnYFLZuQRG4uoI6WWuc4WAi2ar811KG9+BSOyEhvzs5Ti+swguxn+ hDkMovOpYH7rDZYEFgrYFoWY0cn+RTxMV/qbq22GTp3AN2D12s5Ai/mc8wyz3ihG947e OqgxwSfLQjOr/KeiaTu6wHCsP0SFS0KUrH/vTy7rJ1LREMVOwUUGYL5eUIWsV3Gi49aQ Vpn843RV0FlysD2gP0TlfzYMAVMsE44xMvMkoXIZHtj6oKrGct6oMfya1XhcSHgVDZWG IjSQ==
MIME-Version: 1.0
X-Received: by 10.224.115.79 with SMTP id h15mr32012776qaq.41.1373544886989; Thu, 11 Jul 2013 05:14:46 -0700 (PDT)
Received: by 10.49.16.42 with HTTP; Thu, 11 Jul 2013 05:14:46 -0700 (PDT)
In-Reply-To: <alpine.DEB.2.00.1307111201190.8891@uplift.swm.pp.se>
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com> <0B65E3C66FCF4F459F93A1A5767BB35A034AD02C@lhreml514-mbx> <alpine.DEB.2.00.1307111201190.8891@uplift.swm.pp.se>
Date: Thu, 11 Jul 2013 20:14:46 +0800
Message-ID: <CANF0JMAuRm2c+-L0SzD902vAt4gdsWqawVMt6=MLkkNkmza6RQ@mail.gmail.com>
Subject: Re: Regarding call Chinese names
From: Hui Deng <denghui02@gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Content-Type: multipart/alternative; boundary=047d7bdc78de1292f904e13b57e4
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 12:14:49 -0000

--047d7bdc78de1292f904e13b57e4
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi Mikael,

I will change informational to no-purpose, not require IETF to publish it.
what we do is just want to help people who would like to follow it.

I personally feel that this is maybe one of not easier part for western
people to do in today IETF.  and chinese's names sound maybe more diffcult
than other eastern languages.

Best regards,

-Hui



2013/7/11 Mikael Abrahamsson <swmike@swm.pp.se>

> On Thu, 11 Jul 2013, Zhongxin (Victor) wrote:
>
>  BRAVO, techies not speaking Chinese would no longer mispronounce =93Huaw=
ei=94
>> as the name of some U.S state.
>>
>
> I have asked Huawei staff how it's pronounced and I think I get it fairly
> right. People who hasn't, might get confused because when I use that
> pronounciation it's not the prevelant pronounciation. About your example,
> there are plenty of places in the US with french origins, and in US
> english, these are pronounced differently than in french. What's correct?
> Perhaps if Huawei would call itself Whow-wei in latin characters more
> people would get it right, if this is a really sensitive issue.
>
> Linux has similar issue, Linus Torvalds native language is swedish, but
> he's also a native finnish speaker:
>
> <http://danielmiessler.com/**blog/dont-ever-argue-again-**
> about-the-pronunciation-of-**linux<http://danielmiessler.com/blog/dont-ev=
er-argue-again-about-the-pronunciation-of-linux>
> >
>
> How many english speakers pronounce Linux correctly? Linus' first name? I=
n
> what language? Do native chinese get it right? Is it really worth spendin=
g
> time debating it? My name is pronounced differently in english and in
> swedish, just like Linus' name is. I don't get upset when people get it
> "wrong". Btw, it's pronounced Mii-ka-el in swedish (where the ii is a lon=
g
> version of the initial sound in "industry").
>
> So while I read with interest the documents presented in the original pos=
t
> in this thread, I don't expect to understand and remember all of what's i=
n
> them.
>
> Are these documents intended to be published as informational RFCs (it
> says "intended status: informational")? Are we intending to have one for
> each 'major' language in the world? Where is the cutoff for 'major' statu=
s
> of a language?
>
> Should the IETF really publish documents about human languages that
> doesn't really have anything to do with Internet Engineering?
>
> --
> Mikael Abrahamsson    email: swmike@swm.pp.se

--047d7bdc78de1292f904e13b57e4
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi Mikael,</div><div>=A0</div><div>I=A0will change in=
formational to no-purpose, not require IETF to publish it. what we do is ju=
st want to help people who would like to follow it.</div><div>=A0</div><div=
>I personally feel that this is maybe one of=A0not easier=A0part for wester=
n people to do in today=A0IETF.=A0 and chinese&#39;s names=A0sound maybe mo=
re diffcult than=A0other eastern=A0languages.</div>
<div>=A0</div><div>Best regards,</div><div>=A0</div><div>-Hui</div><div>=A0=
</div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">2=
013/7/11 Mikael Abrahamsson <span dir=3D"ltr">&lt;<a href=3D"mailto:swmike@=
swm.pp.se" target=3D"_blank">swmike@swm.pp.se</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 class=3D"im">On Thu, 11 Jul 2013, Zhong=
xin (Victor) wrote:<br>
<br>
<blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-=
color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class=
=3D"gmail_quote">
BRAVO, techies not speaking Chinese would no longer mispronounce =93Huawei=
=94 as the name of some U.S state.<br>
</blockquote>
<br></div>
I have asked Huawei staff how it&#39;s pronounced and I think I get it fair=
ly right. People who hasn&#39;t, might get confused because when I use that=
 pronounciation it&#39;s not the prevelant pronounciation. About your examp=
le, there are plenty of places in the US with french origins, and in US eng=
lish, these are pronounced differently than in french. What&#39;s correct? =
Perhaps if Huawei would call itself Whow-wei in latin characters more peopl=
e would get it right, if this is a really sensitive issue.<br>

<br>
Linux has similar issue, Linus Torvalds native language is swedish, but he&=
#39;s also a native finnish speaker:<br>
<br>
&lt;<a href=3D"http://danielmiessler.com/blog/dont-ever-argue-again-about-t=
he-pronunciation-of-linux" target=3D"_blank">http://danielmiessler.com/<u><=
/u>blog/dont-ever-argue-again-<u></u>about-the-pronunciation-of-<u></u>linu=
x</a>&gt;<br>

<br>
How many english speakers pronounce Linux correctly? Linus&#39; first name?=
 In what language? Do native chinese get it right? Is it really worth spend=
ing time debating it? My name is pronounced differently in english and in s=
wedish, just like Linus&#39; name is. I don&#39;t get upset when people get=
 it &quot;wrong&quot;. Btw, it&#39;s pronounced Mii-ka-el in swedish (where=
 the ii is a long version of the initial sound in &quot;industry&quot;).<br=
>

<br>
So while I read with interest the documents presented in the original post =
in this thread, I don&#39;t expect to understand and remember all of what&#=
39;s in them.<br>
<br>
Are these documents intended to be published as informational RFCs (it says=
 &quot;intended status: informational&quot;)? Are we intending to have one =
for each &#39;major&#39; language in the world? Where is the cutoff for &#3=
9;major&#39; status of a language?<br>

<br>
Should the IETF really publish documents about human languages that doesn&#=
39;t really have anything to do with Internet Engineering?<span class=3D"HO=
EnZb"><font color=3D"#888888"><br>
<br>
-- <br>
Mikael Abrahamsson =A0 =A0email: <a href=3D"mailto:swmike@swm.pp.se" target=
=3D"_blank">swmike@swm.pp.se</a></font></span></blockquote></div><br></div>

--047d7bdc78de1292f904e13b57e4--

From arturo.servin@gmail.com  Thu Jul 11 06:55:07 2013
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E91E611E8175 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 06:55:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OEStE+ooLcXT for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 06:55:06 -0700 (PDT)
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 403E411E8172 for <ietf@ietf.org>; Thu, 11 Jul 2013 06:55:06 -0700 (PDT)
Received: by mail-yh0-f41.google.com with SMTP id z20so3236244yhz.0 for <ietf@ietf.org>; Thu, 11 Jul 2013 06:55:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=BGuANaMuEwCmp/DYvEeq2kTe0bbIgQFJVU+JKVGBadQ=; b=d8MlpWGw5LCCK1RorZ0grDbVtxVVmNbU//G9G7+akZC6e01QyuNWJedQiZHLchJRND zy983n98KKF5dVqPpsE615UvoNNHvqIAfRlW9aEruYN6he9aMBq6gkZz8iwHoOMQw2rb xSepk2t3UgzxeqFebIHzTXqtzT9jnEjq2/KoqO4U4D7BZTvdls77l8rb2P84Rc2vcokM MAp0VAso7vJADDDNdz6lNqoclFolaEWD59exCZDPfnkaMrS9wRZET0qSz5whIrMAizDr 5qUrBymmLFbD7iGQH+D/D6LAKz8ktVOhrLuqdJ3R3N0IADdTSMtAfocQsUD6W+P+oFOC y3QA==
X-Received: by 10.236.117.175 with SMTP id j35mr20880568yhh.84.1373550904969;  Thu, 11 Jul 2013 06:55:04 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local ([2001:13c7:7001:7000:a867:6c39:d539:23d2]) by mx.google.com with ESMTPSA id o1sm60538007yho.2.2013.07.11.06.55.02 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 11 Jul 2013 06:55:03 -0700 (PDT)
Message-ID: <51DEB93B.7020004@gmail.com>
Date: Thu, 11 Jul 2013 10:55:07 -0300
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Regarding call Chinese names
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com> <6.2.5.6.2.20130710170747.10088580@resistor.net>
In-Reply-To: <6.2.5.6.2.20130710170747.10088580@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 13:55:07 -0000

    Great document, I really liked.

    Same as SM I would suggest change "western" for something else.

    And I would also suggest to move section 4 before explaining the
titles. I guess the reading would be much easier.

Regards,
as

On 7/10/13 9:55 PM, S Moonesamy wrote:
> Hi Deng Hui,
> At 17:04 10-07-2013, Hui Deng wrote:
>> We submitted two drafts to help people here to correctly call chinese
>> people names:
>>
>> http://tools.ietf.org/html/draft-deng-call-chinese-names-00
>>
>>    http://tools.ietf.org/html/draft-zcao-chinese-pronounce-00
>
> I would like to thank you and your co-author on taking the initiative
> to write the drafts.  I don't know whether I am western or not. :-)
>
> In Section 3 of draft-deng-call-chinese-names-00:
>
>   'Two generic titles that have similar meanings to "Mr." and
>    "Ms./Mrs." are "Xian1sheng1" and "Nv3Shi4".'
>
>   "(1,2,3,4 in this section will be explained in next section)
>
> There are digits in two words in the above.  I suggest making the
> comment about the numbers clearer by mentioning that the digits are
> intentional and they are used to denote the tone.
>
> Regards,
> S. Moonesamy 


From simon.perreault@viagenie.ca  Thu Jul 11 06:58:13 2013
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69BE811E817F for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 06:58:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.477
X-Spam-Level: 
X-Spam-Status: No, score=-2.477 tagged_above=-999 required=5 tests=[AWL=0.123,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yrRh1HV9PgmD for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 06:58:13 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id EDDCC11E817E for <ietf@ietf.org>; Thu, 11 Jul 2013 06:58:12 -0700 (PDT)
Received: from [IPv6:::1] (unknown [IPv6:2001:660:3001:4012:5b8:1f9e:c21b:48d7]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 42E3D40405 for <ietf@ietf.org>; Thu, 11 Jul 2013 09:58:12 -0400 (EDT)
Message-ID: <51DEB9F2.9040405@viagenie.ca>
Date: Thu, 11 Jul 2013 15:58:10 +0200
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Regarding call Chinese names
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com>
In-Reply-To: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 13:58:13 -0000

Le 2013-07-11 02:04, Hui Deng a écrit :
> We submitted two drafts to help people here to correctly call chinese
> people names:
> 
> http://tools.ietf.org/html/draft-deng-call-chinese-names-00 
>    http://tools.ietf.org/html/draft-zcao-chinese-pronounce-00

Very cool! Thanks for writing this!

I have a question: I think I've seen Chinese names written in both
orders. That is, sometimes "Hui Deng" will be written "Deng Hui". Am I
right? Does this happen often? What is the most common order? Is there a
way to guess what order a name is written in? Sometimes it's not easy
for non-Sinophones to know which part is the given name and which part
is the family name.

Thanks,
Simon

From arturo.servin@gmail.com  Thu Jul 11 07:03:48 2013
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3C8211E812B for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 07:03:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lo19LBzkwVt9 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 07:03:47 -0700 (PDT)
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 3665311E8115 for <ietf@ietf.org>; Thu, 11 Jul 2013 07:03:47 -0700 (PDT)
Received: by mail-qa0-f51.google.com with SMTP id f11so4195163qae.17 for <ietf@ietf.org>; Thu, 11 Jul 2013 07:03:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=koKFTAqpiMJkH5RpGsgxkCuLiN2W1NgeT7XilOkmQd8=; b=Jo4KaTDJSF8ftwsPoI7SQ/qSdZN81oOD65D5ZMz970Jk/3V6Yf/HKgjUT7pEQQToL0 z+R+ROklziDGvkOyqXuMyNb+6I+jwUwHZhj9tu2yRmDzZlaqCf/4W4NfFM/HeHrpf895 Y9mmQT/+EeBSL4VL2N8CGUK1NlaKSF0sGG6babuS0ubcHrMCH/fa6yqDAFufWvEQfR9k L6/vHMvXq1DrnJj1MAJTrq3cX824sJsk+150ZtDJbQbqb9IIVUtYftDYDsQwa2tjrWqJ ADl1NfxWO7JTcjD1k7R1pAPKDW/c0ssHNO3ysXKLO1mDE54/qwRWOaJZiicPwdM1AO9A 5nUA==
X-Received: by 10.224.115.5 with SMTP id g5mr33127114qaq.53.1373551426637; Thu, 11 Jul 2013 07:03:46 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local ([2001:13c7:7001:7000:a867:6c39:d539:23d2]) by mx.google.com with ESMTPSA id ff5sm28703758qeb.6.2013.07.11.07.03.44 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 11 Jul 2013 07:03:45 -0700 (PDT)
Message-ID: <51DEBB45.6080308@gmail.com>
Date: Thu, 11 Jul 2013 11:03:49 -0300
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Simon Perreault <simon.perreault@viagenie.ca>
Subject: Re: Regarding call Chinese names
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com> <51DEB9F2.9040405@viagenie.ca>
In-Reply-To: <51DEB9F2.9040405@viagenie.ca>
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 14:03:48 -0000

On 7/11/13 10:58 AM, Simon Perreault wrote:
> I have a question: I think I've seen Chinese names written in both
> orders. That is, sometimes "Hui Deng" will be written "Deng Hui". Am I
> right? Does this happen often? What is the most common order? Is there a
> way to guess what order a name is written in? Sometimes it's not easy
> for non-Sinophones to know which part is the given name and which part
> is the family name.
Same question.

It would be good to add something about this in the draft.

Again, great doc.

Cheers,
as

From Ted.Lemon@nominum.com  Thu Jul 11 07:16:12 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7245211E8189 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 07:16:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vL1rhU1+LiIn for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 07:16:03 -0700 (PDT)
Received: from exprod7og103.obsmtp.com (exprod7og103.obsmtp.com [64.18.2.159]) by ietfa.amsl.com (Postfix) with ESMTP id 47D7B21F9A6D for <ietf@ietf.org>; Thu, 11 Jul 2013 07:16:03 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob103.postini.com ([64.18.6.12]) with SMTP ID DSNKUd6+HWtJjQE8UZuh1k3Wm/s3CFn520jR@postini.com; Thu, 11 Jul 2013 07:16:03 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 82EF31B821B for <ietf@ietf.org>; Thu, 11 Jul 2013 07:15:57 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 3647E190052; Thu, 11 Jul 2013 07:15:56 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Thu, 11 Jul 2013 07:15:56 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Hui Deng <denghui02@gmail.com>
Subject: Re: Regarding call Chinese names
Thread-Topic: Regarding call Chinese names
Thread-Index: AQHOfcpDSTits9fmh0mJ3UeAESXzVplfscgAgAAJ4ICAAB6SAIAAIdkA
Date: Thu, 11 Jul 2013 14:15:54 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077520A892@mbx-01.win.nominum.com>
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com> <0B65E3C66FCF4F459F93A1A5767BB35A034AD02C@lhreml514-mbx> <alpine.DEB.2.00.1307111201190.8891@uplift.swm.pp.se> <CANF0JMAuRm2c+-L0SzD902vAt4gdsWqawVMt6=MLkkNkmza6RQ@mail.gmail.com>
In-Reply-To: <CANF0JMAuRm2c+-L0SzD902vAt4gdsWqawVMt6=MLkkNkmza6RQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <E2655A3E72544E4EA3A429D6936CF4D2@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 14:16:12 -0000

On Jul 11, 2013, at 8:14 AM, Hui Deng <denghui02@gmail.com> wrote:
> I personally feel that this is maybe one of not easier part for western p=
eople to do in today IETF.  and chinese's names sound maybe more diffcult t=
han other eastern languages.

I think these documents are useful for IETFers who care, and possibly for o=
thers.   Pinyin transliteration is not safely pronounceable without help.  =
 It's true that many European languages are hard for speakers of other lang=
uages to pronounce also, and I would not personally object to more helpful =
documents of this type for other languages.   I think that what would motiv=
ate this would be author interest=97that's what we usually let drive volunt=
eer translations of IETF messages into other languages, for example.   E.g.=
, there are numerous translations for the Tao; these are done on a voluntee=
r basis, so if you don't see one for your language, and this bothers you, t=
he onus is on you to solve it.



From hartmans@mit.edu  Thu Jul 11 07:16:30 2013
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6DA811E8191 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 07:16:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.566
X-Spam-Level: 
X-Spam-Status: No, score=-102.566 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oPUPijiOuFkz for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 07:16:25 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 5683111E8194 for <ietf@ietf.org>; Thu, 11 Jul 2013 07:16:23 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id D812820134; Thu, 11 Jul 2013 10:11:35 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wdir4rRn4zZe; Thu, 11 Jul 2013 10:11:35 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (c-98-216-0-82.hsd1.ma.comcast.net [98.216.0.82]) (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; Thu, 11 Jul 2013 10:11:35 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 6BA1188435; Thu, 11 Jul 2013 10:15:35 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Arturo Servin <arturo.servin@gmail.com>
Subject: Re: Regarding call Chinese names
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com> <6.2.5.6.2.20130710170747.10088580@resistor.net> <51DEB93B.7020004@gmail.com>
Date: Thu, 11 Jul 2013 10:15:35 -0400
In-Reply-To: <51DEB93B.7020004@gmail.com> (Arturo Servin's message of "Thu, 11 Jul 2013 10:55:07 -0300")
Message-ID: <tsltxk1rxmg.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
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 14:16:31 -0000

Hi.
As I mentioned in  private mail, I think these are really great
documents and will work on learning the advice contained in them.

I hope we will all strive to pronounce names of contributors and their
companies as they would wish us to pronounce them.

I was wondering if call-chinese-names could contain some advice on
mailing lists and IM discussions.
In this message should I say that  Hui Deng wrote a great draft, or Deng
Hui?

When reading the from line of a message what should I do to try and
figure out which name is the given name or the family name?  The note
that family names are generally one character was very helpful in this regard.

From cyrus@daboo.name  Thu Jul 11 07:22:27 2013
Return-Path: <cyrus@daboo.name>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A38E421F9D91 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 07:22:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 256UTTo9umMD for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 07:22:22 -0700 (PDT)
Received: from daboo.name (daboo.name [173.13.55.49]) by ietfa.amsl.com (Postfix) with ESMTP id 4518011E8166 for <ietf@ietf.org>; Thu, 11 Jul 2013 07:22:21 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id D004746FB756; Thu, 11 Jul 2013 10:22:20 -0400 (EDT)
X-Virus-Scanned: amavisd-new at example.com
Received: from daboo.name ([127.0.0.1]) by localhost (daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aaJae_0SvqNI; Thu, 11 Jul 2013 10:22:20 -0400 (EDT)
Received: from caldav.corp.apple.com (unknown [17.45.162.46]) by daboo.name (Postfix) with ESMTPSA id 3084246FB74B; Thu, 11 Jul 2013 10:22:18 -0400 (EDT)
Date: Thu, 11 Jul 2013 10:22:15 -0400
From: Cyrus Daboo <cyrus@daboo.name>
To: Simon Perreault <simon.perreault@viagenie.ca>, ietf@ietf.org
Subject: Re: Regarding call Chinese names
Message-ID: <F108A063F7E85E5F9C89ADBF@caldav.corp.apple.com>
In-Reply-To: <51DEB9F2.9040405@viagenie.ca>
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com> <51DEB9F2.9040405@viagenie.ca>
X-Mailer: Mulberry/4.1.0a3 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size=1630
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 14:22:27 -0000

Hi Simon,

--On July 11, 2013 at 3:58:10 PM +0200 Simon Perreault 
<simon.perreault@viagenie.ca> wrote:

>> We submitted two drafts to help people here to correctly call chinese
>> people names:
>>
>> http://tools.ietf.org/html/draft-deng-call-chinese-names-00
>>    http://tools.ietf.org/html/draft-zcao-chinese-pronounce-00
>
> Very cool! Thanks for writing this!
>
> I have a question: I think I've seen Chinese names written in both
> orders. That is, sometimes "Hui Deng" will be written "Deng Hui". Am I
> right? Does this happen often? What is the most common order? Is there a
> way to guess what order a name is written in? Sometimes it's not easy
> for non-Sinophones to know which part is the given name and which part
> is the family name.

Well that actually brings up a good technical point!

In iCalendar (RFC5545) we have properties to represent the organizer and 
attendee of meetings. A parameter (attribute) of those properties is "CN" - 
defined to be the "common name" of the corresponding calendar user. 
Obviously that is a single string and typically the concatenation of first 
name/last name. But that of course is a very "Western" approach.

I have had several people request that iCalendar instead define new 
parameters for "FIRST-NAME" and "LAST-NAME". That then gives clients the 
option of re-ordering those for display purposes based on user locales and 
preferences.

So, from a technical standpoint, it seems better to always represent user 
names using components (last, first, middle)? vCard does have an "N" 
property where individual components of a name can be broken out.

-- 
Cyrus Daboo


From simon.perreault@viagenie.ca  Thu Jul 11 07:28:06 2013
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BA0511E8175 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 07:28:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level: 
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[AWL=0.114,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p93BUiZe5RgB for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 07:28:05 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id D8EF911E816E for <ietf@ietf.org>; Thu, 11 Jul 2013 07:28:05 -0700 (PDT)
Received: from [IPv6:::1] (unknown [IPv6:2001:660:3001:4012:5b8:1f9e:c21b:48d7]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 2A35B403E7; Thu, 11 Jul 2013 10:28:05 -0400 (EDT)
Message-ID: <51DEC0F5.3010406@viagenie.ca>
Date: Thu, 11 Jul 2013 16:28:05 +0200
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Cyrus Daboo <cyrus@daboo.name>
Subject: Re: Regarding call Chinese names
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com> <51DEB9F2.9040405@viagenie.ca> <F108A063F7E85E5F9C89ADBF@caldav.corp.apple.com>
In-Reply-To: <F108A063F7E85E5F9C89ADBF@caldav.corp.apple.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 14:28:06 -0000

Le 2013-07-11 16:22, Cyrus Daboo a 閏rit :
> So, from a technical standpoint, it seems better to always represent
> user names using components (last, first, middle)? vCard does have an
> "N" property where individual components of a name can be broken out.

I'm nowhere near an expert on this topic, but I distinctly remember
during the vCard 4 effort some participants saying that some cultures
just don't separate names into parts. In those cultures, you would just
have *a name*. Like an opaque, atomic blob I guess.

Simon

From stephen.farrell@cs.tcd.ie  Thu Jul 11 07:34:10 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F4D211E81B8 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 07:34:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.46
X-Spam-Level: 
X-Spam-Status: No, score=-102.46 tagged_above=-999 required=5 tests=[AWL=0.140, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z7MVaMh+2y11 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 07:34:04 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id A69DE11E8192 for <ietf@ietf.org>; Thu, 11 Jul 2013 07:34:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 975C8BE74; Thu, 11 Jul 2013 15:33:36 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 62HVPHwnoJxk; Thu, 11 Jul 2013 15:33:35 +0100 (IST)
Received: from [10.87.48.9] (unknown [86.42.17.76]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 71CD5BE6E; Thu, 11 Jul 2013 15:33:35 +0100 (IST)
Message-ID: <51DEC235.2040905@cs.tcd.ie>
Date: Thu, 11 Jul 2013 15:33:25 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: Cyrus Daboo <cyrus@daboo.name>
Subject: Re: Regarding call Chinese names
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com> <51DEB9F2.9040405@viagenie.ca> <F108A063F7E85E5F9C89ADBF@caldav.corp.apple.com>
In-Reply-To: <F108A063F7E85E5F9C89ADBF@caldav.corp.apple.com>
X-Enigmail-Version: 1.5.1
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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 14:34:10 -0000

On 07/11/2013 03:22 PM, Cyrus Daboo wrote:
> 
> In iCalendar (RFC5545) we have properties to represent the organizer and
> attendee of meetings. A parameter (attribute) of those properties is
> "CN" - defined to be the "common name" of the corresponding calendar
> user. Obviously that is a single string and typically the concatenation
> of first name/last name. But that of course is a very "Western" approach.
> 
> I have had several people request that iCalendar instead define new
> parameters for "FIRST-NAME" and "LAST-NAME". That then gives clients the
> option of re-ordering those for display purposes based on user locales
> and preferences.

I guess that's inherited from X.500 via ldap. But CN is just one X.500
name attribute and there were others for firstname, lastname etc. (So
it wasn't at all a 'western' approach, at least if you go by mid-1980's
standards;-) Anyway, no harm adding those to iCalendar or whatever, but
be good to try be compatible(ish) with ldap and the ever-creaky X.500;-)

There's some stuff in rfc5280 related to that but I'd have to go
looking to see what'd be the best thing to which to refer.

I'd expect the scim WG to also have (maybe) other options that you
could build from too. Not sure of details there.

S.

From hallam@gmail.com  Thu Jul 11 07:34:15 2013
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C622B11E81BC for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 07:34:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.289
X-Spam-Level: 
X-Spam-Status: No, score=-2.289 tagged_above=-999 required=5 tests=[AWL=0.310,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cFkw-VSBOvBd for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 07:34:15 -0700 (PDT)
Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) by ietfa.amsl.com (Postfix) with ESMTP id C979611E81BA for <ietf@ietf.org>; Thu, 11 Jul 2013 07:34:14 -0700 (PDT)
Received: by mail-wi0-f170.google.com with SMTP id ey16so13717871wid.5 for <ietf@ietf.org>; Thu, 11 Jul 2013 07:34:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=S63qSn6yD4U2Xt/Zm4aSaxPJGiqazPnpngA0yExE14E=; b=gOSsJrlM9bFMShrpt2EXN4j5Zbzo8VlSyhPczBKmDh4llbi27u5994lon1D7zDHhZc QWtE8VA4uB13FjRIXnzxTyd8P3lm97HYGUbCfvB7j8w5SDm6vcqGCUZXd6x4VzfVeknW LXpF33/VIuZLquA7DjWRDHZEcwzB7Pq6G2++DyxcLHeXgvnXll6bP1xwGwpwB6iUZcaE fKizJUEBHdBHbfbk8n+Wk9CEAIw8+5EKfurKnKiiVE5195KYZKvOauvraSeSaYdnMJOb 3Tqc3zYod9wchcwz5i7dQhOjwPIj9YFJ1ptyAidAt3xzFFrCwlRj1TU9cdepVqNHU+LF xGoQ==
MIME-Version: 1.0
X-Received: by 10.194.242.134 with SMTP id wq6mr20818126wjc.94.1373553253894;  Thu, 11 Jul 2013 07:34:13 -0700 (PDT)
Received: by 10.194.6.65 with HTTP; Thu, 11 Jul 2013 07:34:13 -0700 (PDT)
In-Reply-To: <C053B4F4-4821-4132-B872-3F8A611B2F5F@unina.it>
References: <CE0388EA.21B7F%Josh.Howlett@ja.net> <803FCD9A-6B8A-45EC-914F-E2114C581EA1@gmail.com> <C053B4F4-4821-4132-B872-3F8A611B2F5F@unina.it>
Date: Thu, 11 Jul 2013 10:34:13 -0400
Message-ID: <CAMm+Lwjpw6uodpZHuQ-rW4hJ7ViUHqrFBwTJYGkXCtH1c2x1ww@mail.gmail.com>
Subject: Re: IETF registration fee?
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Simon Pietro Romano <spromano@unina.it>
Content-Type: multipart/alternative; boundary=089e0141a1fcc7511604e13d49cc
Cc: Keith Moore <moore@network-heretics.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 14:34:16 -0000

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

There are several interlocking issues with the day passes and cross area
participation.

One issue is the fact that the IETF chose a business model in which profits
from the conferences fund the organization and the IETF has no ability to
reconsider or change decisions of that sort. I can see that as being an
existential threat to the IETF in a decade or two since the demand for
(unpaid) external participation is going to grow and the technologies for
supporting external participation will eventually not suck.

Using paid conferences as a profit center is a risky long term prospect at
best. Refusing to adapt the format of the conferences to protect the profit
center worse. And in the case of the IETF the whole purpose of the
organization is to develop the technologies that are undermining the paid
conference model. We are sawing the board we are standing on.


Cross area participation is a good thing but the way the IETF supports this
is terrible. I won't be coming to Berlin because there is only one WG that
I have a reason to attend in person and it is not worth making the flight
for a two hour meeting, much of which is summaries.

I much prefer the OASIS or W3C model for plenary meetings where my WG
session will be doing one or two solid days of design work and the plenary
sessions are on the Wednesday and consist of a series of presentations
designed to inform people about the work going on in each area.

Sitting in watching other WGs is not a good way to find out what is going
on. Area meetings are more useful.

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

<div dir=3D"ltr">There are several interlocking issues with the day passes =
and cross area participation.=A0<div><br></div><div>One issue is the fact t=
hat the IETF chose a business model in which profits from the conferences f=
und the organization and the IETF has no ability to reconsider or change de=
cisions of that sort. I can see that as being an existential threat to the =
IETF in a decade or two since the demand for (unpaid) external participatio=
n is going to grow and the technologies for supporting external participati=
on will eventually not suck.</div>
<div><br></div><div style>Using paid conferences as a profit center is a ri=
sky long term prospect at best. Refusing to adapt the format of the confere=
nces to protect the profit center worse. And in the case of the IETF the wh=
ole purpose of the organization is to develop the technologies that are und=
ermining the paid conference model. We are sawing the board we are standing=
 on.</div>
<div style><br></div><div><br></div><div style>Cross area participation is =
a good thing but the way the IETF supports this is terrible. I won&#39;t be=
 coming to Berlin because there is only one WG that I have a reason to atte=
nd in person and it is not worth making the flight for a two hour meeting, =
much of which is summaries.</div>
<div style><br></div><div style>I much prefer the OASIS or W3C model for pl=
enary meetings where my WG session will be doing one or two solid days of d=
esign work and the plenary sessions are on the Wednesday and consist of a s=
eries of presentations designed to inform people about the work going on in=
 each area.</div>
<div style><br></div><div style>Sitting in watching other WGs is not a good=
 way to find out what is going on. Area meetings are more useful.=A0</div><=
div><br></div></div>

--089e0141a1fcc7511604e13d49cc--

From cyrus@daboo.name  Thu Jul 11 07:34:46 2013
Return-Path: <cyrus@daboo.name>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62D3F11E81BA for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 07:34:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FM-A3pq4Auj6 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 07:34:40 -0700 (PDT)
Received: from daboo.name (daboo.name [173.13.55.49]) by ietfa.amsl.com (Postfix) with ESMTP id 0364211E812B for <ietf@ietf.org>; Thu, 11 Jul 2013 07:34:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 9F65346FB967; Thu, 11 Jul 2013 10:34:37 -0400 (EDT)
X-Virus-Scanned: amavisd-new at example.com
Received: from daboo.name ([127.0.0.1]) by localhost (daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tisyIZw2tkfF; Thu, 11 Jul 2013 10:34:37 -0400 (EDT)
Received: from caldav.corp.apple.com (unknown [17.45.162.46]) by daboo.name (Postfix) with ESMTPSA id 3B52C46FB95A; Thu, 11 Jul 2013 10:34:36 -0400 (EDT)
Date: Thu, 11 Jul 2013 10:34:33 -0400
From: Cyrus Daboo <cyrus@daboo.name>
To: Simon Perreault <simon.perreault@viagenie.ca>
Subject: Re: Regarding call Chinese names
Message-ID: <5AD0581898082CED236D82B0@caldav.corp.apple.com>
In-Reply-To: <51DEC0F5.3010406@viagenie.ca>
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com> <51DEB9F2.9040405@viagenie.ca> <F108A063F7E85E5F9C89ADBF@caldav.corp.apple.com> <51DEC0F5.3010406@viagenie.ca>
X-Mailer: Mulberry/4.1.0a3 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size=947
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 14:34:46 -0000

Hi Simon,

--On July 11, 2013 at 4:28:05 PM +0200 Simon Perreault 
<simon.perreault@viagenie.ca> wrote:

>> So, from a technical standpoint, it seems better to always represent
>> user names using components (last, first, middle)? vCard does have an
>> "N" property where individual components of a name can be broken out.
>
> I'm nowhere near an expert on this topic, but I distinctly remember
> during the vCard 4 effort some participants saying that some cultures
> just don't separate names into parts. In those cultures, you would just
> have *a name*. Like an opaque, atomic blob I guess.

True. And in the iCalendar world attendees can also be non-human entities 
like rooms or resources, which typically do not have separate components 
for their names (e.g., "Conference Room 1", "HD Projector", etc). But that 
case can be handled by simply specifying the full name in the "LAST-NAME" 
field and leave the others blank.

-- 
Cyrus Daboo


From Ted.Lemon@nominum.com  Thu Jul 11 07:38:31 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0038C11E81A4 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 07:38:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.722
X-Spam-Level: 
X-Spam-Status: No, score=-105.722 tagged_above=-999 required=5 tests=[AWL=-0.877, BAYES_00=-2.599, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G6APuwSCwBBI for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 07:38:24 -0700 (PDT)
Received: from exprod7og118.obsmtp.com (exprod7og118.obsmtp.com [64.18.2.8]) by ietfa.amsl.com (Postfix) with ESMTP id 4D49311E8189 for <ietf@ietf.org>; Thu, 11 Jul 2013 07:38:24 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob118.postini.com ([64.18.6.12]) with SMTP ID DSNKUd7DX3Rmr8v7prApcdgLDpGYLMn+Eorv@postini.com; Thu, 11 Jul 2013 07:38:24 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id BCE001B81CF for <ietf@ietf.org>; Thu, 11 Jul 2013 07:38:23 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id B56FD190052; Thu, 11 Jul 2013 07:38:23 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Thu, 11 Jul 2013 07:38:23 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Simon Perreault <simon.perreault@viagenie.ca>
Subject: Re: Regarding call Chinese names
Thread-Topic: Regarding call Chinese names
Thread-Index: AQHOfcpDSTits9fmh0mJ3UeAESXzVplf9x4AgAALPAA=
Date: Thu, 11 Jul 2013 14:38:23 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077520AAD3@mbx-01.win.nominum.com>
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com> <51DEB9F2.9040405@viagenie.ca>
In-Reply-To: <51DEB9F2.9040405@viagenie.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="gb2312"
Content-ID: <0546B06ADA4E954C87EE7310C03B6C36@nominum.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 14:38:31 -0000

T24gSnVsIDExLCAyMDEzLCBhdCA5OjU4IEFNLCBTaW1vbiBQZXJyZWF1bHQgPHNpbW9uLnBlcnJl
YXVsdEB2aWFnZW5pZS5jYT4gd3JvdGU6DQo+IElzIHRoZXJlIGENCj4gd2F5IHRvIGd1ZXNzIHdo
YXQgb3JkZXIgYSBuYW1lIGlzIHdyaXR0ZW4gaW4/IFNvbWV0aW1lcyBpdCdzIG5vdCBlYXN5DQo+
IGZvciBub24tU2lub3Bob25lcyB0byBrbm93IHdoaWNoIHBhcnQgaXMgdGhlIGdpdmVuIG5hbWUg
YW5kIHdoaWNoIHBhcnQNCj4gaXMgdGhlIGZhbWlseSBuYW1lLg0KDQpJdCdzIHVzdWFsbHkgaW4g
dGhlIENoaW5lc2Ugb3JkZXIgaW4gdGhlIGVtYWlsIGFkZHJlc3MuDQoNCg==

From john-ietf@jck.com  Thu Jul 11 08:17:22 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E173C21F9B03 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 08:17:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.578
X-Spam-Level: 
X-Spam-Status: No, score=-102.578 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yNzmyU7eq8Uo for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 08:17:17 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 12D0B21F9AE2 for <ietf@ietf.org>; Thu, 11 Jul 2013 08:17:16 -0700 (PDT)
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 1UxIcF-0001XY-GF; Thu, 11 Jul 2013 11:17:07 -0400
Date: Thu, 11 Jul 2013 11:17:02 -0400
From: John C Klensin <john-ietf@jck.com>
To: Phillip Hallam-Baker <hallam@gmail.com>, Simon Pietro Romano <spromano@unina.it>
Subject: Re: IETF registration fee?
Message-ID: <C66F2B4BC73DB85224494CB1@JcK-HP8200.jck.com>
In-Reply-To: <CAMm+Lwjpw6uodpZHuQ-rW4hJ7ViUHqrFBwTJYGkXCtH1c2x1ww@mail.gmail.com>
References: <CE0388EA.21B7F%Josh.Howlett@ja.net> <803FCD9A-6B8A-45EC-914F-E2114C581EA1@gmail.com> <C053B4F4-4821-4132-B872-3F8A611B2F5F@unina.it> <CAMm+Lwjpw6uodpZHuQ-rW4hJ7ViUHqrFBwTJYGkXCtH1c2x1ww@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: Keith Moore <moore@network-heretics.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 15:17:23 -0000

--On Thursday, July 11, 2013 10:34 -0400 Phillip Hallam-Baker
<hallam@gmail.com> wrote:

>...
> Using paid conferences as a profit center is a risky long term
> prospect at best. Refusing to adapt the format of the
> conferences to protect the profit center worse. 

Or adapting the format to attract more paying attendees, such a
what we have sometimes called "tourists", with no real
expectation that they will do work, because it increases the
income.

Still better than building a funding structure based on sale of
publications, however :-(

   john





From stephen@sprunk.org  Thu Jul 11 08:23:34 2013
Return-Path: <stephen@sprunk.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 653C321F9C8D for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 08:23:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.109
X-Spam-Level: 
X-Spam-Status: No, score=-1.109 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LfzY2kE3BwHw for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 08:23:27 -0700 (PDT)
Received: from nm10-vm7.access.bullet.mail.gq1.yahoo.com (nm10-vm7.access.bullet.mail.gq1.yahoo.com [216.39.63.188]) by ietfa.amsl.com (Postfix) with ESMTP id B2D6721F9CE1 for <ietf@ietf.org>; Thu, 11 Jul 2013 08:23:22 -0700 (PDT)
Received: from [216.39.60.174] by nm10.access.bullet.mail.gq1.yahoo.com with NNFMP; 11 Jul 2013 15:23:21 -0000
Received: from [98.138.226.243] by tm10.access.bullet.mail.gq1.yahoo.com with NNFMP; 11 Jul 2013 15:23:21 -0000
Received: from [127.0.0.1] by smtp114.sbc.mail.ne1.yahoo.com with NNFMP; 11 Jul 2013 15:23:21 -0000
X-Yahoo-Newman-Id: 239247.42950.bm@smtp114.sbc.mail.ne1.yahoo.com
X-Yahoo-Newman-Property: ymail-3
X-YMail-OSG: MFzIE0MVM1lnILQaIgryTGhFlEpvaKhwRiSPey8ydb904uE BK5p8uDiq23FZJmdoj_GK9X0lHGupnKtCqwtEo8ClHncIi8lYFZQnstJEJ3o AtsAzEGBKFkXWxqpeGDdOfDGBwLjHiScSNIvtIBR9QGjnvJ7rUkRLtC28zGk fQ0STR8JgKQs0H.vAV0nUCi4TPX_pbIteq0ZRqQpkhWIz3_8kvgvLsI_HC4k fa5tnVXJ5wZ3Xlvp6PYzSKYPMqabnsfl63SRDTOJgW3ksj5dAqrZMC2Ilhd_ EZzkis4tGV3e0YoT0CoU5sPDx.fnRfxVto1Z4168ibh8UrUzhJ6Tdf1DX9iv 6MluxyIu1jKv8644Q5nbHWCtQyzvyETY7k6VimEb7cYLLm9TqLjTEGb2pL35 N52HNAxG3phnKZIN1EDZpRQXNPXQ.gB1TiTvaWeTqnzpDSYYD5_y74VERMEx mU_R5N1.g3fCvCX9UjhhOLwq.zQKE_vpVUb1J3ypHu3d1UJGJQbxOgbX.rh5 SHl8Y6.noeVFvSh77Qrk5uaj2KvSzbLJkSWnav08BAc4PC2g-
X-Yahoo-SMTP: EYvcGKyswBB8plhV5pc8yMz3blwA5zta_j4l
X-Rocket-Received: from [192.168.1.67] (stephen@99.136.80.184 with plain) by smtp114.sbc.mail.ne1.yahoo.com with SMTP; 11 Jul 2013 08:23:21 -0700 PDT
Message-ID: <51DECDE8.4080405@sprunk.org>
Date: Thu, 11 Jul 2013 10:23:20 -0500
From: Stephen Sprunk <stephen@sprunk.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:10.0) Gecko/20120206 Thunderbird/10.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Regarding call Chinese names
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com> <51DEB9F2.9040405@viagenie.ca>
In-Reply-To: <51DEB9F2.9040405@viagenie.ca>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms040305010507030001030102"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 15:23:34 -0000

This is a cryptographically signed message in MIME format.

--------------ms040305010507030001030102
Content-Type: multipart/alternative;
 boundary="------------060005030704050009010908"

This is a multi-part message in MIME format.
--------------060005030704050009010908
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 11-Jul-13 08:58, Simon Perreault wrote:
> I have a question: I think I've seen Chinese names written in both
> orders. That is, sometimes "Hui Deng" will be written "Deng Hui". Am
> I right? Does this happen often? What is the most common order? Is
> there a way to guess what order a name is written in? Sometimes it's
> not easy for non-Sinophones to know which part is the given name and
> which part is the family name.

It is more common for the given name to come first when written in
Pinyin, following the rule for other languages written in Latin
characters, but exceptions are frequent enough that one can't rely on
it.  A useful and growing convention is to write the family name in all
caps.  Using the above example, if "Deng" were the family name, you
might see:

Hui DENG
or
DENG Hui

whereas if "Hui" were the family name, you might see:

Deng HUI
or
HUI Deng

Also, most family names have a single syllable; all of the top 100 are,
which accounts for 85% of the population of China.  So, if exactly one
of the names has multiple syllables, it is reasonably safe to assume
that is the given name, absent a more definitive clue.

S

--=20
Stephen Sprunk         "God does not play dice."  --Albert Einstein
CCIE #3723         "God is an inveterate gambler, and He throws the
K5SSS        dice at every possible opportunity." --Stephen Hawking

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

<html>
  <head>
    <meta content=3D"text/html; charset=3DUTF-8" http-equiv=3D"Content-Ty=
pe">
  </head>
  <body bgcolor=3D"#FFFFFF" text=3D"#000000">
    On 11-Jul-13 08:58, Simon Perreault wrote:<br>
    <span style=3D"white-space: pre;">&gt; I have a question: I think I'v=
e
      seen Chinese names written in both <br>
      &gt; orders. That is, sometimes "Hui Deng" will be written "Deng
      Hui". Am<br>
      &gt; I right? Does this happen often? What is the most common
      order? Is <br>
      &gt; there a way to guess what order a name is written in?
      Sometimes it's<br>
      &gt; not easy for non-Sinophones to know which part is the given
      name and<br>
      &gt; which part is the family name.</span><br>
    <br>
    It is more common for the given name to come first when written in
    Pinyin, following the rule for other languages written in Latin
    characters, but exceptions are frequent enough that one can't rely
    on it.=C2=A0 A useful and growing convention is to write the family n=
ame
    in all caps.=C2=A0 Using the above example, if "Deng" were the family=

    name, you might see:<br>
    <br>
    Hui DENG<br>
    or<br>
    DENG Hui<br>
    <br>
    whereas if "Hui" were the family name, you might see:<br>
    <br>
    Deng HUI<br>
    or<br>
    HUI Deng<br>
    <br>
    Also, most family names have a single syllable; all of the top 100
    are, which accounts for 85% of the population of China.=C2=A0 So, if
    exactly one of the names has multiple syllables, it is reasonably
    safe to assume that is the given name, absent a more definitive
    clue.<br>
    <br>
    S<br>
    <br>
    -- <br>
    Stephen Sprunk=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 "God d=
oes not play dice."=C2=A0 --Albert Einstein<br>
    CCIE #3723=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 "God is an=
 inveterate gambler, and He throws the<br>
    K5SSS=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 dice at every possibl=
e opportunity." --Stephen Hawking<br>
  </body>
</html>

--------------060005030704050009010908--

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

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIFezCC
BXcwggNfoAMCAQICAw13sTANBgkqhkiG9w0BAQUFADB5MRAwDgYDVQQKEwdSb290IENBMR4w
HAYDVQQLExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNBIENlcnQgU2lnbmlu
ZyBBdXRob3JpdHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0Lm9yZzAeFw0xMzA3
MDgwNDU3MTVaFw0xNDAxMDQwNDU3MTVaMD0xGDAWBgNVBAMTD0NBY2VydCBXb1QgVXNlcjEh
MB8GCSqGSIb3DQEJARYSc3RlcGhlbkBzcHJ1bmsub3JnMIIBIjANBgkqhkiG9w0BAQEFAAOC
AQ8AMIIBCgKCAQEA1qAUmWE5Nv/9HFl7f52VrEoGqhbYG1rPE7go13pSxgUBi02iDNKyDTJH
b/CswpO/FE9p34QbUlnOXY3LRrLh+/NaS496breDA8mRKCceNHIPaiK3Mwpl0q787WQalrp9
mBV2jKHobOMOWbtNiuYSq6k4qfqIvFJvGOsgizcqeMjjLyR8GimjGCQYuH2o970PhlNidpAj
mVMCBehc3RhjmevEn4ydIL7j0bmFj9YuLxaoISq6icdh7VFxqAzdEbHhQHKp1N8aNq5yhcWD
M//Bq8MpMd1+zNse/pVc7/42G5iArYkImUbu/P48PgR8ZX9D59hJxP7kRyKVT9dbTNkh4wID
AQABo4IBQjCCAT4wDAYDVR0TAQH/BAIwADBWBglghkgBhvhCAQ0ESRZHVG8gZ2V0IHlvdXIg
b3duIGNlcnRpZmljYXRlIGZvciBGUkVFIGhlYWQgb3ZlciB0byBodHRwOi8vd3d3LkNBY2Vy
dC5vcmcwDgYDVR0PAQH/BAQDAgOoMEAGA1UdJQQ5MDcGCCsGAQUFBwMEBggrBgEFBQcDAgYK
KwYBBAGCNwoDBAYKKwYBBAGCNwoDAwYJYIZIAYb4QgQBMDIGCCsGAQUFBwEBBCYwJDAiBggr
BgEFBQcwAYYWaHR0cDovL29jc3AuY2FjZXJ0Lm9yZzAxBgNVHR8EKjAoMCagJKAihiBodHRw
Oi8vY3JsLmNhY2VydC5vcmcvcmV2b2tlLmNybDAdBgNVHREEFjAUgRJzdGVwaGVuQHNwcnVu
ay5vcmcwDQYJKoZIhvcNAQEFBQADggIBAIC5YDnhJnffDDJARyQlAFKmnMTPacWRQNIBz7Q9
PHC7RyEDNV+nUMEnukVtI0Kx8whLjQjNg6wiulfsT4ex7L9Y5iATmvKlCU81JP02lkfYXlLf
xKBcFIwRv5CUC2kES9e+DrZ51PKuAlJD5J7FpFThMrISSmuEh3Tc1kPD9D9s4gEEre7toLoW
oE4xA6Lqq7Ly/clkR0mabFDlEwowN4CfnTH6IUmM2PzCAAIVgMCK4dU3P99MgByDauQ4LKgL
bo2gwCxr52T/ovFqIuvMBf3Qf6CcOIjdv1LbjHzyTpLEFXE4eeFZTjCxL6y6Afi7JkCuavrk
miBTxb7hdyze4FDa2YHpIvN8ZQHHsfqpUbFXl9CLwYFkdnTwalTR5yJQV2gASOpC8eWFYoff
ObA+u8s6jb26RZZ6Dp3Lo1eQCPJbqYnJHaQfAr69/y1V7+KFUVttTFZxc+IIUUFPB1pL4IuS
FH362sF1KkauoI1fzQx+DWjEFPduSHlfxZ6ufueV0oht52Ie0igSrgl0ngnxKMI/LGx9WNyS
Smvs3gBtrYU6Nf1SgdCn/K16QBgvGSbru7LVdtd/p+WJRb54DZOmZvwYXrtkIwHiDB3UVz1L
gT7sL9O0uk/bC2NAI8UrE5PrtsEh0IdjFrq6bdYUGZGjtLO+Re3gYfMGUC5E4PQPmeemMYID
lDCCA5ACAQEwgYAweTEQMA4GA1UEChMHUm9vdCBDQTEeMBwGA1UECxMVaHR0cDovL3d3dy5j
YWNlcnQub3JnMSIwIAYDVQQDExlDQSBDZXJ0IFNpZ25pbmcgQXV0aG9yaXR5MSEwHwYJKoZI
hvcNAQkBFhJzdXBwb3J0QGNhY2VydC5vcmcCAw13sTAJBgUrDgMCGgUAoIIB6DAYBgkqhkiG
9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMzA3MTExNTIzMjBaMCMGCSqG
SIb3DQEJBDEWBBQexCyisPT4hu8D7vukxK4GgVNYhzBfBgkqhkiG9w0BCQ8xUjBQMAsGCWCG
SAFlAwQBAjAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYF
Kw4DAgcwDQYIKoZIhvcNAwICASgwgZEGCSsGAQQBgjcQBDGBgzCBgDB5MRAwDgYDVQQKEwdS
b290IENBMR4wHAYDVQQLExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNBIENl
cnQgU2lnbmluZyBBdXRob3JpdHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0Lm9y
ZwIDDXexMIGTBgsqhkiG9w0BCRACCzGBg6CBgDB5MRAwDgYDVQQKEwdSb290IENBMR4wHAYD
VQQLExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNBIENlcnQgU2lnbmluZyBB
dXRob3JpdHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0Lm9yZwIDDXexMA0GCSqG
SIb3DQEBAQUABIIBACRrA6EagPinepNYR8SJJBMPj/5R78vKs5I2pKjrSSafnxu0hhFbNVAb
3nv7mAiOhCETx5sTPtd86qXlJuzppzxrBPgs9aFOrfEPkkWlzkS+L+OCI62MD1FuN+5fqT7K
E0/n0ZdYagnlXTA8vmK/QpL8L66cc/OKBvo7JUYwKFyCBHwWvxZIRr63k7vwfOLrAxNfHWMs
Tkl2HoCUWWTWHW3PXToSeJsUvGVLn8FwvYGAz3kJkX5TssIP6eKVh9MKLtI2GtH+cuzIUX+B
Gk1rdihrx0dXOZAyihywfpYOd0Q1a7PlkRTbQ0G04s1Os0yoAO6qk9oZRonrG8+3Z5hTsfYA
AAAAAAA=
--------------ms040305010507030001030102--

From jnc@mercury.lcs.mit.edu  Thu Jul 11 08:26:20 2013
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BDE521F9D9E for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 08:26:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zMjevXDhqmpx for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 08:26:05 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 69BFD21F99F9 for <ietf@ietf.org>; Thu, 11 Jul 2013 08:26:04 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id E7ED418C1C7; Thu, 11 Jul 2013 11:26:00 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: Regarding call Chinese names
Message-Id: <20130711152600.E7ED418C1C7@mercury.lcs.mit.edu>
Date: Thu, 11 Jul 2013 11:26:00 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 15:26:20 -0000

    > From: Simon Perreault <simon.perreault@viagenie.ca>

    > I think I've seen Chinese names written in both orders. That is,
    > sometimes "Hui Deng" will be written "Deng Hui". Am I right? Does this
    > happen often?

I'm not certain about Chinese, but I know that with Japanese names, which
have the same issue (family name first in native language), both orders
happen a fair amount. (This also happens with Hungarian names, which also
use family-first - rare in the West, but it does happen.)

    > Is there a way to guess what order a name is written in? Sometimes it's
    > not easy for non-Sinophones to know which part is the given name and
    > which part is the family name.

Unless you know a certain amount about the language, my guess would be 'no'.

Hence the common practise in some academic circles of giving the family name
in all capitals, to show which it is. So whether you see Junichiro KOIZUMI
or KOIZUMI Junichiro, you know what you're seeing.

Maybe the IETF should adopt that practise in, e.g., attendee lists?

I'm not sure what to do about e.g. RFC's - there's a pretty strict "X. Yyyy"
form for names, where X is the given initial, the Yyyy the family name. Do we
want to change that, or just say 'sorry, family-first people, you'll have to
mangle your name to fit the RFC format'?

(That happens already in other cases, BTW. I'm called by my _middle_ name -
which caused all sorts of issues for the I-D software when "J. Noel Chiappa"
tried to submit a draft listing "N. Chiappa". It Did Not Like.)

Do we want to encourage people to do the capitalization in their email
addresses (the full-name part, not the mailbox name part), so that people
know? That's obviously not under our control, but we might _suggest_ it.

	Noel

From moore@network-heretics.com  Thu Jul 11 08:29:34 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B0D021F9DA5 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 08:29:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.432
X-Spam-Level: 
X-Spam-Status: No, score=-3.432 tagged_above=-999 required=5 tests=[AWL=0.167,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5eUHgK3dMm1f for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 08:29:29 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id 2FCA921F9DBA for <ietf@ietf.org>; Thu, 11 Jul 2013 08:29:20 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 6940E207BA; Thu, 11 Jul 2013 11:29:10 -0400 (EDT)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute2.internal (MEProxy); Thu, 11 Jul 2013 11:29:10 -0400
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 :content-transfer-encoding; s=smtpout; bh=r4VDjFbkgxq3s78ZAf0Pab 49u/c=; b=LeX50O6iAfC9xd8qW5cHKpBPGCqe4GfCnbEH9q6sZDIazOACQEkdS3 m2YJULALX9Ymqpx7fN+hrCMfOgLLwYfzpXT9cvU8Uy48qQw/N403NT72z+E3zKdK ZATd40uwsfn1Dot0eMah6pt+U0EFl/SUZ2JiaNMk2dmWRUlzynVBc=
X-Sasl-enc: p55Yqv+lQdJzZYyxUNkF4YpGkdwbYTBVN2w7G6gxJ3kT 1373556549
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 53C0E6804DC; Thu, 11 Jul 2013 11:29:09 -0400 (EDT)
Message-ID: <51DECF3C.3050901@network-heretics.com>
Date: Thu, 11 Jul 2013 11:29:00 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: IETF registration fee?
References: <CE0388EA.21B7F%Josh.Howlett@ja.net> <803FCD9A-6B8A-45EC-914F-E2114C581EA1@gmail.com> <C053B4F4-4821-4132-B872-3F8A611B2F5F@unina.it> <CAMm+Lwjpw6uodpZHuQ-rW4hJ7ViUHqrFBwTJYGkXCtH1c2x1ww@mail.gmail.com> <C66F2B4BC73DB85224494CB1@JcK-HP8200.jck.com>
In-Reply-To: <C66F2B4BC73DB85224494CB1@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 15:29:34 -0000

On 07/11/2013 11:17 AM, John C Klensin wrote:
>
> --On Thursday, July 11, 2013 10:34 -0400 Phillip Hallam-Baker
> <hallam@gmail.com> wrote:
>
>> ...
>> Using paid conferences as a profit center is a risky long term
>> prospect at best. Refusing to adapt the format of the
>> conferences to protect the profit center worse.
> Or adapting the format to attract more paying attendees, such a
> what we have sometimes called "tourists", with no real
> expectation that they will do work, because it increases the
> income.
>
> Still better than building a funding structure based on sale of
> publications, however :-(

The best idea that I've come up with would be for IETF to offer 
tutorials (not at IETF meetings, but at other times and places) to teach 
people about current and emerging Internet technology, and use the 
proceeds from those to pay for its standards-making and -maintenance 
efforts.   Part of the function of the tutorials could be to serve as a 
means of getting user feedback for just how well IETF standards were or 
were not meeting their needs.

Of course, there are hazards associated with any approach.   One could 
imagine, for instance, that the IETF tutorial division could end up 
being much larger than the IETF standards division, and that IETF 
standards making would suffer from the desire to optimize performance of 
the cash cow.     Or that there would be conflicts between what the 
teachers taught as best practices, and the practices recommended by IETF 
standards.

At any rate, it certainly would be a significant change from the current 
way we operate.

Keith


From kathleen.moriarty@emc.com  Thu Jul 11 08:40:00 2013
Return-Path: <kathleen.moriarty@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87AB521F9E9E for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 08:40:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.934
X-Spam-Level: 
X-Spam-Status: No, score=-1.934 tagged_above=-999 required=5 tests=[AWL=0.665,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YEWoLyRIKDxV for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 08:39:54 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 9BE7421F9E6D for <ietf@ietf.org>; Thu, 11 Jul 2013 08:39:54 -0700 (PDT)
Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r6BFdo27025822 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 11 Jul 2013 11:39:52 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd04.lss.emc.com [10.254.222.226]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor); Thu, 11 Jul 2013 11:39:43 -0400
Received: from mxhub16.corp.emc.com (mxhub16.corp.emc.com [128.222.70.237]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r6BFdgl3029144; Thu, 11 Jul 2013 11:39:42 -0400
Received: from mx15a.corp.emc.com ([169.254.1.184]) by mxhub16.corp.emc.com ([128.222.70.237]) with mapi; Thu, 11 Jul 2013 11:39:42 -0400
From: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
To: John C Klensin <john-ietf@jck.com>, Phillip Hallam-Baker <hallam@gmail.com>, Simon Pietro Romano <spromano@unina.it>
Date: Thu, 11 Jul 2013 11:39:41 -0400
Subject: RE: IETF registration fee?
Thread-Topic: IETF registration fee?
Thread-Index: Ac5+SdEbPff13QO0QLO03INnQk/euQAAPQ5A
Message-ID: <F5063677821E3B4F81ACFB7905573F24DF2F8111@MX15A.corp.emc.com>
References: <CE0388EA.21B7F%Josh.Howlett@ja.net> <803FCD9A-6B8A-45EC-914F-E2114C581EA1@gmail.com> <C053B4F4-4821-4132-B872-3F8A611B2F5F@unina.it> <CAMm+Lwjpw6uodpZHuQ-rW4hJ7ViUHqrFBwTJYGkXCtH1c2x1ww@mail.gmail.com> <C66F2B4BC73DB85224494CB1@JcK-HP8200.jck.com>
In-Reply-To: <C66F2B4BC73DB85224494CB1@JcK-HP8200.jck.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: Keith Moore <moore@network-heretics.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 15:40:00 -0000

Tourists can turn into long term contributing attendees if they like what t=
hey see and think it will be an effective forum to get work done.  We need =
to collectively do a better job helping new people get acclimated to being =
effective at the IETF.  The mentoring program, ISOC policy makers, and othe=
r efforts should help to improve this over time.

I do agree that we need to improve materials so that people can better unde=
rstand the work happening in each WG.  I know people can read the drafts, b=
ut sometimes how the drafts connect or why they matter collectively is not =
apparent, or even how/why to use which drafts for what purpose.  Drafts and=
 RFCs are great, but other media would be helpful here I think.  The tutori=
als is an interesting idea.  I think youtube videos may be effective as wel=
l without having to schedule meetings for tutorials.

Thanks,
Kathleen

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Joh=
n C Klensin
Sent: Thursday, July 11, 2013 11:17 AM
To: Phillip Hallam-Baker; Simon Pietro Romano
Cc: Keith Moore; ietf@ietf.org
Subject: Re: IETF registration fee?



--On Thursday, July 11, 2013 10:34 -0400 Phillip Hallam-Baker
<hallam@gmail.com> wrote:

>...
> Using paid conferences as a profit center is a risky long term
> prospect at best. Refusing to adapt the format of the
> conferences to protect the profit center worse.=20

Or adapting the format to attract more paying attendees, such a
what we have sometimes called "tourists", with no real
expectation that they will do work, because it increases the
income.

Still better than building a funding structure based on sale of
publications, however :-(

   john






From d3e3e3@gmail.com  Thu Jul 11 08:41:07 2013
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0146721F9D08 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 08:41:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.425
X-Spam-Level: 
X-Spam-Status: No, score=-102.425 tagged_above=-999 required=5 tests=[AWL=0.175, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1ePY4Oycskqi for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 08:41:06 -0700 (PDT)
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 9249321F9C21 for <ietf@ietf.org>; Thu, 11 Jul 2013 08:40:47 -0700 (PDT)
Received: by mail-ob0-f180.google.com with SMTP id eh20so9920140obb.39 for <ietf@ietf.org>; Thu, 11 Jul 2013 08:40:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=1170BWE8yScRYcXfIo0CrVVEFj9VUFksmSSLRLSdmBI=; b=cW44GDzOjIFuS27hyJNveeb2rbMFy/ci95FeFwD7MBscD8Q7tVzMyIr9eOJx1FjVG9 7xeQqHecfVZIa2eGrPTn8I0QX+4qDlkcFZ5/Q4bsMbXQ7UJYjXFCcFLZlNKk4iKqXy7T KxzAmEi5C9uLg++ZnDPGaPj33K7vyvPNRNupZXG+1ccgV7gm1dEGsthHZBCEE8zjSqLV Q5ft2pRMPBfShr7RUvMmvdB1WssHTllDv4LSZlbW0zuSBGqp5tE2abRa296SdNTWGrGh Tycs+XpRB9QkkB36AIoxRFIiv8qFzQvEIY78fl28C7bZ6S8VPGjrxA+vMHY94MdgHsAI Pcbw==
X-Received: by 10.182.165.232 with SMTP id zb8mr32403164obb.101.1373557247044;  Thu, 11 Jul 2013 08:40:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.73.106 with HTTP; Thu, 11 Jul 2013 08:40:26 -0700 (PDT)
In-Reply-To: <F108A063F7E85E5F9C89ADBF@caldav.corp.apple.com>
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com> <51DEB9F2.9040405@viagenie.ca> <F108A063F7E85E5F9C89ADBF@caldav.corp.apple.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Thu, 11 Jul 2013 11:40:26 -0400
Message-ID: <CAF4+nEF_VnR2DNd_LDehXwJNn=0CT0Qkz3hKrBHuffVFvdXLMg@mail.gmail.com>
Subject: Re: Regarding call Chinese names
To: Cyrus Daboo <cyrus@daboo.name>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 15:41:07 -0000

First/Last = bad/ambiguous

Family (or maybe inherited) / Given = good

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


On Thu, Jul 11, 2013 at 10:22 AM, Cyrus Daboo <cyrus@daboo.name> wrote:
> Hi Simon,
>
>
> --On July 11, 2013 at 3:58:10 PM +0200 Simon Perreault
> <simon.perreault@viagenie.ca> wrote:
>
>>> We submitted two drafts to help people here to correctly call chinese
>>> people names:
>>>
>>> http://tools.ietf.org/html/draft-deng-call-chinese-names-00
>>>    http://tools.ietf.org/html/draft-zcao-chinese-pronounce-00
>>
>>
>> Very cool! Thanks for writing this!
>>
>> I have a question: I think I've seen Chinese names written in both
>> orders. That is, sometimes "Hui Deng" will be written "Deng Hui". Am I
>> right? Does this happen often? What is the most common order? Is there a
>> way to guess what order a name is written in? Sometimes it's not easy
>> for non-Sinophones to know which part is the given name and which part
>> is the family name.
>
>
> Well that actually brings up a good technical point!
>
> In iCalendar (RFC5545) we have properties to represent the organizer and
> attendee of meetings. A parameter (attribute) of those properties is "CN" -
> defined to be the "common name" of the corresponding calendar user.
> Obviously that is a single string and typically the concatenation of first
> name/last name. But that of course is a very "Western" approach.
>
> I have had several people request that iCalendar instead define new
> parameters for "FIRST-NAME" and "LAST-NAME". That then gives clients the
> option of re-ordering those for display purposes based on user locales and
> preferences.
>
> So, from a technical standpoint, it seems better to always represent user
> names using components (last, first, middle)? vCard does have an "N"
> property where individual components of a name can be broken out.
>
> --
> Cyrus Daboo
>

From john-ietf@jck.com  Thu Jul 11 08:44:22 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D7BC21F9D95 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 08:44:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.579
X-Spam-Level: 
X-Spam-Status: No, score=-103.579 tagged_above=-999 required=5 tests=[AWL=1.020, BAYES_00=-2.599, GB_I_LETTER=-2, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gaM1FZUanSGZ for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 08:44:16 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 595B821F9F65 for <ietf@ietf.org>; Thu, 11 Jul 2013 08:44:16 -0700 (PDT)
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 1UxJ2V-0001b1-NE; Thu, 11 Jul 2013 11:44:15 -0400
Date: Thu, 11 Jul 2013 11:44:10 -0400
From: John C Klensin <john-ietf@jck.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: Regarding call Chinese names
Message-ID: <98A72410A713CA571EE406B6@JcK-HP8200.jck.com>
In-Reply-To: <20130711152600.E7ED418C1C7@mercury.lcs.mit.edu>
References: <20130711152600.E7ED418C1C7@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
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 15:44:22 -0000

--On Thursday, July 11, 2013 11:26 -0400 Noel Chiappa
<jnc@mercury.lcs.mit.edu> wrote:

>     > From: Simon Perreault <simon.perreault@viagenie.ca>
> 
>     > I think I've seen Chinese names written in both orders.
> That is,     > sometimes "Hui Deng" will be written "Deng
> Hui". Am I right? Does this     > happen often?
> 
> I'm not certain about Chinese, but I know that with Japanese
> names, which have the same issue (family name first in native
> language), both orders happen a fair amount. (This also
> happens with Hungarian names, which also use family-first -
> rare in the West, but it does happen.)
>...

Not that rare if one includes "family name in the middle" as
another case that is unusual relative to "normal English" usage.

Worse, the "standard" convention for expressing a Chinese names
in Latin characters differs among Chinese-speaking populations/
countries.  One can usually deduce which one is the family name/
surname from context (not limited to knowing a "certain amount
about the language, but it sometimes requires a lot of context.
And, as you know, the "most family names are one character and
most personal names are more than one" rule mentioned in the
draft works for Chinese names but not for Japanese ones.

Incidentally, purging "first name" and "last name" from our
vocabulary would be a big step in avoiding confusion.

> Hence the common practise in some academic circles of giving
> the family name in all capitals, to show which it is. So
> whether you see Junichiro KOIZUMI or KOIZUMI Junichiro, you
> know what you're seeing.

Not just in academic circles but in some UN ones and elsewhere.
I strongly recommend wider adoption of this convention and note
that it has been used in some RFCs (but not consistently).

> Maybe the IETF should adopt that practise in, e.g., attendee
> lists?
> 
> I'm not sure what to do about e.g. RFC's - there's a pretty
> strict "X. Yyyy" form for names, where X is the given initial,
> the Yyyy the family name. Do we want to change that, or just
> say 'sorry, family-first people, you'll have to mangle your
> name to fit the RFC format'?

The upper-case family name convention helps if there is any
possible ambiguity.  I also note that this is all sufficiently
confusing that at least one RFC was published with 
   "First-letter-of-family-name. Personal-name"
for the editor.

Comments to the RSE might be in order and some of the
suggestions in this draft probably belong in the Style Guide,
especially as things evolve toward having author/editor names in
their original scripts.

>...
> Do we want to encourage people to do the capitalization in
> their email addresses (the full-name part, not the mailbox
> name part), so that people know? That's obviously not under
> our control, but we might _suggest_ it.

Indeed.

Folks, might I encourage making editorial and similar
suggestions in notes to the authors rather than trying to edit
the document on the IETF list?

best,
  john




From stephen@sprunk.org  Thu Jul 11 08:50:14 2013
Return-Path: <stephen@sprunk.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A85BD21F9DFC for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 08:50:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.714
X-Spam-Level: 
X-Spam-Status: No, score=-1.714 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qivNMWHnFqZP for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 08:50:08 -0700 (PDT)
Received: from nm6-vm6.access.bullet.mail.gq1.yahoo.com (nm6-vm6.access.bullet.mail.gq1.yahoo.com [216.39.63.154]) by ietfa.amsl.com (Postfix) with ESMTP id 1BF1121F9F65 for <ietf@ietf.org>; Thu, 11 Jul 2013 08:50:07 -0700 (PDT)
Received: from [216.39.60.168] by nm6.access.bullet.mail.gq1.yahoo.com with NNFMP; 11 Jul 2013 15:50:06 -0000
Received: from [67.195.23.146] by tm4.access.bullet.mail.gq1.yahoo.com with NNFMP; 11 Jul 2013 15:50:05 -0000
Received: from [127.0.0.1] by smtp118.sbc.mail.gq1.yahoo.com with NNFMP; 11 Jul 2013 15:50:05 -0000
X-Yahoo-Newman-Id: 934394.28214.bm@smtp118.sbc.mail.gq1.yahoo.com
X-Yahoo-Newman-Property: ymail-3
X-YMail-OSG: p_.gMqcVM1k1W.MgJknncumIuf1CYEKXDT0FlgmB.kZ8YWg W5NCzMJ3Gori9xQypqat1F95t2w0BTMrEdh7gA66d95_GtwVyGIYIuXDQhFC ubyA8jKPDi8JkaLmHL4xShy6QYpEHd3rmNVyNMYXuIMZxlH6Vu1XDxYaFdTD AXzaHgEJmCLG9RtF.1FbrKZBZN6gYUbQCAiaVQMy7woOTJIYgdDtjNgZ6xGX Bp9TEG2_3H64W7wQdtn1wBT9398pnt2ZxTMoj5xslC623LbQkt65Tphl25ZC 1Yv9hZ4F.q9DE0ZHcZxQ7jG2cjLO.aau_lu9Ucz6YJodULhuH_mrSMMzx0m. Wa2kfk5GPVoSXQfhR811si9zLgmlrphD58XtHvHghaXJ6N.Y1RigZtocqdjt 0GpW20zX69aEvu8Jeiu9OYs9JZQyBhy.IETiccAMmBUmdALKOZR9r3Cx970B sRryeWV7SHGNbGbEwXt0F_JrHSLX_RJss8aVQh8XpiXj4DOo1dmzx1GYlEDm leczCiWCXi4UGpfOiBd4NSDZyCKvz7cFwsGwN1EuHjvnjxNZ2kWOpViyA5Bl vPCIH2m62VhMHHSO394Eb1tsIsMP6TuRcS.eUY7d39crROoUN8qr1ToKAXA_ uJ.9_MeQLcmOUal6J4dM6OnVv_RCYlfx6_Q--
X-Yahoo-SMTP: EYvcGKyswBB8plhV5pc8yMz3blwA5zta_j4l
X-Rocket-Received: from [192.168.1.67] (stephen@99.136.80.184 with plain) by smtp118.sbc.mail.gq1.yahoo.com with SMTP; 11 Jul 2013 15:50:05 +0000 UTC
Message-ID: <51DED42B.8040202@sprunk.org>
Date: Thu, 11 Jul 2013 10:50:03 -0500
From: Stephen Sprunk <stephen@sprunk.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:10.0) Gecko/20120206 Thunderbird/10.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Regarding call Chinese names
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com>
In-Reply-To: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms010707080008050305060008"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 15:50:15 -0000

This is a cryptographically signed message in MIME format.

--------------ms010707080008050305060008
Content-Type: multipart/alternative;
 boundary="------------020403010507060904020706"

This is a multi-part message in MIME format.
--------------020403010507060904020706
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 10-Jul-13 19:04, Hui Deng wrote:
> We submitted two drafts to help people here to correctly call chinese
> people names:
>
> http://tools.ietf.org/html/draft-deng-call-chinese-names-00=20
>
>    http://tools.ietf.org/html/draft-zcao-chinese-pronounce-00
>

While "first name" and "last name" may be useful for many Western
readers, they tend to produce confusing statements like "put his/her
Last name first, and first name last."  I would prefer the order-neutral
terms "given name" and "family name", which results in the more sensible
"put his/her family name first and given name last."

Also, the section on tones (which BTW belongs in the pronunciation
document, not the names document) is a good example of how allowing
UTF-8, rather than just US-ASCII, would be useful.  "Lao3ban3"
(Wade-Giles) requires memorizing what the various tone numbers mean,
whereas "L=C7=8Eob=C7=8En" (Pinyin) provides a visual representation of t=
he proper
tone, which will be more accessible to most readers.

S

--=20
Stephen Sprunk         "God does not play dice."  --Albert Einstein
CCIE #3723         "God is an inveterate gambler, and He throws the
K5SSS        dice at every possible opportunity." --Stephen Hawking


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

<html>
  <head>
    <meta content=3D"text/html; charset=3DUTF-8" http-equiv=3D"Content-Ty=
pe">
  </head>
  <body bgcolor=3D"#FFFFFF" text=3D"#000000">
    On 10-Jul-13 19:04, Hui Deng wrote:
    <blockquote
cite=3D"mid:CANF0JMBtNf9+=3D+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gm=
ail.com"
      type=3D"cite">
      <div dir=3D"ltr">We submitted two drafts to help people here to
        correctly call chinese people names:
        <div><font color=3D"#000000" face=3D"=E5=AE=8B=E4=BD=93" size=3D"=
3">
          </font>
          <p style=3D"margin:0cm 0cm 0pt"><span lang=3D"EN-US"><a
                moz-do-not-send=3D"true"
                href=3D"http://tools.ietf.org/html/draft-deng-call-chines=
e-names-00"
                target=3D"_blank"><span
style=3D"background:white;color:rgb(17,85,204);font-family:&quot;Arial&qu=
ot;,&quot;sans-serif&quot;;font-size:10pt">http://tools.ietf.org/html/dra=
ft-deng-call-chinese-names-00</span></a></span><span
style=3D"background:white;color:rgb(34,34,34);font-family:&quot;Arial&quo=
t;,&quot;sans-serif&quot;;font-size:10pt"
              lang=3D"EN-US">=C2=A0</span></p>
          <font color=3D"#000000" face=3D"=E5=AE=8B=E4=BD=93" size=3D"3">=

          </font>
          <p style=3D"margin:0cm 0cm 0pt"><span
style=3D"background:white;color:rgb(34,34,34);font-family:&quot;Arial&quo=
t;,&quot;sans-serif&quot;;font-size:10pt"
              lang=3D"EN-US">=C2=A0 =C2=A0</span><span lang=3D"EN-US"><a
                moz-do-not-send=3D"true"
                href=3D"http://tools.ietf.org/html/draft-zcao-chinese-pro=
nounce-00"
                target=3D"_blank"><span
style=3D"background:white;color:rgb(17,85,204);font-family:&quot;Arial&qu=
ot;,&quot;sans-serif&quot;;font-size:10pt">http://tools.ietf.org/html/dra=
ft-zcao-chinese-pronounce-00</span></a></span></p>
        </div>
      </div>
    </blockquote>
    <br>
    While "first name" and "last name" may be useful for many Western
    readers, they tend to produce confusing statements like "put his/her
    Last name first, and first name last."=C2=A0 I would prefer the
    order-neutral terms "given name" and "family name", which results in
    the more sensible "put his/her family name first and given name
    last."<br>
    <br>
    Also, the section on tones (which BTW belongs in the pronunciation
    document, not the names document) is a good example of how allowing
    UTF-8, rather than just US-ASCII, would be useful.=C2=A0 "Lao3ban3"
    (Wade-Giles) requires memorizing what the various tone numbers mean,
    whereas "L=C7=8Eob=C7=8En" (Pinyin) provides a visual representation =
of the
    proper tone, which will be more accessible to most readers.<br>
    <br>
    S<br>
    <pre class=3D"moz-signature" cols=3D"72">--=20
Stephen Sprunk         "God does not play dice."  --Albert Einstein
CCIE #3723         "God is an inveterate gambler, and He throws the
K5SSS        dice at every possible opportunity." --Stephen Hawking
</pre>
  </body>
</html>

--------------020403010507060904020706--

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

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIFezCC
BXcwggNfoAMCAQICAw13sTANBgkqhkiG9w0BAQUFADB5MRAwDgYDVQQKEwdSb290IENBMR4w
HAYDVQQLExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNBIENlcnQgU2lnbmlu
ZyBBdXRob3JpdHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0Lm9yZzAeFw0xMzA3
MDgwNDU3MTVaFw0xNDAxMDQwNDU3MTVaMD0xGDAWBgNVBAMTD0NBY2VydCBXb1QgVXNlcjEh
MB8GCSqGSIb3DQEJARYSc3RlcGhlbkBzcHJ1bmsub3JnMIIBIjANBgkqhkiG9w0BAQEFAAOC
AQ8AMIIBCgKCAQEA1qAUmWE5Nv/9HFl7f52VrEoGqhbYG1rPE7go13pSxgUBi02iDNKyDTJH
b/CswpO/FE9p34QbUlnOXY3LRrLh+/NaS496breDA8mRKCceNHIPaiK3Mwpl0q787WQalrp9
mBV2jKHobOMOWbtNiuYSq6k4qfqIvFJvGOsgizcqeMjjLyR8GimjGCQYuH2o970PhlNidpAj
mVMCBehc3RhjmevEn4ydIL7j0bmFj9YuLxaoISq6icdh7VFxqAzdEbHhQHKp1N8aNq5yhcWD
M//Bq8MpMd1+zNse/pVc7/42G5iArYkImUbu/P48PgR8ZX9D59hJxP7kRyKVT9dbTNkh4wID
AQABo4IBQjCCAT4wDAYDVR0TAQH/BAIwADBWBglghkgBhvhCAQ0ESRZHVG8gZ2V0IHlvdXIg
b3duIGNlcnRpZmljYXRlIGZvciBGUkVFIGhlYWQgb3ZlciB0byBodHRwOi8vd3d3LkNBY2Vy
dC5vcmcwDgYDVR0PAQH/BAQDAgOoMEAGA1UdJQQ5MDcGCCsGAQUFBwMEBggrBgEFBQcDAgYK
KwYBBAGCNwoDBAYKKwYBBAGCNwoDAwYJYIZIAYb4QgQBMDIGCCsGAQUFBwEBBCYwJDAiBggr
BgEFBQcwAYYWaHR0cDovL29jc3AuY2FjZXJ0Lm9yZzAxBgNVHR8EKjAoMCagJKAihiBodHRw
Oi8vY3JsLmNhY2VydC5vcmcvcmV2b2tlLmNybDAdBgNVHREEFjAUgRJzdGVwaGVuQHNwcnVu
ay5vcmcwDQYJKoZIhvcNAQEFBQADggIBAIC5YDnhJnffDDJARyQlAFKmnMTPacWRQNIBz7Q9
PHC7RyEDNV+nUMEnukVtI0Kx8whLjQjNg6wiulfsT4ex7L9Y5iATmvKlCU81JP02lkfYXlLf
xKBcFIwRv5CUC2kES9e+DrZ51PKuAlJD5J7FpFThMrISSmuEh3Tc1kPD9D9s4gEEre7toLoW
oE4xA6Lqq7Ly/clkR0mabFDlEwowN4CfnTH6IUmM2PzCAAIVgMCK4dU3P99MgByDauQ4LKgL
bo2gwCxr52T/ovFqIuvMBf3Qf6CcOIjdv1LbjHzyTpLEFXE4eeFZTjCxL6y6Afi7JkCuavrk
miBTxb7hdyze4FDa2YHpIvN8ZQHHsfqpUbFXl9CLwYFkdnTwalTR5yJQV2gASOpC8eWFYoff
ObA+u8s6jb26RZZ6Dp3Lo1eQCPJbqYnJHaQfAr69/y1V7+KFUVttTFZxc+IIUUFPB1pL4IuS
FH362sF1KkauoI1fzQx+DWjEFPduSHlfxZ6ufueV0oht52Ie0igSrgl0ngnxKMI/LGx9WNyS
Smvs3gBtrYU6Nf1SgdCn/K16QBgvGSbru7LVdtd/p+WJRb54DZOmZvwYXrtkIwHiDB3UVz1L
gT7sL9O0uk/bC2NAI8UrE5PrtsEh0IdjFrq6bdYUGZGjtLO+Re3gYfMGUC5E4PQPmeemMYID
lDCCA5ACAQEwgYAweTEQMA4GA1UEChMHUm9vdCBDQTEeMBwGA1UECxMVaHR0cDovL3d3dy5j
YWNlcnQub3JnMSIwIAYDVQQDExlDQSBDZXJ0IFNpZ25pbmcgQXV0aG9yaXR5MSEwHwYJKoZI
hvcNAQkBFhJzdXBwb3J0QGNhY2VydC5vcmcCAw13sTAJBgUrDgMCGgUAoIIB6DAYBgkqhkiG
9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMzA3MTExNTUwMDNaMCMGCSqG
SIb3DQEJBDEWBBRMSgW6f7rciyO2oCZ1eA6ssFaNfTBfBgkqhkiG9w0BCQ8xUjBQMAsGCWCG
SAFlAwQBAjAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYF
Kw4DAgcwDQYIKoZIhvcNAwICASgwgZEGCSsGAQQBgjcQBDGBgzCBgDB5MRAwDgYDVQQKEwdS
b290IENBMR4wHAYDVQQLExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNBIENl
cnQgU2lnbmluZyBBdXRob3JpdHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0Lm9y
ZwIDDXexMIGTBgsqhkiG9w0BCRACCzGBg6CBgDB5MRAwDgYDVQQKEwdSb290IENBMR4wHAYD
VQQLExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNBIENlcnQgU2lnbmluZyBB
dXRob3JpdHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0Lm9yZwIDDXexMA0GCSqG
SIb3DQEBAQUABIIBAIhAsQmHSexjax3+s3I/Euthm4FnPr90/skYLYC2n7W+P8ARd8tZ4uIn
Ejhi+R9Ob3J3epPb4JhrmbxhFy4f6c2uYttoityaZ7VToBTU561Z0zbTPw7srKqf/tQGf4Vv
knA3DwFd5GrL9ZRUCa7UUZ5O49CCr6YY6LmA2C8Flu198tSvzrZ6eJ5610c4nCnR9jGbhiPK
Hg8fZ3pEG1HpnWrSSkLca8xTk9r+HApOcSNDGj161NEzi8vOSQ7JsyUO5kBIbwG6bt5E7aOP
pj+2cvCkGHjsOQKEcB2l0SiL4fnJr2zFnalW3XiyMI18eJZZevp/hyUxxMK8A2kq7ZJDnE4A
AAAAAAA=
--------------ms010707080008050305060008--

From simon.perreault@viagenie.ca  Thu Jul 11 08:57:28 2013
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11B7221F9CDD for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 08:57:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.493
X-Spam-Level: 
X-Spam-Status: No, score=-2.493 tagged_above=-999 required=5 tests=[AWL=0.107,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QT7l66iWtstt for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 08:57:27 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id A821221F9CD3 for <ietf@ietf.org>; Thu, 11 Jul 2013 08:57:27 -0700 (PDT)
Received: from [IPv6:::1] (unknown [IPv6:2001:660:3001:4012:5b8:1f9e:c21b:48d7]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 8FE5A403E7 for <ietf@ietf.org>; Thu, 11 Jul 2013 11:57:24 -0400 (EDT)
Message-ID: <51DED5E4.1030400@viagenie.ca>
Date: Thu, 11 Jul 2013 17:57:24 +0200
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Regarding call Chinese names
References: <20130711152600.E7ED418C1C7@mercury.lcs.mit.edu> <98A72410A713CA571EE406B6@JcK-HP8200.jck.com>
In-Reply-To: <98A72410A713CA571EE406B6@JcK-HP8200.jck.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 15:57:28 -0000

Le 2013-07-11 17:44, John C KLENSIN a 閏rit :
>> Hence the common practise in some academic circles of giving
>> the family name in all capitals, to show which it is. So
>> whether you see Junichiro KOIZUMI or KOIZUMI Junichiro, you
>> know what you're seeing.
> 
> Not just in academic circles but in some UN ones and elsewhere.
> I strongly recommend wider adoption of this convention and note
> that it has been used in some RFCs (but not consistently).

It is omnipresent in everyday life in France as well.

Simon

From paf@frobbit.se  Thu Jul 11 08:58:06 2013
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 656FB21F9E87 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 08:58:06 -0700 (PDT)
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=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AzoCIlBDj9Et for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 08:58:06 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id DB43321F9E81 for <ietf@ietf.org>; Thu, 11 Jul 2013 08:58:05 -0700 (PDT)
Received: from [10.21.12.62] (unknown [196.38.31.134]) by mail.frobbit.se (Postfix) with ESMTPSA id 650E321FB0; Thu, 11 Jul 2013 17:58:00 +0200 (CEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Regarding call Chinese names
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <98A72410A713CA571EE406B6@JcK-HP8200.jck.com>
Date: Thu, 11 Jul 2013 17:57:06 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <7FEFDB4B-E746-4859-B0EC-0CCC59E71FF1@frobbit.se>
References: <20130711152600.E7ED418C1C7@mercury.lcs.mit.edu> <98A72410A713CA571EE406B6@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1508)
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 15:58:06 -0000

On 11 jul 2013, at 17:44, John C Klensin <john-ietf@jck.com> wrote:

> Not that rare if one includes "family name in the middle" as
> another case that is unusual relative to "normal English" usage.

Maybe people from Iceland should start explaining how things work there?

;-)

   Patrik


From spromano@unina.it  Thu Jul 11 09:05:54 2013
Return-Path: <spromano@unina.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C215321F9926 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 09:05:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.718
X-Spam-Level: 
X-Spam-Status: No, score=-100.718 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6H-5Hoc+pRH7 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 09:05:47 -0700 (PDT)
Received: from smtp1.unina.it (smtp1.unina.it [192.132.34.61]) by ietfa.amsl.com (Postfix) with ESMTP id B87E321F9F6F for <ietf@ietf.org>; Thu, 11 Jul 2013 09:05:41 -0700 (PDT)
Received: from [143.225.162.130] ([143.225.162.130]) (authenticated bits=0) by smtp1.unina.it (8.14.4/8.14.4) with ESMTP id r6BG5SLY004963 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 11 Jul 2013 18:05:29 +0200
Subject: Re: IETF registration fee?
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: multipart/alternative; boundary="Apple-Mail=_64698137-19DE-4420-970F-A4CC12B813EC"
From: Simon Pietro Romano <spromano@unina.it>
In-Reply-To: <F5063677821E3B4F81ACFB7905573F24DF2F8111@MX15A.corp.emc.com>
Date: Thu, 11 Jul 2013 18:05:34 +0200
Message-Id: <62CA331C-4CCA-414A-8AE5-91FA37B4FED3@unina.it>
References: <CE0388EA.21B7F%Josh.Howlett@ja.net> <803FCD9A-6B8A-45EC-914F-E2114C581EA1@gmail.com> <C053B4F4-4821-4132-B872-3F8A611B2F5F@unina.it> <CAMm+Lwjpw6uodpZHuQ-rW4hJ7ViUHqrFBwTJYGkXCtH1c2x1ww@mail.gmail.com> <C66F2B4BC73DB85224494CB1@JcK-HP8200.jck.com> <F5063677821E3B4F81ACFB7905573F24DF2F8111@MX15A.corp.emc.com>
To: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
X-Mailer: Apple Mail (2.1283)
Cc: John C Klensin <john-ietf@jck.com>, Keith Moore <moore@network-heretics.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 16:05:54 -0000

--Apple-Mail=_64698137-19DE-4420-970F-A4CC12B813EC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Hi Kathleen,

> think.  The tutorials is an interesting idea.  I think youtube videos =
may be effective as well without having to schedule meetings for =
tutorials.

I think the IETF leadership is already looking after this. Have a look =
at:

http://iaoc.ietf.org/
http://www.ietf.org/edu/process-oriented-tutorials.html#newcomers
http://www.ietf.org/edu/process-oriented-tutorials.html#wgleadership
http://www.ietf.org/edu/process-oriented-tutorials.html#creatingids
http://www.ietf.org/edu/technical-tutorials.html#netconfandyang
http://www.ietf.org/edu/technical-tutorials.html#opsandmanagement
http://www.ietf.org/edu/technical-tutorials.html#routing
http://www.ietf.org/edu/technical-tutorials.html#security

All of these have been recorded at recent IETF meetings, and some of =
them will be re-recorded at an enhanced quality level in order to =
improve the quality of experience for the end users.

Cheers,

Simon

>=20
> Thanks,
> Kathleen
>=20
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf =
Of John C Klensin
> Sent: Thursday, July 11, 2013 11:17 AM
> To: Phillip Hallam-Baker; Simon Pietro Romano
> Cc: Keith Moore; ietf@ietf.org
> Subject: Re: IETF registration fee?
>=20
>=20
>=20
> --On Thursday, July 11, 2013 10:34 -0400 Phillip Hallam-Baker
> <hallam@gmail.com> wrote:
>=20
>> ...
>> Using paid conferences as a profit center is a risky long term
>> prospect at best. Refusing to adapt the format of the
>> conferences to protect the profit center worse.=20
>=20
> Or adapting the format to attract more paying attendees, such a
> what we have sometimes called "tourists", with no real
> expectation that they will do work, because it increases the
> income.
>=20
> Still better than building a funding structure based on sale of
> publications, however :-(
>=20
>   john
>=20
>=20
>=20
>=20
>=20
>=20

                     					       _\\|//_
                           				      ( O-O )
   ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
                    				Simon Pietro Romano
             				 Universita' di Napoli Federico =
II
                		     Computer Engineering Department=20
	             Phone: +39 081 7683823 -- Fax: +39 081 7683816
                                           e-mail: spromano@unina.it

		    <<Molti mi dicono che lo scoraggiamento =CB l'alibi =
degli=20
		    idioti. Ci rifletto un istante; e mi scoraggio>>. =
Magritte.
               			                     oooO
  ~~~~~~~~~~~~~~~~~~~~~~~(   )~~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
					                 \ (            =
(   )
			                                  \_)          ) =
/
                                                                       =
(_/






--Apple-Mail=_64698137-19DE-4420-970F-A4CC12B813EC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi =
Kathleen,<div><br></div><div><div><blockquote type=3D"cite"><div>think. =
&nbsp;The tutorials is an interesting idea. &nbsp;I think youtube videos =
may be effective as well without having to schedule meetings for =
tutorials.<br></div></blockquote><div><br></div>I think the IETF =
leadership is already looking after this. Have a look =
at:</div><div><br></div><div><a =
href=3D"http://iaoc.ietf.org/">http://iaoc.ietf.org/</a></div><div><a =
href=3D"http://www.ietf.org/edu/process-oriented-tutorials.html#newcomers"=
>http://www.ietf.org/edu/process-oriented-tutorials.html#newcomers</a></di=
v><div><a =
href=3D"http://www.ietf.org/edu/process-oriented-tutorials.html#wgleadersh=
ip">http://www.ietf.org/edu/process-oriented-tutorials.html#wgleadership</=
a></div><div><a =
href=3D"http://www.ietf.org/edu/process-oriented-tutorials.html#creatingid=
s">http://www.ietf.org/edu/process-oriented-tutorials.html#creatingids</a>=
</div><div><a =
href=3D"http://www.ietf.org/edu/technical-tutorials.html#netconfandyang">h=
ttp://www.ietf.org/edu/technical-tutorials.html#netconfandyang</a></div><d=
iv><a =
href=3D"http://www.ietf.org/edu/technical-tutorials.html#opsandmanagement"=
>http://www.ietf.org/edu/technical-tutorials.html#opsandmanagement</a></di=
v><div><a =
href=3D"http://www.ietf.org/edu/technical-tutorials.html#routing">http://w=
ww.ietf.org/edu/technical-tutorials.html#routing</a></div><div><a =
href=3D"http://www.ietf.org/edu/technical-tutorials.html#security">http://=
www.ietf.org/edu/technical-tutorials.html#security</a></div><div><br></div=
><div>All of these have been recorded at recent IETF meetings, and some =
of them will be re-recorded at an enhanced quality level in order to =
improve the quality of experience for the end =
users.</div><div><br></div><div>Cheers,</div><div><br></div><div>Simon</di=
v><div><br><blockquote =
type=3D"cite"><div><br>Thanks,<br>Kathleen<br><br>-----Original =
Message-----<br>From: <a =
href=3D"mailto:ietf-bounces@ietf.org">ietf-bounces@ietf.org</a> =
[mailto:ietf-bounces@ietf.org] On Behalf Of John C Klensin<br>Sent: =
Thursday, July 11, 2013 11:17 AM<br>To: Phillip Hallam-Baker; Simon =
Pietro Romano<br>Cc: Keith Moore; <a =
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br>Subject: Re: IETF =
registration fee?<br><br><br><br>--On Thursday, July 11, 2013 10:34 =
-0400 Phillip Hallam-Baker<br>&lt;<a =
href=3D"mailto:hallam@gmail.com">hallam@gmail.com</a>&gt; =
wrote:<br><br><blockquote type=3D"cite">...<br></blockquote><blockquote =
type=3D"cite">Using paid conferences as a profit center is a risky long =
term<br></blockquote><blockquote type=3D"cite">prospect at best. =
Refusing to adapt the format of the<br></blockquote><blockquote =
type=3D"cite">conferences to protect the profit center worse. =
<br></blockquote><br>Or adapting the format to attract more paying =
attendees, such a<br>what we have sometimes called "tourists", with no =
real<br>expectation that they will do work, because it increases =
the<br>income.<br><br>Still better than building a funding structure =
based on sale of<br>publications, however :-(<br><br> =
&nbsp;&nbsp;john<br><br><br><br><br><br><br></div></blockquote></div><br><=
div apple-content-edited=3D"true">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">					=
</span><span class=3D"Apple-converted-space">&nbsp;</span>&nbsp; &nbsp; =
&nbsp; _\\|//_</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
</span>&nbsp; &nbsp; &nbsp;&nbsp;( O-O )</div><div>&nbsp; =
&nbsp;~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~</div><di=
v>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;<span class=3D"Apple-converted-space">&nbsp;</span><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
</span>Simon Pietro Romano</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;<span class=3D"Apple-tab-span" style=3D"white-space: pre; =
">				</span><span =
class=3D"Apple-converted-space">&nbsp;</span>Universita' di Napoli =
Federico II</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;&nbsp;<span class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
	</span>&nbsp; &nbsp; &nbsp;Computer Engineering =
Department&nbsp;</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	</span>&nbsp; &nbsp; &nbsp;&nbsp; &nbsp; =
&nbsp; &nbsp; Phone: +39 081 7683823 -- Fax: +39 081 =
7683816</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;e-mail: <a =
href=3D"mailto:spromano@unina.it">spromano@unina.it</a></div><div><br></di=
v><div><span class=3D"Apple-tab-span" style=3D"white-space: pre; ">		=
</span>&nbsp; &nbsp; &lt;&lt;Molti mi dicono che lo scoraggiamento =CB =
l'alibi degli&nbsp;</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">		</span>&nbsp;&nbsp; =
&nbsp;idioti. Ci rifletto un istante; e mi scoraggio&gt;&gt;. =
Magritte.</div><div>&nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; =
&nbsp;<span class=3D"Apple-converted-space">&nbsp;</span><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">			=
</span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;oooO</div><div>&nbsp; ~~~~~~~~~~~~~~~~~~~~~~~( &nbsp; =
)~~~&nbsp;Oooo~~~~~~~~~~~~~~~~~~~~~~~~~</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
	</span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;\ ( &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;( &nbsp; =
)</div><div><span class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
		</span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
\_) &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;) /</div><div>&nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp;(_/</div></div><div><br></div></div><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<br></div></body></html>=

--Apple-Mail=_64698137-19DE-4420-970F-A4CC12B813EC--

From moore@network-heretics.com  Thu Jul 11 09:10:17 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2041921F9F95 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 09:10:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.474
X-Spam-Level: 
X-Spam-Status: No, score=-3.474 tagged_above=-999 required=5 tests=[AWL=0.125,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fXSl6FjwMHb5 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 09:10:12 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id 4CC2021F9B89 for <ietf@ietf.org>; Thu, 11 Jul 2013 09:10:10 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 8F8C420162; Thu, 11 Jul 2013 12:09:38 -0400 (EDT)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute2.internal (MEProxy); Thu, 11 Jul 2013 12:09:38 -0400
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 :content-transfer-encoding; s=smtpout; bh=9pH2FJ2fGQTOJlzQIqIowV OiBFI=; b=fbkWQbbp9vnaSqB0dFG87Jc9pm6nvKxhO0+iu8HDi8csoCsegDFOhh zS3nd3IICNTBBsfr9KpLmGI6RJLFyRPNtMF3Z9q+pKzaDl6PAR1AbxlnmwHeEM22 usTCyhjotKPXNRZP2JRvKB37X9RkoDLONHOEiojsWptzKml/TXhJk=
X-Sasl-enc: 8zrUUT/Bc+OEAviBA3PhJBKgzv83txAQaTqAhDrpPiZM 1373558978
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 865C368028F; Thu, 11 Jul 2013 12:09:37 -0400 (EDT)
Message-ID: <51DED8B8.3030306@network-heretics.com>
Date: Thu, 11 Jul 2013 12:09:28 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
Subject: Re: IETF registration fee?
References: <CE0388EA.21B7F%Josh.Howlett@ja.net> <803FCD9A-6B8A-45EC-914F-E2114C581EA1@gmail.com> <C053B4F4-4821-4132-B872-3F8A611B2F5F@unina.it> <CAMm+Lwjpw6uodpZHuQ-rW4hJ7ViUHqrFBwTJYGkXCtH1c2x1ww@mail.gmail.com> <C66F2B4BC73DB85224494CB1@JcK-HP8200.jck.com> <F5063677821E3B4F81ACFB7905573F24DF2F8111@MX15A.corp.emc.com>
In-Reply-To: <F5063677821E3B4F81ACFB7905573F24DF2F8111@MX15A.corp.emc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: John C Klensin <john-ietf@jck.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 16:10:17 -0000

On 07/11/2013 11:39 AM, Moriarty, Kathleen wrote:
> The tutorials is an interesting idea.  I think youtube videos may be effective as well without having to schedule meetings for tutorials.
Note that I was suggesting tutorials as a revenue source for IETF.     I 
doubt that youtube videos would work well for this.

Keith


From ted.ietf@gmail.com  Thu Jul 11 10:01:36 2013
Return-Path: <ted.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19A0F21F9983 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 10:01:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level: 
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[AWL=-0.386, BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id boKKkr24P+UY for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 10:01:35 -0700 (PDT)
Received: from mail-ie0-x233.google.com (mail-ie0-x233.google.com [IPv6:2607:f8b0:4001:c03::233]) by ietfa.amsl.com (Postfix) with ESMTP id 4B4BF21F9974 for <ietf@ietf.org>; Thu, 11 Jul 2013 10:01:35 -0700 (PDT)
Received: by mail-ie0-f179.google.com with SMTP id c10so17749743ieb.24 for <ietf@ietf.org>; Thu, 11 Jul 2013 10:01:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=4L9H6eamCNxHBTT6jYOE2KtekDbEAwRtPuXFVTE/cCM=; b=uEOVtEwZt+pitAr29F+Soj73iRB9i4AbYZHMxx+aLhNiCYOZaMb3heCeXEeDnL0Aie SkddwXGyuaclWipzDA9ebyel486ZbTif2xiNzxx2gMIVbf+SQYMcz+6pH94TNPjzOm5b 4zvNjhBBP4y03VLgNbfWuvt5o6HAU226b8gWqg8v83TuJ0Tcs0l21UNCrhzGPIPBrbmu l4JvBV5YmIoxsTPhvRnE6fK0wUo7E1/SNWJiwvmbsfmpmSQB3/muyPx8zdm0kgIKj/4G z5PF7kHzRg4XTkHDFhYi/mP+gkO96bubz+R4auOMnGmVARLLmhj7R+ScZnIP69MeG0l6 0+Ng==
MIME-Version: 1.0
X-Received: by 10.50.164.167 with SMTP id yr7mr8445890igb.22.1373562094768; Thu, 11 Jul 2013 10:01:34 -0700 (PDT)
Received: by 10.42.29.202 with HTTP; Thu, 11 Jul 2013 10:01:34 -0700 (PDT)
In-Reply-To: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com>
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com>
Date: Thu, 11 Jul 2013 10:01:34 -0700
Message-ID: <CA+9kkMDZoX0Eq4TcbpP=+YMPmq-F3CAGB1dSogYJa6V2F-irbQ@mail.gmail.com>
Subject: Re: Regarding call Chinese names
From: Ted Hardie <ted.ietf@gmail.com>
To: Hui Deng <denghui02@gmail.com>
Content-Type: multipart/alternative; boundary=089e0122a7fcbc5c4204e13f584a
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 17:01:36 -0000

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

Howdy,

Thanks for your efforts.  I would suggest, however, that you re-title your
drafts so that "Chinese" is restricted to the populations which use pinyin
and have standardized on what English speakers call Mandarin (=E5=9C=8B=E8=
=AA=9E
or =E6=99=AE=E9=80=9A=E8=A9=B1, depending on your background).  Those who u=
se  romanizations based
on other dialects, in line with their familial pronunciation, would
otherwise be treated as not "Chinese".

regards,

Ted Hardie


On Wed, Jul 10, 2013 at 5:04 PM, Hui Deng <denghui02@gmail.com> wrote:

> Hello all
>
> We submitted two drafts to help people here to correctly call chinese
> people names:
>
> http://tools.ietf.org/html/draft-deng-call-chinese-names-00
>
>    http://tools.ietf.org/html/draft-zcao-chinese-pronounce-00
>
>
>
> Feel free to let us know if you have any other issues?
>
> Best regards,
>
>
>
> -Hui Deng
>

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

Howdy,<br><br>Thanks for your efforts.=C2=A0 I would suggest, however, that=
 you re-title your drafts so that &quot;Chinese&quot; is restricted to the =
populations which use pinyin and have standardized on what English speakers=
 call Mandarin (=E5=9C=8B=E8=AA=9E<br>
or =E6=99=AE=E9=80=9A=E8=A9=B1, depending on your background).=C2=A0 Those =
who use=C2=A0 romanizations based on other dialects, in line with their fam=
ilial pronunciation, would otherwise be treated as not &quot;Chinese&quot;.=
=C2=A0 <br><br>regards,<br><br>Ted Hardie<br>
<br><br><div class=3D"gmail_quote">On Wed, Jul 10, 2013 at 5:04 PM, Hui Den=
g <span dir=3D"ltr">&lt;<a href=3D"mailto:denghui02@gmail.com" target=3D"_b=
lank">denghui02@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex">
<div dir=3D"ltr"><div>Hello all</div><div>=C2=A0</div><div>We submitted two=
 drafts to help people here to correctly call chinese people names:</div><d=
iv><font color=3D"#000000" face=3D"=E5=AE=8B=E4=BD=93" size=3D"3">

</font><p style=3D"margin:0cm 0cm 0pt"><span lang=3D"EN-US"><a href=3D"http=
://tools.ietf.org/html/draft-deng-call-chinese-names-00" target=3D"_blank">=
<span style=3D"background:white;color:rgb(17,85,204);font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;;font-size:10pt">http://tools.ietf.org/html/d=
raft-deng-call-chinese-names-00</span></a></span><span style=3D"background:=
white;color:rgb(34,34,34);font-family:&quot;Arial&quot;,&quot;sans-serif&qu=
ot;;font-size:10pt" lang=3D"EN-US">=C2=A0</span></p>

<font color=3D"#000000" face=3D"=E5=AE=8B=E4=BD=93" size=3D"3">

</font><p style=3D"margin:0cm 0cm 0pt"><span style=3D"background:white;colo=
r:rgb(34,34,34);font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;font-s=
ize:10pt" lang=3D"EN-US">=C2=A0 =C2=A0</span><span lang=3D"EN-US"><a href=
=3D"http://tools.ietf.org/html/draft-zcao-chinese-pronounce-00" target=3D"_=
blank"><span style=3D"background:white;color:rgb(17,85,204);font-family:&qu=
ot;Arial&quot;,&quot;sans-serif&quot;;font-size:10pt">http://tools.ietf.org=
/html/draft-zcao-chinese-pronounce-00</span></a></span></p>

<p style=3D"margin:0cm 0cm 0pt"><span lang=3D"EN-US"></span>=C2=A0</p><p st=
yle=3D"margin:0cm 0cm 0pt"><span lang=3D"EN-US">Feel free to let us know if=
 you have any other issues?</span></p><p style=3D"margin:0cm 0cm 0pt"><span=
 lang=3D"EN-US">Best regards,</span></p>
<span class=3D"HOEnZb"><font color=3D"#888888">
<p style=3D"margin:0cm 0cm 0pt"><span lang=3D"EN-US"></span>=C2=A0</p><p st=
yle=3D"margin:0cm 0cm 0pt"><span lang=3D"EN-US">-Hui Deng</span></p><font c=
olor=3D"#000000" face=3D"=E5=AE=8B=E4=BD=93" size=3D"3">

</font></font></span></div></div>
</blockquote></div><br>

--089e0122a7fcbc5c4204e13f584a--

From melinda.shore@gmail.com  Thu Jul 11 10:03:26 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AAF0621F9A70 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 10:03:26 -0700 (PDT)
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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OL+09NUBdjzu for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 10:03:26 -0700 (PDT)
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 4835B21F9974 for <ietf@ietf.org>; Thu, 11 Jul 2013 10:03:26 -0700 (PDT)
Received: by mail-pa0-f42.google.com with SMTP id rl6so8089012pac.29 for <ietf@ietf.org>; Thu, 11 Jul 2013 10:03:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=scndm22Rv7eBp4selpB9gxiLVGhhuNQo/Q0M94rGEHM=; b=M95FXnk7Ra4Zyv1DB7dBgRobH0tK5jbVLv/fiHEdS7/XeHVEA8mG71RIvrsRNjjTQ5 RoSoJT64oF9EYUylXwU89Xs71QqWaPlJpPbHHCDc/0jziVObrBdkenITEHEA2uUD2ml/ krUN8xmbSzqFGk9J/xzq54Q3WxKzVnzaqJnYGW3wNRlUeUuTi6xC9x0ICVn/9Xj4QJ/H /iF6Hd06p5JF+eF2SlDsCmGryAgidfuMqge0lpPEbjfueBljKK+k39anCiim+oqVJbI0 SA3r179N/4FBanrLr9j8+wRj+wvGvyF6eJcqQ9wh91gtxoBfZJ0ngoILMVW/9rSfYDUQ 5Clw==
X-Received: by 10.66.224.237 with SMTP id rf13mr39653204pac.26.1373562205003;  Thu, 11 Jul 2013 10:03:25 -0700 (PDT)
Received: from spandex.local (216-67-40-63-rb1.fai.dsl.dynamic.acsalaska.net. [216.67.40.63]) by mx.google.com with ESMTPSA id ve3sm40683154pbc.14.2013.07.11.10.03.23 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 11 Jul 2013 10:03:24 -0700 (PDT)
Message-ID: <51DEE55A.4050402@gmail.com>
Date: Thu, 11 Jul 2013 09:03:22 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Regarding call Chinese names
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com> <0B65E3C66FCF4F459F93A1A5767BB35A034AD02C@lhreml514-mbx> <alpine.DEB.2.00.1307111201190.8891@uplift.swm.pp.se> <CANF0JMAuRm2c+-L0SzD902vAt4gdsWqawVMt6=MLkkNkmza6RQ@mail.gmail.com>
In-Reply-To: <CANF0JMAuRm2c+-L0SzD902vAt4gdsWqawVMt6=MLkkNkmza6RQ@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 17:03:26 -0000

On 7/11/13 4:14 AM, Hui Deng wrote:
> I personally feel that this is maybe one of not easier part for western
> people to do in today IETF.  and chinese's names sound maybe more
> diffcult than other eastern languages.

I know it is for me, and I'm grateful for the draft.  I agree
that this is probably not appropriate for publication as an RFC
but it would certainly be useful to find someplace for it in the
wiki.  The chairs wiki might be an option but I think it's of
broader interest and use.

Melinda


From ajs@anvilwalrusden.com  Thu Jul 11 10:34:05 2013
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C535721F9EDB for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 10:34:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.747
X-Spam-Level: 
X-Spam-Status: No, score=-0.747 tagged_above=-999 required=5 tests=[AWL=0.093,  BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r8aJmoUVu0hw for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 10:34:01 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id DB15921F9EB8 for <ietf@ietf.org>; Thu, 11 Jul 2013 10:33:58 -0700 (PDT)
Received: from mx1.yitter.info (nat-07-mht.dyndns.com [216.146.45.246]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 6404C8A031; Thu, 11 Jul 2013 17:33:57 +0000 (UTC)
Date: Thu, 11 Jul 2013 13:33:38 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: IAB Statement on Dotless Domains
Message-ID: <20130711173337.GA4207@mx1.yitter.info>
References: <1984CBB8-6862-4DBB-AFAE-F8461E694083@vigilsec.com> <6.2.5.6.2.20130710180152.100c7ed0@resistor.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6.2.5.6.2.20130710180152.100c7ed0@resistor.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: iab@iab.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 17:34:06 -0000

Hi,

On Wed, Jul 10, 2013 at 08:23:36PM -0700, S Moonesamy wrote:

> responsibility about the RFC Series.  The IAB statement refers to
> RFCs from the www.faqs.org website.

Thanks for pointing this out.  It is indeed embarrassing.  This was a
clerical error.  We have fixed it.

By way of explanation: we used a wiki to develop the statement
collaboratively.  It turns out that the wiki software automatically
creates links to the faq.org listing of RFCs whenever "RFC NNNN" shows
up in running text.  We failed to remove these (auto-generated) links
when we posted the statement on the IAB site, so that's why they
showed up.  We'll be more careful about this in future.

Best regards,

Andrew (as an IAB member)

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From jnc@mercury.lcs.mit.edu  Thu Jul 11 10:35:05 2013
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C56821F9F31 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 10:35:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dF+xVvjWrcW2 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 10:35:00 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 5291F21F9F03 for <ietf@ietf.org>; Thu, 11 Jul 2013 10:35:00 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 87B0518C08B; Thu, 11 Jul 2013 13:34:57 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: Regarding call Chinese names
Message-Id: <20130711173457.87B0518C08B@mercury.lcs.mit.edu>
Date: Thu, 11 Jul 2013 13:34:57 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 17:35:05 -0000

    > From: Melinda Shore <melinda.shore@gmail.com>

    > I agree that this is probably not appropriate for publication as an RFC
    > but it would certainly be useful to find someplace for it in the wiki. 

Actually, it would be good to have a series of these (or maybe one page with
a number of sections): we could also use one for Hispanic names (patronymic
_and_ matronymic 'family name'), for cultures which only use _one_ name (no
family names), etc, etc.

And as Patrik points out, there are also the Icelanders.. :-)

	Noel

From akatlas@gmail.com  Thu Jul 11 10:46:03 2013
Return-Path: <akatlas@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D8F821F9B07 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 10:46:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.183
X-Spam-Level: 
X-Spam-Status: No, score=-2.183 tagged_above=-999 required=5 tests=[AWL=0.416,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HX3TgNA+AXU6 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 10:46:02 -0700 (PDT)
Received: from mail-ie0-x235.google.com (mail-ie0-x235.google.com [IPv6:2607:f8b0:4001:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id 6F39D11E818C for <ietf@ietf.org>; Thu, 11 Jul 2013 10:45:39 -0700 (PDT)
Received: by mail-ie0-f181.google.com with SMTP id x12so18822184ief.12 for <ietf@ietf.org>; Thu, 11 Jul 2013 10:45:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=jw6Y7FS2DrIyvJIjPbV83Q8DQhUh2X83derqoRZGI28=; b=VsfP5gRfN2Wa8NHdMAYIkAcov1C4CpJrVDF82X7EQMY4S3iU6j4CGzOeDpo7CG0+jj T4jRpWj0tIzMxmpDrzsH8T+JFQSPUtkbivRsvzQ286rmgIIjuM8b7H950u5IKWOMUz5p 1cg0DIMpDYTsqEPPemQjKzjsXK7Xyo04XxX725e6vX8XmrKYbn3AHwajBayKDGRHtHBj qLzXA8GvOI1nVhE8zuZdNPSxZvD4aB0L87RUsEZY9cbB+S8o5hnRtAt4op4Q8JXZ7tay DzmBLfAn7qw4L3KNYOGPXnHxBiHSLbZxq+l19S2V+DvY2oZa9yDJOO5GcOHg+EYraTK/ K/0w==
MIME-Version: 1.0
X-Received: by 10.50.1.20 with SMTP id 20mr37359789igi.56.1373564737941; Thu, 11 Jul 2013 10:45:37 -0700 (PDT)
Received: by 10.64.47.168 with HTTP; Thu, 11 Jul 2013 10:45:37 -0700 (PDT)
In-Reply-To: <51DED8B8.3030306@network-heretics.com>
References: <CE0388EA.21B7F%Josh.Howlett@ja.net> <803FCD9A-6B8A-45EC-914F-E2114C581EA1@gmail.com> <C053B4F4-4821-4132-B872-3F8A611B2F5F@unina.it> <CAMm+Lwjpw6uodpZHuQ-rW4hJ7ViUHqrFBwTJYGkXCtH1c2x1ww@mail.gmail.com> <C66F2B4BC73DB85224494CB1@JcK-HP8200.jck.com> <F5063677821E3B4F81ACFB7905573F24DF2F8111@MX15A.corp.emc.com> <51DED8B8.3030306@network-heretics.com>
Date: Thu, 11 Jul 2013 13:45:37 -0400
Message-ID: <CAG4d1rekxN9SOgTnDU+3vS5-C7oy9xdOYKLR0oUgvAXRPsEbxQ@mail.gmail.com>
Subject: Re: IETF registration fee?
From: Alia Atlas <akatlas@gmail.com>
To: Keith Moore <moore@network-heretics.com>
Content-Type: multipart/alternative; boundary=e89a8f64303447f8fe04e13ff6ef
Cc: John C Klensin <john-ietf@jck.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 17:46:03 -0000

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

On Thu, Jul 11, 2013 at 12:09 PM, Keith Moore <moore@network-heretics.com>wrote:

> On 07/11/2013 11:39 AM, Moriarty, Kathleen wrote:
>
>> The tutorials is an interesting idea.  I think youtube videos may be
>> effective as well without having to schedule meetings for tutorials.
>>
> Note that I was suggesting tutorials as a revenue source for IETF.     I
> doubt that youtube videos would work well for this.


But perhaps using some of the Massive On-line Courses infrastructure could?
 That would provide the key benefit of being able to clarify and ask
questions above and beyond a video without requiring physical colocation.

Alia

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

<div dir=3D"ltr">On Thu, Jul 11, 2013 at 12:09 PM, Keith Moore <span dir=3D=
"ltr">&lt;<a href=3D"mailto:moore@network-heretics.com" target=3D"_blank">m=
oore@network-heretics.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extr=
a"><div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On 07/11/2013 11:39 AM, Mo=
riarty, Kathleen wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
The tutorials is an interesting idea. =A0I think youtube videos may be effe=
ctive as well without having to schedule meetings for tutorials.<br>
</blockquote></div>
Note that I was suggesting tutorials as a revenue source for IETF. =A0 =A0 =
I doubt that youtube videos would work well for this.</blockquote><div><br>=
</div><div>But perhaps using some of the Massive On-line Courses infrastruc=
ture could? =A0That would provide the key benefit of being able to clarify =
and ask questions above and beyond a video without requiring physical coloc=
ation.</div>
<div><br></div><div>Alia=A0</div></div></div></div>

--e89a8f64303447f8fe04e13ff6ef--

From wesley.george@twcable.com  Thu Jul 11 11:29:43 2013
Return-Path: <wesley.george@twcable.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65C8F21F9FCE for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 11:29:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.563
X-Spam-Level: 
X-Spam-Status: No, score=-0.563 tagged_above=-999 required=5 tests=[AWL=-0.100, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a3s3HolRUybQ for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 11:29:38 -0700 (PDT)
Received: from cdcipgw01.twcable.com (cdcipgw01.twcable.com [165.237.91.110]) by ietfa.amsl.com (Postfix) with ESMTP id 167D521F9F9C for <ietf@ietf.org>; Thu, 11 Jul 2013 11:29:38 -0700 (PDT)
X-SENDER-IP: 10.136.163.10
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.89,1045,1367985600"; d="scan'208";a="32245846"
Received: from unknown (HELO PRVPEXHUB01.corp.twcable.com) ([10.136.163.10]) by cdcipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 11 Jul 2013 14:29:28 -0400
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.79]) by PRVPEXHUB01.corp.twcable.com ([10.136.163.10]) with mapi; Thu, 11 Jul 2013 14:29:35 -0400
From: "George, Wes" <wesley.george@twcable.com>
To: Melinda Shore <melinda.shore@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
Date: Thu, 11 Jul 2013 14:29:35 -0400
Subject: RE: Regarding call Chinese names
Thread-Topic: Regarding call Chinese names
Thread-Index: Ac5+WaoPIx0Cd+Y/TWemnGxdqBaFfAAAQGEQ
Message-ID: <2671C6CDFBB59E47B64C10B3E0BD5923043722F56B@PRVPEXVS15.corp.twcable.com>
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com> <0B65E3C66FCF4F459F93A1A5767BB35A034AD02C@lhreml514-mbx> <alpine.DEB.2.00.1307111201190.8891@uplift.swm.pp.se> <CANF0JMAuRm2c+-L0SzD902vAt4gdsWqawVMt6=MLkkNkmza6RQ@mail.gmail.com> <51DEE55A.4050402@gmail.com>
In-Reply-To: <51DEE55A.4050402@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 18:29:43 -0000

> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Melinda Shore

> I agree
> that this is probably not appropriate for publication as an RFC
> but it would certainly be useful to find someplace for it in the
> wiki.  The chairs wiki might be an option but I think it's of
> broader interest and use.
>
> Melinda

[WEG] I think writing language documentation isn't really a good use of IET=
F resources, even at an individual level, because neither the problem nor t=
he knowledge necessary to address it is specific to the IETF, nor is the pr=
oblem limited to Mandarin participants. As others have noted, this is just =
one of many languages represented by IETFers that we'd have to treat simila=
rly.
Further, an I-D is not a particularly useful format in which to present the=
 info. Raw text in the form of "$phoneme as in $English_word" may not alway=
s be helpful, especially to nonnative English speakers who now have to work=
 through two layers of pronunciation.  Being able to click on a button to h=
ear sample pronunciations, especially in the case of words where tones matt=
er, is very helpful.

So if pronunciation guides end up in the Wiki or the Tao or some other yet =
to be written Diversity and Cultural guide hosted within IETF, I think it's=
 more useful to simply reference things already extant instead of generatin=
g our own. Those representing the language in question could certainly help=
 us to source and vet the information, but that's much quicker and more eff=
icient than writing it themselves.
Protocol reuse, hurray! :-)
e.g.
http://mandarin.about.com/od/pronunciation/a/How-To-Pronounce-Mandarin-Chin=
ese.htm
http://en.wikibooks.org/wiki/Japanese/Pronunciation
http://en.wikipedia.org/wiki/Swedish_phonology

To be clear, I'm not saying that this doesn't expose a real problem, and th=
e draft certainly drew attention to it, but I also don't think that more do=
cumentation will solve it, especially since the information is already read=
ily available in more accessible formats. I think what you'll find is that =
there are two types of folks (in IETF and generally) - those who see an att=
empt at proper pronunciation and cultural awareness as important and worth =
making extra effort to learn proactively, and those who believe that if it'=
s an issue, the person on the receiving end will correct them when they get=
 it wrong (and hopefully not repeat the mistake).
Not making a value judgment on either, merely an observation.

Thanks
Wes George

PS: guess which one is my given name and which my surname? Even native Engl=
ish speakers aren't immune from name confusion. :-)


Anything below this line has been added by my company's mail server, I have=
 no control over it.
-----------------

This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From joseph.yee@gmail.com  Thu Jul 11 12:50:00 2013
Return-Path: <joseph.yee@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8248021F99A9 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 12:50:00 -0700 (PDT)
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=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dAOjjl7PRjvV for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 12:49:59 -0700 (PDT)
Received: from mail-ie0-x229.google.com (mail-ie0-x229.google.com [IPv6:2607:f8b0:4001:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id C2A6021F9AAB for <ietf@ietf.org>; Thu, 11 Jul 2013 12:49:59 -0700 (PDT)
Received: by mail-ie0-f169.google.com with SMTP id 10so18817195ied.14 for <ietf@ietf.org>; Thu, 11 Jul 2013 12:49:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=YUXKrqY4WFACBditBM5G96UViG4BjyeKwbuANDydDn4=; b=MF4bbuGiqK/LnRNrnNzhmxITXYXbLv5anUEdkg2SigdFxe9PgpSNRPOG70vZ6fVJSy 85jJJRIDqZj00/mBi3JwEGkF/OL+OMFxiagtyhBMiXa8ZIWrCHhvz2HoK3nlVFo1RUeW 105lIX5XrR7UKWbkSsJHdhe2OM7U7OGh0gNz6z0U7adhzHLNGleQiqaZUEgXhxmXFadH jLEvKnBgsFvNBPPnJI9+g4vEMl9goMnz4QiWeOTDr1fN0dPth9bkNjOdzZFy1ruW4KdB EuGe3bmOb6shDCqHF5MUo3IGO+kR+9RiZZDVBeXZN1Ckw5eRmsift1K0WXzIc4e5vfL1 z5xA==
MIME-Version: 1.0
X-Received: by 10.43.14.74 with SMTP id pp10mr2939794icb.87.1373572198752; Thu, 11 Jul 2013 12:49:58 -0700 (PDT)
Received: by 10.64.49.108 with HTTP; Thu, 11 Jul 2013 12:49:58 -0700 (PDT)
In-Reply-To: <CAF4+nEF_VnR2DNd_LDehXwJNn=0CT0Qkz3hKrBHuffVFvdXLMg@mail.gmail.com>
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com> <51DEB9F2.9040405@viagenie.ca> <F108A063F7E85E5F9C89ADBF@caldav.corp.apple.com> <CAF4+nEF_VnR2DNd_LDehXwJNn=0CT0Qkz3hKrBHuffVFvdXLMg@mail.gmail.com>
Date: Thu, 11 Jul 2013 15:49:58 -0400
Message-ID: <CADRqEyqEmj9t6CmTnj95y9b6H=UfKpo6cJs4VZrtTdHdPur2SQ@mail.gmail.com>
Subject: Re: Regarding call Chinese names
From: Joseph Yee <joseph.yee@gmail.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Content-Type: multipart/alternative; boundary=bcaec519692ffae98104e141b2c3
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 19:50:00 -0000

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

+1

And should remove middle-name / middle-initial.  It's very bad.

Joseph


On Thu, Jul 11, 2013 at 11:40 AM, Donald Eastlake <d3e3e3@gmail.com> wrote:

> First/Last = bad/ambiguous
>
> Family (or maybe inherited) / Given = good
>
> Thanks,
> Donald
> =============================
>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>  155 Beaver Street, Milford, MA 01757 USA
>  d3e3e3@gmail.com
>
>
> On Thu, Jul 11, 2013 at 10:22 AM, Cyrus Daboo <cyrus@daboo.name> wrote:
> > Hi Simon,
> >
> >
> > --On July 11, 2013 at 3:58:10 PM +0200 Simon Perreault
> > <simon.perreault@viagenie.ca> wrote:
> >
> >>> We submitted two drafts to help people here to correctly call chinese
> >>> people names:
> >>>
> >>> http://tools.ietf.org/html/draft-deng-call-chinese-names-00
> >>>    http://tools.ietf.org/html/draft-zcao-chinese-pronounce-00
> >>
> >>
> >> Very cool! Thanks for writing this!
> >>
> >> I have a question: I think I've seen Chinese names written in both
> >> orders. That is, sometimes "Hui Deng" will be written "Deng Hui". Am I
> >> right? Does this happen often? What is the most common order? Is there a
> >> way to guess what order a name is written in? Sometimes it's not easy
> >> for non-Sinophones to know which part is the given name and which part
> >> is the family name.
> >
> >
> > Well that actually brings up a good technical point!
> >
> > In iCalendar (RFC5545) we have properties to represent the organizer and
> > attendee of meetings. A parameter (attribute) of those properties is
> "CN" -
> > defined to be the "common name" of the corresponding calendar user.
> > Obviously that is a single string and typically the concatenation of
> first
> > name/last name. But that of course is a very "Western" approach.
> >
> > I have had several people request that iCalendar instead define new
> > parameters for "FIRST-NAME" and "LAST-NAME". That then gives clients the
> > option of re-ordering those for display purposes based on user locales
> and
> > preferences.
> >
> > So, from a technical standpoint, it seems better to always represent user
> > names using components (last, first, middle)? vCard does have an "N"
> > property where individual components of a name can be broken out.
> >
> > --
> > Cyrus Daboo
> >
>

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

<div dir=3D"ltr"><div><div>+1<br><br></div>And should remove middle-name / =
middle-initial.=C2=A0 It&#39;s very bad.<br><br></div>Joseph<br></div><div =
class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Thu, Jul 11, 20=
13 at 11:40 AM, Donald Eastlake <span dir=3D"ltr">&lt;<a href=3D"mailto:d3e=
3e3@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:1p=
x #ccc solid;padding-left:1ex">First/Last =3D bad/ambiguous<br>
<br>
Family (or maybe inherited) / Given =3D good<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>
=C2=A0Donald E. Eastlake 3rd =C2=A0 <a href=3D"tel:%2B1-508-333-2270" value=
=3D"+15083332270">+1-508-333-2270</a> (cell)<br>
=C2=A0155 Beaver Street, Milford, MA 01757 USA<br>
=C2=A0<a href=3D"mailto:d3e3e3@gmail.com">d3e3e3@gmail.com</a><br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
On Thu, Jul 11, 2013 at 10:22 AM, Cyrus Daboo &lt;<a href=3D"mailto:cyrus@d=
aboo.name">cyrus@daboo.name</a>&gt; wrote:<br>
&gt; Hi Simon,<br>
&gt;<br>
&gt;<br>
&gt; --On July 11, 2013 at 3:58:10 PM +0200 Simon Perreault<br>
&gt; &lt;<a href=3D"mailto:simon.perreault@viagenie.ca">simon.perreault@via=
genie.ca</a>&gt; wrote:<br>
&gt;<br>
&gt;&gt;&gt; We submitted two drafts to help people here to correctly call =
chinese<br>
&gt;&gt;&gt; people names:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; <a href=3D"http://tools.ietf.org/html/draft-deng-call-chinese-=
names-00" target=3D"_blank">http://tools.ietf.org/html/draft-deng-call-chin=
ese-names-00</a><br>
&gt;&gt;&gt; =C2=A0 =C2=A0<a href=3D"http://tools.ietf.org/html/draft-zcao-=
chinese-pronounce-00" target=3D"_blank">http://tools.ietf.org/html/draft-zc=
ao-chinese-pronounce-00</a><br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; Very cool! Thanks for writing this!<br>
&gt;&gt;<br>
&gt;&gt; I have a question: I think I&#39;ve seen Chinese names written in =
both<br>
&gt;&gt; orders. That is, sometimes &quot;Hui Deng&quot; will be written &q=
uot;Deng Hui&quot;. Am I<br>
&gt;&gt; right? Does this happen often? What is the most common order? Is t=
here a<br>
&gt;&gt; way to guess what order a name is written in? Sometimes it&#39;s n=
ot easy<br>
&gt;&gt; for non-Sinophones to know which part is the given name and which =
part<br>
&gt;&gt; is the family name.<br>
&gt;<br>
&gt;<br>
&gt; Well that actually brings up a good technical point!<br>
&gt;<br>
&gt; In iCalendar (RFC5545) we have properties to represent the organizer a=
nd<br>
&gt; attendee of meetings. A parameter (attribute) of those properties is &=
quot;CN&quot; -<br>
&gt; defined to be the &quot;common name&quot; of the corresponding calenda=
r user.<br>
&gt; Obviously that is a single string and typically the concatenation of f=
irst<br>
&gt; name/last name. But that of course is a very &quot;Western&quot; appro=
ach.<br>
&gt;<br>
&gt; I have had several people request that iCalendar instead define new<br=
>
&gt; parameters for &quot;FIRST-NAME&quot; and &quot;LAST-NAME&quot;. That =
then gives clients the<br>
&gt; option of re-ordering those for display purposes based on user locales=
 and<br>
&gt; preferences.<br>
&gt;<br>
&gt; So, from a technical standpoint, it seems better to always represent u=
ser<br>
&gt; names using components (last, first, middle)? vCard does have an &quot=
;N&quot;<br>
&gt; property where individual components of a name can be broken out.<br>
&gt;<br>
&gt; --<br>
&gt; Cyrus Daboo<br>
&gt;<br>
</div></div></blockquote></div><br></div>

--bcaec519692ffae98104e141b2c3--

From brian.e.carpenter@gmail.com  Thu Jul 11 13:50:15 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 449C011E8118 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 13:50:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.508
X-Spam-Level: 
X-Spam-Status: No, score=-102.508 tagged_above=-999 required=5 tests=[AWL=0.091, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B9m5gvN6++UE for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 13:50:14 -0700 (PDT)
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 9A43021F9FCF for <ietf@ietf.org>; Thu, 11 Jul 2013 13:50:14 -0700 (PDT)
Received: by mail-pa0-f42.google.com with SMTP id rl6so8314734pac.1 for <ietf@ietf.org>; Thu, 11 Jul 2013 13:50:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=pPk0Cynd9JdYrL4s+RgvPPortTx7gvO88U/BrIeXQp8=; b=vNKL2iZjICjLaUMMmgHUi4O1O3wBgkHPGLA3WEUBxXOFcWQUe1jiSEnxy/bVZsijAU tO3g8GgIboLNUXTU1v7Tca8EzUM08ATKNT+XqT47y1/iuj7d7rGMM+40GJ0F1+1LtkNi oummZduKnz2k5oC5yELrGO+qSQSHLEqJ7J75VYRGkeQxTyQjaSUJ7Yh4AsPPodZjKQx8 c8KE+9H92vudiWFyJqNPvMQoU1r4rRPfkb2TOzYunNiFU+euHAykmZL/JwfIlKuJ5qk7 mt+MEVI4ZNSg1moKtZ6FBY+2nAxo0PYnKCHWDqjFV9M01PAxiZFDDM/XYLhlysVWB1l/ 5/jA==
X-Received: by 10.68.52.10 with SMTP id p10mr38802089pbo.92.1373575811982; Thu, 11 Jul 2013 13:50:11 -0700 (PDT)
Received: from [192.168.178.23] (124.199.69.111.dynamic.snap.net.nz. [111.69.199.124]) by mx.google.com with ESMTPSA id ve3sm41429980pbc.14.2013.07.11.13.50.09 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 11 Jul 2013 13:50:11 -0700 (PDT)
Message-ID: <51DF1A8A.2040404@gmail.com>
Date: Fri, 12 Jul 2013 08:50:18 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Douglas Otis <doug.mtview@gmail.com>
Subject: Re: IETF registration fee?
References: <CE0388EA.21B7F%Josh.Howlett@ja.net>	<803FCD9A-6B8A-45EC-914F-E2114C581EA1@gmail.com> <C053B4F4-4821-4132-B872-3F8A611B2F5F@unina.it>
In-Reply-To: <C053B4F4-4821-4132-B872-3F8A611B2F5F@unina.it>
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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 20:50:15 -0000

Douglas,
...
>> Those traveling thousands of miles already confront many uncertainties.  Those that elect to participate remotely should be afforded greater certainty of being able to participate when problems occur at local venues or with transportation.  Increasing participation without the expense of the brick and mortar and travel should offer long term benefits and increased fairness. 

How much would you be willing to pay for remote participation
(assuming it was of high quality)?

$600 for the week (cookies and taxes not included)?

    Brian

From moore@network-heretics.com  Thu Jul 11 14:20:05 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D2FA21E804B for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 14:20:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.499
X-Spam-Level: 
X-Spam-Status: No, score=-3.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vBM81enIP5b5 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 14:20:00 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id 4CDAD11E8118 for <ietf@ietf.org>; Thu, 11 Jul 2013 14:20:00 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 0F0A320A2D for <ietf@ietf.org>; Thu, 11 Jul 2013 17:19:58 -0400 (EDT)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute5.internal (MEProxy); Thu, 11 Jul 2013 17:19:58 -0400
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=aofyXsWJW4Eu8q6KER8PnY M5cGM=; b=NnrVU0yREh6IzdRZD/quBOmWaa8G+cAzJChuG7DxziIU3afOGfQK1Z e7sTemYt7dSMyXeMI+1TBuSe+o9xnOoYp+do3mAN/FT4ecxfI35uCwUjgjrDV5QD LvuwqDn8yhVgrAIeYbDrYMdfVLYZXwNBRcFNCS3KOF2I5vzmCl7zE=
X-Sasl-enc: 2IM9b0RDpAyJxkcuiHet8nU9sSPf1XMhuogF+xGP1E8W 1373577597
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 66DBAC00E84; Thu, 11 Jul 2013 17:19:57 -0400 (EDT)
Message-ID: <51DF2173.4030902@network-heretics.com>
Date: Thu, 11 Jul 2013 17:19:47 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF registration fee?
References: <CE0388EA.21B7F%Josh.Howlett@ja.net>	<803FCD9A-6B8A-45EC-914F-E2114C581EA1@gmail.com> <C053B4F4-4821-4132-B872-3F8A611B2F5F@unina.it> <51DF1A8A.2040404@gmail.com>
In-Reply-To: <51DF1A8A.2040404@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 21:20:05 -0000

On 07/11/2013 04:50 PM, Brian E Carpenter wrote:
> Douglas,
> ...
>>> Those traveling thousands of miles already confront many uncertainties.  Those that elect to participate remotely should be afforded greater certainty of being able to participate when problems occur at local venues or with transportation.  Increasing participation without the expense of the brick and mortar and travel should offer long term benefits and increased fairness.
> How much would you be willing to pay for remote participation
> (assuming it was of high quality)?

Not much.   Remote participation misses the whole point of IETF 
meetings.   Sure, it's useful to be able to listen on WG sessions and 
make a comment or two.   But the WG sessions generally aren't actually 
worth very much, especially the way that they tend to be run these 
days.   The most important work gets done in the hallways and over food 
and drink.

So IETF is in this very strange position of supporting itself by 
charging a large amount of money for an activity that's mostly 
peripheral to getting useful work done.

Keith


From doug.mtview@gmail.com  Thu Jul 11 14:37:22 2013
Return-Path: <doug.mtview@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B22DA11E8183 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 14:37:22 -0700 (PDT)
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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y4ne4yi1fVo1 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 14:37:22 -0700 (PDT)
Received: from mail-yh0-x230.google.com (mail-yh0-x230.google.com [IPv6:2607:f8b0:4002:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id 275FC21F9F3C for <ietf@ietf.org>; Thu, 11 Jul 2013 14:37:21 -0700 (PDT)
Received: by mail-yh0-f48.google.com with SMTP id z12so3380912yhz.7 for <ietf@ietf.org>; Thu, 11 Jul 2013 14:37:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=THP8ga8JEN/hedAU/hUEDevyKdX2Tkw6g9XAIF1ny8U=; b=XabUjbJa3YcacclPLHdoOn8DRcG5vG0iEJV2FefaiTnge2j9qxOUHNk9vI5bt8nDgo 4TCZ4PL+fd2Ki6KsJUt5MXgMYQFdYdwSqTZqFRoQM2eMRdQjr4znNbuBbzFcXRPJhWNd GqGw5MYl65jWfUiTtaH6kS5vJZKlAsplbx5+9Tx+zAEFN0zx+k09+wQrVS86Ji1YKvy2 gDwa1baprii/GQiaIble+8jO3XMu7K6TD+dakbNrrrQW3Q9jBzF7Q+TbRVWc64ksaGPi 4SNhE9fP/Sqr6x/6A6FCivLJLPFvNTmyi5S9m+GjYa7y7w2ww4rZr+oZ8HAp2n1kAhyO Uxug==
X-Received: by 10.236.123.112 with SMTP id u76mr22381493yhh.59.1373578640588;  Thu, 11 Jul 2013 14:37:20 -0700 (PDT)
Received: from [192.168.0.54] (107-0-5-6-ip-static.hfc.comcastbusiness.net. [107.0.5.6]) by mx.google.com with ESMTPSA id s47sm23003262yhl.19.2013.07.11.14.37.18 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 11 Jul 2013 14:37:19 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: IETF registration fee?
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <51DF1A8A.2040404@gmail.com>
Date: Thu, 11 Jul 2013 14:37:18 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <E3893DC9-363F-4553-B7FC-12202FE8EC6C@gmail.com>
References: <CE0388EA.21B7F%Josh.Howlett@ja.net>	<803FCD9A-6B8A-45EC-914F-E2114C581EA1@gmail.com> <C053B4F4-4821-4132-B872-3F8A611B2F5F@unina.it> <51DF1A8A.2040404@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1508)
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 21:37:22 -0000

On Jul 11, 2013, at 1:50 PM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:

> Douglas,
> ...
>>> Those traveling thousands of miles already confront many =
uncertainties.  Those that elect to participate remotely should be =
afforded greater certainty of being able to participate when problems =
occur at local venues or with transportation.  Increasing participation =
without the expense of the brick and mortar and travel should offer long =
term benefits and increased fairness.=20
>=20
> How much would you be willing to pay for remote participation
> (assuming it was of high quality)?
>=20
> $600 for the week (cookies and taxes not included)?

Dear Brian,

A $600 price would represent a significant savings for most participants =
traveling large distances and using hotels.  If remote participants were =
given a first class status, such that even when physical venues lost =
Internet access, meetings continued.  The number of overall participants =
should increase and have the effect of demanding much lower meeting =
fees.

I suspect this will require abandoning the use of unmoderated inbound =
access to audio channels.  This has not worked very well.  Echo =
cancelation, noise, and disruption is likely too problematic as well as =
resource intensive.  Whatever is used must be rock solid.

The IETF already supports a hallway channel.  When the goal is to sell =
products or services, face-to-face becomes far more important.  There =
are many other organizations better at playing that role.  I have also =
experienced these face-to-face meetings many times being used to subvert =
ongoing efforts.  Strictly moderated and fully recorded meetings hold a =
greater promise of providing fairness.=20

Imagine XMPP as a control channel for moderators in conjunction with =
meeting channels that automatically recognize requests to speak. The =
meeting agenda should already indicate who is to speak, with their =
presentations available before the beginning of the meetings.  Nothing =
could  be done without everything being recorded and available remotely.=20=


Regards,
Douglas Otis=

From prvs=79044d999c=aallen@blackberry.com  Thu Jul 11 15:25:05 2013
Return-Path: <prvs=79044d999c=aallen@blackberry.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F52011E81B9 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 15:25:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.203
X-Spam-Level: 
X-Spam-Status: No, score=-5.203 tagged_above=-999 required=5 tests=[AWL=0.001,  BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f11pA5Txyh7Y for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 15:25:00 -0700 (PDT)
Received: from mhs060cnc.rim.net (mhs060cnc.rim.net [208.65.73.34]) by ietfa.amsl.com (Postfix) with ESMTP id 15A4511E8129 for <ietf@ietf.org>; Thu, 11 Jul 2013 15:24:59 -0700 (PDT)
X-AuditID: 0a41282f-b7fb96d0000066bb-51-51df30b22c42
Received: from XCT102ADS.rim.net (xct102ads.rim.net [10.67.111.43]) by mhs060cnc.rim.net (SBG) with SMTP id 5C.10.26299.2B03FD15; Thu, 11 Jul 2013 17:24:50 -0500 (CDT)
Received: from XMB104ADS.rim.net ([fe80::2494:a63d:e3:723b]) by XCT102ADS.rim.net ([fe80::4806:2e1d:2b7c:cfdf%22]) with mapi id 14.02.0328.009; Thu, 11 Jul 2013 17:24:50 -0500
From: Andrew Allen <aallen@blackberry.com>
To: "moore@network-heretics.com" <moore@network-heretics.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: IETF registration fee?
Thread-Topic: IETF registration fee?
Thread-Index: AQHOfZNs9+3G9+ovWkC6ol6WAqusl5lelWGAgAAONoCAAADwAIAAETCAgAAI24CAACWAAIAAmIyAgADMjQCAAAg9gP//vlu8
Date: Thu, 11 Jul 2013 22:24:49 +0000
Message-ID: <BBF5DDFE515C3946BC18D733B20DAD2338DC5B5A@XMB104ADS.rim.net>
In-Reply-To: <51DF2173.4030902@network-heretics.com>
Accept-Language: en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.67.110.251]
Content-Type: text/plain; charset="iso-8859-1"
content-transfer-encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrBKsWRmVeSWpSXmKPExsXC5ZyvrbvJ4H6gwf7TFhbPNs5nsZj09Ryb A5PHkiU/mTwmnQgLYIpqYLRJSiwpC85Mz9O3s0nMy8svSSxJVUhJLU62VfJJTU/MUQgoyixL TK5UcMksTs5JzMxNLVJSyEyxVTJRUijISUxOzU3NK7FVSiwoSM1LUbLjUsAANkBlmXkKqXnJ +SmZeem2Sp7B/roWFqaWuoZKdroJnTwZJx42sBVc4K3YfXYSWwPjb64uRk4OCQETiUNvZjNC 2GISF+6tZ+ti5OIQEljJKLHtxSlWCGczo8Ts5QfYQarYBLQk9h+ezgRiiwgkSOx7e4kFxBYW UJa48f8pUDcHUFxF4uL1GIiSPIldM86ygtgsAqoSv6ftBFvGK+AhsWDiCrCRnEBHHLvdBBZn FJCV2H32Oth4ZgFxiVtP5jNBHCcgsWTPeWYIW1Ti5eN/rBC2osSMPfNZIer1JG5MncIGYWtL LFv4mhlil6DEyZlPWCYwisxCMnYWkpZZSFpmIWlZwMiyilEwN6PYwMwgOS9ZrygzVy8vtWQT IyjqHTX0dzC+fW9xiFGAg1GJh/e67P1AIdbEsuLK3EOMEhzMSiK8wVfuBQrxpiRWVqUW5ccX leakFh9idAWGxERmKe7kfGBCyiuJNzYwwM1REue1Ons2UEggHZhkslNTC1KLYOYwcXCC7OGS EikGporUosTSkox4UEKLLwamNKkGxqwgtx+P6g9MVWhcEbK3VWaBMnv+0w4by0fyWjyvVmjG 7HwX11HxuL5j7ZHwSdpKbyc+ymPf9PPtuaavS09KPuN+oHDV0s6xtfH+srhzrSf1lK4v22ch 3bQne+aCqMKdV8+LfMlNjXOwuRTItsduw8nft9gXXFC3yTixff++vOj+bXPnXf5R8VOJpTgj 0VCLuag4EQBgwMlPOwMAAA==
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 22:25:06 -0000

I think that misses the point.

The WG sessions are where the issues are raised and the opinions and positio=
ns are stated.

Offline over the food and drink in small groups is where the detailed discus=
sion and finding of solutions to resolve those issues usually takes place. 

Such a phenomena is not unique to just IETF - its the nature of the beast.

Andrew

----- Original Message -----
From: Keith Moore [mailto:moore@network-heretics.com]
Sent: Thursday, July 11, 2013 04:19 PM Central Standard Time=0A=
To: ietf@ietf.org <ietf@ietf.org>
Subject: Re: IETF registration fee?

On 07/11/2013 04:50 PM, Brian E Carpenter wrote:
> Douglas,
> ...
>>> Those traveling thousands of miles already confront many uncertainties.=
  Those that elect to participate remotely should be afforded greater certai=
nty of being able to participate when problems occur at local venues or with=
 transportation.  Increasing participation without the expense of the brick=
 and mortar and travel should offer long term benefits and increased fairnes=
s.
> How much would you be willing to pay for remote participation
> (assuming it was of high quality)?

Not much.   Remote participation misses the whole point of IETF 
meetings.   Sure, it's useful to be able to listen on WG sessions and 
make a comment or two.   But the WG sessions generally aren't actually 
worth very much, especially the way that they tend to be run these 
days.   The most important work gets done in the hallways and over food 
and drink.

So IETF is in this very strange position of supporting itself by 
charging a large amount of money for an activity that's mostly 
peripheral to getting useful work done.

Keith


---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential infor=
mation, privileged material (including material protected by the solicitor-c=
lient or other applicable privileges), or constitute non-public information.=
 Any use of this information by anyone other than the intended recipient is=
 prohibited. If you have received this transmission in error, please immedia=
tely reply to the sender and delete this information from your system. Use,=
 dissemination, distribution, or reproduction of this transmission by uninte=
nded recipients is not authorized and may be unlawful.

From moore@network-heretics.com  Thu Jul 11 15:27:40 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FF5B11E81CE for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 15:27:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.516
X-Spam-Level: 
X-Spam-Status: No, score=-3.516 tagged_above=-999 required=5 tests=[AWL=0.083,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XWMuoA7cfN3z for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 15:27:35 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id 2133E11E81C0 for <ietf@ietf.org>; Thu, 11 Jul 2013 15:27:34 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 01E3F20E89; Thu, 11 Jul 2013 18:27:32 -0400 (EDT)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute6.internal (MEProxy); Thu, 11 Jul 2013 18:27:32 -0400
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 :content-transfer-encoding; s=smtpout; bh=UXFMh5nxfnx05GVMsrd5sl lG/D8=; b=A4Fs+6moAq42ayxnIPbjPHM6TxHELgf5ieQ8PB58OVifiyJzM4VdWL qT1WBpA3gqcgku7htdXfF6y1O/8q3BztDO/LnS6jCGuGTshmHUHQzWLpA2eK5FY1 mF/SnWQ0DNFTU05LWy7NBJCrKMjUayHyfOX2wkEjicV9BPkSg+pZE=
X-Sasl-enc: hrRA/zr8jYORlW9Vs1YNC7tLT/LdASgncfRP2+JlBdPD 1373581652
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id C40B66801EC; Thu, 11 Jul 2013 18:27:31 -0400 (EDT)
Message-ID: <51DF314A.2080602@network-heretics.com>
Date: Thu, 11 Jul 2013 18:27:22 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: Andrew Allen <aallen@blackberry.com>
Subject: Re: IETF registration fee?
References: <BBF5DDFE515C3946BC18D733B20DAD2338DC5B5A@XMB104ADS.rim.net>
In-Reply-To: <BBF5DDFE515C3946BC18D733B20DAD2338DC5B5A@XMB104ADS.rim.net>
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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 22:27:40 -0000

On 07/11/2013 06:24 PM, Andrew Allen wrote:
> I think that misses the point.
>
> The WG sessions are where the issues are raised and the opinions and positions are stated.

As far as I can tell, these days the WG sessions are where endless 
PowerPoint presentations are held and bored people check email.

Keith


From sob@harvard.edu  Thu Jul 11 16:11:19 2013
Return-Path: <sob@harvard.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 453CE21F9E0C for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 16:11:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9u7xY2TcQJds for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 16:11:13 -0700 (PDT)
Received: from ackroyd.harvard.edu (ackroyd.harvard.edu [128.103.208.29]) by ietfa.amsl.com (Postfix) with ESMTP id 709DE21F999C for <ietf@ietf.org>; Thu, 11 Jul 2013 16:11:13 -0700 (PDT)
Received: from exchange.university.harvard.edu (entwedge0000001.university.harvard.edu [10.35.2.152]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ackroyd.harvard.edu (Postfix) with ESMTP id 12157EA3E4; Thu, 11 Jul 2013 19:11:12 -0400 (EDT)
Received: from ENTWHUBT0000003.university.harvard.edu (192.168.36.24) by ENTWEDGE0000001.university.harvard.edu (10.35.2.152) with Microsoft SMTP Server (TLS) id 14.2.342.3; Thu, 11 Jul 2013 19:10:52 -0400
Received: from ENTWEXMB0000008.university.harvard.edu ([169.254.1.137]) by entwhubt0000003.university.harvard.edu ([192.168.36.24]) with mapi id 14.02.0342.003; Thu, 11 Jul 2013 19:11:11 -0400
From: "Bradner, Scott" <sob@harvard.edu>
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: Last Call: RFC 2050 to historic
Thread-Topic: Last Call: RFC 2050 to historic
Thread-Index: AQHOfcG6HbWKPpNInk29dddkWOADiw==
Date: Thu, 11 Jul 2013 23:11:11 +0000
Message-ID: <33E57758-D9FE-414C-8F28-E64EEAD4CA8D@harvard.edu>
References: <20130710213959.9266.65720.idtracker@ietfa.amsl.com> <0BFC28DF-EAE5-4EEC-B178-D562A4A5C577@harvard.edu> <83562D0A-4059-4B34-900A-C0745BA4F69E@piuha.net>
In-Reply-To: <83562D0A-4059-4B34-900A-C0745BA4F69E@piuha.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [136.248.127.162]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <E091C3E36C3B8647A921B3AC98BCE24F@Exchange.university.harvard.edu>
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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 23:11:19 -0000

tnx

Scott

On Jul 10, 2013, at 7:45 PM, Jari Arkko <jari.arkko@piuha.net> wrote:

>=20
> Scott,
>=20
>> is there a reason to not disclose who the individual participant is?
>=20
> No, but actually that text just came from the standard boilerplate for th=
e last call text in these cases. In reality has been several people asking =
for this to be done, e.g., SM wrote a document about 2050 and a few other R=
FCs, several IESG members felt that this needs to be done after the 2050bis=
 was approved, etc.
>=20
> Jari
>=20


From l.wood@surrey.ac.uk  Thu Jul 11 17:09:05 2013
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98E6321E8063 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 17:09:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.553
X-Spam-Level: 
X-Spam-Status: No, score=-3.553 tagged_above=-999 required=5 tests=[AWL=0.045,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wpH2Mov+puby for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 17:09:00 -0700 (PDT)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.168]) by ietfa.amsl.com (Postfix) with ESMTP id 5AB7521E804D for <ietf@ietf.org>; Thu, 11 Jul 2013 17:08:59 -0700 (PDT)
Received: from [195.245.230.131:50393] by server-8.bemta-3.messagelabs.com id 60/38-18692-4194FD15; Fri, 12 Jul 2013 00:08:52 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-11.tower-78.messagelabs.com!1373587731!30724382!1
X-Originating-IP: [131.227.200.39]
X-StarScan-Received: 
X-StarScan-Version: 6.9.9; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 20115 invoked from network); 12 Jul 2013 00:08:52 -0000
Received: from exht012p.surrey.ac.uk (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-11.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 12 Jul 2013 00:08:52 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT012P.surrey.ac.uk ([131.227.200.39]) with mapi; Fri, 12 Jul 2013 01:08:51 +0100
From: <l.wood@surrey.ac.uk>
To: <hallam@gmail.com>, <spromano@unina.it>
Date: Fri, 12 Jul 2013 01:08:50 +0100
Subject: RE: IETF registration fee?
Thread-Topic: IETF registration fee?
Thread-Index: Ac5+RC9vBozAmwS4R4WsrsfBnfsPFAATwEE2
Message-ID: <290E20B455C66743BE178C5C84F12408223F494EFA@EXMB01CMS.surrey.ac.uk>
References: <CE0388EA.21B7F%Josh.Howlett@ja.net> <803FCD9A-6B8A-45EC-914F-E2114C581EA1@gmail.com> <C053B4F4-4821-4132-B872-3F8A611B2F5F@unina.it>, <CAMm+Lwjpw6uodpZHuQ-rW4hJ7ViUHqrFBwTJYGkXCtH1c2x1ww@mail.gmail.com>
In-Reply-To: <CAMm+Lwjpw6uodpZHuQ-rW4hJ7ViUHqrFBwTJYGkXCtH1c2x1ww@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: moore@network-heretics.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jul 2013 00:09:05 -0000

This neglects to mention that the IETF is really an activity of the Interne=
t Society - see RFC2301 for takeover details.

As such, the IETF is a business unit of ISOC, which is a non-profit (charit=
able organization) and which can subsidize the IETF, allowing different con=
ference/payment models to be tried out.

(I've never really understood the IETF business model. I understand ISOC's =
model even less.)


Lloyd Wood
http://sat-net.com/L.Wood/


________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Phillip Ha=
llam-Baker [hallam@gmail.com]
Sent: 11 July 2013 15:34
To: Simon Pietro Romano
Cc: Keith Moore; ietf@ietf.org
Subject: Re: IETF registration fee?

There are several interlocking issues with the day passes and cross area pa=
rticipation.

One issue is the fact that the IETF chose a business model in which profits=
 from the conferences fund the organization and the IETF has no ability to =
reconsider or change decisions of that sort. I can see that as being an exi=
stential threat to the IETF in a decade or two since the demand for (unpaid=
) external participation is going to grow and the technologies for supporti=
ng external participation will eventually not suck.

Using paid conferences as a profit center is a risky long term prospect at =
best. Refusing to adapt the format of the conferences to protect the profit=
 center worse. And in the case of the IETF the whole purpose of the organiz=
ation is to develop the technologies that are undermining the paid conferen=
ce model. We are sawing the board we are standing on.


Cross area participation is a good thing but the way the IETF supports this=
 is terrible. I won't be coming to Berlin because there is only one WG that=
 I have a reason to attend in person and it is not worth making the flight =
for a two hour meeting, much of which is summaries.

I much prefer the OASIS or W3C model for plenary meetings where my WG sessi=
on will be doing one or two solid days of design work and the plenary sessi=
ons are on the Wednesday and consist of a series of presentations designed =
to inform people about the work going on in each area.

Sitting in watching other WGs is not a good way to find out what is going o=
n. Area meetings are more useful.


From l.wood@surrey.ac.uk  Thu Jul 11 17:15:58 2013
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 093A521F9A19 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 17:15:57 -0700 (PDT)
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=[AWL=-0.458, BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KINkw+5cRts3 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 17:15:50 -0700 (PDT)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.137]) by ietfa.amsl.com (Postfix) with ESMTP id 7F98321F995F for <ietf@ietf.org>; Thu, 11 Jul 2013 17:15:49 -0700 (PDT)
Received: from [195.245.231.67:63239] by server-1.bemta-5.messagelabs.com id 3A/8F-21460-3BA4FD15; Fri, 12 Jul 2013 00:15:47 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-2.tower-82.messagelabs.com!1373588146!29478783!1
X-Originating-IP: [131.227.200.39]
X-StarScan-Received: 
X-StarScan-Version: 6.9.9; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 30532 invoked from network); 12 Jul 2013 00:15:46 -0000
Received: from exht012p.surrey.ac.uk (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-2.tower-82.messagelabs.com with AES128-SHA encrypted SMTP; 12 Jul 2013 00:15:46 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT012P.surrey.ac.uk ([131.227.200.39]) with mapi; Fri, 12 Jul 2013 01:15:45 +0100
From: <l.wood@surrey.ac.uk>
To: <l.wood@surrey.ac.uk>, <hallam@gmail.com>, <spromano@unina.it>
Date: Fri, 12 Jul 2013 01:15:31 +0100
Subject: RE: IETF registration fee?
Thread-Topic: IETF registration fee?
Thread-Index: Ac5+RC9vBozAmwS4R4WsrsfBnfsPFAATwEE2AAButDY=
Message-ID: <290E20B455C66743BE178C5C84F12408223F494EFB@EXMB01CMS.surrey.ac.uk>
References: <CE0388EA.21B7F%Josh.Howlett@ja.net> <803FCD9A-6B8A-45EC-914F-E2114C581EA1@gmail.com> <C053B4F4-4821-4132-B872-3F8A611B2F5F@unina.it>, <CAMm+Lwjpw6uodpZHuQ-rW4hJ7ViUHqrFBwTJYGkXCtH1c2x1ww@mail.gmail.com>, <290E20B455C66743BE178C5C84F12408223F494EFA@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F12408223F494EFA@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
Cc: moore@network-heretics.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jul 2013 00:15:58 -0000

oops. RFC2031.

Lloyd Wood
http://sat-net.com/L.Wood/


________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of l.wood@sur=
rey.ac.uk [l.wood@surrey.ac.uk]
Sent: 12 July 2013 01:08
To: hallam@gmail.com; spromano@unina.it
Cc: moore@network-heretics.com; ietf@ietf.org
Subject: RE: IETF registration fee?

This neglects to mention that the IETF is really an activity of the Interne=
t Society - see RFC2301 for takeover details.

As such, the IETF is a business unit of ISOC, which is a non-profit (charit=
able organization) and which can subsidize the IETF, allowing different con=
ference/payment models to be tried out.

(I've never really understood the IETF business model. I understand ISOC's =
model even less.)


Lloyd Wood
http://sat-net.com/L.Wood/


________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Phillip Ha=
llam-Baker [hallam@gmail.com]
Sent: 11 July 2013 15:34
To: Simon Pietro Romano
Cc: Keith Moore; ietf@ietf.org
Subject: Re: IETF registration fee?

There are several interlocking issues with the day passes and cross area pa=
rticipation.

One issue is the fact that the IETF chose a business model in which profits=
 from the conferences fund the organization and the IETF has no ability to =
reconsider or change decisions of that sort. I can see that as being an exi=
stential threat to the IETF in a decade or two since the demand for (unpaid=
) external participation is going to grow and the technologies for supporti=
ng external participation will eventually not suck.

Using paid conferences as a profit center is a risky long term prospect at =
best. Refusing to adapt the format of the conferences to protect the profit=
 center worse. And in the case of the IETF the whole purpose of the organiz=
ation is to develop the technologies that are undermining the paid conferen=
ce model. We are sawing the board we are standing on.


Cross area participation is a good thing but the way the IETF supports this=
 is terrible. I won't be coming to Berlin because there is only one WG that=
 I have a reason to attend in person and it is not worth making the flight =
for a two hour meeting, much of which is summaries.

I much prefer the OASIS or W3C model for plenary meetings where my WG sessi=
on will be doing one or two solid days of design work and the plenary sessi=
ons are on the Wednesday and consist of a series of presentations designed =
to inform people about the work going on in each area.

Sitting in watching other WGs is not a good way to find out what is going o=
n. Area meetings are more useful.


From liushucheng@huawei.com  Thu Jul 11 17:57:29 2013
Return-Path: <liushucheng@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9B6211E823B for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 17:57:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o9zc5S486vRE for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 17:57:25 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 4367411E8135 for <ietf@ietf.org>; Thu, 11 Jul 2013 17:57:25 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AUY01111; Fri, 12 Jul 2013 00:57:22 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 12 Jul 2013 01:54:43 +0100
Received: from SZXEML456-HUB.china.huawei.com (10.82.67.199) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 12 Jul 2013 01:55:20 +0100
Received: from SZXEML546-MBX.china.huawei.com ([169.254.3.181]) by szxeml456-hub.china.huawei.com ([10.82.67.199]) with mapi id 14.01.0323.007; Fri, 12 Jul 2013 08:55:14 +0800
From: "Will Liu (Shucheng)" <liushucheng@huawei.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: All fees include 19% VAT?
Thread-Topic: All fees include 19% VAT?
Thread-Index: Ac5+mncyMYEa0ORGSvO/SCl0z79i5g==
Date: Fri, 12 Jul 2013 00:55:13 +0000
Message-ID: <C9B5F12337F6F841B35C404CF0554ACB4B46DD64@szxeml546-mbx.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.66.78.79]
Content-Type: multipart/alternative; boundary="_000_C9B5F12337F6F841B35C404CF0554ACB4B46DD64szxeml546mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jul 2013 00:57:29 -0000

--_000_C9B5F12337F6F841B35C404CF0554ACB4B46DD64szxeml546mbxchi_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Folks,

I am a little confused by the following words. The sum for an early bird is=
 650$, right? Or do we need to pay extra VAT (which make the sum larger tha=
n 650$)? The last sentence is really confusing.

Early-Bird: $650 USD, if paid in full prior to 2400 UTC July 19, 2013.
All fees include 19% VAT
A FINAL receipt will be sent with all the required VAT information by July =
28th. Instructions will be included on the process to follow to recover the=
 VAT paid by qualified attendees or their employer.

Regards,
Shucheng (Will)
---------------------------------------------------------------------------=
--------
Shucheng LIU (Will), Ph.D.
Research Engineer  at  Huawei Technologies Co.,Ltd
Email: liushucheng@huawei.com<mailto:liushucheng@huawei.com>
http://cn.linkedin.com/in/shucheng
---------------------------------------------------------------------------=
--------


--_000_C9B5F12337F6F841B35C404CF0554ACB4B46DD64szxeml546mbxchi_
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:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:m=3D"http://schema=
s.microsoft.com/office/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html=
40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:\5B8B\4F53;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@\5B8B\4F53";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.apple-converted-space
	{mso-style-name:apple-converted-space;}
.MsoChpDefault
	{mso-style-type:export-only;}
/* Page Definitions */
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
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"ZH-CN" link=3D"blue" vlink=3D"purple" style=3D"text-justify-t=
rim:punctuation">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US">Folks,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">I am a little confused by the f=
ollowing words. The sum for an early bird is 650$, right? Or do we need to =
pay extra VAT (which make the sum larger than 650$)? The last sentence is r=
eally confusing.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:8.0pt;font-f=
amily:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#26445B">Early-Bird: $=
650 USD,<span class=3D"apple-converted-space">&nbsp;</span><b>if paid in fu=
ll</b><span class=3D"apple-converted-space">&nbsp;</span>prior to 2400 UTC
 July 19, 2013.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">All fees include 19% VAT<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:8.0pt;font-f=
amily:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#26445B">A FINAL recei=
pt will be sent with all the required VAT information by July 28th. Instruc=
tions will be included on the process to follow to recover
 the VAT paid by qualified attendees or their employer.</span><span lang=3D=
"EN-US"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Regards,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Shucheng (Will)<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US">----------------------------------------------------------------=
-------------------<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US">Shucheng LIU (Will), Ph.D.<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US">Research Engineer &nbsp;at &nbsp;Huawei Technologies Co.,Ltd<o:p=
></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US">Email:
<a href=3D"mailto:liushucheng@huawei.com"><span style=3D"color:blue">liushu=
cheng@huawei.com</span></a><o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US"><a href=3D"http://cn.linkedin.com/in/shucheng"><span style=3D"co=
lor:blue">http://cn.linkedin.com/in/shucheng</span></a><o:p></o:p></span></=
p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US">----------------------------------------------------------------=
-------------------<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
</body>
</html>

--_000_C9B5F12337F6F841B35C404CF0554ACB4B46DD64szxeml546mbxchi_--

From joelja@bogus.com  Thu Jul 11 18:14:36 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1891611E820C for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 18:14:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.181
X-Spam-Level: 
X-Spam-Status: No, score=-102.181 tagged_above=-999 required=5 tests=[AWL=-0.182, BAYES_00=-2.599, J_CHICKENPOX_45=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QFv4YtxHiL48 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 18:14:35 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 821C311E80D3 for <ietf@ietf.org>; Thu, 11 Jul 2013 18:14:35 -0700 (PDT)
Received: from joels-MacBook-Air.local (c-71-193-176-225.hsd1.wa.comcast.net [71.193.176.225]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r6C1EURH094932 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Fri, 12 Jul 2013 01:14:30 GMT (envelope-from joelja@bogus.com)
Message-ID: <51DF5870.1000609@bogus.com>
Date: Thu, 11 Jul 2013 18:14:24 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:22.0) Gecko/20100101 Thunderbird/22.0
MIME-Version: 1.0
To: "Will Liu (Shucheng)" <liushucheng@huawei.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: All fees include 19% VAT?
References: <C9B5F12337F6F841B35C404CF0554ACB4B46DD64@szxeml546-mbx.china.huawei.com>
In-Reply-To: <C9B5F12337F6F841B35C404CF0554ACB4B46DD64@szxeml546-mbx.china.huawei.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.2.7 (nagasaki.bogus.com [147.28.0.81]); Fri, 12 Jul 2013 01:14:31 +0000 (UTC)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jul 2013 01:14:36 -0000

On 7/11/13 5:55 PM, Will Liu (Shucheng) wrote:
>
> Folks,
>
> I am a little confused by the following words. The sum for an early 
> bird is 650$, right? Or do we need to pay extra VAT (which make the 
> sum larger than 650$)? The last sentence is really confusing.
>
The vat is included. $650 is what you're paying and what the bill will 
be for.
>
> Early-Bird: $650 USD,*if paid in full*prior to 2400 UTC July 19, 2013.
>
> All fees include 19% VAT
>
> A FINAL receipt will be sent with all the required VAT information by 
> July 28th. Instructions will be included on the process to follow to 
> recover the VAT paid by qualified attendees or their employer.
>
> Regards,
>
> Shucheng (Will)
>
> -----------------------------------------------------------------------------------
>
> Shucheng LIU (Will), Ph.D.
>
> Research Engineer  at  Huawei Technologies Co.,Ltd
>
> Email: liushucheng@huawei.com <mailto:liushucheng@huawei.com>
>
> http://cn.linkedin.com/in/shucheng
>
> -----------------------------------------------------------------------------------
>


From zehn.cao@gmail.com  Thu Jul 11 18:35:06 2013
Return-Path: <zehn.cao@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC3A311E8202 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 18:35:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ir3-a8FPvrbX for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 18:35:06 -0700 (PDT)
Received: from mail-wi0-x234.google.com (mail-wi0-x234.google.com [IPv6:2a00:1450:400c:c05::234]) by ietfa.amsl.com (Postfix) with ESMTP id 35A1511E81DD for <ietf@ietf.org>; Thu, 11 Jul 2013 18:35:06 -0700 (PDT)
Received: by mail-wi0-f180.google.com with SMTP id c10so136198wiw.1 for <ietf@ietf.org>; Thu, 11 Jul 2013 18:35:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=+BO67mUrQEe4qfoOUSu3h/iq0pjbWbggHXZ98+MtBis=; b=deBgSPdMqkpAKMa3zLvvkCKwjoGogAd53aQXMGXF6LZ55NeOAqk6G8vyjh9vXw0RLD lj8BTi/j2MeyeVOw2EsJqiltEl1qeD9SJ6My8wjg8p7I/i58+Bc+UiRvtc04v9fn4Eaz RPuYkJYUCE7w4q8wcwXMKJulbyjtRXxopoUEwvCt54wEIAd7h7A8/mHzFjEJNy5K2pu0 5ecz8G9sqpW8cxX3+tA9DOWrmtfuXxC89T4hvy8YnipVo6OhPsZ4uTKQi8pD1RQCIJdi p4UAKTBmJ2kg+hQd6h0kTe5BXy2lO03gLYVmG1Xgx3oLlFKklt3v+irsrkvO60CJV5vV WZIw==
MIME-Version: 1.0
X-Received: by 10.180.75.41 with SMTP id z9mr298161wiv.22.1373592905187; Thu, 11 Jul 2013 18:35:05 -0700 (PDT)
Received: by 10.217.129.136 with HTTP; Thu, 11 Jul 2013 18:35:05 -0700 (PDT)
In-Reply-To: <51DEB9F2.9040405@viagenie.ca>
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com> <51DEB9F2.9040405@viagenie.ca>
Date: Fri, 12 Jul 2013 09:35:05 +0800
Message-ID: <CAProHATm87UPp1ryY0AhSHvzP4c_TDpg88TWySzSxjdc6JvOZQ@mail.gmail.com>
Subject: Re: Regarding call Chinese names
From: "Cao,Zhen" <zehn.cao@gmail.com>
To: Simon Perreault <simon.perreault@viagenie.ca>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jul 2013 01:35:07 -0000

> Very cool! Thanks for writing this!

Our pleasure.

>
> I have a question: I think I've seen Chinese names written in both
> orders. That is, sometimes "Hui Deng" will be written "Deng Hui". Am I
> right? Does this happen often? What is the most common order? Is there a
> way to guess what order a name is written in? Sometimes it's not easy
> for non-Sinophones to know which part is the given name and which part
> is the family name.

I notice most names in IETF are still presented in the English order,
given name first and family name later.

For names written with Family name first, usually it is encouraged to
put a ',' between.

Thanks,
zhen

>
> Thanks,
> Simon

From zehn.cao@gmail.com  Thu Jul 11 18:47:10 2013
Return-Path: <zehn.cao@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DB9E21F9E00 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 18:47:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id axHtA171h2R4 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 18:47:09 -0700 (PDT)
Received: from mail-we0-x22a.google.com (mail-we0-x22a.google.com [IPv6:2a00:1450:400c:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 67E1021F9CD9 for <ietf@ietf.org>; Thu, 11 Jul 2013 18:47:09 -0700 (PDT)
Received: by mail-we0-f170.google.com with SMTP id w57so7686375wes.29 for <ietf@ietf.org>; Thu, 11 Jul 2013 18:47:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=5GwnD1JXa9eyWX4RDMbtrTaKf6JKWqgJZtfCIrWttDo=; b=r5sakiffshtwow5vLOj3X09RyyOweOb+tK7P9FC03pCZz4R8VGtWX7KdSRcIf43B+V yREkrjUWiVjoSfrvW62PfhNpAj05G7zFrkreOBXQToOvN7XXd3atDrvO6uRhcAWP0fnx s0V8yUkNt7Wrlsfi+AyrvtDF0NwU6ZlGpTqeEJGG9jKaaZw3WkcXaV9imlBMi/orsmqd VZLmNbZCiuaiOtWgGp4p0k6Kqv3j3Ga/Aa9ySm1lrrxyBr88yXAihGzElAAfesdUgVhi l5IzsdWsrCEisUCKlw2SopKSoHb8jQKtqatQN/1+fHLxZK9y4f8oHl1IqDevXvtCV2Ks X7BA==
MIME-Version: 1.0
X-Received: by 10.180.21.229 with SMTP id y5mr147942wie.17.1373593625943; Thu, 11 Jul 2013 18:47:05 -0700 (PDT)
Received: by 10.217.129.136 with HTTP; Thu, 11 Jul 2013 18:47:05 -0700 (PDT)
In-Reply-To: <CAF4+nEF_VnR2DNd_LDehXwJNn=0CT0Qkz3hKrBHuffVFvdXLMg@mail.gmail.com>
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com> <51DEB9F2.9040405@viagenie.ca> <F108A063F7E85E5F9C89ADBF@caldav.corp.apple.com> <CAF4+nEF_VnR2DNd_LDehXwJNn=0CT0Qkz3hKrBHuffVFvdXLMg@mail.gmail.com>
Date: Fri, 12 Jul 2013 09:47:05 +0800
Message-ID: <CAProHAQfiMgnWFEt6udRS7Pv137kupuHgtnjBsA5ERBPSTrYQw@mail.gmail.com>
Subject: Re: Regarding call Chinese names
From: "Cao,Zhen" <zehn.cao@gmail.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jul 2013 01:47:10 -0000

Yes, agree, we will change that accordingly.
Thanks.
On Thu, Jul 11, 2013 at 11:40 PM, Donald Eastlake <d3e3e3@gmail.com> wrote:
> First/Last = bad/ambiguous
>
> Family (or maybe inherited) / Given = good
>
> Thanks,
> Donald
> =============================
>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>  155 Beaver Street, Milford, MA 01757 USA
>  d3e3e3@gmail.com
>
>
> On Thu, Jul 11, 2013 at 10:22 AM, Cyrus Daboo <cyrus@daboo.name> wrote:
>> Hi Simon,
>>
>>
>> --On July 11, 2013 at 3:58:10 PM +0200 Simon Perreault
>> <simon.perreault@viagenie.ca> wrote:
>>
>>>> We submitted two drafts to help people here to correctly call chinese
>>>> people names:
>>>>
>>>> http://tools.ietf.org/html/draft-deng-call-chinese-names-00
>>>>    http://tools.ietf.org/html/draft-zcao-chinese-pronounce-00
>>>
>>>
>>> Very cool! Thanks for writing this!
>>>
>>> I have a question: I think I've seen Chinese names written in both
>>> orders. That is, sometimes "Hui Deng" will be written "Deng Hui". Am I
>>> right? Does this happen often? What is the most common order? Is there a
>>> way to guess what order a name is written in? Sometimes it's not easy
>>> for non-Sinophones to know which part is the given name and which part
>>> is the family name.
>>
>>
>> Well that actually brings up a good technical point!
>>
>> In iCalendar (RFC5545) we have properties to represent the organizer and
>> attendee of meetings. A parameter (attribute) of those properties is "CN" -
>> defined to be the "common name" of the corresponding calendar user.
>> Obviously that is a single string and typically the concatenation of first
>> name/last name. But that of course is a very "Western" approach.
>>
>> I have had several people request that iCalendar instead define new
>> parameters for "FIRST-NAME" and "LAST-NAME". That then gives clients the
>> option of re-ordering those for display purposes based on user locales and
>> preferences.
>>
>> So, from a technical standpoint, it seems better to always represent user
>> names using components (last, first, middle)? vCard does have an "N"
>> property where individual components of a name can be broken out.
>>
>> --
>> Cyrus Daboo
>>

From abdussalambaryun@gmail.com  Thu Jul 11 21:07:58 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC11C11E80BA for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 21:07:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Esy8oCOZtXdl for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 21:07:58 -0700 (PDT)
Received: from mail-pb0-x234.google.com (mail-pb0-x234.google.com [IPv6:2607:f8b0:400e:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id 3A7C511E80A2 for <ietf@ietf.org>; Thu, 11 Jul 2013 21:07:57 -0700 (PDT)
Received: by mail-pb0-f52.google.com with SMTP id xa12so8545526pbc.25 for <ietf@ietf.org>; Thu, 11 Jul 2013 21:07:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=YyKlcaQMnZj8oh7oLvwN7ExSh5GNyb6mLvfgIE6wRes=; b=ZJ3rVI7DyY3mXzC6lrw7t2H12c/8MeXEQwfzTRFzDwZ9j/M0cExTbH7STuP3LiHFrB 8hdU3NAkjg2dnmA1VtRgO2j93Saoo1FqpVJ2zX4B6FEwi8z9n5i66TIji9LfJeRZPyqW ky4TWTKYcqROjZXIR3WccOftKsgp4vlBwqcam4fKYvFyQ6L0vcuDGDqpDszvn+zekUXb nS6xgfVnKxTp20pVOvZ3zrkM12td9igAt4Hod8Y0OqZyiZurOGr2mQqetbWwtwjZgsul 18hnLZ91cc4NapHsIjBNK7HMfeDPB8hQAodNUT1e83vCp9GwWr1STL5OndJAB8Twgeb7 5srA==
MIME-Version: 1.0
X-Received: by 10.68.164.69 with SMTP id yo5mr39631572pbb.96.1373602077657; Thu, 11 Jul 2013 21:07:57 -0700 (PDT)
Received: by 10.68.250.133 with HTTP; Thu, 11 Jul 2013 21:07:57 -0700 (PDT)
Date: Fri, 12 Jul 2013 06:07:57 +0200
Message-ID: <CADnDZ88OavkdTnwx4Lz7-Ucye_3hPUWJKQpP5J3=GXFA1VuZ_g@mail.gmail.com>
Subject: comment for draft-deng-call-chinese-names-00 (was Re: Regarding call Chinese names)
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Hui Deng <denghui02@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jul 2013 04:07:58 -0000

Hi Hui Deng,

My comment for the draft is that I want to relate it to IETF as below,
which I see that already some on IETF addressed by draft already call
names including regional calling culture, which is excellent. The
document will increase awareness and make the IETF culture more
diversive. Comments:

- The draft mentions word *speak*, is their formal and informal
speaking difference in calling names ( you mentioned Mr/Mrs, but I was
not sure it that compulsory formal way. Also what about how they
*write* formally or informally. The word *call* in the title do you
mean only in speaking or calling also in writing.

- I am interested to know more why/how IETF participants (in past) had
difficulty to communicate the names not how western people? So it may
be good to know the history how IETF did call chinese names, or how
they introduced their names in registrations. Secondly, not sure how
the Chinese write and speak the names (is there difference way), as
formal and informal, so I would like to know is there differences in
writing documents, and does authors from this language like to
translate there name to English without changing the tradition ways.
So if you write in chinese do you prefer to write in your
English-document, as author: Hui Deng or Deng Hui?

- Does the draft want to give information to IETF to consider *call*
when speaking or also when writing/reading documents? and if you write
your formal name as your speak names tradition, do you suggest a
method to have in writting names translated to English in IETF doc
(optional for authors) without ignoring the authors' regional culture.
So you may write for this draft: Author- Deng Hui (mandarin) in the
last page of IETF doc and in front page the same formal English
semantic way, as Hui Deng.

Please advise,
Thanks,

AB

On 7/11/13, Hui Deng <denghui02@gmail.com> wrote:
> Hello all
>
> We submitted two drafts to help people here to correctly call chinese
> people names:
>
> http://tools.ietf.org/html/draft-deng-call-chinese-names-00
>
>    http://tools.ietf.org/html/draft-zcao-chinese-pronounce-00
>
>
>
> Feel free to let us know if you have any other issues?
>
> Best regards,
>
>
>
> -Hui Deng
>

From abdussalambaryun@gmail.com  Thu Jul 11 21:27:50 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64EBE11E80F7; Thu, 11 Jul 2013 21:27:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U8xkXnXX48-N; Thu, 11 Jul 2013 21:27:50 -0700 (PDT)
Received: from mail-pd0-x22c.google.com (mail-pd0-x22c.google.com [IPv6:2607:f8b0:400e:c02::22c]) by ietfa.amsl.com (Postfix) with ESMTP id E87B711E80F5; Thu, 11 Jul 2013 21:27:49 -0700 (PDT)
Received: by mail-pd0-f172.google.com with SMTP id z10so8164257pdj.31 for <multiple recipients>; Thu, 11 Jul 2013 21:27:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=XwBkJsRjGvrr7PzNcjT4Ji5DZcS4xO/QoEH2qtv0a44=; b=a5XafrfbCSOkzwB/qYTlnrprekYNpNaxhLKyQJ4yXKfTQwyoPwoR4ZyWUIUXzSDTdx GN42xGl5xjLDjuzdbebFxwxozbxk9n0oGdvA612rWM2G1NXRty1dtQQG6HBsogB4gO/t uS/vvsyOZMOESURkyhjrjByD9cywKdOUkUWNAEyv2Kmlbace3b+7pOM1/9Hby3EVy//D W3D+WL2HMhaiXSMhMCuSOzb/JT0pa8Ce+AD7/+J3y+cm+SpKEk5Mp52hvNoiRjLmGLlk PVT3PYvZuhD+wmuZZ2NLOaHuMw259bNWyPPbdmHPFOYUTrjUS3iW+1FBhX6fBBpkv8cp m+zw==
MIME-Version: 1.0
X-Received: by 10.68.164.69 with SMTP id yo5mr39691884pbb.96.1373603269681; Thu, 11 Jul 2013 21:27:49 -0700 (PDT)
Received: by 10.68.250.133 with HTTP; Thu, 11 Jul 2013 21:27:49 -0700 (PDT)
In-Reply-To: <51DD8551.6090502@cisco.com>
References: <51DD8551.6090502@cisco.com>
Date: Fri, 12 Jul 2013 06:27:49 +0200
Message-ID: <CADnDZ89g=-_V_J65=Lb2VfRv2+pvDPPwX0nyfT-+YE=bLFfCDg@mail.gmail.com>
Subject: Re: IETF registration fee?
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Paul Aitken <paitken@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org, ietf-registrar@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jul 2013 04:27:50 -0000

Hi Paul,

I agree with you if someone attends without presenting work, but I
think the fees is reasonable if we compare with other conferences fees
per day (don't forget your free to presentations of your docs and get
feedback from many sessions, this may change in future if higher
load). If the IETF considers your request, I think it will increase
participation maybe about 5% globaly and 20% locally, so mostly
encourages regional participations. I will also add that if the IETF
can consider newcomers to get discount for one day, because newcomers
may want to get a feeling of the meeting.

AB

On 7/10/13, Paul Aitken <paitken@cisco.com> wrote:
> Can you help me understand why the One Day Pass rate ($350) is so high
> compared with the full week rate ($650 / $800)?
>
> Registering for two days could cost more than a week!
>
> Surely the day rate should be a little more than (week/5), eg about $175
> - $200, to encourage those who only want/need to contribute on
> particular days?
>
> Thanks,
> P.
>

From narten@us.ibm.com  Thu Jul 11 21:53:16 2013
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B58E521F9CFF for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 21:53:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.372
X-Spam-Level: 
X-Spam-Status: No, score=-109.372 tagged_above=-999 required=5 tests=[AWL=-1.228, BAYES_00=-2.599, FRT_ADOBE2=2.455, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hBnZLveeLRsE for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 21:53:10 -0700 (PDT)
Received: from e36.co.us.ibm.com (e36.co.us.ibm.com [32.97.110.154]) by ietfa.amsl.com (Postfix) with ESMTP id D34C121F9CE3 for <ietf@ietf.org>; Thu, 11 Jul 2013 21:53:09 -0700 (PDT)
Received: from /spool/local by e36.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, 11 Jul 2013 22:53:06 -0600
Received: from d03dlp02.boulder.ibm.com (9.17.202.178) by e36.co.us.ibm.com (192.168.1.136) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 11 Jul 2013 22:53:06 -0600
Received: from d03relay01.boulder.ibm.com (d03relay01.boulder.ibm.com [9.17.195.226]) by d03dlp02.boulder.ibm.com (Postfix) with ESMTP id 9FACF3E40030 for <ietf@ietf.org>; Thu, 11 Jul 2013 22:52:44 -0600 (MDT)
Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by d03relay01.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r6C4r5ov090452 for <ietf@ietf.org>; Thu, 11 Jul 2013 22:53:05 -0600
Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1]) by d03av02.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r6C4r5vw029468 for <ietf@ietf.org>; Thu, 11 Jul 2013 22:53:05 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d03av02.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r6C4r4cB029401 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 11 Jul 2013 22:53:04 -0600
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.7/8.12.5) with ESMTP id r6C4r3xh001098 for <ietf@ietf.org>; Fri, 12 Jul 2013 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.7/8.14.7/Submit) id r6C4r3ss001081 for ietf@ietf.org; Fri, 12 Jul 2013 00:53:03 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201307120453.r6C4r3ss001081@rotala.raleigh.ibm.com>
Date: Fri, 12 Jul 2013 00:53:02 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13071204-7606-0000-0000-00000D414E97
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jul 2013 04:53:16 -0000

Total of 135 messages in the last 7 days.
 
script run at: Fri Jul 12 00:53:02 EDT 2013
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  5.19% |    7 |  5.14% |    54819 | l.wood@surrey.ac.uk
  5.19% |    7 |  4.23% |    45126 | john-ietf@jck.com
  4.44% |    6 |  3.52% |    37475 | moore@network-heretics.com
  2.96% |    4 |  3.70% |    39453 | denghui02@gmail.com
  3.70% |    5 |  2.87% |    30590 | dhc@dcrocker.net
  2.96% |    4 |  2.96% |    31531 | doug.mtview@gmail.com
  0.74% |    1 |  4.84% |    51543 | communication@edox.com
  2.96% |    4 |  2.61% |    27819 | d3e3e3@gmail.com
  2.96% |    4 |  2.48% |    26411 | arturo.servin@gmail.com
  2.96% |    4 |  2.46% |    26176 | ted.lemon@nominum.com
  2.96% |    4 |  2.33% |    24811 | jari.arkko@piuha.net
  2.22% |    3 |  2.50% |    26695 | peter@akayla.com
  1.48% |    2 |  2.96% |    31597 | spromano@unina.it
  2.22% |    3 |  2.09% |    22285 | sm+ietf@elandsys.com
  2.22% |    3 |  1.83% |    19504 | zehn.cao@gmail.com
  2.22% |    3 |  1.82% |    19399 | brian.e.carpenter@gmail.com
  1.48% |    2 |  2.53% |    26980 | stephen@sprunk.org
  1.48% |    2 |  2.27% |    24163 | liushucheng@huawei.com
  2.22% |    3 |  1.45% |    15415 | simon.perreault@viagenie.ca
  2.22% |    3 |  1.36% |    14508 | jnc@mercury.lcs.mit.edu
  1.48% |    2 |  1.33% |    14213 | ben@nostrum.com
  0.74% |    1 |  1.96% |    20916 | allison.mankin@gmail.com
  1.48% |    2 |  1.19% |    12664 | bob.hinden@gmail.com
  1.48% |    2 |  1.16% |    12389 | sob@harvard.edu
  1.48% |    2 |  1.16% |    12317 | cyrus@daboo.name
  1.48% |    2 |  1.13% |    12080 | scott.brim@gmail.com
  0.74% |    1 |  1.87% |    19971 | chair@ietf.org
  1.48% |    2 |  1.10% |    11729 | hsantos@isdg.net
  0.74% |    1 |  1.66% |    17648 | victor.zhongxin@huawei.com
  0.74% |    1 |  1.07% |    11398 | joseph.yee@gmail.com
  0.74% |    1 |  0.96% |    10235 | david.black@emc.com
  0.74% |    1 |  0.95% |    10138 | superuser@gmail.com
  0.74% |    1 |  0.94% |    10061 | ida_leung@yahoo.com
  0.74% |    1 |  0.94% |     9998 | skareem@science.alquds.edu
  0.74% |    1 |  0.89% |     9524 | narten@us.ibm.com
  0.74% |    1 |  0.88% |     9327 | mkaushik@us.ibm.com
  0.74% |    1 |  0.86% |     9132 | ted.ietf@gmail.com
  0.74% |    1 |  0.83% |     8839 | hallam@gmail.com
  0.74% |    1 |  0.82% |     8735 | sm@resistor.net
  0.74% |    1 |  0.81% |     8615 | wesley.george@twcable.com
  0.74% |    1 |  0.78% |     8319 | aallen@blackberry.com
  0.74% |    1 |  0.74% |     7885 | mthornbu@adobe.com
  0.74% |    1 |  0.74% |     7836 | abdussalambaryun@gmail.com
  0.74% |    1 |  0.72% |     7684 | dmbond@us.ibm.com
  0.74% |    1 |  0.71% |     7603 | lojakab@cisco.com
  0.74% |    1 |  0.71% |     7520 | akatlas@gmail.com
  0.74% |    1 |  0.70% |     7501 | pthaler@broadcom.com
  0.74% |    1 |  0.70% |     7416 | andy@yumaworks.com
  0.74% |    1 |  0.69% |     7384 | tom@dropfuse.com
  0.74% |    1 |  0.69% |     7331 | iab-chair@iab.org
  0.74% |    1 |  0.69% |     7319 | kathleen.moriarty@emc.com
  0.74% |    1 |  0.68% |     7280 | yding@cs.helsinki.fi
  0.74% |    1 |  0.66% |     7053 | jmh@joelhalpern.com
  0.74% |    1 |  0.66% |     7052 | ynir@checkpoint.com
  0.74% |    1 |  0.64% |     6803 | swmike@swm.pp.se
  0.74% |    1 |  0.64% |     6775 | spencerdawkins.ietf@gmail.com
  0.74% |    1 |  0.63% |     6767 | tjc@ecs.soton.ac.uk
  0.74% |    1 |  0.63% |     6716 | jabley@hopcount.ca
  0.74% |    1 |  0.61% |     6507 | amorris@amsl.com
  0.74% |    1 |  0.59% |     6332 | ole@cisco.com
  0.74% |    1 |  0.58% |     6225 | stephen.farrell@cs.tcd.ie
  0.74% |    1 |  0.58% |     6171 | josh.howlett@ja.net
  0.74% |    1 |  0.58% |     6161 | melinda.shore@gmail.com
  0.74% |    1 |  0.56% |     5970 | joelja@bogus.com
  0.74% |    1 |  0.55% |     5855 | hartmans-ietf@mit.edu
  0.74% |    1 |  0.55% |     5810 | carlosm3011@gmail.com
  0.74% |    1 |  0.54% |     5764 | john@jck.com
  0.74% |    1 |  0.54% |     5751 | randy@psg.com
  0.74% |    1 |  0.53% |     5640 | paitken@cisco.com
  0.74% |    1 |  0.53% |     5605 | elwynd@dial.pipex.com
  0.74% |    1 |  0.52% |     5513 | stpeter@stpeter.im
  0.74% |    1 |  0.50% |     5332 | ajs@anvilwalrusden.com
  0.74% |    1 |  0.48% |     5096 | bmanning@isi.edu
  0.74% |    1 |  0.45% |     4798 | paf@frobbit.se
  0.74% |    1 |  0.45% |     4752 | agenda@ietf.org
--------+------+--------+----------+------------------------
100.00% |  135 |100.00% |  1065755 | Total


From denghui02@gmail.com  Thu Jul 11 22:14:28 2013
Return-Path: <denghui02@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE1F811E8138 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 22:14:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.511
X-Spam-Level: 
X-Spam-Status: No, score=-102.511 tagged_above=-999 required=5 tests=[AWL=0.088, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eqUpR0wBvIfP for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 22:14:28 -0700 (PDT)
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 669DA11E80F8 for <ietf@ietf.org>; Thu, 11 Jul 2013 22:14:28 -0700 (PDT)
Received: by mail-qc0-f170.google.com with SMTP id s1so4812260qcw.15 for <ietf@ietf.org>; Thu, 11 Jul 2013 22:14:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=Eaf4zVouczy5lUC8UOYmUHV3ed1Wn+U3d0PwD63lfcY=; b=G5H3xTHf+ijfUqmd5jjIa9IDymeeikt/zbUS3MkfTp2YHB9xX27+iFFLXqvTrqGqZi cxAa0qYqNuxli0QRaKWgjfP89kib1iUlQHxdI8mWZpUj1/f4uvJ1QOPp+oR1hPuHXlPM B//I/pn1xgw+41ZBAA9VqrUrrJ3OQJYZeYlnDzcLOslDbengRhwuUUVG/sCk1K//+CL2 YPjvKb2S0ZI/x8VN4n0MxB3OfzkxoXjp2jO3yfiOyFgapjDAVA+SrgRkmKOba2A72d2L pmKfsbK84+G8B8yzq764kYGVkzbXPq7CpPYh+sXQQ52yUZ6ULRlr6SsH2hjJ9mO02V4E Q3ow==
MIME-Version: 1.0
X-Received: by 10.49.86.69 with SMTP id n5mr27482266qez.69.1373606066800; Thu, 11 Jul 2013 22:14:26 -0700 (PDT)
Received: by 10.49.16.42 with HTTP; Thu, 11 Jul 2013 22:14:26 -0700 (PDT)
Date: Fri, 12 Jul 2013 13:14:26 +0800
Message-ID: <CANF0JMAGMqc7DZsp2T9qi4bWNq6NvWUq3+Fx6Um9nC-_hyT75A@mail.gmail.com>
Subject: Excuse me for not able to reply shortly
From: Hui Deng <denghui02@gmail.com>
To: IETF Discussion <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=047d7bdc83b8ac4e5e04e14995ae
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jul 2013 05:14:29 -0000

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

Hi all

I am still in the vocation this two weeks out of Beijing with family, quite
diffcult to response in time,  will try to update the drafts before the
deadline. Cao Zhen will help to reply some of the suggestions.

By the way,
surname is "Deng"
given name is "Hui"

Thank you all for the disucssion

I really don't know whether IETF should recommend Deng Hui or Hui Deng

anyway,

Best regards,

Deng Hui

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

<div dir=3D"ltr"><div>Hi all</div><div>=A0</div><div>I am still in the voca=
tion this two weeks out of Beijing with family, quite diffcult to response =
in time,=A0 will try to update the drafts before the deadline. Cao=A0Zhen w=
ill help to reply some of the suggestions.</div>
<div>=A0</div><div>By the way, </div><div>surname is &quot;Deng&quot;</div>=
<div>given name is &quot;Hui&quot;</div><div>=A0</div><div>Thank you all fo=
r the disucssion</div><div>=A0</div><div>I really don&#39;t know whether IE=
TF should recommend Deng Hui or Hui Deng</div>
<div>=A0</div><div>anyway, </div><div>=A0</div><div>Best regards,</div><div=
>=A0</div><div>Deng Hui </div></div>

--047d7bdc83b8ac4e5e04e14995ae--

From randy@psg.com  Fri Jul 12 02:19:01 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35F7521E809C for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 02:19:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.586
X-Spam-Level: 
X-Spam-Status: No, score=-2.586 tagged_above=-999 required=5 tests=[AWL=0.013,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id su4RsIeHtk5l for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 02:19:00 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 5F38111E81E3 for <ietf@ietf.org>; Fri, 12 Jul 2013 02:19:00 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1UxUrS-000NUA-Vy; Fri, 12 Jul 2013 04:21:39 +0000
Date: Thu, 11 Jul 2013 18:21:37 -1000
Message-ID: <m2r4f4xvam.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Zhen Cao <zehn.cao@gmail.com>
Subject: Re: Regarding call Chinese names
In-Reply-To: <CAProHATm87UPp1ryY0AhSHvzP4c_TDpg88TWySzSxjdc6JvOZQ@mail.gmail.com>
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com> <51DEB9F2.9040405@viagenie.ca> <CAProHATm87UPp1ryY0AhSHvzP4c_TDpg88TWySzSxjdc6JvOZQ@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 Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jul 2013 09:19:01 -0000

> I notice most names in IETF are still presented in the English order,
> given name first and family name later.

same issue with japanese names.  there seems to be a convention of
capitalizing the family name

randy

From yding@cs.helsinki.fi  Fri Jul 12 03:19:18 2013
Return-Path: <yding@cs.helsinki.fi>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 796DE21F9D1E for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 03:19:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id koQSP9ihFNkt for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 03:19:06 -0700 (PDT)
Received: from courier.cs.helsinki.fi (courier.cs.helsinki.fi [128.214.9.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64B4B21F9C06 for <ietf@ietf.org>; Fri, 12 Jul 2013 03:19:06 -0700 (PDT)
X-DKIM: Courier DKIM Filter v0.50+pk-2013-06-17 courier.cs.helsinki.fi Fri Jul 12 13:18:47 2013
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cs.helsinki.fi; h=message-id:date:from:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; s= dkim20130528; bh=tOVZWQtbkKD2jzeyLLkZRVQDqp8fL9mNbyfiLLKr7Co=; b= fqfOi2xG2FIizhSq6/icyvPtxsuHs+8GwmXFVrfmlza+JyQu5SJ4KCqZ5ZQa9Wc6 mJQ+BadUSbRsb3xPNL/K0LHScwIyq5AOGcAVy1xMj3yoZ7N0cwX57IKp2hBhVhl4 TP46tmKTk73TsmXfIA4lufFcbPb1OdrRrM+V9xk2jQM=
Received: from [128.232.100.160] (c0160.aw.cl.cam.ac.uk [128.232.100.160]) (AUTH: PLAIN yding, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by mail.cs.helsinki.fi with esmtp; Fri, 12 Jul 2013 13:18:47 +0300 id 00068A98.51DFD807.00005E13
Message-ID: <51DFD801.9030107@cs.helsinki.fi>
Date: Fri, 12 Jul 2013 11:18:41 +0100
From: Aaron Yi DING <yding@cs.helsinki.fi>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
Subject: Re: Regarding call Chinese names
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com> <51DEB9F2.9040405@viagenie.ca> <CAProHATm87UPp1ryY0AhSHvzP4c_TDpg88TWySzSxjdc6JvOZQ@mail.gmail.com> <m2r4f4xvam.wl%randy@psg.com>
In-Reply-To: <m2r4f4xvam.wl%randy@psg.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jul 2013 10:19:18 -0000

On 12/07/13 05:21, Randy Bush wrote:
>> I notice most names in IETF are still presented in the English order,
>> given name first and family name later.
> same issue with japanese names.  there seems to be a convention of
> capitalizing the family name
>
> randy

Indeed a good practice. Capitalizing the family name avoids the 
confusion of oder.

Aaron

From hallam@gmail.com  Fri Jul 12 05:16:48 2013
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C4FB21E804E for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 05:16:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.341
X-Spam-Level: 
X-Spam-Status: No, score=-2.341 tagged_above=-999 required=5 tests=[AWL=0.258,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xh9OS0+i04uv for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 05:16:47 -0700 (PDT)
Received: from mail-we0-x22c.google.com (mail-we0-x22c.google.com [IPv6:2a00:1450:400c:c03::22c]) by ietfa.amsl.com (Postfix) with ESMTP id AAC8721F9FC6 for <ietf@ietf.org>; Fri, 12 Jul 2013 05:16:46 -0700 (PDT)
Received: by mail-we0-f172.google.com with SMTP id q56so8116252wes.31 for <ietf@ietf.org>; Fri, 12 Jul 2013 05:16:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=TRQRKBuU5MhFHp7Cru1ndEGdQ8/6ugPxg5ryDw0+TzI=; b=PZtnp92nHFL3qpC4KwJ8qIhTxQgzZkcXLa1FtfnoHbNjFgr2Dw6MKNY8jmGkPx53SA eJpKhWziA0GpzW/XOkX4bDzpW9Mw78pVZyxNSu83VbGu02tPVg2Ew9nXqKeYrK4HjAtK UqHN7iA2Gqs0SThjQj85ir49ru3nmkl6ovIsIuqD2EhyZjsSYLsfi7WUhwwT/Gy6VyiY V5SKQgneC0weKf/hBv0UJ8HVJjMoNr7IClgd8nfMabXjOdG4nbQbfwIAGd4h8B8AIR3e 1OFFqRrJcVDypT3ev7i79odOHSVyPjJZIoV1dhdbaXfxVLf0Z3RbSAhI1xRt8b6R/gCz ggtw==
MIME-Version: 1.0
X-Received: by 10.180.98.231 with SMTP id el7mr1474823wib.33.1373631404568; Fri, 12 Jul 2013 05:16:44 -0700 (PDT)
Received: by 10.194.6.65 with HTTP; Fri, 12 Jul 2013 05:16:44 -0700 (PDT)
In-Reply-To: <51DDD49E.5090406@dcrocker.net>
References: <1984CBB8-6862-4DBB-AFAE-F8461E694083@vigilsec.com> <51DDD49E.5090406@dcrocker.net>
Date: Fri, 12 Jul 2013 08:16:44 -0400
Message-ID: <CAMm+Lwj8_zmrp=SmUbb=a_4iEGA2zFaF2EDywaAq=5NkKbvp+w@mail.gmail.com>
Subject: Re: IAB Statement on Dotless Domains
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: multipart/alternative; boundary=f46d04428d2aebf84c04e14f7bac
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jul 2013 12:16:48 -0000

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

On Wed, Jul 10, 2013 at 5:39 PM, Dave Crocker <dhc@dcrocker.net> wrote:

> On 7/10/2013 11:59 AM, Russ Housley wrote:
>
>> The IAB has made a statement on dotless domains.  You can find this
>> statement here:
>> http://www.iab.org/documents/**correspondence-reports-**
>> documents/2013-2/iab-**statement-dotless-domains-**considered-harmful/<http://www.iab.org/documents/correspondence-reports-documents/2013-2/iab-statement-dotless-domains-considered-harmful/>
>>
>
>
> It's unfortunate that the IAB did not choose to circulate a draft before
> releasing the Statement.  The Statement could have been made a bit stronger
> in the concern it expresses.
>

Or it may have ended up more balanced or it might have more weight.

The IAB is selected by a process than ensures it is accountable for no one.
Therefore is speaks for no one. If the IAB wants to claim the authority of
speaking for the IETF in any matter it needs to circulate drafts and ensure
that it reflects IETF opinion before claiming to have reached a conclusion.



The DNS is going to go dotless. That is inevitable when people are paying a
quarter million dollars to get a dotless domain from ICANN. Trying to
control the situation with contractual language assumes that ICANN is going
to forgo large amounts of revenue over a technical concern.

Any issues that are created by dotless domains are going to be small
potatoes compared to the horror show resulting from the assignment of
.corp. And no, the problem with .corp is not the fact that there are a few
thousand certificates issued, it is the fact that there is a vast amount of
enterprise infrastructure predicated on the belief that .corp is a reserved
toplevel domain in the same way that 10.x.x.x is a reserved IP zone.

ICANN shows no sign of forgoing the registration fees for .corp which is
only one domain so why are they going to forgo the registration fees for
.microsoft .bankamerica and the other 10,000 companies that would pay that
type of money to protect their brand?

This is big money for the ICANN staff. Beckstrom was paid close to $1
million if you add in all the bonuses. And the bonuses are profit related.
So pretending that ICANN is going to hold off on the commercial
opportunities because of its tax status as a non-profit is to have a
criminally naive view of human nature.

And it is not just ICANN that has a commercial interest here. The proper
use of dotless domains ultimately threatens the commercial interests of the
TLD operators. Some of which are represented on the IAB. And sorry, if I
don't elect people then they don't represent me and f they don't represent
me and my interests I will conclude they represent their employers.


People are going to get used to typing in web.bankamerica or the like
because businesses are going to have a big incentive to drive users to the
dotless domains they control rather than continue to be held hostage by
every rent seeker with a new TLD - of which there will be several thousand
new ones every year under the TLD scheme.

Dotless domains are an inevitable consequence of the expansion of the TLD.
The job of the IAB should be to deal with the inevitable not perform
impressions of King Cnute.


And before people start bringing up all the reasons I am wrong here, first
consider the fact that for many years it was IETF ideology that NATs were a
terrible thing that had to be killed. A position I suspect was largely
driven by some aggressive lobbying by rent-seeking ISPs looking to collect
fees on a per device basis rather than per connection. If you look back in
the archives of the IETF list you will see that my position of NAT, that it
is an essential transitional technology for IPv6 was attacked by many
people sitting on the IAB for many years.

Today most people have come to accept my position on NAT, in fact it has
become the mainstream position. But none of the people who spent time
trying to slap me down or get me to stop expressing a heretical view have
ever said 'hey Phill you were right all along'. And I don't expect things
to be different this time round. But in ten years time it will be obvious
that domains are going to be dotless and three of the biggest dotless
domains are going to be called .apple and .microsoft and .google and they
are going to be the companies writing much of the software used to connect
to the Internet and their commercial interests are not exactly best served
by supporting clapped out thirty year old software programs.


Dotted domains were a bad idea in DNS to start with and giving a
perpetually renewing contract to Network Solutions to operate the best one
was sillier. We should embrace the opportunity to throw a bad engineering
decision into the dustbin of history not try to take the side of the TLD
operators whose rent seeking opportunities are threatened by the inevitable
transition to a dotless scheme.




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

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

<div dir=3D"ltr">On Wed, Jul 10, 2013 at 5:39 PM, Dave Crocker <span dir=3D=
"ltr">&lt;<a href=3D"mailto:dhc@dcrocker.net" target=3D"_blank">dhc@dcrocke=
r.net</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gma=
il_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On 7/10/2013 11:59 AM, Rus=
s Housley wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
The IAB has made a statement on dotless domains. =A0You can find this state=
ment here:<br>
<a href=3D"http://www.iab.org/documents/correspondence-reports-documents/20=
13-2/iab-statement-dotless-domains-considered-harmful/" target=3D"_blank">h=
ttp://www.iab.org/documents/<u></u>correspondence-reports-<u></u>documents/=
2013-2/iab-<u></u>statement-dotless-domains-<u></u>considered-harmful/</a><=
br>

</blockquote>
<br>
<br></div>
It&#39;s unfortunate that the IAB did not choose to circulate a draft befor=
e releasing the Statement. =A0The Statement could have been made a bit stro=
nger in the concern it expresses.<br></blockquote><div><br></div><div style=
>
Or it may have ended up more balanced or it might have more weight.</div><d=
iv style><br></div><div style>The IAB is selected by a process than ensures=
 it is accountable for no one. Therefore is speaks for no one. If the IAB w=
ants to claim the authority of speaking for the IETF in any matter it needs=
 to circulate drafts and ensure that it reflects IETF opinion before claimi=
ng to have reached a conclusion.</div>
<div style><br></div><div style><br></div><div style><br></div><div style>T=
he DNS is going to go dotless. That is inevitable when people are paying a =
quarter million dollars to get a dotless domain from ICANN. Trying to contr=
ol the situation with contractual language assumes that ICANN is going to f=
orgo large amounts of revenue over a technical concern.</div>
<div style><br></div><div style>Any issues that are created by dotless doma=
ins are going to be small potatoes compared to the horror show resulting fr=
om the assignment of .corp. And no, the problem with .corp is not the fact =
that there are a few thousand certificates issued, it is the fact that ther=
e is a vast amount of enterprise infrastructure predicated on the belief th=
at .corp is a reserved toplevel domain in the same way that 10.x.x.x is a r=
eserved IP zone.</div>
<div style><br></div><div style>ICANN shows no sign of forgoing the registr=
ation fees for .corp which is only one domain so why are they going to forg=
o the registration fees for .microsoft .bankamerica and the other 10,000 co=
mpanies that would pay that type of money to protect their brand?=A0</div>
<div style><br></div><div style>This is big money for the ICANN staff. Beck=
strom was paid close to $1 million if you add in all the bonuses. And the b=
onuses are profit related. So pretending that ICANN is going to hold off on=
 the commercial opportunities because of its tax status as a non-profit is =
to have a criminally naive view of human nature.=A0</div>
<div style><br></div><div style>And it is not just ICANN that has a commerc=
ial interest here. The proper use of dotless domains ultimately threatens t=
he commercial interests of the TLD operators. Some of which are represented=
 on the IAB. And sorry, if I don&#39;t elect people then they don&#39;t rep=
resent me and f they don&#39;t represent me and my interests I will conclud=
e they represent their employers.</div>
<div style><br></div><div style><br></div><div style>People are going to ge=
t used to typing in web.bankamerica or the like because businesses are goin=
g to have a big incentive to drive users to the dotless domains they contro=
l rather than continue to be held hostage by every rent seeker with a new T=
LD - of which there will be several thousand new ones every year under the =
TLD scheme.</div>
<div style><br></div><div style>Dotless domains are an inevitable consequen=
ce of the expansion of the TLD. The job of the IAB should be to deal with t=
he inevitable not perform impressions of King Cnute.=A0</div><div style><br=
>
</div><div style>=A0</div><div style>And before people start bringing up al=
l the reasons I am wrong here, first consider the fact that for many years =
it was IETF ideology that NATs were a terrible thing that had to be killed.=
 A position I suspect was largely driven by some aggressive lobbying by ren=
t-seeking ISPs looking to collect fees on a per device basis rather than pe=
r connection. If you look back in the archives of the IETF list you will se=
e that my position of NAT, that it is an essential transitional technology =
for IPv6 was attacked by many people sitting on the IAB for many years.</di=
v>
<div style><br></div><div style>Today most people have come to accept my po=
sition on NAT, in fact it has become the mainstream position. But none of t=
he people who spent time trying to slap me down or get me to stop expressin=
g a heretical view have ever said &#39;hey Phill you were right all along&#=
39;. And I don&#39;t expect things to be different this time round. But in =
ten years time it will be obvious that domains are going to be dotless and =
three of the biggest dotless domains are going to be called .apple and .mic=
rosoft and .google and they are going to be the companies writing much of t=
he software used to connect to the Internet and their commercial interests =
are not exactly best served by supporting clapped out thirty year old softw=
are programs.</div>
<div style><br></div><div style><br></div><div style>Dotted domains were a =
bad idea in DNS to start with and giving a perpetually renewing contract to=
 Network Solutions to operate the best one was sillier. We should embrace t=
he opportunity to throw a bad engineering decision into the dustbin of hist=
ory not try to take the side of the TLD operators whose rent seeking opport=
unities are threatened by the inevitable transition to a dotless scheme.</d=
iv>
<div style><br></div><div style><br></div><div style><br></div></div><div><=
br></div>-- <br>Website: <a href=3D"http://hallambaker.com/">http://hallamb=
aker.com/</a><br>
</div></div>

--f46d04428d2aebf84c04e14f7bac--

From moore@network-heretics.com  Fri Jul 12 05:58:41 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1535921F9E87 for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 05:58:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.528
X-Spam-Level: 
X-Spam-Status: No, score=-3.528 tagged_above=-999 required=5 tests=[AWL=0.071,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id goSMbjnntusO for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 05:58:36 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id D7DED21F9EB8 for <ietf@ietf.org>; Fri, 12 Jul 2013 05:58:35 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id E31A521272 for <ietf@ietf.org>; Fri, 12 Jul 2013 08:58:29 -0400 (EDT)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute5.internal (MEProxy); Fri, 12 Jul 2013 08:58:29 -0400
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=S3VnQ1a6Bd9EvvYoJ/KhM/ rpZD4=; b=WVQHSBaX0CkZm4pEWxNa3OAaGoUX4G/e97jS6TN8e11PUgcGa+wSO3 ZwrFmt64GLpTs/9MeBSaaDhUfYkJFb9Q9+CX3H/lnKK/jR4GpeVijxs9CwmOPihM lj3JZmFQnV56BqRR+tpEC0JLC7Cg/LPUf7pk0nH00lv7i3bmgnNj4=
X-Sasl-enc: RAEpjrLcpabY8P6le8q5BNKW4j4QkbxpFLpu9Av2Iu9I 1373633909
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id DCAD5C00E80; Fri, 12 Jul 2013 08:58:28 -0400 (EDT)
Message-ID: <51DFFD67.4020407@network-heretics.com>
Date: Fri, 12 Jul 2013 08:58:15 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IAB Statement on Dotless Domains
References: <1984CBB8-6862-4DBB-AFAE-F8461E694083@vigilsec.com> <51DDD49E.5090406@dcrocker.net> <CAMm+Lwj8_zmrp=SmUbb=a_4iEGA2zFaF2EDywaAq=5NkKbvp+w@mail.gmail.com>
In-Reply-To: <CAMm+Lwj8_zmrp=SmUbb=a_4iEGA2zFaF2EDywaAq=5NkKbvp+w@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jul 2013 12:58:41 -0000

On 07/12/2013 08:16 AM, Phillip Hallam-Baker wrote:
>
> And before people start bringing up all the reasons I am wrong here, 
> first consider the fact that for many years it was IETF ideology that 
> NATs were a terrible thing that had to be killed. A position I suspect 
> was largely driven by some aggressive lobbying by rent-seeking ISPs 
> looking to collect fees on a per device basis rather than per connection.

You are weakening your argument.   NATs still are a terrible thing that 
need to be killed.   They break applications and prevent many useful 
applications from being used on the Internet.    That much is more 
widely understood now than it was 10-15 years ago.

Keith


From hallam@gmail.com  Fri Jul 12 06:29:06 2013
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FACF11E80F9 for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 06:29:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.405
X-Spam-Level: 
X-Spam-Status: No, score=-2.405 tagged_above=-999 required=5 tests=[AWL=0.194,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id swxUHPJIhai2 for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 06:29:05 -0700 (PDT)
Received: from mail-wi0-x230.google.com (mail-wi0-x230.google.com [IPv6:2a00:1450:400c:c05::230]) by ietfa.amsl.com (Postfix) with ESMTP id AFD7A11E80F3 for <ietf@ietf.org>; Fri, 12 Jul 2013 06:28:58 -0700 (PDT)
Received: by mail-wi0-f176.google.com with SMTP id ey16so680448wid.3 for <ietf@ietf.org>; Fri, 12 Jul 2013 06:28:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=2obfySG9V3nQDs0BsYD3DRkgNA8M18/vIftiLIPkJQo=; b=BAUPjzXOYZw0XhnNsCviU5ujiJRkiVISBzYM3JfvT6bn0INa1r2TTTRJHI2pDwUWrV cQzXbgVJfcGtHPuF0RL/vlcQOG16Wc6VE5ZTMo/yMr5YwKTq+JQ+Ki9MQKH19St36hrp Fei8nlCIjv+R1Xa8kVQkhsf5bj1o5Q/9qK3Xje2H4jouV8wNV2bPABXPtx5ktGKWmaLt Kh5GfXFKnAe6KFakdUduAJfn70sJw7ewF7JB7G+CVEk3BAESZhB9iYEvJn7IzrQRsGhN dIukk45Bwds1ya++LNInfSFe5vet2cZucdwEPTl4OZE6rMUbdTRSD9dt0ejbYbsesEf3 KJEw==
MIME-Version: 1.0
X-Received: by 10.194.179.33 with SMTP id dd1mr23913863wjc.51.1373635737346; Fri, 12 Jul 2013 06:28:57 -0700 (PDT)
Received: by 10.194.6.65 with HTTP; Fri, 12 Jul 2013 06:28:57 -0700 (PDT)
In-Reply-To: <51DFFD67.4020407@network-heretics.com>
References: <1984CBB8-6862-4DBB-AFAE-F8461E694083@vigilsec.com> <51DDD49E.5090406@dcrocker.net> <CAMm+Lwj8_zmrp=SmUbb=a_4iEGA2zFaF2EDywaAq=5NkKbvp+w@mail.gmail.com> <51DFFD67.4020407@network-heretics.com>
Date: Fri, 12 Jul 2013 09:28:57 -0400
Message-ID: <CAMm+LwgOTk-fkuKcu6442zZ_5ti5pWP6oGmP7yV2OgVBQHUqxg@mail.gmail.com>
Subject: Re: IAB Statement on Dotless Domains
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Keith Moore <moore@network-heretics.com>
Content-Type: multipart/alternative; boundary=089e013d0f802ced7304e1507e86
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jul 2013 13:29:06 -0000

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

On Fri, Jul 12, 2013 at 8:58 AM, Keith Moore <moore@network-heretics.com>wrote:

> On 07/12/2013 08:16 AM, Phillip Hallam-Baker wrote:
>
>>
>> And before people start bringing up all the reasons I am wrong here,
>> first consider the fact that for many years it was IETF ideology that NATs
>> were a terrible thing that had to be killed. A position I suspect was
>> largely driven by some aggressive lobbying by rent-seeking ISPs looking to
>> collect fees on a per device basis rather than per connection.
>>
>
> You are weakening your argument.   NATs still are a terrible thing that
> need to be killed.   They break applications and prevent many useful
> applications from being used on the Internet.    That much is more widely
> understood now than it was 10-15 years ago.


The Internet has less than 4 billion addresses for well over six billion
devices.

I think that at this point you are the only person still making the
argument that the world should reject the easy fix for IPv4 address
exhaustion that solves their problems at negligible cost to them for the
sake of forcing them to make a transition that would be very difficult,
expensive and impact every part of the infrastructure.

But it would be nice if at least one of those people who argued against me
when I was making the case for NAT that has now become the accepted
approach would say 'hey Phill you were right there, I am sorry for implying
that you were an evil heretical loon for suggesting it'. Not that I am
holding my breath waiting.

Most folk here value consensus. I do not value consensus when it is wrong.


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

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Fri, Jul 12, 2013 at 8:58 AM, Keith Moore <span dir=3D"ltr">&lt;=
<a href=3D"mailto:moore@network-heretics.com" target=3D"_blank">moore@netwo=
rk-heretics.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/12/2013 08:16 AM, Ph=
illip Hallam-Baker wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
And before people start bringing up all the reasons I am wrong here, first =
consider the fact that for many years it was IETF ideology that NATs were a=
 terrible thing that had to be killed. A position I suspect was largely dri=
ven by some aggressive lobbying by rent-seeking ISPs looking to collect fee=
s on a per device basis rather than per connection.<br>

</blockquote>
<br></div>
You are weakening your argument. =A0 NATs still are a terrible thing that n=
eed to be killed. =A0 They break applications and prevent many useful appli=
cations from being used on the Internet. =A0 =A0That much is more widely un=
derstood now than it was 10-15 years ago.</blockquote>
<div><br></div><div>The Internet has less than 4 billion addresses for well=
 over six billion devices.=A0<br></div><div style><br></div><div style>I th=
ink that at this point you are the only person still making the argument th=
at the world should reject the easy fix for IPv4 address exhaustion that so=
lves their problems at negligible cost to them for the sake of forcing them=
 to make a transition that would be very difficult, expensive and impact ev=
ery part of the infrastructure.</div>
<div style><br></div><div style>But it would be nice if at least one of tho=
se people who argued against me when I was making the case for NAT that has=
 now become the accepted approach would say &#39;hey Phill you were right t=
here, I am sorry for implying that you were an evil heretical loon for sugg=
esting it&#39;. Not that I am holding my breath waiting.</div>
<div style><br></div><div style>Most folk here value consensus. I do not va=
lue consensus when it is wrong.=A0</div></div><br clear=3D"all"><div><br></=
div>-- <br>Website: <a href=3D"http://hallambaker.com/">http://hallambaker.=
com/</a><br>

</div></div>

--089e013d0f802ced7304e1507e86--

From moore@network-heretics.com  Fri Jul 12 06:38:57 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A111B11E811E for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 06:38:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.536
X-Spam-Level: 
X-Spam-Status: No, score=-3.536 tagged_above=-999 required=5 tests=[AWL=0.062,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nlcF+kXfBUJY for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 06:38:52 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id 7471D11E8110 for <ietf@ietf.org>; Fri, 12 Jul 2013 06:38:52 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id D4E53212A7; Fri, 12 Jul 2013 09:38:51 -0400 (EDT)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute4.internal (MEProxy); Fri, 12 Jul 2013 09:38:51 -0400
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=c/fu ufJ/KtBZUhZNc753EWoTlN4=; b=iV8eoGkti6doGDv32l1NG5kBStZOyIG0XTCp ddduecGFY1ZwNnvqPyzyWmct22Xkt8XSyaKag6owPeiB4TdL/dm72DoqjCMx3HlI mQwrcW+msu7Pvw50YYurNDUg5/SRyM2zrdf4VrB15PSyjKF+yA2TCHLQozxv88nX pKJNwK8=
X-Sasl-enc: FrNRsiTobzNRE4TYnl8yBepJq/IHK8n5UYKWPUMdC7u8 1373636330
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 028F7C00E81; Fri, 12 Jul 2013 09:38:49 -0400 (EDT)
Message-ID: <51E006DB.80708@network-heretics.com>
Date: Fri, 12 Jul 2013 09:38:35 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: IAB Statement on Dotless Domains
References: <1984CBB8-6862-4DBB-AFAE-F8461E694083@vigilsec.com> <51DDD49E.5090406@dcrocker.net> <CAMm+Lwj8_zmrp=SmUbb=a_4iEGA2zFaF2EDywaAq=5NkKbvp+w@mail.gmail.com> <51DFFD67.4020407@network-heretics.com> <CAMm+LwgOTk-fkuKcu6442zZ_5ti5pWP6oGmP7yV2OgVBQHUqxg@mail.gmail.com>
In-Reply-To: <CAMm+LwgOTk-fkuKcu6442zZ_5ti5pWP6oGmP7yV2OgVBQHUqxg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------050102090901090709020900"
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jul 2013 13:38:57 -0000

This is a multi-part message in MIME format.
--------------050102090901090709020900
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 07/12/2013 09:28 AM, Phillip Hallam-Baker wrote:
> On Fri, Jul 12, 2013 at 8:58 AM, Keith Moore 
> <moore@network-heretics.com <mailto:moore@network-heretics.com>> wrote:
>
>     On 07/12/2013 08:16 AM, Phillip Hallam-Baker wrote:
>
>
>         And before people start bringing up all the reasons I am wrong
>         here, first consider the fact that for many years it was IETF
>         ideology that NATs were a terrible thing that had to be
>         killed. A position I suspect was largely driven by some
>         aggressive lobbying by rent-seeking ISPs looking to collect
>         fees on a per device basis rather than per connection.
>
>
>     You are weakening your argument.   NATs still are a terrible thing
>     that need to be killed.   They break applications and prevent many
>     useful applications from being used on the Internet.    That much
>     is more widely understood now than it was 10-15 years ago.
>
>
> The Internet has less than 4 billion addresses for well over six 
> billion devices.

No, the Internet has approximately 2**128 addresses.   NATs are a large 
part of the reason that IPv6 adoption has been delayed.

> I think that at this point you are the only person still making the 
> argument that the world should reject the easy fix for IPv4 address 
> exhaustion that solves their problems at negligible cost to them for 
> the sake of forcing them to make a transition that would be very 
> difficult, expensive and impact every part of the infrastructure.

You are wrong both about solving the problems and negligible cost. (And 
the real issue isn't so much the cost, but who pays.)

> But it would be nice if at least one of those people who argued 
> against me when I was making the case for NAT that has now become the 
> accepted approach would say 'hey Phill you were right there, I am 
> sorry for implying that you were an evil heretical loon for suggesting 
> it'. Not that I am holding my breath waiting.

If you were right, someone might say that.

> Most folk here value consensus. I do not value consensus when it is wrong.

Nor do I.

Keith


--------------050102090901090709020900
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 07/12/2013 09:28 AM, Phillip
      Hallam-Baker wrote:<br>
    </div>
    <blockquote
cite="mid:CAMm+LwgOTk-fkuKcu6442zZ_5ti5pWP6oGmP7yV2OgVBQHUqxg@mail.gmail.com"
      type="cite">
      <div dir="ltr">On Fri, Jul 12, 2013 at 8:58 AM, 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">
              <div class="im">On 07/12/2013 08:16 AM, Phillip
                Hallam-Baker wrote:<br>
                <blockquote class="gmail_quote" style="margin:0 0 0
                  .8ex;border-left:1px #ccc solid;padding-left:1ex">
                  <br>
                  And before people start bringing up all the reasons I
                  am wrong here, first consider the fact that for many
                  years it was IETF ideology that NATs were a terrible
                  thing that had to be killed. A position I suspect was
                  largely driven by some aggressive lobbying by
                  rent-seeking ISPs looking to collect fees on a per
                  device basis rather than per connection.<br>
                </blockquote>
                <br>
              </div>
              You are weakening your argument. &nbsp; NATs still are a
              terrible thing that need to be killed. &nbsp; They break
              applications and prevent many useful applications from
              being used on the Internet. &nbsp; &nbsp;That much is more widely
              understood now than it was 10-15 years ago.</blockquote>
            <div><br>
            </div>
            <div>The Internet has less than 4 billion addresses for well
              over six billion devices. <br>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    No, the Internet has approximately 2**128 addresses.&nbsp;&nbsp; NATs are a
    large part of the reason that IPv6 adoption has been delayed.<br>
    <br>
    <blockquote
cite="mid:CAMm+LwgOTk-fkuKcu6442zZ_5ti5pWP6oGmP7yV2OgVBQHUqxg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div style="">I think that at this point you are the only
              person still making the argument that the world should
              reject the easy fix for IPv4 address exhaustion that
              solves their problems at negligible cost to them for the
              sake of forcing them to make a transition that would be
              very difficult, expensive and impact every part of the
              infrastructure.</div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    You are wrong both about solving the problems and negligible cost.&nbsp;&nbsp;
    (And the real issue isn't so much the cost, but who pays.)<br>
    <br>
    <blockquote
cite="mid:CAMm+LwgOTk-fkuKcu6442zZ_5ti5pWP6oGmP7yV2OgVBQHUqxg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div style="">But it would be nice if at least one of those
              people who argued against me when I was making the case
              for NAT that has now become the accepted approach would
              say 'hey Phill you were right there, I am sorry for
              implying that you were an evil heretical loon for
              suggesting it'. Not that I am holding my breath waiting.</div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    If you were right, someone might say that.<br>
    <br>
    <blockquote
cite="mid:CAMm+LwgOTk-fkuKcu6442zZ_5ti5pWP6oGmP7yV2OgVBQHUqxg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div style="">Most folk here value consensus. I do not value
              consensus when it is wrong.</div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    Nor do I.<br>
    <br>
    Keith<br>
    <br>
  </body>
</html>

--------------050102090901090709020900--

From hallam@gmail.com  Fri Jul 12 06:46:46 2013
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CACB221F9F7F; Fri, 12 Jul 2013 06:46:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.427
X-Spam-Level: 
X-Spam-Status: No, score=-2.427 tagged_above=-999 required=5 tests=[AWL=0.172,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yZpU5pDWcnX8; Fri, 12 Jul 2013 06:46:45 -0700 (PDT)
Received: from mail-wi0-x22d.google.com (mail-wi0-x22d.google.com [IPv6:2a00:1450:400c:c05::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 5250421F8624; Fri, 12 Jul 2013 06:46:45 -0700 (PDT)
Received: by mail-wi0-f173.google.com with SMTP id hq4so699691wib.6 for <multiple recipients>; Fri, 12 Jul 2013 06:46:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=QzZhOWdSsCZnnYq4kOrs7RFoxYE02Qjr/4iJVW0ieOU=; b=uS0J7MTk5YmqbJcdEQ9lqa9H3ntVAmBv4G2FT8ozaw9mUQ0o1aW55HYlGqXSah9ySj 6/HwZmnYi1cEI2Zu7Ad9wBZDW6pOA92dBwKKoRqd12OT7cQZZHN2DLSNlxwCwZFW6yWj T0xgT8RUZw8h5YO2jVv3zy+gNlRZjCbUM5luiycKvZ0uKagmF+PJvXTwJEOk0T3LcDEw tyeoVi53bnpMHdq2wPt76rZ9QxxpkWyAS9DrloXsnLh4xqlIGrFiZQ9vFTfgKXyKa02X WmNOwUkJNWG0AS4/sdr6/a/fJKnWxPlU8qcrdkaZu/7uTS4RWZuJp7N/KkSkaBJFOXaf sA4w==
MIME-Version: 1.0
X-Received: by 10.180.126.2 with SMTP id mu2mr1685190wib.63.1373636803827; Fri, 12 Jul 2013 06:46:43 -0700 (PDT)
Received: by 10.194.6.65 with HTTP; Fri, 12 Jul 2013 06:46:43 -0700 (PDT)
In-Reply-To: <CADnDZ89g=-_V_J65=Lb2VfRv2+pvDPPwX0nyfT-+YE=bLFfCDg@mail.gmail.com>
References: <51DD8551.6090502@cisco.com> <CADnDZ89g=-_V_J65=Lb2VfRv2+pvDPPwX0nyfT-+YE=bLFfCDg@mail.gmail.com>
Date: Fri, 12 Jul 2013 09:46:43 -0400
Message-ID: <CAMm+LwiA6-+toYrc9Lsyb+x3cZCG7UQQ=d87Hibh-SjmNOkrxQ@mail.gmail.com>
Subject: Re: IETF registration fee?
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Content-Type: multipart/alternative; boundary=e89a8f642dfcbe21ad04e150bdf6
Cc: ietf-registrar@ietf.org, Paul Aitken <paitken@cisco.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jul 2013 13:46:46 -0000

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

To be clear here, I do not think the IETF conference fee to be at all
unreasonable. I have paid it out of my own pocket on occasion.

My concern here is that arguments of the form 'we can't change the
conference model because IETF needs the money' will lead to disaster. The
Internet is changing a lot of business models at the moment and there is a
lot more destruction going on than creation. It is quite likely that at
some points over the next 10-20 years the conferences will lose money. We
might even be at that point already since the profitability is largely
dependent on getting sponsors and the sponsors are paying to support the
IETF not the meetings.

The world looks very different today than 30 years ago and not just because
there is no Soviet Union. Most of the changes of the last 20 years are
actually the consequences of container freight rather than the Internet.
The dotcom businesses were all about moving atoms, not bits.

The Internet effects are only just starting to be felt. The Internet is
movement of information and we have yet to see the type of major industrial
restructuring in the knowledge industries. Container freight and barcodes
are the reasons that all those mom and pop stationary suppliers were
replaced by Staples and Office Max. We haven't yet seen all those hundreds
of tier 3 universities replaced by franchises affiliated with the big name
universities like MIT, Stanford and the rest. But that is going to happen.


The IETF actually has a perfectly logical business model. ISOC collects a
rent off .org which provides several million a year in income which has to
be spent somehow and the IETF is an activity of ISOC.

Now that is not an argument for 'problem solved' but it is an argument that
the IETF is not forced to keep the conference funding model untouched for
fear of breaking the business model.




On Fri, Jul 12, 2013 at 12:27 AM, Abdussalam Baryun <
abdussalambaryun@gmail.com> wrote:

> Hi Paul,
>
> I agree with you if someone attends without presenting work, but I
> think the fees is reasonable if we compare with other conferences fees
> per day (don't forget your free to presentations of your docs and get
> feedback from many sessions, this may change in future if higher
> load). If the IETF considers your request, I think it will increase
> participation maybe about 5% globaly and 20% locally, so mostly
> encourages regional participations. I will also add that if the IETF
> can consider newcomers to get discount for one day, because newcomers
> may want to get a feeling of the meeting.
>
> AB
>
> On 7/10/13, Paul Aitken <paitken@cisco.com> wrote:
> > Can you help me understand why the One Day Pass rate ($350) is so high
> > compared with the full week rate ($650 / $800)?
> >
> > Registering for two days could cost more than a week!
> >
> > Surely the day rate should be a little more than (week/5), eg about $175
> > - $200, to encourage those who only want/need to contribute on
> > particular days?
> >
> > Thanks,
> > P.
> >
>



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

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

<div dir=3D"ltr">To be clear here, I do not think the IETF conference fee t=
o be at all unreasonable. I have paid it out of my own pocket on occasion.<=
div><br></div><div style>My concern here is that arguments of the form &#39=
;we can&#39;t change the conference model because IETF needs the money&#39;=
 will lead to disaster. The Internet is changing a lot of business models a=
t the moment and there is a lot more destruction going on than creation. It=
 is quite likely that at some points over the next 10-20 years the conferen=
ces will lose money. We might even be at that point already since the profi=
tability is largely dependent on getting sponsors and the sponsors are payi=
ng to support the IETF not the meetings.</div>
<div style><br></div><div style>The world looks very different today than 3=
0 years ago and not just because there is no Soviet Union. Most of the chan=
ges of the last 20 years are actually the consequences of container freight=
 rather than the Internet. The dotcom businesses were all about moving atom=
s, not bits.</div>
<div style><br></div><div style>The Internet effects are only just starting=
 to be felt. The Internet is movement of information and we have yet to see=
 the type of major industrial restructuring in the knowledge industries. Co=
ntainer freight and barcodes are the reasons that all those mom and pop sta=
tionary suppliers were replaced by Staples and Office Max. We haven&#39;t y=
et seen all those hundreds of tier 3 universities replaced by franchises af=
filiated with the big name universities like MIT, Stanford and the rest. Bu=
t that is going to happen.</div>
<div style><br></div><div style><br></div><div style>The IETF actually has =
a perfectly logical business model. ISOC collects a rent off .org which pro=
vides several million a year in income which has to be spent somehow and th=
e IETF is an activity of ISOC.=A0</div>
<div style><br></div><div style>Now that is not an argument for &#39;proble=
m solved&#39; but it is an argument that the IETF is not forced to keep the=
 conference funding model untouched for fear of breaking the business model=
.=A0</div>
<div style><br></div><div style><br></div></div><div class=3D"gmail_extra">=
<br><br><div class=3D"gmail_quote">On Fri, Jul 12, 2013 at 12:27 AM, Abduss=
alam 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">Hi Paul,<br>
<br>
I agree with you if someone attends without presenting work, but I<br>
think the fees is reasonable if we compare with other conferences fees<br>
per day (don&#39;t forget your free to presentations of your docs and get<b=
r>
feedback from many sessions, this may change in future if higher<br>
load). If the IETF considers your request, I think it will increase<br>
participation maybe about 5% globaly and 20% locally, so mostly<br>
encourages regional participations. I will also add that if the IETF<br>
can consider newcomers to get discount for one day, because newcomers<br>
may want to get a feeling of the meeting.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
AB<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
On 7/10/13, Paul Aitken &lt;<a href=3D"mailto:paitken@cisco.com">paitken@ci=
sco.com</a>&gt; wrote:<br>
&gt; Can you help me understand why the One Day Pass rate ($350) is so high=
<br>
&gt; compared with the full week rate ($650 / $800)?<br>
&gt;<br>
&gt; Registering for two days could cost more than a week!<br>
&gt;<br>
&gt; Surely the day rate should be a little more than (week/5), eg about $1=
75<br>
&gt; - $200, to encourage those who only want/need to contribute on<br>
&gt; particular days?<br>
&gt;<br>
&gt; Thanks,<br>
&gt; P.<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>

--e89a8f642dfcbe21ad04e150bdf6--

From scott.brim@gmail.com  Fri Jul 12 07:03:44 2013
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03CDC11E8100 for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 07:03:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fp2pdJDJZQAt for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 07:03:43 -0700 (PDT)
Received: from mail-oa0-x22d.google.com (mail-oa0-x22d.google.com [IPv6:2607:f8b0:4003:c02::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 9182E21F9FA8 for <ietf@ietf.org>; Fri, 12 Jul 2013 07:03:43 -0700 (PDT)
Received: by mail-oa0-f45.google.com with SMTP id j1so12756049oag.4 for <ietf@ietf.org>; Fri, 12 Jul 2013 07:03:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=vq/SXs44+ZdJ9vtEXXN1Q7RSdhzcvSxGGYX6nNsorPU=; b=mICYECWr2QdT+87DKWj/ixPzsR1STL9FEfX897+cHdBftElC92Mjg+shtPMYpPUH9Y Fs5+wTfR2iCPktBEn8hpnGmQpbYo6aBgVPUr/882wOAoNOSMTQPU35455+zybV90SiPC /7OmmhrH9/Mrm7SM9CHZV/3S+uqnspOfoZAykX3n7TlL4xShOU0JtTq5QZB9joY+eXcp BV57LEoBSFNfjBnWyx8dzWczeqUaRhVaVW6/b4OThizx5hQHbD5Z97swnTzZCLwSHe2y AgAQYjfP1rP1ZZgKHOq5roLFR8NIa/2R0A1V1iVR8Xqop7lMaopCcI99lck7VfHalZhn qPzw==
X-Received: by 10.60.135.167 with SMTP id pt7mr35912578oeb.59.1373637823100; Fri, 12 Jul 2013 07:03:43 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.251.226 with HTTP; Fri, 12 Jul 2013 07:03:23 -0700 (PDT)
In-Reply-To: <CANF0JMAGMqc7DZsp2T9qi4bWNq6NvWUq3+Fx6Um9nC-_hyT75A@mail.gmail.com>
References: <CANF0JMAGMqc7DZsp2T9qi4bWNq6NvWUq3+Fx6Um9nC-_hyT75A@mail.gmail.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Fri, 12 Jul 2013 10:03:23 -0400
Message-ID: <CAPv4CP_TgVgEb1hCyb8jk5W26WmPzL2xrySqT3DHDoNQq3iyuQ@mail.gmail.com>
Subject: Re: Excuse me for not able to reply shortly
To: Hui Deng <denghui02@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jul 2013 14:03:44 -0000

On Fri, Jul 12, 2013 at 1:14 AM, Hui Deng <denghui02@gmail.com> wrote:
> I really don't know whether IETF should recommend Deng Hui or Hui Deng

That's the question! :-D

I believe the Chinese participants should reach this consensus
themselves and let the IETF know.  Similarly for other groups, e.g.
Japanese -- when I speak at the microphone, should I say Murai-san or
Jun?  Please decide.

From jnc@mercury.lcs.mit.edu  Fri Jul 12 07:10:43 2013
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC1AF11E810C for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 07:10:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iWHX5soOyNCa for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 07:10:28 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id D194921E8051 for <ietf@ietf.org>; Fri, 12 Jul 2013 07:10:28 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 252DC18C15D; Fri, 12 Jul 2013 10:10:26 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: IAB Statement on Dotless Domains
Message-Id: <20130712141026.252DC18C15D@mercury.lcs.mit.edu>
Date: Fri, 12 Jul 2013 10:10:26 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jul 2013 14:10:43 -0000

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

    > for many years it was IETF ideology that NATs were a terrible thing
    > that had to be killed. A position I suspect was largely driven by some
    > aggressive lobbying by rent-seeking ISPs looking to collect fees on a
    > per device basis rather than per connection.

That is so confused.

First, many (the majority?) of people in the IETF who didn't like NATs had
sound technical reasons for so doing (it breaks end-end, makes third party
referrals in peer-peer applications harder, etc). Those of us who diagree
with them don't (in general) disagree about those costs, just think the
benefits of NAT outweigh them. (See below.)

Second, while the ability to have a per-device fee might have seemed like a
nice fantasy to some ISPs, the reality is that their costs are driven by i)
the total amount of bandwidth used at the site, and ii) the costs of
providing the connection (hardware, configuration, etc). Anyone who tried to
monetize per-device would have had competition from people who only charged
based on their actual costs. And given that NATs are so easy for consumers to
set up, I think most ISPs realize they save them a bundle in customer support
costs (given that each customer call costs them some amazing amount of
money); the inevitable support costs from per-device would diminish the
amount of money allegedly to be made.

    > From: Keith Moore <moore@network-heretics.com>

    > NATs still are a terrible thing that need to be killed. They break
    > applications and prevent many useful applications from being used on
    > the Internet. That much is more widely understood now than it was 10-15
    > years ago.

You're still ignoring what _empirical evidence_ has shown to be true: yes,
there are costs to NAT, but it also has benefits, in that it attacks some of
the fundamental flaws in the IPvN architectures in general (lack of local
allocation of identifiers, ability to relocate [aka renumber] without local
reconfiguration, etc) and in IPv4 in particular (not enough address bits),
and when people look at the overall cost/benefit ratio, they prefer it to the
alternatives.

	Noel

From hallam@gmail.com  Fri Jul 12 07:13:27 2013
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D956021F9A48 for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 07:13:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.444
X-Spam-Level: 
X-Spam-Status: No, score=-2.444 tagged_above=-999 required=5 tests=[AWL=0.155,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sbpu7CAiRfSt for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 07:13:27 -0700 (PDT)
Received: from mail-wg0-x230.google.com (mail-wg0-x230.google.com [IPv6:2a00:1450:400c:c00::230]) by ietfa.amsl.com (Postfix) with ESMTP id 458B521F9D28 for <ietf@ietf.org>; Fri, 12 Jul 2013 07:13:18 -0700 (PDT)
Received: by mail-wg0-f48.google.com with SMTP id f11so8058664wgh.3 for <ietf@ietf.org>; Fri, 12 Jul 2013 07:13:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=9Pdb+26MhVc/bVZTqNqxngNpRToA91IjUKPGW7TK4N8=; b=yjig9DtF3gNxMYJNtrgszrBa6p5UHg22UsJ8vYdXXnyKgT48MMBacOENwnFvJr0fuE 3ibbD/m/8j+GhggFjtfBT00oNPrQv3Omc4GscQtFHoBda8qrBizIY5uva/YTOcapnsVV 0PnjPdMkM05EUnRHluBDjYLLwo+aJsKzRXUYuJ7wpQxQPDslBks2MptAxtdLfkFurSDS 8V6o7YLdAWK9rhnPY+oP7JqB8xoGzCOhZFc81j2N57mqkTUglfGkFW2/XUnMk7VvTjZ2 WUV5d+mbBIBpuCFeeQOy953q82oLTRsYk9ICbFGEV3vsn+QjKagYNR+A86EPDhUbCKlC kR1A==
MIME-Version: 1.0
X-Received: by 10.194.242.134 with SMTP id wq6mr23755399wjc.94.1373638398131;  Fri, 12 Jul 2013 07:13:18 -0700 (PDT)
Received: by 10.194.6.65 with HTTP; Fri, 12 Jul 2013 07:13:18 -0700 (PDT)
In-Reply-To: <51E006DB.80708@network-heretics.com>
References: <1984CBB8-6862-4DBB-AFAE-F8461E694083@vigilsec.com> <51DDD49E.5090406@dcrocker.net> <CAMm+Lwj8_zmrp=SmUbb=a_4iEGA2zFaF2EDywaAq=5NkKbvp+w@mail.gmail.com> <51DFFD67.4020407@network-heretics.com> <CAMm+LwgOTk-fkuKcu6442zZ_5ti5pWP6oGmP7yV2OgVBQHUqxg@mail.gmail.com> <51E006DB.80708@network-heretics.com>
Date: Fri, 12 Jul 2013 10:13:18 -0400
Message-ID: <CAMm+LwiQZ2NQOZ0ygVc5T+jNfQGDMnNae8+K9G7hT1r2wV2xDA@mail.gmail.com>
Subject: Re: IAB Statement on Dotless Domains
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Keith Moore <moore@network-heretics.com>
Content-Type: multipart/alternative; boundary=089e0141a1fcc5470b04e1511c6e
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jul 2013 14:13:28 -0000

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

Keith, read my words, I choose them more carefully than you imagine.

solves their problems at negligible cost TO THEM

What part of that do you disagree with? I don't dispute the fact that NAT
is a suboptimal solution if we look at the system as a whole. But the
reason I deployed NAT in my house was that Roadrunner wanted $10 extra per
month for every device I connected to a maximum of 4. I have over 200 IP
enabled devices in my house.



On Fri, Jul 12, 2013 at 9:38 AM, Keith Moore <moore@network-heretics.com>wrote:

>  On 07/12/2013 09:28 AM, Phillip Hallam-Baker wrote:
>
> On Fri, Jul 12, 2013 at 8:58 AM, Keith Moore <moore@network-heretics.com>wrote:
>
>> On 07/12/2013 08:16 AM, Phillip Hallam-Baker wrote:
>>
>>>
>>> And before people start bringing up all the reasons I am wrong here,
>>> first consider the fact that for many years it was IETF ideology that NATs
>>> were a terrible thing that had to be killed. A position I suspect was
>>> largely driven by some aggressive lobbying by rent-seeking ISPs looking to
>>> collect fees on a per device basis rather than per connection.
>>>
>>
>>  You are weakening your argument.   NATs still are a terrible thing that
>> need to be killed.   They break applications and prevent many useful
>> applications from being used on the Internet.    That much is more widely
>> understood now than it was 10-15 years ago.
>
>
>  The Internet has less than 4 billion addresses for well over six billion
> devices.
>
>
> No, the Internet has approximately 2**128 addresses.   NATs are a large
> part of the reason that IPv6 adoption has been delayed.
>
>
>   I think that at this point you are the only person still making the
> argument that the world should reject the easy fix for IPv4 address
> exhaustion that solves their problems at negligible cost to them for the
> sake of forcing them to make a transition that would be very difficult,
> expensive and impact every part of the infrastructure.
>
>
> You are wrong both about solving the problems and negligible cost.   (And
> the real issue isn't so much the cost, but who pays.)
>
>
>   But it would be nice if at least one of those people who argued against
> me when I was making the case for NAT that has now become the accepted
> approach would say 'hey Phill you were right there, I am sorry for implying
> that you were an evil heretical loon for suggesting it'. Not that I am
> holding my breath waiting.
>
>
> If you were right, someone might say that.
>
>
>   Most folk here value consensus. I do not value consensus when it is
> wrong.
>
>
> Nor do I.
>
> Keith
>
>


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

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

<div dir=3D"ltr">Keith, read my words, I choose them more carefully than yo=
u imagine.<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra"><=
blockquote type=3D"cite" style=3D"color:rgb(80,0,80)"><div dir=3D"ltr"><div=
 class=3D"gmail_extra">
<div class=3D"gmail_quote">solves their problems at negligible cost TO THEM=
</div></div></div></blockquote></div><div class=3D"gmail_extra">What part o=
f that do you disagree with? I don&#39;t dispute the fact that NAT is a sub=
optimal solution if we look at the system as a whole. But the reason I depl=
oyed NAT in my house was that Roadrunner wanted $10 extra per month for eve=
ry device I connected to a maximum of 4. I have over 200 IP enabled devices=
 in my house.<br>
<br><br><br><div class=3D"gmail_quote">On Fri, Jul 12, 2013 at 9:38 AM, Kei=
th Moore <span dir=3D"ltr">&lt;<a href=3D"mailto:moore@network-heretics.com=
" target=3D"_blank">moore@network-heretics.com</a>&gt;</span> wrote:<br><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-lef=
t-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padd=
ing-left:1ex">

 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000"><div class=3D"im">
    <div>On 07/12/2013 09:28 AM, Phillip
      Hallam-Baker wrote:<br>
    </div>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">On Fri, Jul 12, 2013 at 8:58 AM, Keith Moore <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:moore@network-heretics.com" target=3D"_bla=
nk">moore@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:0px 0px 0px 0=
.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-s=
tyle:solid;padding-left:1ex">
              <div>On 07/12/2013 08:16 AM, Phillip
                Hallam-Baker wrote:<br>
                <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0=
px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-le=
ft-style:solid;padding-left:1ex">
                  <br>
                  And before people start bringing up all the reasons I
                  am wrong here, first consider the fact that for many
                  years it was IETF ideology that NATs were a terrible
                  thing that had to be killed. A position I suspect was
                  largely driven by some aggressive lobbying by
                  rent-seeking ISPs looking to collect fees on a per
                  device basis rather than per connection.<br>
                </blockquote>
                <br>
              </div>
              You are weakening your argument. =A0 NATs still are a
              terrible thing that need to be killed. =A0 They break
              applications and prevent many useful applications from
              being used on the Internet. =A0 =A0That much is more widely
              understood now than it was 10-15 years ago.</blockquote>
            <div><br>
            </div>
            <div>The Internet has less than 4 billion addresses for well
              over six billion devices. <br>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <br></div>
    No, the Internet has approximately 2**128 addresses.=A0=A0 NATs are a
    large part of the reason that IPv6 adoption has been delayed.<div class=
=3D"im"><br>
    <br>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div class=3D"gmail_extra">
          <div class=3D"gmail_quote">
            <div>I think that at this point you are the only
              person still making the argument that the world should
              reject the easy fix for IPv4 address exhaustion that
              solves their problems at negligible cost to them for the
              sake of forcing them to make a transition that would be
              very difficult, expensive and impact every part of the
              infrastructure.</div>
          </div>
        </div>
      </div>
    </blockquote>
    <br></div>
    You are wrong both about solving the problems and negligible cost.=A0=
=A0
    (And the real issue isn&#39;t so much the cost, but who pays.)<div clas=
s=3D"im"><br>
    <br>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div class=3D"gmail_extra">
          <div class=3D"gmail_quote">
            <div>But it would be nice if at least one of those
              people who argued against me when I was making the case
              for NAT that has now become the accepted approach would
              say &#39;hey Phill you were right there, I am sorry for
              implying that you were an evil heretical loon for
              suggesting it&#39;. Not that I am holding my breath waiting.<=
/div>
          </div>
        </div>
      </div>
    </blockquote>
    <br></div>
    If you were right, someone might say that.<div class=3D"im"><br>
    <br>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div class=3D"gmail_extra">
          <div class=3D"gmail_quote">
            <div>Most folk here value consensus. I do not value
              consensus when it is wrong.</div>
          </div>
        </div>
      </div>
    </blockquote>
    <br></div>
    Nor do I.<span class=3D""><font color=3D"#888888"><br>
    <br>
    Keith<br>
    <br>
  </font></span></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>

--089e0141a1fcc5470b04e1511c6e--

From hallam@gmail.com  Fri Jul 12 07:16:48 2013
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFFB121F9C03 for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 07:16:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.458
X-Spam-Level: 
X-Spam-Status: No, score=-2.458 tagged_above=-999 required=5 tests=[AWL=0.141,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F5HYzPAWhNmQ for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 07:16:48 -0700 (PDT)
Received: from mail-wi0-x235.google.com (mail-wi0-x235.google.com [IPv6:2a00:1450:400c:c05::235]) by ietfa.amsl.com (Postfix) with ESMTP id DE45C21F9BB7 for <ietf@ietf.org>; Fri, 12 Jul 2013 07:16:42 -0700 (PDT)
Received: by mail-wi0-f181.google.com with SMTP id hq4so736346wib.2 for <ietf@ietf.org>; Fri, 12 Jul 2013 07:16:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=jN6bZ1YFhTW0WNIAQTWL8wwMdmUVsHOgqCcUZC6Uds0=; b=It+bws4UamKC6rIkEZErMzZldAfF8foXzeky6rURUswyriOsJwn6tmVB1vbtWSYb4s /IYJiFIEf/7cbFajyAPbCMFyXWIZlieSlrLUOYkkTEBd9jRSStzyWO9kNjDKU9XaHC2Z KSOzC7N0X/HCqT0mMXvdx5ZnLN/EUvnVbDTd+ZUwlHChqDLHay5Uv0ajuacTDL4mkUsd 3Zaul8I+K31GR361w0K8HBGRLXjIopQg45dG3MYMXio1hKudhZOcrYLcWaCRzD7aj48L piSbzIxWC4nj+orfmj9jEdeCEZH9d6aUVOyym5bDqraeaxi46BDmhUsA5uNdrs+u3Kag fxqA==
MIME-Version: 1.0
X-Received: by 10.180.107.167 with SMTP id hd7mr1779123wib.33.1373638601919; Fri, 12 Jul 2013 07:16:41 -0700 (PDT)
Received: by 10.194.6.65 with HTTP; Fri, 12 Jul 2013 07:16:41 -0700 (PDT)
In-Reply-To: <20130712141026.252DC18C15D@mercury.lcs.mit.edu>
References: <20130712141026.252DC18C15D@mercury.lcs.mit.edu>
Date: Fri, 12 Jul 2013 10:16:41 -0400
Message-ID: <CAMm+Lwi+70=pGi2aRkePdjnQt__LovNG-E_+008RTLOahBhNfw@mail.gmail.com>
Subject: Re: IAB Statement on Dotless Domains
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Content-Type: multipart/alternative; boundary=e89a8f2353a7ead84504e1512850
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jul 2013 14:16:48 -0000

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

On Fri, Jul 12, 2013 at 10:10 AM, Noel Chiappa <jnc@mercury.lcs.mit.edu>wrote:

>



Anyone who tried to
> monetize per-device would have had competition from people who only charged
> based on their actual costs.


So not deploying NAT would somehow magically cause a second broadband
provider to unroll a fiber optic cable to my house?

There was no competition in broadband in my city until Verizon unrolled
FiOS just over a year ago and so your economic theory fails completely as
far as I am concerned. For competition to change behavior there has to be
an open market and the US Internet market has very little of that.


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

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

<div dir=3D"ltr">On Fri, Jul 12, 2013 at 10:10 AM, Noel Chiappa <span dir=
=3D"ltr">&lt;<a href=3D"mailto:jnc@mercury.lcs.mit.edu" target=3D"_blank">j=
nc@mercury.lcs.mit.edu</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">=A0</blockquote><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x">=A0</blockquote>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Anyone who tried to<br>
monetize per-device would have had competition from people who only charged=
<br>
based on their actual costs.</blockquote><div><br></div><div style>So not d=
eploying NAT would somehow magically cause a second broadband provider to u=
nroll a fiber optic cable to my house?</div><div><br></div><div style>
There was no competition in broadband in my city until Verizon unrolled FiO=
S just over a year ago and so your economic theory fails completely as far =
as I am concerned. For competition to change behavior there has to be an op=
en market and the US Internet market has very little of that.</div>
<div><br></div><div>=A0</div></div>-- <br>Website: <a href=3D"http://hallam=
baker.com/">http://hallambaker.com/</a><br>
</div></div>

--e89a8f2353a7ead84504e1512850--

From hallam@gmail.com  Fri Jul 12 07:33:08 2013
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 888A921F9F83 for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 07:33:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.47
X-Spam-Level: 
X-Spam-Status: No, score=-2.47 tagged_above=-999 required=5 tests=[AWL=0.129,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 83PsZhPXg1Ee for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 07:33:07 -0700 (PDT)
Received: from mail-wi0-x234.google.com (mail-wi0-x234.google.com [IPv6:2a00:1450:400c:c05::234]) by ietfa.amsl.com (Postfix) with ESMTP id 3F76821F9D18 for <ietf@ietf.org>; Fri, 12 Jul 2013 07:33:07 -0700 (PDT)
Received: by mail-wi0-f180.google.com with SMTP id c10so753320wiw.13 for <ietf@ietf.org>; Fri, 12 Jul 2013 07:33:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=D0wOuNFOpC9cJ864skNYMFtXHBccZrJm5P+PLUypwQY=; b=lwQuUkp2gJzSt2sCzHRj7ItXzTDOP7dJhB6UwL5nEG+uFv5TOv1HLogJCdUWXKZ5Xr MZmsyR2Dr5057zd6Bzqjvo+rN2Near4Nz1n9EDebbDjQh94FjSxWKza3XoreQzTOJcHL a/6izgS9hBSpJu6mZHQYsJiZnktWpg9XwxhVf9Sa+7Q9mqtWzDdu0oh+F2qQT4abH6uK hlEgSw0EzMvtUfUta559GmOiygsdFx+lCmMh8ms0DVdxoNd08uT3ThZpO6ZQbmdYj/Fo W4MOZY78VM6QDrhfvSw5l1ai0f+edMwgSxaVeoR72H5bbr6Yvq1S58Y9asgL5StvDoxv 4/5Q==
MIME-Version: 1.0
X-Received: by 10.194.242.134 with SMTP id wq6mr23806369wjc.94.1373639586261;  Fri, 12 Jul 2013 07:33:06 -0700 (PDT)
Received: by 10.194.6.65 with HTTP; Fri, 12 Jul 2013 07:33:05 -0700 (PDT)
In-Reply-To: <alpine.LFD.2.10.1307121016420.21010@bofh.nohats.ca>
References: <1984CBB8-6862-4DBB-AFAE-F8461E694083@vigilsec.com> <51DDD49E.5090406@dcrocker.net> <CAMm+Lwj8_zmrp=SmUbb=a_4iEGA2zFaF2EDywaAq=5NkKbvp+w@mail.gmail.com> <alpine.LFD.2.10.1307121016420.21010@bofh.nohats.ca>
Date: Fri, 12 Jul 2013 10:33:05 -0400
Message-ID: <CAMm+LwgkEiyQbJLnqgcKe=7dFJ8pJ-HqYvxzMS6oXULX0FS3Tg@mail.gmail.com>
Subject: Re: IAB Statement on Dotless Domains
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Paul Wouters <paul@nohats.ca>
Content-Type: multipart/alternative; boundary=089e0141a1fc96b24504e151631a
Cc: Dave Crocker <dcrocker@bbiw.net>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jul 2013 14:33:08 -0000

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

On Fri, Jul 12, 2013 at 10:22 AM, Paul Wouters <paul@nohats.ca> wrote:

> On Fri, 12 Jul 2013, Phillip Hallam-Baker wrote:
>
>> And I don't expect things to be different this time round. But in ten
>> years time it will be obvious that
>> domains are going to be dotless and three of the biggest dotless domains
>> are going to be called .apple and .microsoft and .google and they are going
>> to be the companies writing much of
>> the software used to connect to the Internet and their commercial
>> interests are not exactly best served by supporting clapped out thirty year
>> old software programs.
>>
>
> I notice you are missing .oracle and .exchange and .mail. Is that
> because you can't take any more slaps on the back or because you know
> too many companies that have servers in their domain that would get
> bypassed by your awesome magic three software vendors listed above?


No, I limited it to them only because those three companies can flood the
market with software that makes the decision by force majeur. I don't think
the domains you list have the market power on the desktop to be a
sufficient quorum.



>
>  Dotted domains were a bad idea in DNS to start with and giving a
>> perpetually renewing contract to Network Solutions to operate the best one
>> was sillier. We should embrace the opportunity
>> to throw a bad engineering decision into the dustbin of history not try
>> to take the side of the TLD operators whose rent seeking opportunities are
>> threatened by the inevitable transition
>> to a dotless scheme.
>>
>
> I can't wait for your draft suggesting a fix based on a DNS zone that
> whitelists/blacklists those words that can be used dotless withou harm,
> after using /etc/hosts through ansible fails to scale.


The community has only two choices that make sense, either embrace dotless
domains or deploy DNS rules that simply block all the new ICANN TLDs as
unnecessary rent seeking noise. I would actually prefer the second but I
don't think a 'just say no to new TLDs' is a viable proposition.


The proportion of the Internet user community that is aware of default
domain sufixes at all is very unlikely to be as much as 1%. So if we are
going to make a proper argument on the grounds of avoiding user confusion
we should probably be telling software providers to stop supporting the
local domain prefixes in platforms as a security risk. The default path on
this machine is probably verizon.net. I find the default domain suffix to
be sufficiently useless that I never bother to set it.


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

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Fri, Jul 12, 2013 at 10:22 AM, Paul Wouters <span dir=3D"ltr">&l=
t;<a href=3D"mailto:paul@nohats.ca" target=3D"_blank">paul@nohats.ca</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 Fri, 12 Jul 2013, Phill=
ip Hallam-Baker wrote:<br></div><div class=3D"im">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
And I don&#39;t expect things to be different this time round. But in ten y=
ears time it will be obvious that<br>
domains are going to be dotless and three of the biggest dotless domains ar=
e going to be called .apple and .microsoft and .google and they are going t=
o be the companies writing much of<br>
the software used to connect to the Internet and their commercial interests=
 are not exactly best served by supporting clapped out thirty year old soft=
ware programs.<br>
</blockquote>
<br></div>
I notice you are missing .oracle and .exchange and .mail. Is that<br>
because you can&#39;t take any more slaps on the back or because you know<b=
r>
too many companies that have servers in their domain that would get<br>
bypassed by your awesome magic three software vendors listed above?</blockq=
uote><div><br></div><div style>No, I limited it to them only because those =
three companies can flood the market with software that makes the decision =
by force majeur. I don&#39;t think the domains you list have the market pow=
er on the desktop to be a sufficient quorum.</div>
<div><br></div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=3D"i=
m">
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Dotted domains were a bad idea in DNS to start with and giving a perpetuall=
y renewing contract to Network Solutions to operate the best one was sillie=
r. We should embrace the opportunity<br>
to throw a bad engineering decision into the dustbin of history not try to =
take the side of the TLD operators whose rent seeking opportunities are thr=
eatened by the inevitable transition<br>
to a dotless scheme.<br>
</blockquote>
<br></div>
I can&#39;t wait for your draft suggesting a fix based on a DNS zone that<b=
r>
whitelists/blacklists those words that can be used dotless withou harm,<br>
after using /etc/hosts through ansible fails to scale.</blockquote><div><br=
></div><div style>The community has only two choices that make sense, eithe=
r embrace dotless domains or deploy DNS rules that simply block all the new=
 ICANN TLDs as unnecessary rent seeking noise. I would actually prefer the =
second but I don&#39;t think a &#39;just say no to new TLDs&#39; is a viabl=
e proposition.</div>
<div><br></div><div><br></div><div style>The proportion of the Internet use=
r community that is aware of default domain sufixes at all is very unlikely=
 to be as much as 1%. So if we are going to make a proper argument on the g=
rounds of avoiding user confusion we should probably be telling software pr=
oviders to stop supporting the local domain prefixes in platforms as a secu=
rity risk. The default path on this machine is probably <a href=3D"http://v=
erizon.net">verizon.net</a>. I find the default domain suffix to be suffici=
ently useless that I never bother to set it.</div>
<div><br></div><div>=A0</div></div>-- <br>Website: <a href=3D"http://hallam=
baker.com/">http://hallambaker.com/</a><br>
</div></div>

--089e0141a1fc96b24504e151631a--

From d3e3e3@gmail.com  Fri Jul 12 07:37:14 2013
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7797911E812D; Fri, 12 Jul 2013 07:37:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.441
X-Spam-Level: 
X-Spam-Status: No, score=-102.441 tagged_above=-999 required=5 tests=[AWL=0.159, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y3dDpfJQXiXt; Fri, 12 Jul 2013 07:37:14 -0700 (PDT)
Received: from mail-ob0-x232.google.com (mail-ob0-x232.google.com [IPv6:2607:f8b0:4003:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id D050011E8120; Fri, 12 Jul 2013 07:37:13 -0700 (PDT)
Received: by mail-ob0-f178.google.com with SMTP id fb19so11552381obc.9 for <multiple recipients>; Fri, 12 Jul 2013 07:37:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=VWlaJXivMSzrSDqU0cEgqjBo7/AVGwGVfuJl+ZO3HQQ=; b=wH65pBgChwduCfhWTJDY+U1lEzVH87mOu75mHIXNfRMeMDAb+OhBtEuc7aExXZMhub mTUT1zJsGQvdwjDp8nX11NaKW2xun/TOJBH8pzUNn4mK3o5dCKMnhA5NVBjtp4+4co7T mp2igVY8U/isMTKv7sWnyQFDUuYPl/zeDUBtP8MyEyIEfyWr4OG9U6kG+Z5U9Vme10EA imi7YRBRyJGFAlkN5HVMm9eIxYNrnbzIuV+SEbzLvVYuHWUF6hfmcTBcbXgDJdYOTGoX SXcNwaBhctCEvCc2pNdJ2caGVCr9aRAy0p4LoCccYv8t7BvUEWTFrLP3xvllUuR1CHoe gbFg==
X-Received: by 10.60.140.168 with SMTP id rh8mr35971211oeb.17.1373639832244; Fri, 12 Jul 2013 07:37:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.73.106 with HTTP; Fri, 12 Jul 2013 07:36:52 -0700 (PDT)
In-Reply-To: <20130704214504.32221.97724.idtracker@ietfa.amsl.com>
References: <20130704214504.32221.97724.idtracker@ietfa.amsl.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Fri, 12 Jul 2013 10:36:52 -0400
Message-ID: <CAF4+nEHiPaB5LEQyigRTvpTdY-9wzh7uaTMRB31MbYm0yCXs2g@mail.gmail.com>
Subject: Re: [trill] Last Call: <draft-ietf-trill-directory-framework-05.txt> (TRILL (Transparent Interconnection of Lots of Links): Edge Directory Assistance Framework) to Informational RFC
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Cc: trill@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jul 2013 14:37:14 -0000

Based on the approval of draft-ietf-trill-fine-labeling, the directory
framework document should mention TRILL Fine Grained Labels.

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


On Thu, Jul 4, 2013 at 5:45 PM, The IESG <iesg-secretary@ietf.org> wrote:
>
> The IESG has received a request from the Transparent Interconnection of
> Lots of Links WG (trill) to consider the following document:
> - 'TRILL (Transparent Interconnection of Lots of Links): Edge Directory
>    Assistance Framework'
>   <draft-ietf-trill-directory-framework-05.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 2013-07-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
>
>
>    Edge TRILL (Transparent Interconnection of Lots of Links) switches
>    currently learn the mapping between MAC addresses and their egress
>    TRILL switch by observing the data packets they ingress or egress or
>    by the TRILL ESADI (End Station Address Distribution Information)
>    protocol. When an ingress TRILL switch receives a data frame whose
>    destination address (MAC&VLAN) that switch does not know, the data
>    frame is flooded within the frame's VLAN across the TRILL campus.
>
>    This document describes the framework for using directory services to
>    assist edge RBridges in reducing multi-destination frames,
>    particularly unknown unicast frames flooding, and ARP/ND, thus
>    improving TRILL network scalability.
>
>
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-trill-directory-framework/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-trill-directory-framework/ballot/
>
>
> The following IPR Declarations may be related to this I-D:
>
>    http://datatracker.ietf.org/ipr/2007/
>
>
>
> _______________________________________________
> trill mailing list
> trill@ietf.org
> https://www.ietf.org/mailman/listinfo/trill

From afabbie@hotmail.com  Fri Jul 12 07:02:37 2013
Return-Path: <afabbie@hotmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FD5221F9B0F for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 07:02:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_53=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mzun0ETb4DP9 for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 07:02:33 -0700 (PDT)
Received: from dub0-omc2-s11.dub0.hotmail.com (dub0-omc2-s11.dub0.hotmail.com [157.55.1.150]) by ietfa.amsl.com (Postfix) with ESMTP id E0CCC21F9A19 for <ietf@ietf.org>; Fri, 12 Jul 2013 07:02:32 -0700 (PDT)
Received: from DUB122-W44 ([157.55.1.136]) by dub0-omc2-s11.dub0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 12 Jul 2013 07:02:28 -0700
X-TMN: [gAlB22hhIkkZEMRp9V/0U8U23LYgUcWj]
X-Originating-Email: [afabbie@hotmail.com]
Message-ID: <DUB122-W44B553A93E92F897423FEBA5640@phx.gbl>
Content-Type: multipart/alternative; boundary="_aab673d6-fe58-438e-961b-97f33d1b2560_"
From: Fabian Jr <afabbie@hotmail.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Second Call for Volunteers to Serve on the ICANN Nominating Committee
Date: Fri, 12 Jul 2013 17:02:28 +0300
Importance: Normal
In-Reply-To: <FC4B2D1A-369E-4045-B854-90450676D660@iab.org>
References: <FC4B2D1A-369E-4045-B854-90450676D660@iab.org>
MIME-Version: 1.0
X-OriginalArrivalTime: 12 Jul 2013 14:02:28.0701 (UTC) FILETIME=[71DBA8D0:01CE7F08]
X-Mailman-Approved-At: Fri, 12 Jul 2013 08:19:32 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jul 2013 14:02:37 -0000

--_aab673d6-fe58-438e-961b-97f33d1b2560_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

dear chair=2C

this link  =20
http://nomcom.icann.org/bylaws.htm  is not opening !


pls. re-check and advise.

thank you=2C

=20
=0A=
=20
=0A=
Arbogast Fabian=2C
=0A=
cell:+255-78-447-8387


> Subject: Second Call for Volunteers to Serve on the ICANN Nominating Comm=
ittee
> From: iab-chair@iab.org
> Date: Tue=2C 9 Jul 2013 16:09:47 -0400
> To: ietf-announce@ietf.org
> CC: iab@iab.org=3B ietf@ietf.org
>=20
> Please note that the deadline for volunteering is 19 July 2013.  Please p=
ass this call for volunteer to anyone that might be interested.
>=20
> Russ
>=20
> =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D
>=20
> Dear Colleagues=2C
>=20
> The IAB (on behalf of the IETF) has been asked to supply a member to the =
2014 ICANN Nominating Committee (NomCom) by 15 August 2013. We would theref=
ore like to ask the community for volunteers to serve on the ICANN NomCom. =
If you are interested=2C please send a short e-mail to iab-chair at iab.org=
 with a copy to execd at iab.org with your motivation and information conce=
rning your familiarity with the IETF and ICANN.  The deadline for volunteer=
ing is 19 July 2013.
>=20
> The IAB will select from the available candidates=2C taking into account =
the familiarity with ICANN and the IETF=2C their roles=2C and their process=
es. The selected candidate will serve on the ICANN NomCom on personal title=
=3B however=2C we will be looking for a candidate who has an understanding =
of the interests of the technical community.
>=20
> The ICANN NomCom process itself is governed by the ICANN bylaws=3B an abs=
tract of the relevant articles can be found at http://nomcom.icann.org/byla=
ws.htm.  In addition=2C each NomCom determines a number of its own operatio=
nal procedures=2C including the role of the NomCom in recruiting and select=
ing candidates.
>=20
> The ICANN Nominating Committee typically meets in person at or around thr=
ee consecutive ICANN meetings. The first of these meetings=2C when the=20
> committee is formally established=2C will be held  22-23 November 2013 fo=
llowing the Buenos Aires ICANN meeting on 17-21 November. The committee wil=
l next attend the "Spring" ICANN meeting=2C which in 2014 will be in Singap=
ore on 23-27 March 2014. Finally=2C the committee will meet during and afte=
r the "Summer" ICANN meeting in London on 22-26 June 2014 where the final s=
late of candidates for the ICANN Board=2C the GNSO=2C ccNSO=2Cand ALAC will=
 be agreed upon.
>=20
> Candidates should be able to join monthly teleconferences (typically at U=
TC 14:00)=2C with the expectation that these teleconferences will held week=
ly during the candidate assessment process in May-June.
>=20
> NOTE: ICANN does cover travel and hotel costs for a pre-determined number=
 of days at each of the 3 consecutive ICANN meetings.
>=20
> For more information about the ICANN NomCom see: http://nomcom.icann.org/=
.  If you are willing to be considered or would like to nominate someone fo=
r the position=2C please send an email to iab-chair at iab.org and execd at=
 iab.org.
>=20
> On behalf of the IAB=2C
> Russ Housley
> IAB Chair
 		 	   		  =

--_aab673d6-fe58-438e-961b-97f33d1b2560_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 12pt=3B
font-family:Calibri
}
--></style></head>
<body class=3D'hmmessage'><div dir=3D'ltr'>dear chair=2C<br><br>this link&n=
bsp=3B&nbsp=3B <br><pre><a class=3D"c_nobdr t_prs" href=3D"http://nomcom.ic=
ann.org/bylaws.htm" target=3D"_blank">http://nomcom.icann.org/bylaws.htm</a=
>  is not opening !<br><br><br>pls. re-check and advise.<br><br>thank you=
=2C<br></pre><br>&nbsp=3B<br>=0A=
&nbsp=3B<br>=0A=
<em><font color=3D"#1f497d" face=3D"Comic Sans MS">Arbogast Fabian=2C</font=
></em><br>=0A=
<em><font color=3D"#1f497d" face=3D"Comic Sans MS">cell:+255-78-447-8387</f=
ont></em><br><br><br><div>&gt=3B Subject: Second Call for Volunteers to Ser=
ve on the ICANN Nominating Committee<br>&gt=3B From: iab-chair@iab.org<br>&=
gt=3B Date: Tue=2C 9 Jul 2013 16:09:47 -0400<br>&gt=3B To: ietf-announce@ie=
tf.org<br>&gt=3B CC: iab@iab.org=3B ietf@ietf.org<br>&gt=3B <br>&gt=3B Plea=
se note that the deadline for volunteering is 19 July 2013.  Please pass th=
is call for volunteer to anyone that might be interested.<br>&gt=3B <br>&gt=
=3B Russ<br>&gt=3B <br>&gt=3B =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D<br>&g=
t=3B <br>&gt=3B Dear Colleagues=2C<br>&gt=3B <br>&gt=3B The IAB (on behalf =
of the IETF) has been asked to supply a member to the 2014 ICANN Nominating=
 Committee (NomCom) by 15 August 2013. We would therefore like to ask the c=
ommunity for volunteers to serve on the ICANN NomCom. If you are interested=
=2C please send a short e-mail to iab-chair at iab.org with a copy to execd=
 at iab.org with your motivation and information concerning your familiarit=
y with the IETF and ICANN.  The deadline for volunteering is 19 July 2013.<=
br>&gt=3B <br>&gt=3B The IAB will select from the available candidates=2C t=
aking into account the familiarity with ICANN and the IETF=2C their roles=
=2C and their processes. The selected candidate will serve on the ICANN Nom=
Com on personal title=3B however=2C we will be looking for a candidate who =
has an understanding of the interests of the technical community.<br>&gt=3B=
 <br>&gt=3B The ICANN NomCom process itself is governed by the ICANN bylaws=
=3B an abstract of the relevant articles can be found at http://nomcom.ican=
n.org/bylaws.htm.  In addition=2C each NomCom determines a number of its ow=
n operational procedures=2C including the role of the NomCom in recruiting =
and selecting candidates.<br>&gt=3B <br>&gt=3B The ICANN Nominating Committ=
ee typically meets in person at or around three consecutive ICANN meetings.=
 The first of these meetings=2C when the <br>&gt=3B committee is formally e=
stablished=2C will be held  22-23 November 2013 following the Buenos Aires =
ICANN meeting on 17-21 November. The committee will next attend the "Spring=
" ICANN meeting=2C which in 2014 will be in Singapore on 23-27 March 2014. =
Finally=2C the committee will meet during and after the "Summer" ICANN meet=
ing in London on 22-26 June 2014 where the final slate of candidates for th=
e ICANN Board=2C the GNSO=2C ccNSO=2Cand ALAC will be agreed upon.<br>&gt=
=3B <br>&gt=3B Candidates should be able to join monthly teleconferences (t=
ypically at UTC 14:00)=2C with the expectation that these teleconferences w=
ill held weekly during the candidate assessment process in May-June.<br>&gt=
=3B <br>&gt=3B NOTE: ICANN does cover travel and hotel costs for a pre-dete=
rmined number of days at each of the 3 consecutive ICANN meetings.<br>&gt=
=3B <br>&gt=3B For more information about the ICANN NomCom see: http://nomc=
om.icann.org/.  If you are willing to be considered or would like to nomina=
te someone for the position=2C please send an email to iab-chair at iab.org=
 and execd at iab.org.<br>&gt=3B <br>&gt=3B On behalf of the IAB=2C<br>&gt=
=3B Russ Housley<br>&gt=3B IAB Chair<br></div> 		 	   		  </div></body>
</html>=

--_aab673d6-fe58-438e-961b-97f33d1b2560_--

From david.black@emc.com  Fri Jul 12 08:04:41 2013
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 534A511E810E; Fri, 12 Jul 2013 08:04:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.477
X-Spam-Level: 
X-Spam-Status: No, score=-102.477 tagged_above=-999 required=5 tests=[AWL=0.122, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EFaD0y+EAbNI; Fri, 12 Jul 2013 08:04:37 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 1381811E811A; Fri, 12 Jul 2013 08:04:32 -0700 (PDT)
Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r6CF4Cqn004158 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 12 Jul 2013 11:04:13 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd02.lss.emc.com [10.254.221.253]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor); Fri, 12 Jul 2013 11:04:04 -0400
Received: from mxhub17.corp.emc.com (mxhub17.corp.emc.com [10.254.93.46]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r6CF43ka003859; Fri, 12 Jul 2013 11:04:03 -0400
Received: from mx15a.corp.emc.com ([169.254.1.184]) by mxhub17.corp.emc.com ([10.254.93.46]) with mapi; Fri, 12 Jul 2013 11:04:03 -0400
From: "Black, David" <david.black@emc.com>
To: "stefan.winter@restena.lu" <stefan.winter@restena.lu>, "jsalowey@cisco.com" <jsalowey@cisco.com>, General Area Review Team <gen-art@ietf.org>
Date: Fri, 12 Jul 2013 11:04:01 -0400
Subject: RE: Gen-ART review of draft-ietf-abfab-eapapplicability-05
Thread-Topic: Gen-ART review of draft-ietf-abfab-eapapplicability-05
Thread-Index: Ac5rzQ3h5Vr98eb9RParuraCHgwUcgQTfgIgAL1zdeA=
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712983F32EC@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE71298265158@MX15A.corp.emc.com> <8D3D17ACE214DC429325B2B98F3AE712983F2C87@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712983F2C87@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-EMM-MHVC: 1
X-Mailman-Approved-At: Fri, 12 Jul 2013 08:19:42 -0700
Cc: "abfab@ietf.org" <abfab@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "Black, David" <david.black@emc.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jul 2013 15:04:41 -0000

And the -05 version includes the text to address that editorial nit - it's
ready for publication as a Proposed Standard RFC.  Many thanks to the autho=
rs
for productively addressing the review comments.

Thanks,
--David

> -----Original Message-----
> From: Black, David
> Sent: Monday, July 08, 2013 4:44 PM
> To: Black, David; stefan.winter@restena.lu; jsalowey@cisco.com; General A=
rea
> Review Team
> Cc: ietf@ietf.org; abfab@ietf.org
> Subject: Gen-ART review of draft-ietf-abfab-eapapplicability-04
>=20
> The -04 version of this draft resolves the minor issue noted in
> the Gen-ART review of the -03 version.
>=20
> There is a remaining editorial nit, in that the one use of
> "non-network" in the -04 version would benefit from clarification.
> I suggest the following text change to the start of the paragraph
> that's split across pages 3 and 4 (change is to last line of excerpt):
>=20
> OLD
>    Operators need to carefully consider the security implications before
>    relaxing these requirements.  One potentially serious attack exists
>    when channel binding is not required and EAP authentication is
>    introduced into an existing non-network service.
>=20
> NEW
>    Operators need to carefully consider the security implications before
>    relaxing these requirements.  One potentially serious attack exists
>    when channel binding is not required and EAP authentication is
>    introduced into an existing service other than network access.
>=20
> Thanks,
> --David
>=20
> > -----Original Message-----
> > From: Black, David
> > Sent: Monday, June 17, 2013 10:39 PM
> > To: stefan.winter@restena.lu; jsalowey@cisco.com; General Area Review T=
eam
> > Cc: ietf@ietf.org; abfab@ietf.org; Black, David
> > Subject: Gen-ART review of draft-ietf-abfab-eapapplicability-03
> >
> > 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-abfab-eapapplicability-03
> > Reviewer: David L. Black
> > Review Date: June 17, 2003
> > IETF LC End Date: June 17, 2003
> >
> > Summary:
> > This draft is on the right track but has open issues, described in the
> review.
> >
> > This draft updates the applicability statement for EAP to include usage
> > for application layer access via EAP over GSSAPI.  Additional security
> > requirements are introduced for environments in which EAP is used for
> > that purpose.
> >
> > I found one open issue, which is minor, and may be editorial
> >
> > Major issues: None
> >
> > Minor issues: One
> >
> > The next to last paragraph on p.3 begins with this sentence:
> >
> >    For these reasons, channel binding MUST be implemented by peers, EAP
> >    servers and AAA servers in environments where EAP authentication is
> >    used to access application layer services.
> >
> > It appear that this "MUST" requirement applies to all uses of EAP,
> > including network access authentication, not just application layer acc=
ess
> > authentication.  If so, that's not immediately obvious from the text, a=
nd
> > an additional sentence should be added to make this clearer.  If not,
> > the above sentence needs to exclude network access authentication from
> > that requirement.
> >
> > Nits/editorial comments:
> >
> > The same paragraph (p.3) continues with:
> >
> >    In addition, channel
> >    binding MUST default to being required by peers for non-network
> >    authentication.  If the EAP server is aware that authentication is
> >    for something other than a network service, it too MUST default to
> >    requiring channel binding.
> >
> > What is meant by "non-network authentication" and "other than a network
> > service"?  If those mean "other than for network access authentication"
> > as the term "network access authentication" is used in section 1 and
> > RFC 3748, that meaning should be clarified.
> >
> > idnits 2.12.17 generated this comment:
> >
> >   -- The document seems to lack a disclaimer for pre-RFC5378 work, but =
may
> >      have content which was first submitted before 10 November 2008.  I=
f you
> >      have contacted all the original authors and they are all willing t=
o
> grant
> >      the BCP78 rights to the IETF Trust, then this is fine, and you can
> ignore
> >      this comment.  If not, you may need to add the pre-RFC5378 disclai=
mer.
> >      (See the Legal Provisions document at
> >      http://trustee.ietf.org/license-info for more information.)
> >
> > idnits appears to be confused ;-).  The -00 version of this draft is fr=
om
> > 2012,
> > and this draft does not contain sufficient material from RFC 3748 that =
would
> > raise that concern, so this comment should be ok to ignore.
> >
> > Thanks,
> > --David
> > ----------------------------------------------------
> > David L. Black, Distinguished Engineer
> > EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
> > +1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293=
-7786
> > david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> > ----------------------------------------------------


From margaretw42@gmail.com  Thu Jul 11 14:48:51 2013
Return-Path: <margaretw42@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D05011E8129 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 14:48:51 -0700 (PDT)
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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Du3ygwEkS04o for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2013 14:48:50 -0700 (PDT)
Received: from mail-vb0-x229.google.com (mail-vb0-x229.google.com [IPv6:2607:f8b0:400c:c02::229]) by ietfa.amsl.com (Postfix) with ESMTP id C0A1C21F9D56 for <ietf@ietf.org>; Thu, 11 Jul 2013 14:48:50 -0700 (PDT)
Received: by mail-vb0-f41.google.com with SMTP id p13so1017580vbe.0 for <ietf@ietf.org>; Thu, 11 Jul 2013 14:48:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=fe0CRejti0HYfxgeTQT4gI2H1oFP9RJr1zu54KGjAWc=; b=aiU8fehEXSH+10S/EnCnDxN03MDumXpm3uVp/ZIWLNnAkGwr5xmBpfw+biooule32E aH6SSLSy5uiWPhwUYgDI54PrIvdwuV23ynNjs1hX60L2RrM/B05XflAAG8Y1cFkY8VPZ oLvUAtj9vBvMzU/+7sCmQB8hE5nwEUFKlTQikxJ34cML/BB45dKn6xokUHjZZo8kVQ50 z/dlDijRW4AWfWtLzxBUyi23Zrlb6XIEtXKC4W46gNhuQgk7wrp96CHsEaDtOojxz8PS FVEAdQhPPF1CxL4JVHnEs+gbBYcT6hk2KhZ/A/ZqkI1ESqGGLNP8d6hJF/2/IBZwH0ee hKSQ==
X-Received: by 10.52.67.84 with SMTP id l20mr19096581vdt.24.1373579329013; Thu, 11 Jul 2013 14:48:49 -0700 (PDT)
Received: from new-host-3.home (pool-71-184-79-25.bstnma.fios.verizon.net. [71.184.79.25]) by mx.google.com with ESMTPSA id sw5sm31766657vdc.4.2013.07.11.14.48.44 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 11 Jul 2013 14:48:47 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Regarding call Chinese names
From: Margaret Wasserman <margaretw42@gmail.com>
In-Reply-To: <5AD0581898082CED236D82B0@caldav.corp.apple.com>
Date: Thu, 11 Jul 2013 17:48:41 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <A74688A2-5A5A-4F84-9644-C10C82ECE2B2@gmail.com>
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com> <51DEB9F2.9040405@viagenie.ca> <F108A063F7E85E5F9C89ADBF@caldav.corp.apple.com> <51DEC0F5.3010406@viagenie.ca> <5AD0581898082CED236D82B0@caldav.corp.apple.com>
To: Cyrus Daboo <cyrus@daboo.name>
X-Mailer: Apple Mail (2.1508)
X-Mailman-Approved-At: Fri, 12 Jul 2013 08:19:52 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2013 21:48:51 -0000

Cyrus,=20

Even the notion of "First Name" and "Last Name" is specific to a certain =
group of cultures.  "Family Name" and "Given Name" don't always go in =
the same order, and it is not always the case that people are called by =
their given name in informal situations, as you can see in the drafts on =
Chinese Names.  In some cultures, people have more than one surname, and =
in others, people may only have one name.

Here is a nice article, for instance, on how/why people in Spanish =
cultures have two last names.  There are a lot of subtleties here, like =
which one to use in formal address, and how to address a family where =
both parents have two last names=85:

http://perez.cs.vt.edu/twolastnames

In my opinion, it would be better to ask for what you actually want, =
rather than trying to infer what to do from other fields.  For instance, =
you could ask for "Full Name" and "Display Name" or "Badge Name". Or =
"Full Name" and "Informal Name", if what you want is to know how to =
address them informally.  Or, "Full Name" and "Short Name", if what you =
are looking for is something shorter than the full name for use in a UI.

Margaret


On Jul 11, 2013, at 10:34 AM, Cyrus Daboo <cyrus@daboo.name> wrote:

> Hi Simon,
>=20
> --On July 11, 2013 at 4:28:05 PM +0200 Simon Perreault =
<simon.perreault@viagenie.ca> wrote:
>=20
>>> So, from a technical standpoint, it seems better to always represent
>>> user names using components (last, first, middle)? vCard does have =
an
>>> "N" property where individual components of a name can be broken =
out.
>>=20
>> I'm nowhere near an expert on this topic, but I distinctly remember
>> during the vCard 4 effort some participants saying that some cultures
>> just don't separate names into parts. In those cultures, you would =
just
>> have *a name*. Like an opaque, atomic blob I guess.
>=20
> True. And in the iCalendar world attendees can also be non-human =
entities like rooms or resources, which typically do not have separate =
components for their names (e.g., "Conference Room 1", "HD Projector", =
etc). But that case can be handled by simply specifying the full name in =
the "LAST-NAME" field and leave the others blank.
>=20
> --=20
> Cyrus Daboo
>=20


From paitken@cisco.com  Fri Jul 12 03:51:05 2013
Return-Path: <paitken@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7336821F8F38; Fri, 12 Jul 2013 03:51:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bmiGOnBWu5uC; Fri, 12 Jul 2013 03:50:58 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 720C621F8F29; Fri, 12 Jul 2013 03:50:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2275; q=dns/txt; s=iport; t=1373626253; x=1374835853; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=5uIK0WJOlei/DQ1vxL09A/ZMJmjpD4o3gEWTGhB4MQg=; b=H/+d4FtVgPhw5k9W+r50OsrP0FfuFv60QNyznIhI8C1H6evuFRFJfP+k P04kjsWLNVszuhpVSvrMnBjJ69lKrJfLqGpKnw7472QeQTcxJsf9db1TW kF+VWWenIGIKfOc5hvPcGmPPdy0CaWvH0JU15m/7Hft8UDY/rftrcEKnQ 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgkFAC7f31GQ/khN/2dsb2JhbABagwY1wh+BCBZ0giMBAQEEODAQARALGAkWDwkDAgECAUUTAQUCAQGIC7cQj2EHFoNfA5dchiSLKoMS
X-IronPort-AV: E=Sophos;i="4.89,652,1367971200"; d="scan'208";a="84290230"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-2.cisco.com with ESMTP; 12 Jul 2013 10:50:52 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r6CAooAC019300 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 12 Jul 2013 10:50:50 GMT
Received: from [10.61.212.236] ([10.61.212.236]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id r6CAolPE015603; Fri, 12 Jul 2013 11:50:48 +0100 (BST)
Message-ID: <51DFDF87.9040207@cisco.com>
Date: Fri, 12 Jul 2013 11:50:47 +0100
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF registration fee?
References: <51DD8551.6090502@cisco.com> <CADnDZ89g=-_V_J65=Lb2VfRv2+pvDPPwX0nyfT-+YE=bLFfCDg@mail.gmail.com>
In-Reply-To: <CADnDZ89g=-_V_J65=Lb2VfRv2+pvDPPwX0nyfT-+YE=bLFfCDg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Fri, 12 Jul 2013 08:20:13 -0700
Cc: ietf-registrar@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jul 2013 10:51:05 -0000

Why are newcomers attending the IETF? There seems to be an assumption 
that they're coming to participate across the board, or that they should 
be encouraged to do so.

Perhaps that's because it's the model that senior / old-time IETFers 
follow - they're involved in many different groups.

However not everyone has that level of experience or can afford to get 
involved so broadly. Other people could be attending very specific WGs 
which relate directly to what they're working on. The rest of the IETF 
is, frankly, irrelevant to them.

For the past 5 years I've mostly been attending the IETF remotely. I'll 
be in Berlin for two specific WGs. Even if other WGs may be interesting, 
I simply can't afford the time, nor do I have management support to get 
involved with stuff that's unrelated to what I'm working on. In the past 
I've seen others fly in just to attend specific WG meetings.

Yet the IETF doesn't recognise that model. You've got the blue sheets, 
you could do the analysis: attendee versus WG, over time. And add a 
section to the blue-sheet for WG chairs to record remote attendance.

Thanks,
P.


On 12/07/13 05:27, Abdussalam Baryun wrote:
> Hi Paul,
>
> I agree with you if someone attends without presenting work, but I
> think the fees is reasonable if we compare with other conferences fees
> per day (don't forget your free to presentations of your docs and get
> feedback from many sessions, this may change in future if higher
> load). If the IETF considers your request, I think it will increase
> participation maybe about 5% globaly and 20% locally, so mostly
> encourages regional participations. I will also add that if the IETF
> can consider newcomers to get discount for one day, because newcomers
> may want to get a feeling of the meeting.
>
> AB
>
> On 7/10/13, Paul Aitken <paitken@cisco.com> wrote:
>> Can you help me understand why the One Day Pass rate ($350) is so high
>> compared with the full week rate ($650 / $800)?
>>
>> Registering for two days could cost more than a week!
>>
>> Surely the day rate should be a little more than (week/5), eg about $175
>> - $200, to encourage those who only want/need to contribute on
>> particular days?
>>
>> Thanks,
>> P.
>>


From paul@nohats.ca  Fri Jul 12 07:12:39 2013
Return-Path: <paul@nohats.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2834621F9D42 for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 07:12:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.932
X-Spam-Level: 
X-Spam-Status: No, score=-2.932 tagged_above=-999 required=5 tests=[AWL=-0.333, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a6f6p6Hr8k8M for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 07:12:33 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) by ietfa.amsl.com (Postfix) with ESMTP id 3E7A521F9A48 for <ietf@ietf.org>; Fri, 12 Jul 2013 07:12:33 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3bsGL22QhMz50Q; Fri, 12 Jul 2013 10:12:26 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id pgqY8KQs3xfE; Fri, 12 Jul 2013 10:12:24 -0400 (EDT)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) by mx.nohats.ca (Postfix) with ESMTP; Fri, 12 Jul 2013 10:12:24 -0400 (EDT)
Received: by bofh.nohats.ca (Postfix, from userid 500) id 3EA91817D5; Fri, 12 Jul 2013 10:12:24 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 2F1AB817D2; Fri, 12 Jul 2013 10:12:24 -0400 (EDT)
Date: Fri, 12 Jul 2013 10:12:24 -0400 (EDT)
From: Paul Wouters <paul@nohats.ca>
To: Keith Moore <moore@network-heretics.com>
Subject: Re: IAB Statement on Dotless Domains
In-Reply-To: <51E006DB.80708@network-heretics.com>
Message-ID: <alpine.LFD.2.10.1307121007380.21010@bofh.nohats.ca>
References: <1984CBB8-6862-4DBB-AFAE-F8461E694083@vigilsec.com> <51DDD49E.5090406@dcrocker.net> <CAMm+Lwj8_zmrp=SmUbb=a_4iEGA2zFaF2EDywaAq=5NkKbvp+w@mail.gmail.com> <51DFFD67.4020407@network-heretics.com> <CAMm+LwgOTk-fkuKcu6442zZ_5ti5pWP6oGmP7yV2OgVBQHUqxg@mail.gmail.com> <51E006DB.80708@network-heretics.com>
User-Agent: Alpine 2.10 (LFD 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8BIT
X-Mailman-Approved-At: Fri, 12 Jul 2013 08:20:31 -0700
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jul 2013 14:12:39 -0000

On Fri, 12 Jul 2013, Keith Moore wrote:

> On 07/12/2013 09:28 AM, Phillip Hallam-Baker wrote:
>       On Fri, Jul 12, 2013 at 8:58 AM, Keith Moore <moore@network-heretics.com> wrote:
>             On 07/12/2013 08:16 AM, Phillip Hallam-Baker wrote:
>
>                   And before people start bringing up all the reasons I am wrong here, first consider the fact that for many years it was IETF ideology that NATs were a
>                   terrible thing that had to be killed. A position I suspect was largely driven by some aggressive lobbying by rent-seeking ISPs looking to collect fees
>                   on a per device basis rather than per connection.
> 
> 
> You are weakening your argument. � NATs still are a terrible thing that need to be killed.

There is an argument in the above? I read just a misguided opinion with
no facts.

> They break applications and prevent many useful applications from being used on
> the Internet. � 燭hat much is more widely understood now than it was 10-15 years ago.

It was always understood by the engineers. It's the money making machine
that did not care.

>       I think that at this point you are the only person still making the argument that the world should reject the easy fix for IPv4 address exhaustion that solves their problems
>       at negligible cost to them for the sake of forcing them to make a transition that would be very difficult, expensive and impact every part of the infrastructure.

I suggest Phillip is rewarded with a staticly configured 192.168.1.1
address for life on _all_ of his devices.

>       Most folk here value consensus. I do not value consensus when it is wrong.
> 
> Nor do I.

Indeed.

 	"When you're NAT on the net, you're NOT on the net"

 		-- Hugh Daniel

Paul

From paul@nohats.ca  Fri Jul 12 07:14:01 2013
Return-Path: <paul@nohats.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A593B21E8096 for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 07:14:01 -0700 (PDT)
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=[AWL=-0.250, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hn7gsK5hLFL7 for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 07:13:55 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) by ietfa.amsl.com (Postfix) with ESMTP id AD9C821E8051 for <ietf@ietf.org>; Fri, 12 Jul 2013 07:13:55 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3bsGMh6jk9z5L9; Fri, 12 Jul 2013 10:13:52 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id fznVDa0RhEf2; Fri, 12 Jul 2013 10:13:52 -0400 (EDT)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) by mx.nohats.ca (Postfix) with ESMTP; Fri, 12 Jul 2013 10:13:52 -0400 (EDT)
Received: by bofh.nohats.ca (Postfix, from userid 500) id 0B2CD817D5; Fri, 12 Jul 2013 10:13:53 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 01CDE817D2; Fri, 12 Jul 2013 10:13:52 -0400 (EDT)
Date: Fri, 12 Jul 2013 10:13:52 -0400 (EDT)
From: Paul Wouters <paul@nohats.ca>
To: Keith Moore <moore@network-heretics.com>
Subject: Re: IAB Statement on Dotless Domains
In-Reply-To: <alpine.LFD.2.10.1307121007380.21010@bofh.nohats.ca>
Message-ID: <alpine.LFD.2.10.1307121013140.21010@bofh.nohats.ca>
References: <1984CBB8-6862-4DBB-AFAE-F8461E694083@vigilsec.com> <51DDD49E.5090406@dcrocker.net> <CAMm+Lwj8_zmrp=SmUbb=a_4iEGA2zFaF2EDywaAq=5NkKbvp+w@mail.gmail.com> <51DFFD67.4020407@network-heretics.com> <CAMm+LwgOTk-fkuKcu6442zZ_5ti5pWP6oGmP7yV2OgVBQHUqxg@mail.gmail.com> <51E006DB.80708@network-heretics.com> <alpine.LFD.2.10.1307121007380.21010@bofh.nohats.ca>
User-Agent: Alpine 2.10 (LFD 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8BIT
X-Mailman-Approved-At: Fri, 12 Jul 2013 08:20:32 -0700
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jul 2013 14:14:01 -0000

On Fri, 12 Jul 2013, Paul Wouters wrote:

I clearly meant 192.168.1.1 to go to Keith Moore, but the terribly gmail
quoting method confused me in who said what :P

Paul

> Date: Fri, 12 Jul 2013 10:12:24
> From: Paul Wouters <paul@nohats.ca>
> Cc: Phillip Hallam-Baker <hallam@gmail.com>,
>     IETF Discussion Mailing List <ietf@ietf.org>
> To: Keith Moore <moore@network-heretics.com>
> Subject: Re: IAB Statement on Dotless Domains
> 
> On Fri, 12 Jul 2013, Keith Moore wrote:
>
>> On 07/12/2013 09:28 AM, Phillip Hallam-Baker wrote:
>>       On Fri, Jul 12, 2013 at 8:58 AM, Keith Moore 
>> <moore@network-heretics.com> wrote:
>>             On 07/12/2013 08:16 AM, Phillip Hallam-Baker wrote:
>>
>>                   And before people start bringing up all the reasons I am 
>> wrong here, first consider the fact that for many years it was IETF 
>> ideology that NATs were a
>>                   terrible thing that had to be killed. A position I 
>> suspect was largely driven by some aggressive lobbying by rent-seeking ISPs 
>> looking to collect fees
>>                   on a per device basis rather than per connection.
>> 
>> 
>> You are weakening your argument. � NATs still are a terrible thing that 
>> need to be killed.
>
> There is an argument in the above? I read just a misguided opinion with
> no facts.
>
>> They break applications and prevent many useful applications from being 
>> used on
>> the Internet. � 燭hat much is more widely understood now than it was 10-15 
>> years ago.
>
> It was always understood by the engineers. It's the money making machine
> that did not care.
>
>>       I think that at this point you are the only person still making the 
>> argument that the world should reject the easy fix for IPv4 address 
>> exhaustion that solves their problems
>>       at negligible cost to them for the sake of forcing them to make a 
>> transition that would be very difficult, expensive and impact every part of 
>> the infrastructure.
>
> I suggest Phillip is rewarded with a staticly configured 192.168.1.1
> address for life on _all_ of his devices.
>
>>       Most folk here value consensus. I do not value consensus when it is 
>> wrong.
>> 
>> Nor do I.
>
> Indeed.
>
> 	"When you're NAT on the net, you're NOT on the net"
>
> 		-- Hugh Daniel
>
> Paul
>

From paul@nohats.ca  Fri Jul 12 07:22:13 2013
Return-Path: <paul@nohats.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7932C11E811A for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 07:22:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.799
X-Spam-Level: 
X-Spam-Status: No, score=-2.799 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oNJTjRWrvKUG for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 07:22:07 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) by ietfa.amsl.com (Postfix) with ESMTP id 1DA1D21F937E for <ietf@ietf.org>; Fri, 12 Jul 2013 07:22:07 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3bsGY86hmzz50Q; Fri, 12 Jul 2013 10:22:04 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id dnUB8Y780F2t; Fri, 12 Jul 2013 10:22:04 -0400 (EDT)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) by mx.nohats.ca (Postfix) with ESMTP; Fri, 12 Jul 2013 10:22:03 -0400 (EDT)
Received: by bofh.nohats.ca (Postfix, from userid 500) id A4DAA817D5; Fri, 12 Jul 2013 10:22:04 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 9CC90817D2; Fri, 12 Jul 2013 10:22:04 -0400 (EDT)
Date: Fri, 12 Jul 2013 10:22:04 -0400 (EDT)
From: Paul Wouters <paul@nohats.ca>
To: Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: IAB Statement on Dotless Domains
In-Reply-To: <CAMm+Lwj8_zmrp=SmUbb=a_4iEGA2zFaF2EDywaAq=5NkKbvp+w@mail.gmail.com>
Message-ID: <alpine.LFD.2.10.1307121016420.21010@bofh.nohats.ca>
References: <1984CBB8-6862-4DBB-AFAE-F8461E694083@vigilsec.com> <51DDD49E.5090406@dcrocker.net> <CAMm+Lwj8_zmrp=SmUbb=a_4iEGA2zFaF2EDywaAq=5NkKbvp+w@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, 12 Jul 2013 08:20:32 -0700
Cc: Dave Crocker <dcrocker@bbiw.net>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jul 2013 14:22:13 -0000

On Fri, 12 Jul 2013, Phillip Hallam-Baker wrote:

> Today most people have come to accept my position on NAT, in fact it has become the mainstream position.

Or perhaps I was not. But I guess it's software written by those three
companies listed below that's "soo good" that makes quoting clear :P

> But none of the people who spent time trying to slap me down or get me to stop
> expressing a heretical view have ever said 'hey Phill you were right all along'.

Because you're not? (If the quoting worked this time and you really said
NAT's have a value other then being a cheap band-aid for those with lots
of money)

> And I don't expect things to be different this time round. But in ten years time it will be obvious that
> domains are going to be dotless and three of the biggest dotless domains are going to be called .apple and .microsoft and .google and they are going to be the companies writing much of
> the software used to connect to the Internet and their commercial interests are not exactly best served by supporting clapped out thirty year old software programs.

I notice you are missing .oracle and .exchange and .mail. Is that
because you can't take any more slaps on the back or because you know
too many companies that have servers in their domain that would get
bypassed by your awesome magic three software vendors listed above?

> Dotted domains were a bad idea in DNS to start with and giving a perpetually renewing contract to Network Solutions to operate the best one was sillier. We should embrace the opportunity
> to throw a bad engineering decision into the dustbin of history not try to take the side of the TLD operators whose rent seeking opportunities are threatened by the inevitable transition
> to a dotless scheme.

I can't wait for your draft suggesting a fix based on a DNS zone that
whitelists/blacklists those words that can be used dotless withou harm,
after using /etc/hosts through ansible fails to scale.

Paul

From paul@nohats.ca  Fri Jul 12 08:02:46 2013
Return-Path: <paul@nohats.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECF2A21F9477 for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 08:02:46 -0700 (PDT)
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=[AWL=-0.324, BAYES_00=-2.599, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FdvG7oZnhZmA for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 08:02:41 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) by ietfa.amsl.com (Postfix) with ESMTP id CA9B521F97E6 for <ietf@ietf.org>; Fri, 12 Jul 2013 08:02:40 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3bsHRy4cfdz4x2; Fri, 12 Jul 2013 11:02:38 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id 7a-FIuune_kT; Fri, 12 Jul 2013 11:02:37 -0400 (EDT)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) by mx.nohats.ca (Postfix) with ESMTP; Fri, 12 Jul 2013 11:02:37 -0400 (EDT)
Received: by bofh.nohats.ca (Postfix, from userid 500) id 64591817D5; Fri, 12 Jul 2013 11:02:38 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 581AC817D2; Fri, 12 Jul 2013 11:02:38 -0400 (EDT)
Date: Fri, 12 Jul 2013 11:02:38 -0400 (EDT)
From: Paul Wouters <paul@nohats.ca>
To: Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: IAB Statement on Dotless Domains
In-Reply-To: <CAMm+LwgkEiyQbJLnqgcKe=7dFJ8pJ-HqYvxzMS6oXULX0FS3Tg@mail.gmail.com>
Message-ID: <alpine.LFD.2.10.1307121051060.21010@bofh.nohats.ca>
References: <1984CBB8-6862-4DBB-AFAE-F8461E694083@vigilsec.com> <51DDD49E.5090406@dcrocker.net> <CAMm+Lwj8_zmrp=SmUbb=a_4iEGA2zFaF2EDywaAq=5NkKbvp+w@mail.gmail.com> <alpine.LFD.2.10.1307121016420.21010@bofh.nohats.ca> <CAMm+LwgkEiyQbJLnqgcKe=7dFJ8pJ-HqYvxzMS6oXULX0FS3Tg@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, 12 Jul 2013 08:20:32 -0700
Cc: Dave Crocker <dcrocker@bbiw.net>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jul 2013 15:02:47 -0000

On Fri, 12 Jul 2013, Phillip Hallam-Baker wrote:

> I notice you are missing .oracle and .exchange and .mail. Is that
> because you can't take any more slaps on the back or because you know
> too many companies that have servers in their domain that would get
> bypassed by your awesome magic three software vendors listed above?
> 
> No, I limited it to them only because those three companies can flood the market with software that makes the decision by force majeur. I don't think the domains you list have the market
> power on the desktop to be a sufficient quorum.

avoiding answering the implicit question about huge collateral damage
when exchange.company.TLD and oracle.company.TLD start resolving to
company external IPs..... Even if just _one_ airline company would
fall into this trap, it would be millions of dollars of damage alone.
Paid for by vanity domains that make turning clearly visible domain names
into a confusion about what's a single word and what's a domain name.

> The community has only two choices that make sense, either embrace dotless domains or deploy DNS rules that simply block all the new ICANN TLDs as unnecessary rent seeking noise.

We disagree on the the first, and the second one is as relevant as
whether I should add sugar to my morning coffee or not.

> The proportion of the Internet user community that is aware of default domain sufixes at all is very unlikely to be as much as 1%. So if we are going to make a proper argument on the
> grounds of avoiding user confusion we should probably be telling software providers to stop supporting the local domain prefixes in platforms as a security risk. The default path on this
> machine is probably verizon.net. I find the default domain suffix to be sufficiently useless that I never bother to set it.

You think that users know and/or can set a default domain suffix?
That programmers twenty years ago knew and/or understood what that even meant (or you think no one runs 20 year old software?)
That everyone knows about suffix manipulation through their DHCP connections?
And VPN connections?

Apart from that, were you a proponent of the file extension and mime
type wars too? Because as soon as one company takes something like
.profitable as dotless, someone else will claim profitable:// and
all the browsers will just be giant pools of local policy causing
utter confusion and at best will yield a totally unpredictable
user experience for dotless domains. Don't expect a pat on the
shoulder from me in twenty years.

Paul

From housley@vigilsec.com  Fri Jul 12 09:05:58 2013
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D44E21F871D for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 09:05:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.262
X-Spam-Level: 
X-Spam-Status: No, score=-102.262 tagged_above=-999 required=5 tests=[AWL=-0.264, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_53=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aiI2zofu8Lgy for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 09:05:53 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id A908E11E80FE for <ietf@ietf.org>; Fri, 12 Jul 2013 09:05:53 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id C4419F240B3; Fri, 12 Jul 2013 12:06:50 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id TCXnxoWaJeBY; Fri, 12 Jul 2013 12:05:29 -0400 (EDT)
Received: from [192.168.2.109] (pool-96-241-163-41.washdc.fios.verizon.net [96.241.163.41]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 2E097F240B0; Fri, 12 Jul 2013 12:06:46 -0400 (EDT)
Subject: Re: Second Call for Volunteers to Serve on the ICANN Nominating Committee
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: multipart/alternative; boundary=Apple-Mail-8-200956569
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <DUB122-W44B553A93E92F897423FEBA5640@phx.gbl>
Date: Fri, 12 Jul 2013 12:05:47 -0400
Message-Id: <1D04D712-E5C2-416D-BB51-C898357E89FC@vigilsec.com>
References: <FC4B2D1A-369E-4045-B854-90450676D660@iab.org> <DUB122-W44B553A93E92F897423FEBA5640@phx.gbl>
To: Fabian Jr <afabbie@hotmail.com>
X-Mailer: Apple Mail (2.1085)
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jul 2013 16:05:58 -0000

--Apple-Mail-8-200956569
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

http://www.icann.org/en/about/governance/bylaws

On Jul 12, 2013, at 10:02 AM, Fabian Jr wrote:

> dear chair,
>=20
> this link  =20
> http://nomcom.icann.org/bylaws.htm  is not opening !
>=20
>=20
> pls. re-check and advise.
>=20
> thank you,
>=20
> =20
> =20
> Arbogast Fabian,
> cell:+255-78-447-8387
>=20
>=20
> > Subject: Second Call for Volunteers to Serve on the ICANN Nominating =
Committee
> > From: iab-chair@iab.org
> > Date: Tue, 9 Jul 2013 16:09:47 -0400
> > To: ietf-announce@ietf.org
> > CC: iab@iab.org; ietf@ietf.org
> >=20
> > Please note that the deadline for volunteering is 19 July 2013. =
Please pass this call for volunteer to anyone that might be interested.
> >=20
> > Russ
> >=20
> > =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D
> >=20
> > Dear Colleagues,
> >=20
> > The IAB (on behalf of the IETF) has been asked to supply a member to =
the 2014 ICANN Nominating Committee (NomCom) by 15 August 2013. We would =
therefore like to ask the community for volunteers to serve on the ICANN =
NomCom. If you are interested, please send a short e-mail to iab-chair =
at iab.org with a copy to execd at iab.org with your motivation and =
information concerning your familiarity with the IETF and ICANN. The =
deadline for volunteering is 19 July 2013.
> >=20
> > The IAB will select from the available candidates, taking into =
account the familiarity with ICANN and the IETF, their roles, and their =
processes. The selected candidate will serve on the ICANN NomCom on =
personal title; however, we will be looking for a candidate who has an =
understanding of the interests of the technical community.
> >=20
> > The ICANN NomCom process itself is governed by the ICANN bylaws; an =
abstract of the relevant articles can be found at =
http://nomcom.icann.org/bylaws.htm. In addition, each NomCom determines =
a number of its own operational procedures, including the role of the =
NomCom in recruiting and selecting candidates.
> >=20
> > The ICANN Nominating Committee typically meets in person at or =
around three consecutive ICANN meetings. The first of these meetings, =
when the=20
> > committee is formally established, will be held 22-23 November 2013 =
following the Buenos Aires ICANN meeting on 17-21 November. The =
committee will next attend the "Spring" ICANN meeting, which in 2014 =
will be in Singapore on 23-27 March 2014. Finally, the committee will =
meet during and after the "Summer" ICANN meeting in London on 22-26 June =
2014 where the final slate of candidates for the ICANN Board, the GNSO, =
ccNSO,and ALAC will be agreed upon.
> >=20
> > Candidates should be able to join monthly teleconferences (typically =
at UTC 14:00), with the expectation that these teleconferences will held =
weekly during the candidate assessment process in May-June.
> >=20
> > NOTE: ICANN does cover travel and hotel costs for a pre-determined =
number of days at each of the 3 consecutive ICANN meetings.
> >=20
> > For more information about the ICANN NomCom see: =
http://nomcom.icann.org/. If you are willing to be considered or would =
like to nominate someone for the position, please send an email to =
iab-chair at iab.org and execd at iab.org.
> >=20
> > On behalf of the IAB,
> > Russ Housley
> > IAB Chair


--Apple-Mail-8-200956569
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><a =
href=3D"http://www.icann.org/en/about/governance/bylaws">http://www.icann.=
org/en/about/governance/bylaws</a><div><br><div><div>On Jul 12, 2013, at =
10:02 AM, Fabian Jr wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite">

<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style>
<div class=3D"hmmessage"><div dir=3D"ltr">dear chair,<br><br>this =
link&nbsp;&nbsp; <br><pre><a class=3D"c_nobdr t_prs" =
href=3D"http://nomcom.icann.org/bylaws.htm" =
target=3D"_blank">http://nomcom.icann.org/bylaws.htm</a>  is not opening =
!<br><br><br>pls. re-check and advise.<br><br>thank =
you,<br></pre><br>&nbsp;<br>
&nbsp;<br>
<em><font color=3D"#1f497d" face=3D"Comic Sans MS">Arbogast =
Fabian,</font></em><br>
<em><font color=3D"#1f497d" face=3D"Comic Sans =
MS">cell:+255-78-447-8387</font></em><br><br><br><div>&gt; Subject: =
Second Call for Volunteers to Serve on the ICANN Nominating =
Committee<br>&gt; From: <a =
href=3D"mailto:iab-chair@iab.org">iab-chair@iab.org</a><br>&gt; Date: =
Tue, 9 Jul 2013 16:09:47 -0400<br>&gt; To: <a =
href=3D"mailto:ietf-announce@ietf.org">ietf-announce@ietf.org</a><br>&gt; =
CC: <a href=3D"mailto:iab@iab.org">iab@iab.org</a>; <a =
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br>&gt; <br>&gt; Please =
note that the deadline for volunteering is 19 July 2013.  Please pass =
this call for volunteer to anyone that might be interested.<br>&gt; =
<br>&gt; Russ<br>&gt; <br>&gt; =3D =3D =3D =3D =3D =3D =3D =3D =3D =
=3D<br>&gt; <br>&gt; Dear Colleagues,<br>&gt; <br>&gt; The IAB (on =
behalf of the IETF) has been asked to supply a member to the 2014 ICANN =
Nominating Committee (NomCom) by 15 August 2013. We would therefore like =
to ask the community for volunteers to serve on the ICANN NomCom. If you =
are interested, please send a short e-mail to iab-chair at <a =
href=3D"http://iab.org">iab.org</a> with a copy to execd at <a =
href=3D"http://iab.org">iab.org</a> with your motivation and information =
concerning your familiarity with the IETF and ICANN.  The deadline for =
volunteering is 19 July 2013.<br>&gt; <br>&gt; The IAB will select from =
the available candidates, taking into account the familiarity with ICANN =
and the IETF, their roles, and their processes. The selected candidate =
will serve on the ICANN NomCom on personal title; however, we will be =
looking for a candidate who has an understanding of the interests of the =
technical community.<br>&gt; <br>&gt; The ICANN NomCom process itself is =
governed by the ICANN bylaws; an abstract of the relevant articles can =
be found at <a =
href=3D"http://nomcom.icann.org/bylaws.htm">http://nomcom.icann.org/bylaws=
.htm</a>.  In addition, each NomCom determines a number of its own =
operational procedures, including the role of the NomCom in recruiting =
and selecting candidates.<br>&gt; <br>&gt; The ICANN Nominating =
Committee typically meets in person at or around three consecutive ICANN =
meetings. The first of these meetings, when the <br>&gt; committee is =
formally established, will be held  22-23 November 2013 following the =
Buenos Aires ICANN meeting on 17-21 November. The committee will next =
attend the "Spring" ICANN meeting, which in 2014 will be in Singapore on =
23-27 March 2014. Finally, the committee will meet during and after the =
"Summer" ICANN meeting in London on 22-26 June 2014 where the final =
slate of candidates for the ICANN Board, the GNSO, ccNSO,and ALAC will =
be agreed upon.<br>&gt; <br>&gt; Candidates should be able to join =
monthly teleconferences (typically at UTC 14:00), with the expectation =
that these teleconferences will held weekly during the candidate =
assessment process in May-June.<br>&gt; <br>&gt; NOTE: ICANN does cover =
travel and hotel costs for a pre-determined number of days at each of =
the 3 consecutive ICANN meetings.<br>&gt; <br>&gt; For more information =
about the ICANN NomCom see: <a =
href=3D"http://nomcom.icann.org/">http://nomcom.icann.org/</a>.  If you =
are willing to be considered or would like to nominate someone for the =
position, please send an email to iab-chair at <a =
href=3D"http://iab.org">iab.org</a> and execd at <a =
href=3D"http://iab.org">iab.org</a>.<br>&gt; <br>&gt; On behalf of the =
IAB,<br>&gt; Russ Housley<br>&gt; IAB Chair<br></div> 		 	 =
  		  </div></div>
</blockquote></div><br></div></body></html>=

--Apple-Mail-8-200956569--

From johnl@iecc.com  Fri Jul 12 09:24:30 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E1F611E8127 for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 09:24:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.707
X-Spam-Level: 
X-Spam-Status: No, score=-110.707 tagged_above=-999 required=5 tests=[AWL=0.492, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VB4QT29c+YzL for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 09:24:17 -0700 (PDT)
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 A8BB611E811E for <ietf@ietf.org>; Fri, 12 Jul 2013 09:24:11 -0700 (PDT)
Received: (qmail 92463 invoked from network); 12 Jul 2013 16:24:10 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 12 Jul 2013 16:24:10 -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=51e02daa.xn--i8sz2z.k1307; i=johnl@user.iecc.com; bh=Tgb16BqHPRyJthrLiRP/ziBm5BF/dLKzIRYC43HwLhQ=; b=Nurvfw5coqsda7WyVHM3zEU3RVK8m+8mT/WPTGgzF+ZvlozJnJFbGbkqbU3zxD+JbixMcUcUJZyFYDtAtCS0QziLEJJfkrBuM8APOiVjJt454T0mvq3qolT5oKgVjWYaKB+Ts1mZXM9DSFP/V2CuCyIzamrMqbaQ1iz+rewgqOQh7Mzh+aY41uI3O9avCFMsnjusqqjM0GccIa21+QL+KTISHSh6NlXW6ZUkJ0pI4ijINCjvOu9NcUqVgdlr9U7g
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=51e02daa.xn--i8sz2z.k1307; olt=johnl@user.iecc.com; bh=Tgb16BqHPRyJthrLiRP/ziBm5BF/dLKzIRYC43HwLhQ=; b=UYufKs7tnWKSsIz+ND25hl7p0rGjmfbwe3sMHlRPhDr/5cBKT2gw+Bdx//j5KPo2AsCYmewnGsoK4vZwJpLcS3SxG/Ws9df/BDlNBe00QsjV1X9a0BigzOZ5IVar6MXL5PW40vMcMVFcghuVPxICGuAHTCkSnlHDmBAHdv14pOH/PvD+ebLy4IXPldUUCyIa+djnbu3jdEWDeTV+hdZBPBjalkdObGRDEK/Zi/eLk/emw8jvYHdBDNaJGcaJTsst
Date: 12 Jul 2013 16:23:48 -0000
Message-ID: <20130712162348.9441.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: IAB Statement on Dotless Domains
In-Reply-To: <CAMm+LwgkEiyQbJLnqgcKe=7dFJ8pJ-HqYvxzMS6oXULX0FS3Tg@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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jul 2013 16:24:30 -0000

>>> domains are going to be dotless and three of the biggest dotless domains
>>> are going to be called .apple and .microsoft and .google and they are going

I've read the applications for .apple, .microsoft, and .google.  None
of them propose to use dotless names, only the usual 2LDs.  At this
pont there is just one application that proposes a dotless name,
Google's .search, and it's far from clear what will happen to that, or
even if that application would beat out the competing ones from
Amazon, Donuts and dot Now, none of which are dotless.

Do you think they are lying when they say they won't be dotless?

R's,
John

PS: The applications are all linked here.  The financial info is
redacted, but the technical stuff is all present.

https://gtldresult.icann.org/

From hallam@gmail.com  Fri Jul 12 09:24:34 2013
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39EF311E8127 for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 09:24:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.322
X-Spam-Level: 
X-Spam-Status: No, score=-2.322 tagged_above=-999 required=5 tests=[AWL=-0.038, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id abaoY6fmgB5y for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 09:24:30 -0700 (PDT)
Received: from mail-wi0-x230.google.com (mail-wi0-x230.google.com [IPv6:2a00:1450:400c:c05::230]) by ietfa.amsl.com (Postfix) with ESMTP id 39A0F11E811A for <ietf@ietf.org>; Fri, 12 Jul 2013 09:24:22 -0700 (PDT)
Received: by mail-wi0-f176.google.com with SMTP id ey16so884018wid.15 for <ietf@ietf.org>; Fri, 12 Jul 2013 09:24:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=HONr7LQN+e172psyeZF/09Pevs1NW1iWDOR/gvqqRt0=; b=klkd5QA3oAICY/jculckgkvxIfMt3QzyZL9WQ1LSHmSMiNPcPPrsatIrx/XQKk7fgW mqM7gcy4wiB6YH6DOxlLzIMjzzoFuV699FIw1cRvufGQEY9o+Pv8dJBeGaUSQxp3LGjn JPctV+CO/0KXRVGaU6q+PmnhW5EcfQNKCJ8znSOOhMDHV13KPTwN8dsISXvsW+6Eam/o Eb1qrXhUh/p/Pf42DTe8MZYXAkcO0mJhOCHOIS/jitNoTztzxjmI5MLEN5dLcPx9xwFj /sYa71Hq3n8TfdwQzwF0wZ8wXabjrA1IlJh/jUxlS6qe6VnDxZO4RSuvb5gSurmQOoa/ +qhw==
MIME-Version: 1.0
X-Received: by 10.180.182.229 with SMTP id eh5mr2065418wic.63.1373646261971; Fri, 12 Jul 2013 09:24:21 -0700 (PDT)
Received: by 10.194.6.65 with HTTP; Fri, 12 Jul 2013 09:24:21 -0700 (PDT)
In-Reply-To: <alpine.LFD.2.10.1307121051060.21010@bofh.nohats.ca>
References: <1984CBB8-6862-4DBB-AFAE-F8461E694083@vigilsec.com> <51DDD49E.5090406@dcrocker.net> <CAMm+Lwj8_zmrp=SmUbb=a_4iEGA2zFaF2EDywaAq=5NkKbvp+w@mail.gmail.com> <alpine.LFD.2.10.1307121016420.21010@bofh.nohats.ca> <CAMm+LwgkEiyQbJLnqgcKe=7dFJ8pJ-HqYvxzMS6oXULX0FS3Tg@mail.gmail.com> <alpine.LFD.2.10.1307121051060.21010@bofh.nohats.ca>
Date: Fri, 12 Jul 2013 12:24:21 -0400
Message-ID: <CAMm+Lwjk5maZ9AdHakTz=Tg8DtYRSdydRTn2FWjV4yQPC7fnCA@mail.gmail.com>
Subject: Re: IAB Statement on Dotless Domains
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Paul Wouters <paul@nohats.ca>
Content-Type: multipart/alternative; boundary=089e0163491e7df09b04e152f170
Cc: Dave Crocker <dcrocker@bbiw.net>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jul 2013 16:24:34 -0000

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

On Fri, Jul 12, 2013 at 11:02 AM, Paul Wouters <paul@nohats.ca> wrote:

> On Fri, 12 Jul 2013, Phillip Hallam-Baker wrote:
>
>  I notice you are missing .oracle and .exchange and .mail. Is that
>> because you can't take any more slaps on the back or because you know
>> too many companies that have servers in their domain that would get
>> bypassed by your awesome magic three software vendors listed above?
>>
>> No, I limited it to them only because those three companies can flood the
>> market with software that makes the decision by force majeur. I don't think
>> the domains you list have the market
>> power on the desktop to be a sufficient quorum.
>>
>
> avoiding answering the implicit question about huge collateral damage
> when exchange.company.TLD and oracle.company.TLD start resolving to
> company external IPs..... Even if just _one_ airline company would
> fall into this trap, it would be millions of dollars of damage alone.
> Paid for by vanity domains that make turning clearly visible domain names
> into a confusion about what's a single word and what's a domain name.


Which in my view is an excellent argument for the IAB to issue an advisory
warning that such domains are a terrible idea and that ICANN should not
issue such domains under any circumstance.

Unfortunately the IAB is not going to give that advice. They seem to have
passed on advising ICANN not to issue .corp which is going to be a total
security meltdown. It's not 20 pieces of silver at stake here is a quarter
million bucks or more a pop.


I think that there is actually very good reason to believe that the two
domains you cite will not be a problem as Microsoft and Oracle both have
very competent and aggressive legal departments and can be expected to rip
ICANN apart legally limb from limb were they to be silly enough to issue
them to any one else in flagrant violation of their longstanding trademarks.

But there are hundreds of other TLDs that are going to be causing a huge
amount of damage and these are not going to be understood at first.



> You think that users know and/or can set a default domain suffix?
> That programmers twenty years ago knew and/or understood what that even
> meant (or you think no one runs 20 year old software?)
> That everyone knows about suffix manipulation through their DHCP
> connections?
> And VPN connections?
>

That is my point precisely. I think the domain search lists should be
eliminated completely in the platform code because they are a little used
feature with significant and non obvious security implications.



> Apart from that, were you a proponent of the file extension and mime
> type wars too? Because as soon as one company takes something like
> .profitable as dotless, someone else will claim profitable:// and
> all the browsers will just be giant pools of local policy causing
> utter confusion and at best will yield a totally unpredictable
> user experience for dotless domains. Don't expect a pat on the
> shoulder from me in twenty years.
>

For what it is worth I have always considered using file extensions to
specify the file type to be an unscalable hack. Mime types are a lot
better.

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

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Fri, Jul 12, 2013 at 11:02 AM, Paul Wouters <span dir=3D"ltr">&l=
t;<a href=3D"mailto:paul@nohats.ca" target=3D"_blank">paul@nohats.ca</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 Fri, 12 Jul 2013, Phill=
ip Hallam-Baker wrote:<br>
<br>
</div><div class=3D"im"><blockquote class=3D"gmail_quote" style=3D"margin:0=
 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I notice you are missing .oracle and .exchange and .mail. Is that<br>
because you can&#39;t take any more slaps on the back or because you know<b=
r>
too many companies that have servers in their domain that would get<br>
bypassed by your awesome magic three software vendors listed above?<br>
<br>
No, I limited it to them only because those three companies can flood the m=
arket with software that makes the decision by force majeur. I don&#39;t th=
ink the domains you list have the market<br>
power on the desktop to be a sufficient quorum.<br>
</blockquote>
<br></div>
avoiding answering the implicit question about huge collateral damage<br>
when exchange.company.TLD and oracle.company.TLD start resolving to<br>
company external IPs..... Even if just _one_ airline company would<br>
fall into this trap, it would be millions of dollars of damage alone.<br>
Paid for by vanity domains that make turning clearly visible domain names<b=
r>
into a confusion about what&#39;s a single word and what&#39;s a domain nam=
e.</blockquote><div><br></div><div>Which in my view is an excellent argumen=
t for the IAB to issue an advisory warning that such domains are a terrible=
 idea and that ICANN should not issue such domains under any circumstance.<=
/div>
<div><br></div><div>Unfortunately the IAB is not going to give that advice.=
 They seem to have passed on advising ICANN not to issue .corp which is goi=
ng to be a total security meltdown. It&#39;s not 20 pieces of silver at sta=
ke here is a quarter million bucks or more a pop.</div>
<div><br></div><div><br></div><div>I think that there is actually very good=
 reason to believe that the two domains you cite will not be a problem as M=
icrosoft and Oracle both have very competent and aggressive legal departmen=
ts and can be expected to rip ICANN apart legally limb from limb were they =
to be silly enough to issue them to any one else in flagrant violation of t=
heir longstanding trademarks.</div>
<div><br></div><div>But there are hundreds of other TLDs that are going to =
be causing a huge amount of damage and these are not going to be understood=
 at first.</div><div><br></div><div><br></div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
">
<div class=3D"im"><br></div>
You think that users know and/or can set a default domain suffix?<br>
That programmers twenty years ago knew and/or understood what that even mea=
nt (or you think no one runs 20 year old software?)<br>
That everyone knows about suffix manipulation through their DHCP connection=
s?<br>
And VPN connections?<br></blockquote><div><br></div><div>That is my point p=
recisely. I think the domain search lists should be eliminated completely i=
n the platform code because they are a little used feature with significant=
 and non obvious security implications.</div>
<div><br></div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Apart from that, were you a proponent of the file extension and mime<br>
type wars too? Because as soon as one company takes something like<br>
.profitable as dotless, someone else will claim profitable:// and<br>
all the browsers will just be giant pools of local policy causing<br>
utter confusion and at best will yield a totally unpredictable<br>
user experience for dotless domains. Don&#39;t expect a pat on the<br>
shoulder from me in twenty years.<span class=3D"HOEnZb"><font color=3D"#888=
888"><br>
</font></span></blockquote></div><br>For what it is worth I have always con=
sidered using file extensions to specify the file type to be an unscalable =
hack. Mime types are a lot better.=A0<br clear=3D"all"><div><br></div>-- <b=
r>
Website: <a href=3D"http://hallambaker.com/">http://hallambaker.com/</a><br=
>
</div></div>

--089e0163491e7df09b04e152f170--

From hallam@gmail.com  Fri Jul 12 09:41:43 2013
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F58721F9F53 for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 09:41:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.837
X-Spam-Level: 
X-Spam-Status: No, score=-1.837 tagged_above=-999 required=5 tests=[AWL=-0.519, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_39=0.6, NO_RELAYS=-0.001, SARE_MONEYTERMS=0.681]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cQ4zRZYrEOEJ for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 09:41:42 -0700 (PDT)
Received: from mail-we0-x234.google.com (mail-we0-x234.google.com [IPv6:2a00:1450:400c:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id 3028821F9F65 for <ietf@ietf.org>; Fri, 12 Jul 2013 09:41:41 -0700 (PDT)
Received: by mail-we0-f180.google.com with SMTP id w56so8371380wes.11 for <ietf@ietf.org>; Fri, 12 Jul 2013 09:41:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=d9Yxrtf+AHTXes76yXhchurebqqrr9WnpO7hdaO4Oxo=; b=HlPhdf+glOoOJXFE/Qa91B8Pt1p0iBCU7MbJUAjDXjyGFopgD1NYjzTuuHV/V8tcTE SuOm3xVtERxkp2dtIBVzrkHAP66zWZbJR9fyYxIkuHxd2U6rp5I2OUL1DR+YjZ11oIFi VhpJz4VbevdmTfubS9udUS8k5gLqOM+ugtn5UvX06a4afEXn0N1vf1AQxI0/k5hkJg2s n1/dl7oXHG5Hy3pi2otxCunsqs73cAgyYt+HCaz3kNQIshubSlC5z0iy6Dq/dzaPkqDE KOkys4+2Q/Y7/5Dr/rT0w1V2xPH8iv7+Dgx1VmITyNAl68T8vcwReMSmttz3+IqHWxsQ Yw4g==
MIME-Version: 1.0
X-Received: by 10.194.179.33 with SMTP id dd1mr24399625wjc.51.1373647301241; Fri, 12 Jul 2013 09:41:41 -0700 (PDT)
Received: by 10.194.6.65 with HTTP; Fri, 12 Jul 2013 09:41:41 -0700 (PDT)
In-Reply-To: <20130712162348.9441.qmail@joyce.lan>
References: <CAMm+LwgkEiyQbJLnqgcKe=7dFJ8pJ-HqYvxzMS6oXULX0FS3Tg@mail.gmail.com> <20130712162348.9441.qmail@joyce.lan>
Date: Fri, 12 Jul 2013 12:41:41 -0400
Message-ID: <CAMm+Lwhd4B-aA=sH5wiKQT6H5RuTKuAkVajAw169sCTFqLDzWw@mail.gmail.com>
Subject: Re: IAB Statement on Dotless Domains
From: Phillip Hallam-Baker <hallam@gmail.com>
To: John Levine <johnl@taugh.com>
Content-Type: multipart/alternative; boundary=089e013d0f806ff44704e1532fec
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jul 2013 16:41:43 -0000

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

On Fri, Jul 12, 2013 at 12:23 PM, John Levine <johnl@taugh.com> wrote:

> >>> domains are going to be dotless and three of the biggest dotless
> domains
> >>> are going to be called .apple and .microsoft and .google and they are
> going
>
> I've read the applications for .apple, .microsoft, and .google.  None
> of them propose to use dotless names, only the usual 2LDs.  At this
> pont there is just one application that proposes a dotless name,
> Google's .search, and it's far from clear what will happen to that, or
> even if that application would beat out the competing ones from
> Amazon, Donuts and dot Now, none of which are dotless.
>
> Do you think they are lying when they say they won't be dotless?
>
> R's,
> John
>
> PS: The applications are all linked here.  The financial info is
> redacted, but the technical stuff is all present.
>
> https://gtldresult.icann.org/
>

I think the people who wrote those applications on behalf of their
employers are likely to find that other parts of their organization have a
different view after the results are awarded.

There are two parts to the DNS business don't forget. Is Andrew really sure
that if dns.com decides to help users out by returning the A record for
www.microsoft in response to a request for microsoft. and this turns out to
have commercial value that his employer is not going to do the exact same
thing even over his objections? Do you think that DNS.com is going to lose
business to a competitor?

[dns.com is owned by my employer and we also provide recursive DNS services]


I remember all the squeaking and outrage about sitefinder back in the day.
That wasn't my idea but I went along with it as a way to give ICANN a kick
up the rear and stop blocking all progress out of fear of lawsuits. How
many of the people who complained then now work for companies that deploy
the same type of system with the same technical impact? I think you will
find that it is actually quite a large number.


Only five years ago the US banks managed to create a trillion dollar
meltdown because they didn't understand that the perverse market dynamics
they had created would force many of their companies into bankruptcy. And
if the banks had come to that realization and explained the situation to
the Treasury or the Fed they would have had no difficulty getting a
regulatory regime established that would have protected their businesses.

That didn't happen.


Don't expect me to take a stand on your principles. And certainly don't
expect me to endorse a statement of principles if I didn't even have the
opportunity to discuss it before issue.

Most people are averse to chaos. Don't bet your businesses that others are
going to be averse to it.


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

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Fri, Jul 12, 2013 at 12:23 PM, John Levine <span dir=3D"ltr">&lt=
;<a href=3D"mailto:johnl@taugh.com" target=3D"_blank">johnl@taugh.com</a>&g=
t;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">&gt;&gt;&gt; domains are g=
oing to be dotless and three of the biggest dotless domains<br>
&gt;&gt;&gt; are going to be called .apple and .microsoft and .google and t=
hey are going<br>
<br>
</div>I&#39;ve read the applications for .apple, .microsoft, and .google. =
=A0None<br>
of them propose to use dotless names, only the usual 2LDs. =A0At this<br>
pont there is just one application that proposes a dotless name,<br>
Google&#39;s .search, and it&#39;s far from clear what will happen to that,=
 or<br>
even if that application would beat out the competing ones from<br>
Amazon, Donuts and dot Now, none of which are dotless.<br>
<br>
Do you think they are lying when they say they won&#39;t be dotless?<br>
<br>
R&#39;s,<br>
John<br>
<br>
PS: The applications are all linked here. =A0The financial info is<br>
redacted, but the technical stuff is all present.<br>
<br>
<a href=3D"https://gtldresult.icann.org/" target=3D"_blank">https://gtldres=
ult.icann.org/</a><br>
</blockquote></div><br>I think the people who wrote those applications on b=
ehalf of their employers are likely to find that other parts of their organ=
ization have a different view after the results are awarded.</div><div clas=
s=3D"gmail_extra">
<br></div><div class=3D"gmail_extra">There are two parts to the DNS busines=
s don&#39;t forget. Is Andrew really sure that if <a href=3D"http://dns.com=
">dns.com</a> decides to help users out by returning the A record for www.m=
icrosoft in response to a request for microsoft. and this turns out to have=
 commercial value that his employer is not going to do the exact same thing=
 even over his objections? Do you think that DNS.com is going to lose busin=
ess to a competitor?</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">[<a href=3D=
"http://dns.com">dns.com</a> is owned by my employer and we also provide re=
cursive DNS services]</div><div class=3D"gmail_extra"><div><br></div><div><=
br></div>
<div>I remember all the squeaking and outrage about sitefinder back in the =
day. That wasn&#39;t my idea but I went along with it as a way to give ICAN=
N a kick up the rear and stop blocking all progress out of fear of lawsuits=
. How many of the people who complained then now work for companies that de=
ploy the same type of system with the same technical impact? I think you wi=
ll find that it is actually quite a large number.</div>
<div><br></div><div><br></div><div>Only five years ago the US banks managed=
 to create a trillion dollar meltdown because they didn&#39;t understand th=
at the perverse market dynamics they had created would force many of their =
companies into bankruptcy. And if the banks had come to that realization an=
d explained the situation to the Treasury or the Fed they would have had no=
 difficulty getting a regulatory regime established that would have protect=
ed their businesses.</div>
<div><br></div><div>That didn&#39;t happen.</div><div><br></div><div><br></=
div><div>Don&#39;t expect me to take a stand on your principles. And certai=
nly don&#39;t expect me to endorse a statement of principles if I didn&#39;=
t even have the opportunity to discuss it before issue.</div>
<div><br></div><div>Most people are averse to chaos. Don&#39;t bet your bus=
inesses that others are going to be averse to it.</div><div><br></div><div>=
<br></div>-- <br>Website: <a href=3D"http://hallambaker.com/">http://hallam=
baker.com/</a><br>

</div></div>

--089e013d0f806ff44704e1532fec--

From ynir@checkpoint.com  Fri Jul 12 11:05:15 2013
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DAB421F9E97 for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 11:05:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.552
X-Spam-Level: 
X-Spam-Status: No, score=-10.552 tagged_above=-999 required=5 tests=[AWL=0.047, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sc9U16gr5qaD for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 11:05:09 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id D19F821F9E7B for <ietf@ietf.org>; Fri, 12 Jul 2013 11:05:05 -0700 (PDT)
Received: from IL-EX10.ad.checkpoint.com ([194.29.34.147]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r6CI521s032665; Fri, 12 Jul 2013 21:05:02 +0300
X-CheckPoint: {51E0454E-9-1B221DC2-1FFFF}
Received: from DAG-EX10.ad.checkpoint.com ([169.254.3.48]) by IL-EX10.ad.checkpoint.com ([169.254.2.91]) with mapi id 14.02.0342.003; Fri, 12 Jul 2013 21:05:01 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: Excuse me for not able to reply shortly
Thread-Topic: Excuse me for not able to reply shortly
Thread-Index: AQHOfr64MKRIlaFzVUKFGDRSIpKeQZlg4VyAgABDiIA=
Date: Fri, 12 Jul 2013 18:05:01 +0000
Message-ID: <F5AABE6A-DCF4-499D-8F0D-0808DBC5A78E@checkpoint.com>
References: <CANF0JMAGMqc7DZsp2T9qi4bWNq6NvWUq3+Fx6Um9nC-_hyT75A@mail.gmail.com> <CAPv4CP_TgVgEb1hCyb8jk5W26WmPzL2xrySqT3DHDoNQq3iyuQ@mail.gmail.com>
In-Reply-To: <CAPv4CP_TgVgEb1hCyb8jk5W26WmPzL2xrySqT3DHDoNQq3iyuQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.20.85]
x-kse-antivirus-interceptor-info: protection disabled
x-cpdlp: 1109d93a32e8c5cc6a475aa1d57a89a40628ba1311
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <200CA1E627EF354D94B3DACA06D6B499@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jul 2013 18:05:15 -0000

On Jul 12, 2013, at 5:03 PM, Scott Brim <scott.brim@gmail.com>
 wrote:

> On Fri, Jul 12, 2013 at 1:14 AM, Hui Deng <denghui02@gmail.com> wrote:
>> I really don't know whether IETF should recommend Deng Hui or Hui Deng
>=20
> That's the question! :-D
>=20
> I believe the Chinese participants should reach this consensus
> themselves and let the IETF know.  Similarly for other groups, e.g.
> Japanese -- when I speak at the microphone, should I say Murai-san or
> Jun?  Please decide.

I usually try to go by how they sign their mailing list messages. "Hui" in =
the case of Hui Deng, "Yukata" in the case of Yukata Oiwa.



From brian.e.carpenter@gmail.com  Fri Jul 12 13:39:00 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C943421F9ECD for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 13:39:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.513
X-Spam-Level: 
X-Spam-Status: No, score=-102.513 tagged_above=-999 required=5 tests=[AWL=0.086, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KkcjDW0-vQwW for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 13:39:00 -0700 (PDT)
Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id 71DD521F9F6D for <ietf@ietf.org>; Fri, 12 Jul 2013 13:38:52 -0700 (PDT)
Received: by mail-pa0-f53.google.com with SMTP id tj12so9262243pac.40 for <ietf@ietf.org>; Fri, 12 Jul 2013 13:38:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=EvS8ferEQaklsy1u1P8G8jztnKuL9U8p7g2iwOq2KJA=; b=DPzN1EJ5lrrPyufzjRbEo+1vCmXfz8zBf1F/mM0+L9POxdZUGHary1ovE2Q9vxgTsw D15zLxPFaLGwEryG7edeD0aZwcGxDEcjEt3PYSKZDhxt/TfTR9kqijSOoPr1+MV1hTNZ cjSwl1zzENglq0tinwL22gHB2Kq2g7IH3e4GBpTUw0EqJ04CmKAQ7qKAqkNH8E3w4Wm4 cOyA6JMfIR+j6s7EZOl+xYm22Lx7NibKDnKueqXJaCu1ml2cubEytU8tBjtJOgBmrtHq RctmGJIYpWa5ebTmikyo/jnyBbTf+GH/ypWKDCoq8PckVYvNrT/+c/y1Yxfl5ADB8LUX nE5Q==
X-Received: by 10.66.25.10 with SMTP id y10mr44545771paf.96.1373661532020; Fri, 12 Jul 2013 13:38:52 -0700 (PDT)
Received: from [192.168.178.23] (152.195.69.111.dynamic.snap.net.nz. [111.69.195.152]) by mx.google.com with ESMTPSA id qv4sm47023267pbc.16.2013.07.12.13.38.49 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 12 Jul 2013 13:38:51 -0700 (PDT)
Message-ID: <51E06965.7010203@gmail.com>
Date: Sat, 13 Jul 2013 08:39:01 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: John Levine <johnl@taugh.com>
Subject: Re: IAB Statement on Dotless Domains
References: <20130712162348.9441.qmail@joyce.lan>
In-Reply-To: <20130712162348.9441.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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jul 2013 20:39:00 -0000

> Do you think they are lying when they say they won't be dotless?

Since http://dotless won't work in any host that has a default domain
configured, which as far as I can tell is most hosts on earth, I
don't think they're lying.

It may be stupid and a license to print money, but that's another story.

    Brian

From john-ietf@jck.com  Fri Jul 12 13:49:34 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89C3F21F9F26 for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 13:49:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.643
X-Spam-Level: 
X-Spam-Status: No, score=-102.643 tagged_above=-999 required=5 tests=[AWL=-0.044, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CAzeGLL2FPyT for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 13:49:28 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 9762421F9F5F for <ietf@ietf.org>; Fri, 12 Jul 2013 13:49:28 -0700 (PDT)
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 1UxkHQ-0005pU-89 for ietf@ietf.org; Fri, 12 Jul 2013 16:49:28 -0400
Date: Fri, 12 Jul 2013 16:49:23 -0400
From: John C Klensin <john-ietf@jck.com>
To: IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: IAB Statement on Dotless Domains
Message-ID: <639A2CA76490E2DF418176E5@JcK-HP8200.jck.com>
In-Reply-To: <CAMm+Lwjk5maZ9AdHakTz=Tg8DtYRSdydRTn2FWjV4yQPC7fnCA@mail.gmail.com>
References: <1984CBB8-6862-4DBB-AFAE-F8461E694083@vigilsec.com> <51DDD49E.5090406@dcrocker.net> <CAMm+Lwj8_zmrp=SmUbb=a_4iEGA2zFaF2EDywaAq=5NkKbvp+w@mail.gmail.com> <alpine.LFD.2.10.1307121016420.21010@bofh.nohats.ca> <CAMm+LwgkEiyQbJLnqgcKe=7dFJ8pJ-HqYvxzMS6oXULX0FS3Tg@mail.gmail.com> <alpine.LFD.2.10.1307121051060.21010@bofh.nohats.ca> <CAMm+Lwjk5maZ9AdHakTz=Tg8DtYRSdydRTn2FWjV4yQPC7fnCA@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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jul 2013 20:49:34 -0000

Hi.

I've been trying to stay out of the broader conversation here,
but it seems to have gone far enough into general issues...

Disclaimer and context: I felt that the DNS was better off with
deep hierarchy since before the work that led to RFC 1591
started.  I hadn't changed my mind when the NRC report [1] tried
to stress that it was much more important to look at navigation
issues than at how many names one could sell.  I felt the same
way during the gTLD-MOU effort and, during the period leading up
to ICANN, argued that generic TLDs should be encouraged to
compete on services, not only price.  I think we would have been
better off if we had called this critter the "domain mnemonic
system" because we may have been doomed as soon as the world
"name" and the folks who design user interfaces and marketing
campaigns caught up with each other.  For the same reason, I
thought TLD labels should be treated as codes with "names" being
a user interface property and have had misgivings about
top-level IDNs because I was concerned that they would
immediately introduce "name" translation problems [2].  I
haven't changed my mind much in the last several years and
believe that the only likely effect of having a few thousand
TLDs will be to increase the rate at which users --most of whom
already don't know the difference between a domain name and a
search term-- go to search engines rather than trying to
remember and use any but a very few domain names.    I assume
there are folks around ICANN who aren't aware of those views and
the reasoning behind them, but it isn't because either my
versions of them or those of others have been a secret.

That said:

	(1) It is clear to me that ICANN is committed to the
	gTLD course --including generic terms, IDNs and
	variants, and a number of other things that may be
	ill-advised-- and that they, case-by-case decisions
	about a few names notwithstanding, are not going to
	change course unless something happens externally that
	gives them no choice.
	
	(2) In the context of the above, making "statements" at
	this time is largely an effort in a**-covering: allowing
	various entities to say, if something goes wrong, "don't
	blame us, we warned you".   If the IAB really wanted to
	make a statement that might have affected the overall
	situation, the window on that probably closed a year or
	two ago.  Perhaps they should have done that, perhaps
	not, but it is too late.
	
	(3) If the IAB is going to make statements now, for
	whatever reason, I believe those statements should be
	technically comprehensive.  Because I don't expect such
	statements to have any real effect, that has as much or
	more to do with IAB long-term credibility as it does
	with statement content.  For that reason, focusing this
	one on the DNS and ignoring the applications
	consequences is probably suboptimal.

	(4) There may be an IETF community issue with how the
	IAB is handling statements like this.  On the one hand,
	I believe it is very important that the IAB be able to
	reach conclusions and expose them to the wider world
	without IETF consensus approval.  On the other, I think
	that their taking advantage of that too often,
	especially when there should be reason to believe that
	there are useful perspectives in the community that they
	may not have internally, represents poor judgment.
	IMO, there has to be a balance, the IAB has to decide
	where that balance lies, and the community's best
	recourse if they regularly get it wrong involve
	conversations with the Nomcom.

My own guess is that this "new gTLD" stuff is going to work out
badly for the Internet.  In one scenario, some new gTLD
applicants get the domains they asked for, things don't work out
as they expected when they applied (whether technically or
economically makes no difference) and they respond unhappily
(which might involve lawyers but probably doesn't really affect
the IETF or the Internet in a substantive way.  In another,
users go even more to search engines and the value of domain
names drops significantly.  That could, indirectly, have bad
effects on ISOC and how the IETF budget is supported.  In still
another, there could be some nasty effects on ICANN and/or its
leadership that could disrupt whatever balance now exists in
"Internet governance" and/or the interactions among players in,
e.g., the Internet protocol space.

But, IMO, the thing that all these issues and discussions
threads have in common is that we are in between the time that
different plans could have been made and the time that we find
out how things are really going to sort themselves out.  A
"statement" here and there aside, we mostly need to wait... and
debates about what happened in the past and why might be
interesting when the history is written (and maybe when the
finger-pointing starts) but probably aren't actionable in the
interim.

Just my opinion.

    john




[1]

[2] See RFC 4185

From bob.hinden@gmail.com  Fri Jul 12 13:58:57 2013
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D688821F9F5C; Fri, 12 Jul 2013 13:58:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5LqecI5eh5Ju; Fri, 12 Jul 2013 13:58:57 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5957E21F9CC6; Fri, 12 Jul 2013 13:58:52 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: The IAOC <bob.hinden@gmail.com>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: Sunday IAOC Overview Session at the Berlin IETF
X-Test-IDTracker: no
X-IETF-IDTracker: 4.51.p2
Message-ID: <20130712205852.10265.88487.idtracker@ietfa.amsl.com>
Date: Fri, 12 Jul 2013 13:58:52 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 12 Jul 2013 20:58:58 -0000

The IETF Administrative Oversight Committee (IAOC) will hold a session from=
 1500-1650 in
Potsdam 1 at the Berlin IETF on Sunday July 28, 2013.  The purpose is to pr=
ovide an
overview of the IAOC to allow the community to better understand what the I=
AOC does, how
the finances work, venue selection, and provide the IAOC feedback on the jo=
b they are
doing.  =


Remote participation support for this session will be provided by Meetecho.

This will be similar to the session held at IETF86 in Orlando.

The IAOC's responsibilities include:

 - Managing the IETF finances
 - Oversight of the IETF Administrative Director (IAD)
 - Selection and oversight of contracted services
 - Venue selection and operation of the IETF meetings
 - Support for the IETF's IT services (data tracker, web sites,
   tools, etc.)

The topics that will be discussed include:

 - BCP101 - Structure of the IETF Administrative Support Activity (IASA)
 - Operation of the IAOC
 - Financial model and relationship with ISOC
 - Venue selection
 - Q & A

We hope this will improve the community understanding of how the IAOC works=
 and provide
the community an opportunity to provide feedback to the IAOC. =


Please let us know ahead of time if you have specific questions you would l=
ike
to see discussed.

Bob Hinden
IAOC Chair

From johnl@taugh.com  Fri Jul 12 14:40:37 2013
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D952211E8168 for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 14:40:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.67
X-Spam-Level: 
X-Spam-Status: No, score=-2.67 tagged_above=-999 required=5 tests=[AWL=-0.070,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y6lPZHd9hvrk for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 14:40:37 -0700 (PDT)
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 135FC11E8160 for <ietf@ietf.org>; Fri, 12 Jul 2013 14:40:36 -0700 (PDT)
Received: (qmail 65775 invoked from network); 12 Jul 2013 21:40:35 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=100ee.51e077d3.k1307; bh=vgj2ZcCTIZA9GSLmrmPAhfhZiN2oy6PWRZjzuIWZ3uI=; b=wjXZylv1OGw7P+Hssczp4Wyxb9a3dwD+ez5LwUNiH8IwYsmnydVVSc+vZkv4nYtNzTBMUpExXOPOF3GwfJ+iAwQJaUsCLUe8Bo97gPGV3cQT1xkTsx3cgVRWMN2SWyp8K1pwRkkZk3ogezxMdC7pcAPQCtQlqHfPufqFn/Dd2oakPje5na2n0zSlm37fpfg27nMGWuSUvsGPaPB3iEaAzKwwhuMjVFEELRuAvl7Gxh7Oox2xqyAPRhc4Wo+qT9t3
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=100ee.51e077d3.k1307; bh=vgj2ZcCTIZA9GSLmrmPAhfhZiN2oy6PWRZjzuIWZ3uI=; b=AaqTdJwVIpRtUSq2nuP/0D/nFEjy/AWCjGvy/zeobNLeHiw2Kp7qridBHlqDNTcHh17gnOjndNkEY1qRp5ivYxxhXHIBBLgWM9MiQiVeAvR1Uos1KdovAajTaPWprKXzvGZrwnYhSTjMyhCcq/yUxKnP2Cff/A2qh7jghFO+E84S/iOd4kUfCBskcf8LXCHg0GmLACn70T/A7A414O/nYObxT5/zoAFOLnaNqj7psRRrBrzzQENK9swdbsutJ2CB
Received: (ofmipd 127.0.0.1); 12 Jul 2013 21:40:13 -0000
Date: 12 Jul 2013 17:40:35 -0400
Message-ID: <alpine.BSF.2.00.1307121737360.13717@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>
Subject: Re: IAB Statement on Dotless Domains
In-Reply-To: <51E06965.7010203@gmail.com>
References: <20130712162348.9441.qmail@joyce.lan> <51E06965.7010203@gmail.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: MULTIPART/signed; protocol="application/pkcs7-signature"; micalg=sha1; BOUNDARY="3825401791-1916628465-1373665235=:13717"
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jul 2013 21:40:38 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--3825401791-1916628465-1373665235=:13717
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

> Since http://dotless won't work in any host that has a default domain
> configured, ...

It's worse than that.  If there is a name "dotless" in the default domain, 
it'll find that one, otherwise it'll fall back to the TLD.

Point your browser at http://dk/ or http://tm/ and see what happens.

For extra fun, try https://dk/ or https://tm/

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
"I dropped the toothpaste", said Tom, crestfallenly.
--3825401791-1916628465-1373665235=:13717
Content-Type: APPLICATION/pkcs7-signature; name=smime.p7s
Content-Transfer-Encoding: BASE64
Content-Description: S/MIME Cryptographic Signature
Content-Disposition: attachment; filename=smime.p7s

MIIJCQYJKoZIhvcNAQcCoIII+jCCCPYCAQExCzAJBgUrDgMCGgUAMAsGCSqG
SIb3DQEHAaCCBjowggY2MIIFHqADAgECAgMGLywwDQYJKoZIhvcNAQEFBQAw
gYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYD
VQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYD
VQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQTAeFw0xMzAzMTYxOTQ0MDdaFw0xNDAzMTgxMjI4MzVaMFUxGTAX
BgNVBA0TEHFaMXRuOTBuMkdVODZzemYxGDAWBgNVBAMMD2pvaG5sQHRhdWdo
LmNvbTEeMBwGCSqGSIb3DQEJARYPam9obmxAdGF1Z2guY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAve/4NFMbuvtD6QSuXAoYQ0SkaO9s
DiNHA4saJNV0OIXd6dtM87w7OETKWWVq24Ab6vQaYh218oCF1GDdLv6EiRB8
oL1k9sK2v70iAVT83vEnmaj6/hQVcBI6mZJH6LXyCgYSP2e5yBQqJu+hgLte
bdg7kOKW2tb937jDn9KYRVFIlEU0/iu/b/Buwq3ahg2BsG3vg92Zk+Dv5VON
QDLE8x8wdi1cor7qBY/RERw4O3LXo3644OU0t6KS3aQxLrXEvWZHHvLhsAu1
BjYbC+qdSddDT1t+adEnZq9/wMhNGhPWCd/uFDZanSpyM913b7eI1Q2aNgA0
cccjEgBsp8IipwIDAQABo4IC1TCCAtEwCQYDVR0TBAIwADALBgNVHQ8EBAMC
BLAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBSL
djRDW8NpGZJjlhjZ0SLge0hCvjAfBgNVHSMEGDAWgBRTcu2SnODaywFcfH6W
NU7y1LhRgjAaBgNVHREEEzARgQ9qb2hubEB0YXVnaC5jb20wggFMBgNVHSAE
ggFDMIIBPzCCATsGCysGAQQBgbU3AQIDMIIBKjAuBggrBgEFBQcCARYiaHR0
cDovL3d3dy5zdGFydHNzbC5jb20vcG9saWN5LnBkZjCB9wYIKwYBBQUHAgIw
geowJxYgU3RhcnRDb20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkwAwIBARqB
vlRoaXMgY2VydGlmaWNhdGUgd2FzIGlzc3VlZCBhY2NvcmRpbmcgdG8gdGhl
IENsYXNzIDEgVmFsaWRhdGlvbiByZXF1aXJlbWVudHMgb2YgdGhlIFN0YXJ0
Q29tIENBIHBvbGljeSwgcmVsaWFuY2Ugb25seSBmb3IgdGhlIGludGVuZGVk
IHB1cnBvc2UgaW4gY29tcGxpYW5jZSBvZiB0aGUgcmVseWluZyBwYXJ0eSBv
YmxpZ2F0aW9ucy4wNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2NybC5zdGFy
dHNzbC5jb20vY3J0dTEtY3JsLmNybDCBjgYIKwYBBQUHAQEEgYEwfzA5Bggr
BgEFBQcwAYYtaHR0cDovL29jc3Auc3RhcnRzc2wuY29tL3N1Yi9jbGFzczEv
Y2xpZW50L2NhMEIGCCsGAQUFBzAChjZodHRwOi8vYWlhLnN0YXJ0c3NsLmNv
bS9jZXJ0cy9zdWIuY2xhc3MxLmNsaWVudC5jYS5jcnQwIwYDVR0SBBwwGoYY
aHR0cDovL3d3dy5zdGFydHNzbC5jb20vMA0GCSqGSIb3DQEBBQUAA4IBAQCM
pgcOpxRJazPzEBYnhGENuQqzXeLyA3a8XL7YaxaAJwV7ucDVkyQHu35PUEkh
vVgIKnxq6N9WxHiO6GK/imdwS3LrUBbs+0v+95m6YhJv6ZfvAHTyTLqrozXU
ohR5NRFeL0p1OfK1llnl/I71Fe/JNgxJHDn1puzsFoJD3zYCKgNdST3FPNIb
2v/xIiubuB85tiJSWUlc56OkCdBK3ZgBnwYV8LxFmpOlwedaHC6sxIk1rsuX
BHbRIJwLFy2LqVtNm0M5NzBVyPQf72lPn/aaJLbqY5DDm4/lSy94R+CKXabE
6lWan7xmbqdDDlMxGbpMRWV2Cxi5ONp4uNgNcwI6MYIClzCCApMCAQEwgZQw
gYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYD
VQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYD
VQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQQIDBi8sMAkGBSsOAwIaBQCggdgwGAYJKoZIhvcNAQkDMQsGCSqG
SIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTMwNzEyMjE0MDM1WjAjBgkqhkiG
9w0BCQQxFgQUJKQh8G3DlRneOEZ7wWa+ItIuzK8weQYJKoZIhvcNAQkPMWww
ajALBglghkgBZQMEASowCwYJYIZIAWUDBAEWMAsGCWCGSAFlAwQBAjAKBggq
hkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4D
AgcwDQYIKoZIhvcNAwICASgwDQYJKoZIhvcNAQEBBQAEggEAUBOKZQZQo3N8
OF7V8bljNlzvRQ1PCCO1DS6nlMy2W9u2prjhYriIZYyPo47541G2pBZLywew
k+NaQ+Ej3JsGH7hgQoIVsckhHD7uz+iEpEVkPmUJrWZSRr/XWj7hAGIwgtgM
pAidoFz5Che4HcgkW8QZj5nVc8ch6feoH6lbfCSYQOxKjiOk/ar7zmrzlLsZ
Sh8nIwVnnUoHrSlycQw4Nd7taOVRCNn2Lm2taXtZ9mJFaJE7nXKlqYrZT2fc
ZwTazu0FZgkqYlTDSZDHQWPSICj/PdhP5x138i5ISDSwqudljk8dW+0aqgqV
ewhzg6bf38Dikbe988NUaxsaKyW2wA==

--3825401791-1916628465-1373665235=:13717--

From ocl@gih.com  Fri Jul 12 14:53:54 2013
Return-Path: <ocl@gih.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6152E21F9FE9 for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 14:53:54 -0700 (PDT)
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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GSRK4RgGP0YU for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 14:53:53 -0700 (PDT)
Received: from waikiki.gih.co.uk (salsa.gih.co.uk [IPv6:2a00:19e8:10:5::b]) by ietfa.amsl.com (Postfix) with ESMTP id 7035121F9FE7 for <ietf@ietf.org>; Fri, 12 Jul 2013 14:53:52 -0700 (PDT)
Received: from waikiki.gih.co.uk (localhost6.localdomain6 [IPv6:::1]) by waikiki.gih.co.uk (Postfix) with ESMTP id 904CB18F3C4; Fri, 12 Jul 2013 22:53:51 +0100 (BST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=gih.com; h=message-id:date :from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=mahalo1; bh=FlTHr1FXn U7YioI6cILh928yT60=; b=kmBH1IUK07h7RgQd5MQ4O+gxQjDJXfW7XdvxU/l4+ OYkJCSYYWnuJ6qmjjBExFsVpmiiZ78epdYHYB8iHLjM4cUtTA4Ko4jQwf/p+/aAd Dxqi/RJ1/PobdF3AWUxunIQeEFA/V90DIUlPPZDZdW/xKm2VbJMWX0LhM9yQr5Ie Pg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gih.com; h=message-id:date :from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=mahalo1; b=TFS 1q9kNIsq1X8tiIqAGq/44qkxJUP2QvfuMQDX3ezBRos0pkLzrJQ2vCcC2yozoUDt fWdq9TNH0urqKYi8uPJfYicM/MIh1sACOnqn+PAIJ9/SG6WgaDUtLwwL2QlhL5rz AYEacb7UQ+cdSUh3DMP6/Pa0jpdpeab+8mXhYupM=
Received: from [10.21.12.171] (unknown [196.38.31.134]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by waikiki.gih.co.uk (Postfix) with ESMTPSA id F11B918F3C1; Fri, 12 Jul 2013 22:53:49 +0100 (BST)
Message-ID: <51E07AF6.4020803@gih.com>
Date: Fri, 12 Jul 2013 23:53:58 +0200
From: Olivier MJ Crepin-Leblond <ocl@gih.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: IAB Statement on Dotless Domains
References: <1984CBB8-6862-4DBB-AFAE-F8461E694083@vigilsec.com> <51DDD49E.5090406@dcrocker.net> <CAMm+Lwj8_zmrp=SmUbb=a_4iEGA2zFaF2EDywaAq=5NkKbvp+w@mail.gmail.com>
In-Reply-To: <CAMm+Lwj8_zmrp=SmUbb=a_4iEGA2zFaF2EDywaAq=5NkKbvp+w@mail.gmail.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Dave Crocker <dcrocker@bbiw.net>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jul 2013 21:53:54 -0000

On 12/07/2013 14:16, Phillip Hallam-Baker wrote:
> The DNS is going to go dotless. That is inevitable when people are
> paying a quarter million dollars to get a dotless domain from ICANN.
> Trying to control the situation with contractual language assumes that
> ICANN is going to forgo large amounts of revenue over a technical conce=
rn.

Not without a fight with at least one of its advisory committees.
http://atlarge-lists.icann.org/pipermail/alac/2013/003232.html

IMO, given the Advice, it would be unwise for ICANN to move forward with
dotless domains as it stands today.
Kind regards,

Olivier MJ Cr=E9pin-Leblond
ALAC Chair

From eburger@standardstrack.com  Fri Jul 12 17:06:42 2013
Return-Path: <eburger@standardstrack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CF8C21F9262 for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 17:06:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.74
X-Spam-Level: 
X-Spam-Status: No, score=-100.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MmoB-3HcZ-3u for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 17:06:37 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.215.15]) by ietfa.amsl.com (Postfix) with ESMTP id D592321F9E44 for <ietf@ietf.org>; Fri, 12 Jul 2013 17:06:37 -0700 (PDT)
Received: from ip68-100-196-226.dc.dc.cox.net ([68.100.196.226]:55047 helo=[192.168.15.100]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80) (envelope-from <eburger@standardstrack.com>) id 1UxnM8-0007p6-Vw; Fri, 12 Jul 2013 17:06:35 -0700
Content-Type: multipart/signed; boundary="Apple-Mail=_90537E76-0A37-4164-8957-2A330E231C66"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Regarding call Chinese names
From: Eric Burger <eburger@standardstrack.com>
In-Reply-To: <F5D9DB98-4E52-42B0-8707-87781BED6710@yahoo.com>
Date: Fri, 12 Jul 2013 20:06:32 -0400
Message-Id: <26E782F1-8389-4625-890E-665129DFB258@standardstrack.com>
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com> <B580C1FC-5794-433F-81CA-FC649CB75943@yahoo.com> <F5D9DB98-4E52-42B0-8707-87781BED6710@yahoo.com>
To: Ida <ida_leung@yahoo.com>
X-Mailer: Apple Mail (2.1508)
X-OutGoing-Spam-Status: No, score=-2.9
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Get-Message-Sender-Via: biz104.inmotionhosting.com: authenticated_id: eburger+standardstrack.com/only user confirmed/virtual account not confirmed
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Jul 2013 00:06:42 -0000

--Apple-Mail=_90537E76-0A37-4164-8957-2A330E231C66
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

I kept my maiden name, too. Another Western option, hyphenation, was not =
for us. Who wants to be a Spear-Burger? Unless you want a Pepsi and =
chips with that. See http://en.wikipedia.org/wiki/Olympia_Cafe

On Jul 10, 2013, at 9:00 PM, Ida <ida_leung@yahoo.com> wrote:

>=20
>=20
> Sent from my iPad
>=20
> On 2013-07-10, at 8:59 PM, Ida <ida_leung@yahoo.com> wrote:
>=20
>> One comment:  I think most of the Chinese women don't change to our =
husband's last name. So,  my husband is not Mr Leung.  We love to keep =
our own last name.  =20
>>=20
>> ...Ida
>>=20
>> Sent from my iPad
>>=20
>> On 2013-07-10, at 8:04 PM, Hui Deng <denghui02@gmail.com> wrote:
>>=20
>>> Hello all
>>> =20
>>> We submitted two drafts to help people here to correctly call =
chinese people names:
>>> http://tools.ietf.org/html/draft-deng-call-chinese-names-00=20
>>>    http://tools.ietf.org/html/draft-zcao-chinese-pronounce-00
>>> =20
>>> Feel free to let us know if you have any other issues?
>>> Best regards,
>>> =20
>>> -Hui Deng


--Apple-Mail=_90537E76-0A37-4164-8957-2A330E231C66
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-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)

iQIcBAEBAgAGBQJR4JoJAAoJEORoZaSQsc1IC/wP/Al3S6ywLR8Keit4ZgJDGcLu
WgBxsKNNR3/xvrBcziubASyQAPIRGtd1RuVaoRbfMFXxJgPyGeENqUrhaz2bAvBt
xiw4lkrffv06SY5kBFhhDXUU3jQ8gRE1U8wArT3D/1v1dO4XHZaiLvENyXpEXjo3
HObBJ+nAa6r24BjXhAR9Yeb3nxT5lQCsT5/sHU6TjpLYiFGG8pVXqG14ViyIXkGJ
6+GlEz/e3yd5oh83B8HvCDRd7bkFgYEWps0ApGwxlT+c/7r2uSGaewTKBPrIodOk
ZT9squFIgR05ZfZC/SfQpS/IBBUwIcercXmFTGS9JaWNNc3bkOf9XIfcRISEGwdG
oetgG++nHqznLz3R2CjgfWDwawPFzB+YMdSRNg9RELS82wpwnwdNfEdlWCnyyovg
5YJG0u5RzFPBxVLDtP7GErN7JJ0lmLyBrq4fgmbqXJBUY78EV5jHpZxxglXfatDb
h2gf1wugSAhqYcQoMFi1KrgGfBeEpdY+1lCbPE8INdHMBFXaNo9v8V1He958+qv3
iOTXPAoHLIR7SjA9ke+1bOqswdSDSmTQoTngOWSTHZYcPUFAhCuddHZukJHZB2Oc
jQb2uQwS80fZHANk/QPLM/eh0IWAoHuU+1//l+fcwHjNfRLH4kHe2Nm3OZmMxih6
9j/rYaKtZ+xjuDbxceiW
=+kHa
-----END PGP SIGNATURE-----

--Apple-Mail=_90537E76-0A37-4164-8957-2A330E231C66--

From abdussalambaryun@gmail.com  Fri Jul 12 22:51:46 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04AE621F994C for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 22:51:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6HJZKsr+EEpD for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2013 22:51:45 -0700 (PDT)
Received: from mail-pb0-x22e.google.com (mail-pb0-x22e.google.com [IPv6:2607:f8b0:400e:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 6309C21F9DCB for <ietf@ietf.org>; Fri, 12 Jul 2013 22:51:45 -0700 (PDT)
Received: by mail-pb0-f46.google.com with SMTP id rq2so9734886pbb.33 for <ietf@ietf.org>; Fri, 12 Jul 2013 22:51:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=x8p/j1OxGQ99K/FVCww/6Q609GqbqRpFLGM/BXIWa3w=; b=jzCyptISxREEiQ6fJ9IVWRKfXpvEeyyITic2AFJ6fWWUG0LD1FVw0MT/eo71QV31zs taUclAvVCYExWuEBScfjq/EjAMKpdr9NkkXzoOvhD/lpeK0+SNELEMknkcEVMCTaWVOj +HS85DRyyMX/awIEAoCwxxihA7ZE7rETGYDdMyFT+0qMp2bqNHGfyiSvt3nFKdR/rYst u1LA8su/g29FENs7yWXxxJn+66Ppib2JDupWBOy+PnxZJOLQSINMdFJoVcc7FrO9A6Dq tI2vOYc8pN3aLUYW5xDqK/MA1FeevFbD7AXwHm0QRETTnLjIirawAEAyILzlJtqgLUX8 SW4A==
MIME-Version: 1.0
X-Received: by 10.68.164.69 with SMTP id yo5mr44769649pbb.96.1373694700167; Fri, 12 Jul 2013 22:51:40 -0700 (PDT)
Received: by 10.68.250.133 with HTTP; Fri, 12 Jul 2013 22:51:39 -0700 (PDT)
In-Reply-To: <20130712205852.10265.88487.idtracker@ietfa.amsl.com>
References: <20130712205852.10265.88487.idtracker@ietfa.amsl.com>
Date: Sat, 13 Jul 2013 07:51:39 +0200
Message-ID: <CADnDZ8-Gx_=rL7g-0MDSLqXRDmgH5mBP1gu-3vCF_Ng66kncGA@mail.gmail.com>
Subject: Re: Sunday IAOC Overview Session at the Berlin IETF
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Bob Hinden <bob.hinden@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Jul 2013 05:51:46 -0000

Hi Bob,

IMO the questions/comments that may be ok to see added to discuss are:

1) Venue selection and operation of the IETF meetings
++++++++++++++++
- Selection of the current venue and was there difficulties until
getting to this meeting session time. From the managing meeting
(providing services) and the community use of the meeting. (10 minute
discuss if needed).

- Is there an alternative venue if the venue was closed for any
emergency reason at any time? or only one plan so if the plan changes
there can be problems with the communities expected plan because they
were not aware of the needed information per time.

- Is there an historic/informational RFC issued by IAOC of
difficulties or important comments in past of venues attended?

- Regarding advice within emergency situations (in or out the meeting
venue), is it considered within chosing the managing meeting
plan/venue, and is the emergency solution an available information for
attended participants and who will attend within a meeting day.

- Someone may like to know if is going to attend at a meeting, how is
the meeting venue managed per time slots, is there a way of quick
feedback/communication of registered-community for meetings (you may
say IETF list but are they connected). The information availability
can be used for others not attended and whom may attend at any time.
(the venue ran out of coffee/water, so I may buy one while going to
venue, or any other issue which can happen out of expected/plan).

2) Other issue:
+++++++++
-Is there a future work plan milestones discussed? can be added to [*]
-I am not sure if was discussed before and answered (I am sorry if
repeated), where do I go to find important past/current Q&A for IAOC
(to avoid efforts to be wasted, and unite best answers)? if not
available it can be good to find it at [*].

[*] http://iaoc.ietf.org/

AB

On 7/12/13, The IAOC <bob.hinden@gmail.com> wrote:
> The IETF Administrative Oversight Committee (IAOC) will hold a session from
> 1500-1650 in
> Potsdam 1 at the Berlin IETF on Sunday July 28, 2013.  The purpose is to
> provide an
> overview of the IAOC to allow the community to better understand what the
> IAOC does, how
> the finances work, venue selection, and provide the IAOC feedback on the job
> they are
> doing.
>
> Remote participation support for this session will be provided by Meetecho.
>
> This will be similar to the session held at IETF86 in Orlando.
>
> The IAOC's responsibilities include:
>
>  - Managing the IETF finances
>  - Oversight of the IETF Administrative Director (IAD)
>  - Selection and oversight of contracted services
>  - Venue selection and operation of the IETF meetings
>  - Support for the IETF's IT services (data tracker, web sites,
>    tools, etc.)
>
> The topics that will be discussed include:
>
>  - BCP101 - Structure of the IETF Administrative Support Activity (IASA)
>  - Operation of the IAOC
>  - Financial model and relationship with ISOC
>  - Venue selection
>  - Q & A
>
> We hope this will improve the community understanding of how the IAOC works
> and provide
> the community an opportunity to provide feedback to the IAOC.
>
> Please let us know ahead of time if you have specific questions you would
> like
> to see discussed.
>
> Bob Hinden
> IAOC Chair
>

From jason_livingood@cable.comcast.com  Sat Jul 13 07:25:53 2013
Return-Path: <jason_livingood@cable.comcast.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B0F721F9DBE for <ietf@ietfa.amsl.com>; Sat, 13 Jul 2013 07:25:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.896
X-Spam-Level: 
X-Spam-Status: No, score=-100.896 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HOST_EQ_MODEMCABLE=1.368, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8uOUTf9rEpxK for <ietf@ietfa.amsl.com>; Sat, 13 Jul 2013 07:25:46 -0700 (PDT)
Received: from cable.comcast.com (pacdcavout01.cable.comcast.com [69.241.43.119]) by ietfa.amsl.com (Postfix) with ESMTP id ADE7521F9DCD for <ietf@ietf.org>; Sat, 13 Jul 2013 07:25:46 -0700 (PDT)
Received: from ([24.40.56.116]) by pacdcavout01.cable.comcast.com with ESMTP  id 97wm3m1.58404615; Sat, 13 Jul 2013 10:23:39 -0400
Received: from PACDCEXHUB04.cable.comcast.com (24.40.56.121) by pacdcexhub03.cable.comcast.com (24.40.56.116) with Microsoft SMTP Server (TLS) id 14.2.318.1; Sat, 13 Jul 2013 10:25:44 -0400
Received: from PACDCEXMB06.cable.comcast.com ([169.254.8.71]) by pacdcexhub04.cable.comcast.com ([fe80::1532:d330:f9a5:c8a1%18]) with mapi id 14.02.0318.001; Sat, 13 Jul 2013 10:25:43 -0400
From: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
To: IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: IAB Statement on Dotless Domains
Thread-Topic: IAB Statement on Dotless Domains
Thread-Index: AQHOfvms/arzTQ9l2kC/lFyt3C7W8JlhRAyAgAAIlICAAAKxgIAACbMAgAFSv4A=
Date: Sat, 13 Jul 2013 14:25:42 +0000
Message-ID: <10229F86C86EB444898E629583FD4171B1C992F9@PACDCEXMB06.cable.comcast.com>
In-Reply-To: <CAMm+LwiQZ2NQOZ0ygVc5T+jNfQGDMnNae8+K9G7hT1r2wV2xDA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.4.120824
x-originating-ip: [68.87.16.248]
Content-Type: multipart/alternative; boundary="_000_10229F86C86EB444898E629583FD4171B1C992F9PACDCEXMB06cabl_"
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Jul 2013 14:25:53 -0000

--_000_10229F86C86EB444898E629583FD4171B1C992F9PACDCEXMB06cabl_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

There must be something similar to Godwin's Law whereby any IETF discussion=
 can devolve into a debate over NAT. ;-)

Jason

On 7/12/13 10:13 AM, "Phillip Hallam-Baker" <hallam@gmail.com<mailto:hallam=
@gmail.com>> wrote:

Keith, read my words, I choose them more carefully than you imagine.

solves their problems at negligible cost TO THEM
What part of that do you disagree with? I don't dispute the fact that NAT i=
s a suboptimal solution if we look at the system as a whole. But the reason=
 I deployed NAT in my house was that Roadrunner wanted $10 extra per month =
for every device I connected to a maximum of 4. I have over 200 IP enabled =
devices in my house.


--_000_10229F86C86EB444898E629583FD4171B1C992F9PACDCEXMB06cabl_
Content-Type: text/html; charset="us-ascii"
Content-ID: <23E803C28546504885185109E6E55C2B@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 16px; font-fami=
ly: Calibri, sans-serif; ">
<div>
<div>
<div>There must be something similar to Godwin's Law whereby any IETF discu=
ssion can devolve into a debate over NAT. ;-)</div>
</div>
</div>
<div><br>
</div>
<div>Jason</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div>
<div>On 7/12/13 10:13 AM, &quot;Phillip Hallam-Baker&quot; &lt;<a href=3D"m=
ailto:hallam@gmail.com">hallam@gmail.com</a>&gt; wrote:</div>
</div>
<div><br>
</div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"BORDER-LEFT:=
 #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div>
<div dir=3D"ltr">Keith, read my words, I choose them more carefully than yo=
u imagine.
<div class=3D"gmail_extra"><br>
</div>
<div class=3D"gmail_extra">
<blockquote type=3D"cite" style=3D"color:rgb(80,0,80)">
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">solves their problems at negligible cost TO THEM=
</div>
</div>
</div>
</blockquote>
</div>
<div class=3D"gmail_extra">What part of that do you disagree with? I don't =
dispute the fact that NAT is a suboptimal solution if we look at the system=
 as a whole. But the reason I deployed NAT in my house was that Roadrunner =
wanted $10 extra per month for every
 device I connected to a maximum of 4. I have over 200 IP enabled devices i=
n my house.<br>
<br>
</div>
</div>
</div>
</div>
</blockquote>
</span>
</body>
</html>

--_000_10229F86C86EB444898E629583FD4171B1C992F9PACDCEXMB06cabl_--

From dhc@dcrocker.net  Sat Jul 13 07:28:36 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DAC3321F9DCD for <ietf@ietfa.amsl.com>; Sat, 13 Jul 2013 07:28:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.595
X-Spam-Level: 
X-Spam-Status: No, score=-6.595 tagged_above=-999 required=5 tests=[AWL=0.004,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id boev1twxHIGQ for <ietf@ietfa.amsl.com>; Sat, 13 Jul 2013 07:28:32 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 0042821F9BB3 for <ietf@ietf.org>; Sat, 13 Jul 2013 07:28:31 -0700 (PDT)
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 r6DESQDV004133 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 13 Jul 2013 07:28:29 -0700
Message-ID: <51E163ED.5060309@dcrocker.net>
Date: Sat, 13 Jul 2013 07:27:57 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
Subject: Re: IAB Statement on Dotless Domains
References: <10229F86C86EB444898E629583FD4171B1C992F9@PACDCEXMB06.cable.comcast.com>
In-Reply-To: <10229F86C86EB444898E629583FD4171B1C992F9@PACDCEXMB06.cable.comcast.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, 13 Jul 2013 07:28:29 -0700 (PDT)
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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, 13 Jul 2013 14:28:37 -0000

On 7/13/2013 7:25 AM, Livingood, Jason wrote:
> There must be something similar to Godwin's Law whereby any IETF
> discussion can devolve into a debate over NAT. ;-)


It's not devolution, it's translation into our private context.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From jason_livingood@cable.comcast.com  Sat Jul 13 07:35:23 2013
Return-Path: <jason_livingood@cable.comcast.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C260D21F9C25 for <ietf@ietfa.amsl.com>; Sat, 13 Jul 2013 07:35:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.063
X-Spam-Level: 
X-Spam-Status: No, score=-103.063 tagged_above=-999 required=5 tests=[AWL=2.167, BAYES_00=-2.599, HOST_EQ_MODEMCABLE=1.368, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jA6QPyl3Qaq5 for <ietf@ietfa.amsl.com>; Sat, 13 Jul 2013 07:35:18 -0700 (PDT)
Received: from cable.comcast.com (copdcavout01.cable.comcast.com [76.96.32.253]) by ietfa.amsl.com (Postfix) with ESMTP id 7D7CD21F9C1B for <ietf@ietf.org>; Sat, 13 Jul 2013 07:35:18 -0700 (PDT)
Received: from ([24.40.56.114]) by copdcavout01.cable.comcast.com with ESMTP  id C7WM3M1.82325411; Sat, 13 Jul 2013 08:33:25 -0600
Received: from PACDCEXMB06.cable.comcast.com ([169.254.8.71]) by PACDCEXHUB01.cable.comcast.com ([fe80::84e8:95f3:f13b:169e%12]) with mapi id 14.02.0318.001; Sat, 13 Jul 2013 10:35:14 -0400
From: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: IAB Statement on Dotless Domains
Thread-Topic: IAB Statement on Dotless Domains
Thread-Index: AQHOfwy4/arzTQ9l2kC/lFyt3C7W8JlhZqcAgAAW1ICAATDEgA==
Date: Sat, 13 Jul 2013 14:35:13 +0000
Message-ID: <10229F86C86EB444898E629583FD4171B1C99376@PACDCEXMB06.cable.comcast.com>
In-Reply-To: <CAMm+Lwjk5maZ9AdHakTz=Tg8DtYRSdydRTn2FWjV4yQPC7fnCA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.4.120824
x-originating-ip: [68.87.16.249]
Content-Type: multipart/alternative; boundary="_000_10229F86C86EB444898E629583FD4171B1C99376PACDCEXMB06cabl_"
MIME-Version: 1.0
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Jul 2013 14:35:23 -0000

--_000_10229F86C86EB444898E629583FD4171B1C99376PACDCEXMB06cabl_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

On 7/12/13 12:24 PM, "Phillip Hallam-Baker" <hallam@gmail.com<mailto:hallam=
@gmail.com>> wrote:
Unfortunately the IAB is not going to give that advice. They seem to have p=
assed on advising ICANN not to issue .corp which is going to be a total sec=
urity meltdown.

The report at http://www.icann.org/en/groups/ssac/documents/sac-057-en.pdf =
is relevant here (though obviously it is an SSAC document and not an IAB do=
cument, which I think is part of the point you may be making).

It's not 20 pieces of silver at stake here is a quarter million bucks or mo=
re a pop.

FWIW, I think for most larger companies with multi-billion dollar revenues =
streams it is less about the up-front fees to apply & operationalize a gTLD=
 than the long term business potential.

Jason

--_000_10229F86C86EB444898E629583FD4171B1C99376PACDCEXMB06cabl_
Content-Type: text/html; charset="us-ascii"
Content-ID: <40D8DEA99D390B468B5D3E8098E30786@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 16px; font-fami=
ly: Calibri, sans-serif; ">
<div>
<div>
<div>On 7/12/13 12:24 PM, &quot;Phillip Hallam-Baker&quot; &lt;<a href=3D"m=
ailto:hallam@gmail.com">hallam@gmail.com</a>&gt; wrote:</div>
</div>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"BORDER-LEFT:=
 #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<div>Unfortunately the IAB is not going to give that advice. They seem to h=
ave passed on advising ICANN not to issue .corp which is going to be a tota=
l security meltdown.
</div>
</div>
</div>
</div>
</blockquote>
</span>
<div><br>
</div>
<div>The report at&nbsp;<a href=3D"http://www.icann.org/en/groups/ssac/docu=
ments/sac-057-en.pdf">http://www.icann.org/en/groups/ssac/documents/sac-057=
-en.pdf</a>&nbsp;is relevant here (though obviously it is an SSAC document =
and not an IAB document, which I think is part
 of the point you may be making).</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"BORDER-LEFT:=
 #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<div>It's not 20 pieces of silver at stake here is a quarter million bucks =
or more a pop.</div>
</div>
</div>
</div>
</blockquote>
</span>
<div><br>
</div>
<div>FWIW, I think for most larger companies with multi-billion dollar reve=
nues streams it is less about the up-front fees to apply &amp; operationali=
ze a gTLD than the long term business potential.&nbsp;</div>
<div><br>
</div>
<div>Jason</div>
</body>
</html>

--_000_10229F86C86EB444898E629583FD4171B1C99376PACDCEXMB06cabl_--

From jnc@mercury.lcs.mit.edu  Sat Jul 13 08:27:55 2013
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B416721F9E0F for <ietf@ietfa.amsl.com>; Sat, 13 Jul 2013 08:27:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nSqo5Q4VWEXJ for <ietf@ietfa.amsl.com>; Sat, 13 Jul 2013 08:27:50 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id A31CC21F8EDF for <ietf@ietf.org>; Sat, 13 Jul 2013 08:27:50 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 8F79D18C0D0; Sat, 13 Jul 2013 11:27:47 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: IAB Statement on Dotless Domains
Message-Id: <20130713152747.8F79D18C0D0@mercury.lcs.mit.edu>
Date: Sat, 13 Jul 2013 11:27:47 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Jul 2013 15:27:55 -0000

    > From: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>

    > FWIW, I think for most larger companies with multi-billion dollar
    > revenues streams it is less about the up-front fees to apply &
    > operationalize a gTLD than the long term business potential.

I guess I'm missing something. How exactly is having a gTLD going to bring in
the Big Bucks? Do people actually type addresses into the address bars on
their browsers any more, or do they just type what they're looking for into
the search bar?

	Noel

From arturo.servin@gmail.com  Sat Jul 13 08:38:43 2013
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6CDB21F9E9C for <ietf@ietfa.amsl.com>; Sat, 13 Jul 2013 08:38:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sW8lSYtCz9jB for <ietf@ietfa.amsl.com>; Sat, 13 Jul 2013 08:38:43 -0700 (PDT)
Received: from mail-qc0-x22d.google.com (mail-qc0-x22d.google.com [IPv6:2607:f8b0:400d:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 6159221F9E91 for <ietf@ietf.org>; Sat, 13 Jul 2013 08:38:43 -0700 (PDT)
Received: by mail-qc0-f173.google.com with SMTP id l10so5551764qcy.18 for <ietf@ietf.org>; Sat, 13 Jul 2013 08:38:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=ORhaEx/e1dBkuvfhNdTX/BCv/ypyl8+YgKZy2/uiX/U=; b=kDUwROGBK7sshS+C27tbtpoAbjSQaUaHQdKxBiDA2zjuzmK1QO4l50MCzYqXD+utZq izosVaHf9CQDGYZ7/9FWsgJiACcYWWpyRaOplA0nDjXAgFltcxXxa2FHrRSTLjODCZY/ M+Xa+t9EP85Msatv1GU0zbNF8+OnbUUxunt5hYbuBL2+1Z7s37Yxqijv75WfQSxrkghC L9JZOVyMFDJ1SdQo8j7oSn0B9VBB55h9v7ynsYI/7ORKUY1GHLP3CgfCZkxs7sIOStnI lZmnPLAK3hU265/Nb1X9dAAgQHge55hdaSKYJmjUWkrOckplg8tGwpONf0q1+QV+xxEW b2lA==
X-Received: by 10.224.119.148 with SMTP id z20mr43701004qaq.111.1373729922844;  Sat, 13 Jul 2013 08:38:42 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local ([2800:af:ba30:f1e1:9573:87d:69eb:3838]) by mx.google.com with ESMTPSA id r2sm41484687qeh.7.2013.07.13.08.38.40 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 13 Jul 2013 08:38:41 -0700 (PDT)
Message-ID: <51E17481.40601@gmail.com>
Date: Sat, 13 Jul 2013 12:38:41 -0300
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: IAB Statement on Dotless Domains
References: <20130713152747.8F79D18C0D0@mercury.lcs.mit.edu>
In-Reply-To: <20130713152747.8F79D18C0D0@mercury.lcs.mit.edu>
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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Jul 2013 15:38:44 -0000

On 7/13/13 12:27 PM, Noel Chiappa wrote:
>     > From: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
>
>     > FWIW, I think for most larger companies with multi-billion dollar
>     > revenues streams it is less about the up-front fees to apply &
>     > operationalize a gTLD than the long term business potential.
>
> I guess I'm missing something. How exactly is having a gTLD going to bring in
> the Big Bucks? Do people actually type addresses into the address bars on
> their browsers any more, or do they just type what they're looking for into
> the search bar?
>
> 	Noel
    Not even using a search bar anymore. Some browsers do a search
whilst you are writing the hostname that you want to access. So for
facebook I just normally type "fac", twitter "twi" and it autocompletes.
For Google and wikipedia I do not even try to go to their web page. For
a search (google) I just type what I am looking for and that is all, for
wikipedia I do the same and 95% of the times the first search result is
the link to them.

Regards,
as

From hsantos@isdg.net  Sat Jul 13 09:24:39 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E43021F9E0F for <ietf@ietfa.amsl.com>; Sat, 13 Jul 2013 09:24:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.49
X-Spam-Level: 
X-Spam-Status: No, score=-101.49 tagged_above=-999 required=5 tests=[AWL=-1.036, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, J_CHICKENPOX_39=0.6, SARE_MONEYTERMS=0.681, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AI6Xr3tw9MzS for <ietf@ietfa.amsl.com>; Sat, 13 Jul 2013 09:24:35 -0700 (PDT)
Received: from dkim.winserver.com (catinthebox.net [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id C773221F9BF7 for <ietf@ietf.org>; Sat, 13 Jul 2013 09:24:34 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=4341; t=1373732669; h=Received:Received: Message-ID:Date:From:To:Subject:Organization:List-ID; bh=27vsTbl F9W28I6BzglMWSyWMBp4=; b=X6bJyDhOERRmRVFZvB/mjvHywDvvF8z4Yg1GaVf cZWOXQc2RKv370+bJEortrBlgEeEjpk24PRdqHOQ1YtnxLBILejVKJzh+/u/twzC R9jX57pQGfmcWHY6cVc7IkbvMXfAO6SPCRDol++KFn/sKqMQC9tda+IAZLDUwpSu whrE=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sat, 13 Jul 2013 12:24:29 -0400
Received: from [208.247.131.8] ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 195223880.12089.1256; Sat, 13 Jul 2013 12:24:28 -0400
Message-ID: <51E17E86.6040504@isdg.net>
Date: Sat, 13 Jul 2013 12:21:26 -0400
From: Hector Santos <hsantos@isdg.net>
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: IAB Statement on Dotless Domains
References: <CAMm+LwgkEiyQbJLnqgcKe=7dFJ8pJ-HqYvxzMS6oXULX0FS3Tg@mail.gmail.com> <20130712162348.9441.qmail@joyce.lan> <CAMm+Lwhd4B-aA=sH5wiKQT6H5RuTKuAkVajAw169sCTFqLDzWw@mail.gmail.com>
In-Reply-To: <CAMm+Lwhd4B-aA=sH5wiKQT6H5RuTKuAkVajAw169sCTFqLDzWw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Jul 2013 16:24:39 -0000

All the discussion details are overwhelming  but I do seem to feel there 
is a marketing and branding problem especially when it comes to 
searching a domain at the USER DATA ENTRY LEVEL, i.e. slow keyboard input.

For example, I own WINSERVER.COM.  Try typing WINSERVER in google (for 
the first time, clear cache is necessary) and see how the 
auto-suggestion goes as you type and searching for it yield not 
WINSERVER.COM first, but places related to WINdows SERVERS like 
microsoft first.  The last time I tried it on a friend's PC to prove the 
point, it was the 3rd hit after two Microsoft links were shown.

I think it is unfair and  if I was really worry about it is possible 
subject to some long time usage trade marking infringement claim.  Why 
is GOOGLE is not, from a technical standpoint, yielding the DNS answer 
first, with the WINSERVER.COM site first?

Of course, I understand the money, profit, business side of it, and also 
a technical side with the Google's "smart" BI algorithms used. But most 
people who would be searching for WINSERVER, they are not really 
interested in "WINDOWS SERVERS" first.

I don't think its a winning battle, but there are some ethical issues 
that could be addressed as a global common.  Perhaps an I-D can be 
written to SUGGEST that Searching Techniques SHOULD check the DNS 
solution first.  That may include the dotless answer I suppose as well.

--
HLS

On 7/12/2013 12:41 PM, Phillip Hallam-Baker wrote:
> On Fri, Jul 12, 2013 at 12:23 PM, John Levine <johnl@taugh.com> wrote:
>
>>>>> domains are going to be dotless and three of the biggest dotless
>> domains
>>>>> are going to be called .apple and .microsoft and .google and they are
>> going
>>
>> I've read the applications for .apple, .microsoft, and .google.  None
>> of them propose to use dotless names, only the usual 2LDs.  At this
>> pont there is just one application that proposes a dotless name,
>> Google's .search, and it's far from clear what will happen to that, or
>> even if that application would beat out the competing ones from
>> Amazon, Donuts and dot Now, none of which are dotless.
>>
>> Do you think they are lying when they say they won't be dotless?
>>
>> R's,
>> John
>>
>> PS: The applications are all linked here.  The financial info is
>> redacted, but the technical stuff is all present.
>>
>> https://gtldresult.icann.org/
>>
>
> I think the people who wrote those applications on behalf of their
> employers are likely to find that other parts of their organization have a
> different view after the results are awarded.
>
> There are two parts to the DNS business don't forget. Is Andrew really sure
> that if dns.com decides to help users out by returning the A record for
> www.microsoft in response to a request for microsoft. and this turns out to
> have commercial value that his employer is not going to do the exact same
> thing even over his objections? Do you think that DNS.com is going to lose
> business to a competitor?
>
> [dns.com is owned by my employer and we also provide recursive DNS services]
>
>
> I remember all the squeaking and outrage about sitefinder back in the day.
> That wasn't my idea but I went along with it as a way to give ICANN a kick
> up the rear and stop blocking all progress out of fear of lawsuits. How
> many of the people who complained then now work for companies that deploy
> the same type of system with the same technical impact? I think you will
> find that it is actually quite a large number.
>
>
> Only five years ago the US banks managed to create a trillion dollar
> meltdown because they didn't understand that the perverse market dynamics
> they had created would force many of their companies into bankruptcy. And
> if the banks had come to that realization and explained the situation to
> the Treasury or the Fed they would have had no difficulty getting a
> regulatory regime established that would have protected their businesses.
>
> That didn't happen.
>
>
> Don't expect me to take a stand on your principles. And certainly don't
> expect me to endorse a statement of principles if I didn't even have the
> opportunity to discuss it before issue.
>
> Most people are averse to chaos. Don't bet your businesses that others are
> going to be averse to it.
>
>


From johnl@iecc.com  Sat Jul 13 09:29:21 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E38321F9DB5 for <ietf@ietfa.amsl.com>; Sat, 13 Jul 2013 09:29:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.74
X-Spam-Level: 
X-Spam-Status: No, score=-110.74 tagged_above=-999 required=5 tests=[AWL=0.459, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KqftLJgyr6qf for <ietf@ietfa.amsl.com>; Sat, 13 Jul 2013 09:29:17 -0700 (PDT)
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 1F9A121F9CF1 for <ietf@ietf.org>; Sat, 13 Jul 2013 09:29:16 -0700 (PDT)
Received: (qmail 82396 invoked from network); 13 Jul 2013 16:29:16 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 13 Jul 2013 16:29:16 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=51e1805b.xn--btvx9d.k1307; i=johnl@user.iecc.com; bh=Z2B4x9jYwxYXr70/H3md17Nbrgh8mTg98dZEMgSYJmI=; b=l2d54/oxIIVygSVcoW0r4yFIVmGcuL0YAuNonp3moAyeRi9eKuMPXQQbziITFvAznZXf88X7kmZLW9BO0vAeYHMcBbEtLvLWoPiheW687pXMiqO/JRdcBuGhgaiAaBO26gLe6RI16KDE0YBYhaCMFIPgVPoMYRmGN4phLARPsQKgLfcVTrntFduWk73nCJ/EHBYAB3kAaBOUiJHKURnChjZxetVqs8sAXIblTJ7VvVKuZ0Rvr2h4upRSDo+Fj8cj
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=51e1805b.xn--btvx9d.k1307; olt=johnl@user.iecc.com; bh=Z2B4x9jYwxYXr70/H3md17Nbrgh8mTg98dZEMgSYJmI=; b=cs+wCpwQd6UVJ4LH6z51wgAkqWN0eNMoPTPo6nsq9484oxiQJVAWMxbHyBOdbUITd+ac4MO4bp8ysKojE+oELC5428MOSNuthwzoLRgm9YR55LX8ogvj/dvRCHevWwQq4oudRlDP0o7unitZMvpCXR/cakyspnNOI6Fr9tyvud4zF5rYZRFd/GrHnLMlpfVKHGEen/3LbvPiYDLQibgzkx3KxcwyworX6JZo9dixFoL3ENClLr0DcLGxyCpXovDt
Date: 13 Jul 2013 16:28:53 -0000
Message-ID: <20130713162853.10597.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: IAB Statement on Dotless Domains
In-Reply-To: <20130713152747.8F79D18C0D0@mercury.lcs.mit.edu>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Jul 2013 16:29:21 -0000

>I guess I'm missing something. How exactly is having a gTLD going to bring in
>the Big Bucks? Do people actually type addresses into the address bars on
>their browsers any more, or do they just type what they're looking for into
>the search bar?

Let's just say you're not allowed to ask that question, any more than
you can ask a fundamentalist Christian how he knows he's going to
heaven.

You are definitely not allowed to look at the history of .AERO,
.TRAVEL, .JOBS, .ASIA, .MUSEUM, .COOP, .MOBI, .TEL or .PRO.




From john-ietf@jck.com  Sat Jul 13 09:52:19 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC4EF21F9E43 for <ietf@ietfa.amsl.com>; Sat, 13 Jul 2013 09:52:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.638
X-Spam-Level: 
X-Spam-Status: No, score=-102.638 tagged_above=-999 required=5 tests=[AWL=-0.039, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JthTeJ+Iew7f for <ietf@ietfa.amsl.com>; Sat, 13 Jul 2013 09:52:11 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id D2CA121F9D31 for <ietf@ietf.org>; Sat, 13 Jul 2013 09:52:10 -0700 (PDT)
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 1Uy33J-0008BD-Sa; Sat, 13 Jul 2013 12:52:09 -0400
Date: Sat, 13 Jul 2013 12:52:04 -0400
From: John C Klensin <john-ietf@jck.com>
To: John Levine <johnl@taugh.com>, ietf@ietf.org
Subject: Re: IAB Statement on Dotless Domains
Message-ID: <2EDBEC5D8CF4B0A1758D4CA1@JcK-HP8200.jck.com>
In-Reply-To: <20130713162853.10597.qmail@joyce.lan>
References: <20130713162853.10597.qmail@joyce.lan>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Jul 2013 16:52:20 -0000

--On Saturday, July 13, 2013 16:28 +0000 John Levine
<johnl@taugh.com> wrote:

>> I guess I'm missing something. How exactly is having a gTLD
>> going to bring in the Big Bucks? Do people actually type
>> addresses into the address bars on their browsers any more,
>> or do they just type what they're looking for into the search
>> bar?
> 
> Let's just say you're not allowed to ask that question, any
> more than you can ask a fundamentalist Christian how he knows
> he's going to heaven.

Noel asked at least two different questions.  One is not
supposed to ask either of them, whether your analogy is
appropriate or not.  (And see my note from yesterday.)
 
> You are definitely not allowed to look at the history of .AERO,
> .TRAVEL, .JOBS, .ASIA, .MUSEUM, .COOP, .MOBI, .TEL or .PRO.

One could quibble about that list -- I'd think about deleting
one or two that actually met the rather narrow expectations for
them and maybe add a few others that didn't.  But, yes, the
track record of big profits from selling names out of new gTLDs,
especially if "defensive registrations" are excluded, has been
abysmal.

As far as I know, the only completely successful business model
for post-2001 new gTLDs that were not intended as a service for
a restricted community has involved an extreme form of the
"encourage defensive registrations" model, so extreme that
others have described it as "extortion".

   john


From hsantos@isdg.net  Sat Jul 13 10:01:49 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BBCF21F9AFD for <ietf@ietfa.amsl.com>; Sat, 13 Jul 2013 10:01:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.433
X-Spam-Level: 
X-Spam-Status: No, score=-102.433 tagged_above=-999 required=5 tests=[AWL=0.166, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KgGmCYx5w6nQ for <ietf@ietfa.amsl.com>; Sat, 13 Jul 2013 10:01:44 -0700 (PDT)
Received: from mail.santronics.com (secure.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 74EA721F9CCC for <ietf@ietf.org>; Sat, 13 Jul 2013 10:01:43 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1531; t=1373734895; h=Received:Received: Message-ID:Date:From:To:Subject:Organization:List-ID; bh=aMm59o8 sfWX0C7fzF8BoQ6JT5zo=; b=iykiHvzYb/uTmAo4lW5/FqbjIjYyndbLmJw/Tve A+RGuoPM9tceYrLY3pE7AwissDOvKfUnpKLydJhueBWERpBYioASUJBauL3xvsTm Du8hv5V8xb/omUgrSRjqsG6JxxMiTLY/hQagYZ+iiZFeqSY4ZF3LUNBrk5gbLmcR GDrw=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sat, 13 Jul 2013 13:01:35 -0400
Received: from [208.247.131.8] ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 197448844.12089.3672; Sat, 13 Jul 2013 13:01:33 -0400
Message-ID: <51E18737.4080903@isdg.net>
Date: Sat, 13 Jul 2013 12:58:31 -0400
From: Hector Santos <hsantos@isdg.net>
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: IAB Statement on Dotless Domains
References: <20130713152747.8F79D18C0D0@mercury.lcs.mit.edu>
In-Reply-To: <20130713152747.8F79D18C0D0@mercury.lcs.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Jul 2013 17:01:49 -0000

On 7/13/2013 11:27 AM, Noel Chiappa wrote:
>      > From: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
>
>      > FWIW, I think for most larger companies with multi-billion dollar
>      > revenues streams it is less about the up-front fees to apply &
>      > operationalize a gTLD than the long term business potential.
>
> I guess I'm missing something. How exactly is having a gTLD going to bring in
> the Big Bucks? Do people actually type addresses into the address bars on
> their browsers any more, or do they just type what they're looking for into
> the search bar?
>
> 	Noel

Define people.  The layman will not type the protocol (http://),  and 
the auto-suggestion technology is so advanced, you will get multiple 
different sets of results that may or may not include the DNS solution 
as the first part of the result.

Try typing out my domain, winserver.com. First timers will not get the 
WINSERVER.COM web site, but Microsoft's WIN SERVER 201x and/or WINDOWS 
SERVER web sites first.

Overall, while I believe winserver and winserver.com are technically 
different as with winserver.net, winserver.org, etc, I think it would be 
unfair if a dotless WINSERVER dns entry was prevailing over my 
winserver.com domain.   Perhaps an I-D describing a BCP for searching 
orders will help, if not already, available.  If Dotless domains are to 
be inter-networking ready as it already in used for intra-networking 
operations, then perhaps it should be a FALLBACK answer to the .com, 
.net, org lookup.

--
HLS


From ynir@checkpoint.com  Sat Jul 13 11:20:46 2013
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0903721F9D21 for <ietf@ietfa.amsl.com>; Sat, 13 Jul 2013 11:20:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.556
X-Spam-Level: 
X-Spam-Status: No, score=-10.556 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 01jbLtML+Yn2 for <ietf@ietfa.amsl.com>; Sat, 13 Jul 2013 11:20:41 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 25F4721F9DA1 for <ietf@ietf.org>; Sat, 13 Jul 2013 11:20:36 -0700 (PDT)
Received: from IL-EX10.ad.checkpoint.com ([194.29.34.147]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r6DIKKfE004685; Sat, 13 Jul 2013 21:20:21 +0300
X-CheckPoint: {51E19A64-0-1B221DC2-1FFFF}
Received: from DAG-EX10.ad.checkpoint.com ([169.254.3.48]) by IL-EX10.ad.checkpoint.com ([169.254.2.91]) with mapi id 14.02.0342.003; Sat, 13 Jul 2013 21:20:19 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Hector Santos <hsantos@isdg.net>
Subject: Re: IAB Statement on Dotless Domains
Thread-Topic: IAB Statement on Dotless Domains
Thread-Index: AQHOf92HAFrivg72VUiwNFpPx9QSvZliomKAgAAW2oA=
Date: Sat, 13 Jul 2013 18:20:18 +0000
Message-ID: <3725D4B2-65DA-45FA-AAEE-309F45CD6F18@checkpoint.com>
References: <20130713152747.8F79D18C0D0@mercury.lcs.mit.edu> <51E18737.4080903@isdg.net>
In-Reply-To: <51E18737.4080903@isdg.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.21.84]
x-kse-antivirus-interceptor-info: protection disabled
x-cpdlp: 11074c6f9cabb739f14ddbf03d44759777624e15b0
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <981DA49E9516694DA90ABF6A07621D7B@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Jul 2013 18:20:46 -0000

On Jul 13, 2013, at 7:58 PM, Hector Santos <hsantos@isdg.net> wrote:
>=20
> Try typing out my domain, winserver.com. First timers will not get the WI=
NSERVER.COM web site, but Microsoft's WIN SERVER 201x and/or WINDOWS SERVER=
 web sites first.

I did as you suggested earlier, and typed "winserver", but not into Google'=
s search bar. I typed it into the address bar of Safari. Like Chrome, the a=
ddress bar and search bar are the same. I got these suggestions, sorted by =
category:

  Google Search
     winserver
     win server 2012
     win server 2008
     win server 2003
     win server 2013
  Search Suggestions
     Santronic's Wildcat! Interactive Net Server (WINSE...     winserver.co=
m
     WinServer - Home                                          winserver.co=
deplex.com
     Wildcat! Open Site                                        opensite.win=
server.com

So finding your site is not that difficult for first-timers. But regardless=
, the people who type in addresses or DNS names in full are rare and far be=
tween.=

From fernando@gont.com.ar  Sat Jul 13 11:34:54 2013
Return-Path: <fernando@gont.com.ar>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70BF521F9CE0 for <ietf@ietfa.amsl.com>; Sat, 13 Jul 2013 11:34:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UrxGPN2XES39 for <ietf@ietfa.amsl.com>; Sat, 13 Jul 2013 11:34:53 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 7C89621F9CD9 for <ietf@ietf.org>; Sat, 13 Jul 2013 11:34:53 -0700 (PDT)
Received: from [2001:5c0:1400:a::5a9] by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fernando@gont.com.ar>) id 1Uy4eg-00012Y-Tt; Sat, 13 Jul 2013 20:34:51 +0200
Message-ID: <51E19DC9.9050305@gont.com.ar>
Date: Sat, 13 Jul 2013 20:34:49 +0200
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: ipv6hackers Meeting in Berlin (July 30, 2013)
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Jul 2013 18:34:54 -0000

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

FYI

Folks,

We finally put everything in place to announce the very first IPv6
Hackers meeting.

All the relevant info is available at::
<http://www.ipv6hackers.org/meetings/berlin-2013>


- ---- cut here ----
IPv6 Hackers Meeting - Berlin 2013

** What **

- From a couple of years now, we have had a mailing-list devoted to IPv6
hacking (i.e., testing, tools, low-level stuff, etc.), home of the
"ipv6hackers" group. The mailing-list ("charter", subscription options,
etc.) is available at:
<http://lists.si6networks.com/listinfo/ipv6hackers/>.

We're planning to have our first in-person meeting, which will feature a
number of presentations (which MUST be accompanied
with code and/or measurements/testing).


** When **

July 30 (Tuesday), 2013. From 16:00 to 19:00.


** Where **

Salzufer 14, 10587  Berlin, Germany. EANTC AG (European Advanced
Networking Test Center) Headquarters.

If you'll be arriving from the IETF 87 venue (Intercontinental Berlin),
it's about a 30-minute walk.

Maps available here: <http://www.ipv6hackers.org/meetings/berlin-2013>


** How to participate **

The meeting is open for participation, at no cost.

If you have any interesting stuff to present, please send the following
information to <info@ipv6hackers.org> *before* July 23, 2013:

 * Proposed presentation title
 * Abstract
 * Speaker name

Note: All presentations must be practical in nature. They must feature
tools, testing, and/or measurements.
- ---- cut here ----

- -- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





- -- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@si6networks.com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAEBAgAGBQJR4Z25AAoJEJbuqe/Qdv/xqJgH/27sT5uYP9xyH2WlvzzhINE7
7FHEtUMJ9iLlUjcHqp7vz/u2AoB1vaxS0zVN1cGI2FszYe7E5jo9Y3SxhheGJbhn
ih9H0MT/tgJcVkUi1bVnmlgPl408WZTtQ87Akq/ZNcTOLM9PtC3q71qRgJdLp3AC
pp18+lMRqqc4AxQRDzrh1xdozKAuRSOlDFSLFRXdpj0MkAux5qchnerDWQqxMaf/
hBywuHWFMdce6LfBpm91+MwXKXFLaNt89eDWeFbLoQazRA16qLjsTFyPMTgvfjvY
VcZWuJE4N5iWWAMM0mlcyIM0D1Jd/mdYUxl1p/psCkx5e0wgkf0ult5FJa/T0vc=
=1Bwn
-----END PGP SIGNATURE-----

From warren@kumari.net  Sat Jul 13 11:48:27 2013
Return-Path: <warren@kumari.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8197421F9C0B for <ietf@ietfa.amsl.com>; Sat, 13 Jul 2013 11:48:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.524
X-Spam-Level: 
X-Spam-Status: No, score=-102.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XjZaYMmASpg4 for <ietf@ietfa.amsl.com>; Sat, 13 Jul 2013 11:48:23 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B7C521F9DFC for <ietf@ietf.org>; Sat, 13 Jul 2013 11:48:21 -0700 (PDT)
Received: from [10.21.11.75] (unknown [196.38.31.134]) by vimes.kumari.net (Postfix) with ESMTPSA id 39BE51B407D8; Sat, 13 Jul 2013 14:48:18 -0400 (EDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_B32EC6CC-6936-45F9-85E3-278E343EEC29"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [IETF] Re: Regarding call Chinese names
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <26E782F1-8389-4625-890E-665129DFB258@standardstrack.com>
Date: Sat, 13 Jul 2013 14:48:10 -0400
Message-Id: <4CAD06C6-784D-4337-9903-6896AA9731BA@kumari.net>
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com> <B580C1FC-5794-433F-81CA-FC649CB75943@yahoo.com> <F5D9DB98-4E52-42B0-8707-87781BED6710@yahoo.com> <26E782F1-8389-4625-890E-665129DFB258@standardstrack.com>
To: Eric Burger <eburger@standardstrack.com>
X-Mailer: Apple Mail (2.1508)
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Jul 2013 18:48:27 -0000

--Apple-Mail=_B32EC6CC-6936-45F9-85E3-278E343EEC29
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Jul 12, 2013, at 8:06 PM, Eric Burger <eburger@standardstrack.com> =
wrote:

> I kept my maiden name, too.

And I took my wife's last name when we married.=20
This caused no end of confusion at the marriage office, with their =
Borland C "Turbo Vision" Text menu system app, with a space for a =
"maiden" name for the female to change her name, but not the male=85

W



> Another Western option, hyphenation, was not for us. Who wants to be a =
Spear-Burger? Unless you want a Pepsi and chips with that. See =
http://en.wikipedia.org/wiki/Olympia_Cafe
>=20
> On Jul 10, 2013, at 9:00 PM, Ida <ida_leung@yahoo.com> wrote:
>=20
>>=20
>>=20
>> Sent from my iPad
>>=20
>> On 2013-07-10, at 8:59 PM, Ida <ida_leung@yahoo.com> wrote:
>>=20
>>> One comment:  I think most of the Chinese women don't change to our =
husband's last name. So,  my husband is not Mr Leung.  We love to keep =
our own last name.  =20
>>>=20
>>> ...Ida
>>>=20
>>> Sent from my iPad
>>>=20
>>> On 2013-07-10, at 8:04 PM, Hui Deng <denghui02@gmail.com> wrote:
>>>=20
>>>> Hello all
>>>>=20
>>>> We submitted two drafts to help people here to correctly call =
chinese people names:
>>>> http://tools.ietf.org/html/draft-deng-call-chinese-names-00=20
>>>>   http://tools.ietf.org/html/draft-zcao-chinese-pronounce-00
>>>>=20
>>>> Feel free to let us know if you have any other issues?
>>>> Best regards,
>>>>=20
>>>> -Hui Deng
>=20

--
Consider orang-utans.
In all the worlds graced by their presence, it is suspected that they =
can talk but choose not to do so in case humans put them to work, =
possibly in the television industry. In fact they can talk. It's just =
that they talk in Orang-utan. Humans are only capable of listening in =
Bewilderment.
-- Terry Practhett



--Apple-Mail=_B32EC6CC-6936-45F9-85E3-278E343EEC29
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-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)

iEYEARECAAYFAlHhoPAACgkQ/sGA6gkxszjWLACguqT/Yi4jHOfjmOf9/0G009QA
MeEAoImbc/urEz4FMPeqg8i7KIrYZchH
=TneI
-----END PGP SIGNATURE-----

--Apple-Mail=_B32EC6CC-6936-45F9-85E3-278E343EEC29--

From cos@mip.polyamory.org  Sat Jul 13 13:11:34 2013
Return-Path: <cos@mip.polyamory.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79F7721F9A98 for <ietf@ietfa.amsl.com>; Sat, 13 Jul 2013 13:11:34 -0700 (PDT)
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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RTDKRfUFIDhK for <ietf@ietfa.amsl.com>; Sat, 13 Jul 2013 13:11:30 -0700 (PDT)
Received: from mip.polyamory.org (mip.polyamory.org [199.201.145.10]) by ietfa.amsl.com (Postfix) with ESMTP id 390F921F9A8E for <ietf@ietf.org>; Sat, 13 Jul 2013 13:11:30 -0700 (PDT)
Received: by mip.polyamory.org (Postfix, from userid 1002) id 917D910760; Sat, 13 Jul 2013 16:11:22 -0400 (EDT)
Date: Sat, 13 Jul 2013 16:11:22 -0400
From: Ofer Inbar <cos@aaaaa.org>
To: Phillip Hallam-Baker <hallam@gmail.com>, Dave Crocker <dcrocker@bbiw.net>, IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: IAB Statement on Dotless Domains
Message-ID: <20130713201122.GO29401@mip.aaaaa.org>
References: <1984CBB8-6862-4DBB-AFAE-F8461E694083@vigilsec.com> <51DDD49E.5090406@dcrocker.net> <CAMm+Lwj8_zmrp=SmUbb=a_4iEGA2zFaF2EDywaAq=5NkKbvp+w@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAMm+Lwj8_zmrp=SmUbb=a_4iEGA2zFaF2EDywaAq=5NkKbvp+w@mail.gmail.com>
User-Agent: Mutt/1.4.2.3i
Organization: American Association Against Acronym Abuse
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Jul 2013 20:11:34 -0000

Reading some of this discussion leaves me puzzled because I can't tell
which things that some people are saying are intended to be about
"dotless" use of domains, or are intended to be about the expansion of
top level domains in general.

The IAB's statement does not seem to be about whether or not new TLDs
should be issued, or what good or bad effects that will have; the IAB
statement rather seems to assume as a given that new TLDs will come.
Yet a significant portion of the debate on this thread seems to be
about that.

In theory, any of the "classic" TLDs could've been used in a "dotless"
fashion, but they haven't been.  What the IAB statement is about is to
urge that none of the new TLDs be used "dotlessly" either.  That's a
separate matter from whether they should come into being in the first place.

What this brings to mind is that we used to have implicit DNS domain
search in the early days of DNS.  When edu.com accidentally hijacked
a huge chunk of the Internet, most of the net very quickly got rid of
implicit search, and we got the explicit DNS search feature that many
people are discussing now.

If some new TLD gets used in a dotless fashion in a way that truly
does cause major trouble, I expect we'll see sites all over the net
quickly deploying DNS resolvers that discard A, AAAA, or MX records
at the top level, to protect their users.
  -- Cos

From tom@dropfuse.com  Sat Jul 13 13:25:56 2013
Return-Path: <tom@dropfuse.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 217D621F9E73 for <ietf@ietfa.amsl.com>; Sat, 13 Jul 2013 13:25:56 -0700 (PDT)
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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 69o5-aV1VvhE for <ietf@ietfa.amsl.com>; Sat, 13 Jul 2013 13:25:51 -0700 (PDT)
Received: from mail01.dropfuse.com (mail.ams.dropfuse.com [198.211.127.66]) by ietfa.amsl.com (Postfix) with ESMTP id 5D81321F9DA8 for <ietf@ietf.org>; Sat, 13 Jul 2013 13:25:51 -0700 (PDT)
Received: by mail01.dropfuse.com (Postfix, from userid 1003) id B02226FB2D; Sat, 13 Jul 2013 20:25:49 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dropfuse.com; s=mail; t=1373747149; bh=8l2fKdgW/mi1TRKRPGeAzPWdz/dAXsusrQFQ92zsYdg=; h=Date:From:To:Subject:References:In-Reply-To; b=twX+4C1IX0ij7npfuQ9llcPoMiWHyDXr2Q5+mtj2s7RUGR+m/3XNmdx/4By6rqrD9 qTS5GVJpEKuFcKP6pMCj+FJP3j53/z6Rh8zd3h1VPDExd/lyw+zP6EKFmTf6/ZL9HW 9p8+PVZl1/w/p7of1ftYocy9g03JZ/3Q7faRYrSs=
Received: from [192.168.1.126] (cpc5-bagu10-2-0-cust364.1-3.cable.virginmedia.com [86.10.189.109]) by mail01.dropfuse.com (Postfix) with ESMTPSA id DA5D76FB27 for <ietf@ietf.org>; Sat, 13 Jul 2013 20:25:48 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dropfuse.com; s=mail; t=1373747148; bh=8l2fKdgW/mi1TRKRPGeAzPWdz/dAXsusrQFQ92zsYdg=; h=Date:From:To:Subject:References:In-Reply-To; b=SZnmjEFehw2Si9CWg33yIrbNHpRivfIvFPz9yYgHvGbEz9+DsF92IbrFb5/VaGIvQ 4NjKWTquToC0f8Eud+it+dVXx3yHl2CMhSGQWxE4nAFayrnv13ic8SVo36tAtC18Bt ShXEuvvnFBu0fddW8GD8Fjnf0pEH4vEt+4CDFYIY=
Message-ID: <51E1B7C6.3010403@dropfuse.com>
Date: Sat, 13 Jul 2013 21:25:42 +0100
From: Tom McLoughlin <tom@dropfuse.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IAB Statement on Dotless Domains
References: <1984CBB8-6862-4DBB-AFAE-F8461E694083@vigilsec.com> <51DDD49E.5090406@dcrocker.net> <CAMm+Lwj8_zmrp=SmUbb=a_4iEGA2zFaF2EDywaAq=5NkKbvp+w@mail.gmail.com> <20130713201122.GO29401@mip.aaaaa.org>
In-Reply-To: <20130713201122.GO29401@mip.aaaaa.org>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Jul 2013 20:25:56 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
 
It could just be me but something about http://example doesn't feel
right, I'd rather have http://example.com over http://example

Regards,
Tom McLoughlin

On 13/07/2013 21:11, Ofer Inbar wrote:
> Reading some of this discussion leaves me puzzled because I can't tell
> which things that some people are saying are intended to be about
> "dotless" use of domains, or are intended to be about the expansion of
> top level domains in general.
>
> The IAB's statement does not seem to be about whether or not new TLDs
> should be issued, or what good or bad effects that will have; the IAB
> statement rather seems to assume as a given that new TLDs will come.
> Yet a significant portion of the debate on this thread seems to be
> about that.
>
> In theory, any of the "classic" TLDs could've been used in a "dotless"
> fashion, but they haven't been.  What the IAB statement is about is to
> urge that none of the new TLDs be used "dotlessly" either.  That's a
> separate matter from whether they should come into being in the first
place.
>
> What this brings to mind is that we used to have implicit DNS domain
> search in the early days of DNS.  When edu.com accidentally hijacked
> a huge chunk of the Internet, most of the net very quickly got rid of
> implicit search, and we got the explicit DNS search feature that many
> people are discussing now.
>
> If some new TLD gets used in a dotless fashion in a way that truly
> does cause major trouble, I expect we'll see sites all over the net
> quickly deploying DNS resolvers that discard A, AAAA, or MX records
> at the top level, to protect their users.
>   -- Cos

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
 
iF4EAREIAAYFAlHht8UACgkQAfPjg38gQ2AhugEAjQ3klca8lGVhrMPXHrfPG070
6lh5a920j5hXy7dWpzUBAIr7Yi2oDsKoicUYj0XZBADNuflcoXJMPGULGOZD0KM4
=isSY
-----END PGP SIGNATURE-----


From hsantos@isdg.net  Sun Jul 14 06:37:54 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 156F311E8124 for <ietf@ietfa.amsl.com>; Sun, 14 Jul 2013 06:37:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.451
X-Spam-Level: 
X-Spam-Status: No, score=-102.451 tagged_above=-999 required=5 tests=[AWL=0.148, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EQSFBUCP859j for <ietf@ietfa.amsl.com>; Sun, 14 Jul 2013 06:37:49 -0700 (PDT)
Received: from groups.winserver.com (dkim.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 1412521F9D8E for <ietf@ietf.org>; Sun, 14 Jul 2013 06:37:48 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=947; t=1373809062; h=Received:Received: Message-ID:Date:From:To:Subject:Organization:List-ID; bh=jIPjp5o EKRuZj54/Rry2OBanbUw=; b=I4jJW7Oek5rfQLax/h0cqn8vnRvybMB0A+e6lRd zfn4R0OmwgdCWQJqW5VjEkt5GVcHFZLOsWEqEKPShvmlvg5YvZXjD9HUeY7Z4BPU wzsiQmyLWnl8jbXU6DjjZvzXrBJtasXzZHDvl/1tA40JOMEjC1XqzK61XZY4dlj4 xtZY=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sun, 14 Jul 2013 09:37:42 -0400
Received: from [208.247.131.8] ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 271616041.13163.3484; Sun, 14 Jul 2013 09:37:41 -0400
Message-ID: <51E2A8EE.5010200@isdg.net>
Date: Sun, 14 Jul 2013 09:34:38 -0400
From: Hector Santos <hsantos@isdg.net>
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Yoav Nir <ynir@checkpoint.com>
Subject: Dotless Domain conflict with user searching and branding  [was: IAB Statement on Dotless Domain]
References: <20130713152747.8F79D18C0D0@mercury.lcs.mit.edu> <51E18737.4080903@isdg.net> <3725D4B2-65DA-45FA-AAEE-309F45CD6F18@checkpoint.com>
In-Reply-To: <3725D4B2-65DA-45FA-AAEE-309F45CD6F18@checkpoint.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Jul 2013 13:37:54 -0000

On 7/13/2013 2:20 PM, Yoav Nir wrote:
>
>
> So finding your site is not that difficult for first-timers. But regardless, the people who type in addresses or DNS names in full are rare and far between.
>

Agreed. Just to see again, I tried it on my wife's new computer with 
Chrome and it showed:

     Windows Server on aws.amazon.com
     Windows Server 2012 at microsoft.com
     www.winserver.com

Am I off-base to suggest that the IETF can address this "dotless" domain 
searching confusion with a INFO or BCP suggesting software *should* 
consider DNS solution first over non-DNS solutions?

It raises a fairness question as the method of communications becoming 
closer to obsolete from the user's standpoint, i.e. no protocol is 
necessary to type (hence via the browser, HTTP is the default protocol).

I am now wondering what if we tried to add a dotless winserver zone into 
our DNS.  Will the software even allow it?

--
HLS


From ynir@checkpoint.com  Sun Jul 14 06:53:13 2013
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8203911E8125 for <ietf@ietfa.amsl.com>; Sun, 14 Jul 2013 06:53:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ba8oz4GITu6W for <ietf@ietfa.amsl.com>; Sun, 14 Jul 2013 06:53:08 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 1F09321F9017 for <ietf@ietf.org>; Sun, 14 Jul 2013 06:53:07 -0700 (PDT)
Received: from IL-EX10.ad.checkpoint.com ([194.29.34.147]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r6EDr2Pr001507; Sun, 14 Jul 2013 16:53:05 +0300
X-CheckPoint: {51E2AD3E-0-1B221DC2-1FFFF}
Received: from DAG-EX10.ad.checkpoint.com ([169.254.3.48]) by IL-EX10.ad.checkpoint.com ([169.254.2.91]) with mapi id 14.02.0342.003; Sun, 14 Jul 2013 16:53:02 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Hector Santos <hsantos@isdg.net>
Subject: Re: Dotless Domain conflict with user searching and branding  [was: IAB Statement on Dotless Domain]
Thread-Topic: Dotless Domain conflict with user searching and branding [was: IAB Statement on Dotless Domain]
Thread-Index: AQHOgJdcJ6w979BTH0uBKb0REqdMkZlj/3IA
Date: Sun, 14 Jul 2013 13:53:01 +0000
Message-ID: <A0984871-D92D-4110-9001-16B363B65AC0@checkpoint.com>
References: <20130713152747.8F79D18C0D0@mercury.lcs.mit.edu> <51E18737.4080903@isdg.net> <3725D4B2-65DA-45FA-AAEE-309F45CD6F18@checkpoint.com> <51E2A8EE.5010200@isdg.net>
In-Reply-To: <51E2A8EE.5010200@isdg.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [91.90.139.159]
x-kse-antivirus-interceptor-info: protection disabled
x-cpdlp: 11a18f444495748d31d57cf52d714c26ab5193000b
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <B6B5586A290F5B4CABF6DA8B9F81A4A6@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Jul 2013 13:53:13 -0000

On Jul 14, 2013, at 4:34 PM, Hector Santos <hsantos@isdg.net> wrote:

>=20
>=20
> On 7/13/2013 2:20 PM, Yoav Nir wrote:
>>=20
>>=20
>> So finding your site is not that difficult for first-timers. But regardl=
ess, the people who type in addresses or DNS names in full are rare and far=
 between.
>>=20
>=20
> Agreed. Just to see again, I tried it on my wife's new computer with Chro=
me and it showed:
>=20
>    Windows Server on aws.amazon.com
>    Windows Server 2012 at microsoft.com
>    www.winserver.com
>=20
> Am I off-base to suggest that the IETF can address this "dotless" domain =
searching confusion with a INFO or BCP suggesting software *should* conside=
r DNS solution first over non-DNS solutions?

SM is way ahead of you :-) :
http://tools.ietf.org/html/draft-moonesamy-dotless-domains-00

>=20
> It raises a fairness question as the method of communications becoming cl=
oser to obsolete from the user's standpoint, i.e. no protocol is necessary =
to type (hence via the browser, HTTP is the default protocol).
>=20
> I am now wondering what if we tried to add a dotless winserver zone into =
our DNS.  Will the software even allow it?
>=20
> --
> HLS


From hsantos@isdg.net  Sun Jul 14 08:07:11 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFC7421E8089 for <ietf@ietfa.amsl.com>; Sun, 14 Jul 2013 08:07:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.466
X-Spam-Level: 
X-Spam-Status: No, score=-102.466 tagged_above=-999 required=5 tests=[AWL=0.133, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xTVhv1Ya4xZq for <ietf@ietfa.amsl.com>; Sun, 14 Jul 2013 08:07:06 -0700 (PDT)
Received: from catinthebox.net (ftp.catinthebox.net [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 6237921F9F7A for <ietf@ietf.org>; Sun, 14 Jul 2013 08:07:06 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1705; t=1373814414; h=Received:Received: Message-ID:Date:From:To:Subject:Organization:List-ID; bh=DJH60OL C9dM3wrC30suZATyMJlM=; b=YQNOlUjsiEA7SXyZ5KXPxk/sk0GBjPuEX4gh8Cp Fpt4tiwMq4RCdGYhyu/1Y0tE6K5xmCdBPPKyftz83FfKShz0arkV10jZlD1oFWXt NCQCgkeQC/YyB7oQLVtPtlPH7/7qZiFVJ1BwICziHNyrec3V4ynN1oMtdDmIUiEw Anls=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sun, 14 Jul 2013 11:06:54 -0400
Received: from [208.247.131.8] ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 276967234.13163.2124; Sun, 14 Jul 2013 11:06:53 -0400
Message-ID: <51E2BDD6.6090402@isdg.net>
Date: Sun, 14 Jul 2013 11:03:50 -0400
From: Hector Santos <hsantos@isdg.net>
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: Dotless Domain conflict with user searching and branding  [was: IAB Statement on Dotless Domain]
References: <20130713152747.8F79D18C0D0@mercury.lcs.mit.edu> <51E18737.4080903@isdg.net> <3725D4B2-65DA-45FA-AAEE-309F45CD6F18@checkpoint.com> <51E2A8EE.5010200@isdg.net> <A0984871-D92D-4110-9001-16B363B65AC0@checkpoint.com>
In-Reply-To: <A0984871-D92D-4110-9001-16B363B65AC0@checkpoint.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, S Moonesamy <sm+ietf@elandsys.com>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Jul 2013 15:07:11 -0000

On 7/14/2013 9:53 AM, Yoav Nir wrote:
>
> On Jul 14, 2013, at 4:34 PM, Hector Santos <hsantos@isdg.net> wrote:
>
>>
>>
>> On 7/13/2013 2:20 PM, Yoav Nir wrote:
>>>
>>>
>>> So finding your site is not that difficult for first-timers. But regardless, the people who type in addresses or DNS names in full are rare and far between.
>>>
>>
>> Agreed. Just to see again, I tried it on my wife's new computer with Chrome and it showed:
>>
>>     Windows Server on aws.amazon.com
>>     Windows Server 2012 at microsoft.com
>>     www.winserver.com
>>
>> Am I off-base to suggest that the IETF can address this "dotless" domain searching confusion with a INFO or BCP suggesting software *should* consider DNS solution first over non-DNS solutions?
>
> SM is way ahead of you :-) :
> http://tools.ietf.org/html/draft-moonesamy-dotless-domains-00

Good show SM.

I have a very popular 5-6 years old resource web page related to using 
jQuery-based Auto-Suggestion methods with source.  It uses a DOMAIN 
query for an example for the auto-suggestion.   You can see how easy it 
is to just use an NON-DNS database solution.   A DNS-solution would have 
a higher overhead with this full duplex concept.

http://beta.winserver.com/public/test/MultiSuggestTest.wct

Whats funny, is that as I type Winserver here, it also pulls the dotless 
domain.   This data source was a collection of "Bad domains" as rejected 
and collected by our SMTP server!  So at some point, a dotless winserver 
was used and rejected by our SMTP server.

This illustrates a good part of the issue, from how SMTP currently 
behaves and also from the user standpoint, the searching may pull the 
dotless domain first.

--
HLS









From dhc@dcrocker.net  Sun Jul 14 08:50:01 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F45121E808B for <ietf@ietfa.amsl.com>; Sun, 14 Jul 2013 08:50:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.595
X-Spam-Level: 
X-Spam-Status: No, score=-6.595 tagged_above=-999 required=5 tests=[AWL=0.004,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vuAGHq0uHrDh for <ietf@ietfa.amsl.com>; Sun, 14 Jul 2013 08:49:46 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 0D41611E8129 for <ietf@ietf.org>; Sun, 14 Jul 2013 08:49:46 -0700 (PDT)
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 r6EFnec9000903 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Sun, 14 Jul 2013 08:49:45 -0700
Message-ID: <51E2C876.6070501@dcrocker.net>
Date: Sun, 14 Jul 2013 08:49:10 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: IAB Statement on Dotless Domains
References: <1984CBB8-6862-4DBB-AFAE-F8461E694083@vigilsec.com> <51DDD49E.5090406@dcrocker.net> <CAMm+Lwj8_zmrp=SmUbb=a_4iEGA2zFaF2EDywaAq=5NkKbvp+w@mail.gmail.com> <20130713201122.GO29401@mip.aaaaa.org>
In-Reply-To: <20130713201122.GO29401@mip.aaaaa.org>
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, 14 Jul 2013 08:49:45 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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, 14 Jul 2013 15:50:01 -0000

> Reading some of this discussion leaves me puzzled because I can't tell
> which things that some people are saying are intended to be about
> "dotless" use of domains, or are intended to be about the expansion of
> top level domains in general.


Yes, they should be trreated as entirely separate topics.


My own comments are only about the technical and operational assessment 
of using dotless domains; I'm not commenting on any policy or political 
issues:

      Dotless domain names have roughly 30 years of standards, software 
and operations practice working against them.  They have always been 
treated either as an error or as a short-form to possible alternatives.

      Moving an extremely well-established installed base of perhaps 
hundreds of independent software implementations, thousands of different 
independent operational environments, and billions of users from 
treating dotless names one way to another should be seen as an 
impossible task.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From denghui02@gmail.com  Sun Jul 14 16:31:49 2013
Return-Path: <denghui02@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB49C21F9B85 for <ietf@ietfa.amsl.com>; Sun, 14 Jul 2013 16:31:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.525
X-Spam-Level: 
X-Spam-Status: No, score=-102.525 tagged_above=-999 required=5 tests=[AWL=0.074, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uBL2L2ZET8xu for <ietf@ietfa.amsl.com>; Sun, 14 Jul 2013 16:31:49 -0700 (PDT)
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 345D121F9B60 for <ietf@ietf.org>; Sun, 14 Jul 2013 16:31:49 -0700 (PDT)
Received: by mail-qa0-f45.google.com with SMTP id ci6so1289827qab.18 for <ietf@ietf.org>; Sun, 14 Jul 2013 16:31:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=awvFrceYtzuyS7ruJCYVpO/cPbI53cikkk9oYp09hiI=; b=ccHuFguDHkxcLayFazsjLix3nUXlsD41U3TIsDMqHl53aEMIsFix0BDzHbrZ3UIaN8 j3mjbJ8IbxSrhIQ7uX3g+7L43uUdlNYOSeBWdY21DPvbM+vWHIv3N9KkFMN7H16uID8r 2T8oPWuuW+0qQ+FhR76YEnP0dybCIc9D7TE4uaAwVVgltqYo3qGdgOhnN3Ak+1AsXO85 2eHbeT6j46waK7SxxVuVOZaF/4jFULoZv+R3NIeN2nC4A9WvLblC8tUHdKI+XR8GfGeZ D80y0Zo+CZ1j26n01qg+Jrtvmf9C62X2EP93WbjAixi+sccaLgPliQyrrHp1vHVhSRNC aNKg==
MIME-Version: 1.0
X-Received: by 10.49.15.130 with SMTP id x2mr7093573qec.47.1373844707616; Sun, 14 Jul 2013 16:31:47 -0700 (PDT)
Received: by 10.49.16.42 with HTTP; Sun, 14 Jul 2013 16:31:47 -0700 (PDT)
In-Reply-To: <51DEB93B.7020004@gmail.com>
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com> <6.2.5.6.2.20130710170747.10088580@resistor.net> <51DEB93B.7020004@gmail.com>
Date: Mon, 15 Jul 2013 07:31:47 +0800
Message-ID: <CANF0JMA4SezrN-7gvc_oSAocG7fX5uT_bCPqHucGovHk=VNCfA@mail.gmail.com>
Subject: Re: Regarding call Chinese names
From: Hui Deng <denghui02@gmail.com>
To: Arturo Servin <arturo.servin@gmail.com>
Content-Type: multipart/alternative; boundary=047d7bd7579ec64ffb04e1812553
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Jul 2013 23:31:50 -0000

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

Hi Arturo,

diffcult for us, english speaking people other than western,
Section 4 has been moved.

thanks for your comments,

-Hui


2013/7/11 Arturo Servin <arturo.servin@gmail.com>

>
>     Great document, I really liked.
>
>     Same as SM I would suggest change "western" for something else.
>
>     And I would also suggest to move section 4 before explaining the
> titles. I guess the reading would be much easier.
>
> Regards,
> as
>
> On 7/10/13 9:55 PM, S Moonesamy wrote:
> > Hi Deng Hui,
> > At 17:04 10-07-2013, Hui Deng wrote:
> >> We submitted two drafts to help people here to correctly call chinese
> >> people names:
> >>
> >> http://tools.ietf.org/html/draft-deng-call-chinese-names-00
> >>
> >>    http://tools.ietf.org/html/draft-zcao-chinese-pronounce-00
> >
> > I would like to thank you and your co-author on taking the initiative
> > to write the drafts.  I don't know whether I am western or not. :-)
> >
> > In Section 3 of draft-deng-call-chinese-names-00:
> >
> >   'Two generic titles that have similar meanings to "Mr." and
> >    "Ms./Mrs." are "Xian1sheng1" and "Nv3Shi4".'
> >
> >   "(1,2,3,4 in this section will be explained in next section)
> >
> > There are digits in two words in the above.  I suggest making the
> > comment about the numbers clearer by mentioning that the digits are
> > intentional and they are used to denote the tone.
> >
> > Regards,
> > S. Moonesamy
>
>

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

<div dir=3D"ltr"><div>Hi Arturo,</div><div>=A0</div><div>diffcult for us, e=
nglish speaking people other than western, </div><div>Section 4 has been mo=
ved.</div><div>=A0</div><div>thanks for your comments,</div><div>=A0</div><=
div>-Hui</div>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">2013/7/=
11 Arturo Servin <span dir=3D"ltr">&lt;<a href=3D"mailto:arturo.servin@gmai=
l.com" target=3D"_blank">arturo.servin@gmail.com</a>&gt;</span><br><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex">
<br>
=A0 =A0 Great document, I really liked.<br>
<br>
=A0 =A0 Same as SM I would suggest change &quot;western&quot; for something=
 else.<br>
<br>
=A0 =A0 And I would also suggest to move section 4 before explaining the<br=
>
titles. I guess the reading would be much easier.<br>
<br>
Regards,<br>
as<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
On 7/10/13 9:55 PM, S Moonesamy wrote:<br>
&gt; Hi Deng Hui,<br>
&gt; At 17:04 10-07-2013, Hui Deng wrote:<br>
&gt;&gt; We submitted two drafts to help people here to correctly call chin=
ese<br>
&gt;&gt; people names:<br>
&gt;&gt;<br>
&gt;&gt; <a href=3D"http://tools.ietf.org/html/draft-deng-call-chinese-name=
s-00" target=3D"_blank">http://tools.ietf.org/html/draft-deng-call-chinese-=
names-00</a><br>
&gt;&gt;<br>
&gt;&gt; =A0 =A0<a href=3D"http://tools.ietf.org/html/draft-zcao-chinese-pr=
onounce-00" target=3D"_blank">http://tools.ietf.org/html/draft-zcao-chinese=
-pronounce-00</a><br>
&gt;<br>
&gt; I would like to thank you and your co-author on taking the initiative<=
br>
&gt; to write the drafts. =A0I don&#39;t know whether I am western or not. =
:-)<br>
&gt;<br>
&gt; In Section 3 of draft-deng-call-chinese-names-00:<br>
&gt;<br>
&gt; =A0 &#39;Two generic titles that have similar meanings to &quot;Mr.&qu=
ot; and<br>
&gt; =A0 =A0&quot;Ms./Mrs.&quot; are &quot;Xian1sheng1&quot; and &quot;Nv3S=
hi4&quot;.&#39;<br>
&gt;<br>
&gt; =A0 &quot;(1,2,3,4 in this section will be explained in next section)<=
br>
&gt;<br>
&gt; There are digits in two words in the above. =A0I suggest making the<br=
>
&gt; comment about the numbers clearer by mentioning that the digits are<br=
>
&gt; intentional and they are used to denote the tone.<br>
&gt;<br>
&gt; Regards,<br>
&gt; S. Moonesamy<br>
<br>
</div></div></blockquote></div><br></div>

--047d7bd7579ec64ffb04e1812553--

From denghui02@gmail.com  Sun Jul 14 16:32:58 2013
Return-Path: <denghui02@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 276A821F9BA0 for <ietf@ietfa.amsl.com>; Sun, 14 Jul 2013 16:32:58 -0700 (PDT)
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=[AWL=0.063, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jmOrcanwC9hD for <ietf@ietfa.amsl.com>; Sun, 14 Jul 2013 16:32:57 -0700 (PDT)
Received: from mail-qe0-x22e.google.com (mail-qe0-x22e.google.com [IPv6:2607:f8b0:400d:c02::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 9237021F9B9D for <ietf@ietf.org>; Sun, 14 Jul 2013 16:32:57 -0700 (PDT)
Received: by mail-qe0-f46.google.com with SMTP id nd7so6062681qeb.5 for <ietf@ietf.org>; Sun, 14 Jul 2013 16:32:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=XY1NxD6PZNHuQ1Fas1tC7DPrOH5Jd0Z1SXRnqCXhQgE=; b=ntnRxbs1vLfeuNxG/5oigj7ehf1Fy0NAOYWkmsyo8K3SYLJhiG+3GD5GmAy/+qJ88u o5wmCkBfNodwd0S7ut1Ef1nGsZm7rm8iy+RD/dkzlGnA3dBdq1F3TOmedYh2qR0m99pF YmwYxwyWozLXD/wr73D0tmRZLJbaNBaJv2BMXBxeO0s02JDMTzbiTaBLbQm/Pj91RXot JIfAWi6djnNY1gJv68KzsytXQEpPIaHbRioxWp8pV9SzG/dclWEhER52gIL/xKedXKCh g18bR7vgK18HF7OEVHgxLW4DLuRRubEfw9EDcw8w1kfwkiRAjUC0VZyE3jNAZEnNZLXS zqsQ==
MIME-Version: 1.0
X-Received: by 10.49.86.168 with SMTP id q8mr46502068qez.32.1373844777026; Sun, 14 Jul 2013 16:32:57 -0700 (PDT)
Received: by 10.49.16.42 with HTTP; Sun, 14 Jul 2013 16:32:56 -0700 (PDT)
In-Reply-To: <51DEB9F2.9040405@viagenie.ca>
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com> <51DEB9F2.9040405@viagenie.ca>
Date: Mon, 15 Jul 2013 07:32:56 +0800
Message-ID: <CANF0JMAeYaP8uXQt1n7vOaUG_E8eLm+e23k2Za65atdx22Q45A@mail.gmail.com>
Subject: Re: Regarding call Chinese names
From: Hui Deng <denghui02@gmail.com>
To: Simon Perreault <simon.perreault@viagenie.ca>
Content-Type: multipart/alternative; boundary=047d7bdc96dae9a88004e18129cb
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Jul 2013 23:32:58 -0000

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

will mention this and candidate ways in the next version.
thanks,

-Hui


2013/7/11 Simon Perreault <simon.perreault@viagenie.ca>

> Le 2013-07-11 02:04, Hui Deng a =E9crit :
> > We submitted two drafts to help people here to correctly call chinese
> > people names:
> >
> > http://tools.ietf.org/html/draft-deng-call-chinese-names-00
> >    http://tools.ietf.org/html/draft-zcao-chinese-pronounce-00
>
> Very cool! Thanks for writing this!
>
> I have a question: I think I've seen Chinese names written in both
> orders. That is, sometimes "Hui Deng" will be written "Deng Hui". Am I
> right? Does this happen often? What is the most common order? Is there a
> way to guess what order a name is written in? Sometimes it's not easy
> for non-Sinophones to know which part is the given name and which part
> is the family name.
>
> Thanks,
> Simon
>

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

<div dir=3D"ltr"><div>will mention this and candidate ways in the next vers=
ion.</div><div>thanks,</div><div>=A0</div><div>-Hui</div></div><div class=
=3D"gmail_extra"><br><br><div class=3D"gmail_quote">2013/7/11 Simon Perreau=
lt <span dir=3D"ltr">&lt;<a href=3D"mailto:simon.perreault@viagenie.ca" tar=
get=3D"_blank">simon.perreault@viagenie.ca</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">Le 2013-07-11 02:04, Hui Deng a =E9crit :<br=
>
<div class=3D"im">&gt; We submitted two drafts to help people here to corre=
ctly call chinese<br>
&gt; people names:<br>
&gt;<br>
&gt; <a href=3D"http://tools.ietf.org/html/draft-deng-call-chinese-names-00=
" target=3D"_blank">http://tools.ietf.org/html/draft-deng-call-chinese-name=
s-00</a><br>
&gt; =A0 =A0<a href=3D"http://tools.ietf.org/html/draft-zcao-chinese-pronou=
nce-00" target=3D"_blank">http://tools.ietf.org/html/draft-zcao-chinese-pro=
nounce-00</a><br>
<br>
</div>Very cool! Thanks for writing this!<br>
<br>
I have a question: I think I&#39;ve seen Chinese names written in both<br>
orders. That is, sometimes &quot;Hui Deng&quot; will be written &quot;Deng =
Hui&quot;. Am I<br>
right? Does this happen often? What is the most common order? Is there a<br=
>
way to guess what order a name is written in? Sometimes it&#39;s not easy<b=
r>
for non-Sinophones to know which part is the given name and which part<br>
is the family name.<br>
<br>
Thanks,<br>
Simon<br>
</blockquote></div><br></div>

--047d7bdc96dae9a88004e18129cb--

From denghui02@gmail.com  Sun Jul 14 16:35:34 2013
Return-Path: <denghui02@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1312821F9B8D for <ietf@ietfa.amsl.com>; Sun, 14 Jul 2013 16:35:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.544
X-Spam-Level: 
X-Spam-Status: No, score=-102.544 tagged_above=-999 required=5 tests=[AWL=0.055, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HWuZ1JcdJZAW for <ietf@ietfa.amsl.com>; Sun, 14 Jul 2013 16:35:33 -0700 (PDT)
Received: from mail-qc0-x22f.google.com (mail-qc0-x22f.google.com [IPv6:2607:f8b0:400d:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 7899D21F9B89 for <ietf@ietf.org>; Sun, 14 Jul 2013 16:35:33 -0700 (PDT)
Received: by mail-qc0-f175.google.com with SMTP id k14so5932741qcv.34 for <ietf@ietf.org>; Sun, 14 Jul 2013 16:35:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=P2TssCSIj2XwhEWmDdJZGdgaHFyrvdMWA3ohMcHABYg=; b=bIxNJsxoT46TFuXuyPIRT8PaGdGTew4pD4guJvOS9E81Nm3V6m4yx5FjPiGDzIN4TO VnUttQszPdQqZzTzMAN5D0st3J4UFGm8FJmjtyD2zS8Ia3lmepDxXgNGYVtASF4DzYCs VQQ0u2ccCmp7YHnm8tJkcPbGuf3nI/yUzeCIgAsi9JdFtIXG27gNnhxweyuNJVGvb2hU EtsutIO72jGQA+h/0iasKSrfKnY9vmj4trX+CthbtIM4+bZisz4a9OZeXZEp7E6yBUQM UqV11P1M0UvMeN0/XjtHdwov7YFvl5YDb2+2Q1pFneg/ykidn+w0+kSsP6ri2eadorrO w7PQ==
MIME-Version: 1.0
X-Received: by 10.49.15.130 with SMTP id x2mr7103570qec.47.1373844932940; Sun, 14 Jul 2013 16:35:32 -0700 (PDT)
Received: by 10.49.16.42 with HTTP; Sun, 14 Jul 2013 16:35:32 -0700 (PDT)
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B63077520A892@mbx-01.win.nominum.com>
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com> <0B65E3C66FCF4F459F93A1A5767BB35A034AD02C@lhreml514-mbx> <alpine.DEB.2.00.1307111201190.8891@uplift.swm.pp.se> <CANF0JMAuRm2c+-L0SzD902vAt4gdsWqawVMt6=MLkkNkmza6RQ@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077520A892@mbx-01.win.nominum.com>
Date: Mon, 15 Jul 2013 07:35:32 +0800
Message-ID: <CANF0JMAEmGtd_cBT2XJ2DGccf70Qd0sgQ31TKM1A6cdo-MdQ2w@mail.gmail.com>
Subject: Re: Regarding call Chinese names
From: Hui Deng <denghui02@gmail.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Content-Type: multipart/alternative; boundary=047d7bd7579e3472b704e1813337
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Jul 2013 23:35:34 -0000

--047d7bd7579e3472b704e1813337
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

revised to "for english speaking people who care"
thanks

-Hui


2013/7/11 Ted Lemon <Ted.Lemon@nominum.com>

> On Jul 11, 2013, at 8:14 AM, Hui Deng <denghui02@gmail.com> wrote:
> > I personally feel that this is maybe one of not easier part for western
> people to do in today IETF.  and chinese's names sound maybe more diffcul=
t
> than other eastern languages.
>
> I think these documents are useful for IETFers who care, and possibly for
> others.   Pinyin transliteration is not safely pronounceable without help=
.
>   It's true that many European languages are hard for speakers of other
> languages to pronounce also, and I would not personally object to more
> helpful documents of this type for other languages.   I think that what
> would motivate this would be author interest=97that's what we usually let
> drive volunteer translations of IETF messages into other languages, for
> example.   E.g., there are numerous translations for the Tao; these are
> done on a volunteer basis, so if you don't see one for your language, and
> this bothers you, the onus is on you to solve it.
>
>
>

--047d7bd7579e3472b704e1813337
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>revised=A0to &quot;for english speaking people who ca=
re&quot;</div><div>thanks</div><div>=A0</div><div>-Hui</div></div><div clas=
s=3D"gmail_extra"><br><br><div class=3D"gmail_quote">2013/7/11 Ted Lemon <s=
pan dir=3D"ltr">&lt;<a href=3D"mailto:Ted.Lemon@nominum.com" target=3D"_bla=
nk">Ted.Lemon@nominum.com</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 class=3D"im">On Jul 11, 2013, at 8:14 A=
M, Hui Deng &lt;<a href=3D"mailto:denghui02@gmail.com">denghui02@gmail.com<=
/a>&gt; wrote:<br>

&gt; I personally feel that this is maybe one of not easier part for wester=
n people to do in today IETF. =A0and chinese&#39;s names sound maybe more d=
iffcult than other eastern languages.<br>
<br>
</div>I think these documents are useful for IETFers who care, and possibly=
 for others. =A0 Pinyin transliteration is not safely pronounceable without=
 help. =A0 It&#39;s true that many European languages are hard for speakers=
 of other languages to pronounce also, and I would not personally object to=
 more helpful documents of this type for other languages. =A0 I think that =
what would motivate this would be author interest=97that&#39;s what we usua=
lly let drive volunteer translations of IETF messages into other languages,=
 for example. =A0 E.g., there are numerous translations for the Tao; these =
are done on a volunteer basis, so if you don&#39;t see one for your languag=
e, and this bothers you, the onus is on you to solve it.<br>

<br>
<br>
</blockquote></div><br></div>

--047d7bd7579e3472b704e1813337--

From denghui02@gmail.com  Sun Jul 14 16:41:41 2013
Return-Path: <denghui02@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBBD121F9021 for <ietf@ietfa.amsl.com>; Sun, 14 Jul 2013 16:41:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.55
X-Spam-Level: 
X-Spam-Status: No, score=-102.55 tagged_above=-999 required=5 tests=[AWL=0.049, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IViXyzIwoSLB for <ietf@ietfa.amsl.com>; Sun, 14 Jul 2013 16:41:41 -0700 (PDT)
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 2B29721F841B for <ietf@ietf.org>; Sun, 14 Jul 2013 16:41:41 -0700 (PDT)
Received: by mail-qc0-f170.google.com with SMTP id s1so5969900qcw.29 for <ietf@ietf.org>; Sun, 14 Jul 2013 16:41:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Da/RirP3lqHbf1nAca8mC9tK6DVcAredzdaOaSP9MjE=; b=xEFISA59OUvNhtzro/wMp9xT03IOgaZu3Mq+3dEJ1RgBBLYF476Z37hZR1xmC+0/pH vmOMjqd6MWQwvxiQajDRbuwB8jrnB+qWUT0SHfMO3d3uF3Kz1Zlrcsl3TxsYs73x7/lx FDI1N1ep/oLu1ZwQYdAbRBimWiu/yOoEkY6sCfbsx3IrnuHWqrdUo4uTZooBGnJ3DfOs qbowXCYqGwCPu+/Pjg4UbYlQqK8v2dgZt6VJACNeIB6UQsjpruh70CD7E21ZHWJgI2Ka duSHVu+pEoKV/zUO4Syl+fCsJeFUbEoG11eoO+jSj1MY0V1ZI3xUUAubMeYrJn8hkstY 6QDg==
MIME-Version: 1.0
X-Received: by 10.224.21.6 with SMTP id h6mr34599791qab.14.1373845293541; Sun, 14 Jul 2013 16:41:33 -0700 (PDT)
Received: by 10.49.16.42 with HTTP; Sun, 14 Jul 2013 16:41:33 -0700 (PDT)
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B63077520AAD3@mbx-01.win.nominum.com>
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com> <51DEB9F2.9040405@viagenie.ca> <8D23D4052ABE7A4490E77B1A012B63077520AAD3@mbx-01.win.nominum.com>
Date: Mon, 15 Jul 2013 07:41:33 +0800
Message-ID: <CANF0JMDmVWgrrSf8_or=+hHNxKAFAymgRE-7D8mGo9VAeVawBA@mail.gmail.com>
Subject: Re: Regarding call Chinese names
From: Hui Deng <denghui02@gmail.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Content-Type: multipart/alternative; boundary=001a11c294cab2ace704e1814824
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Jul 2013 23:41:42 -0000

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

Right, it seems most email addresses are the correct order as far as my
email

denghui@chinamobile.com
denghui02@gmail.com
denghui02@hotmail.com

-Hui


2013/7/11 Ted Lemon <Ted.Lemon@nominum.com>

> On Jul 11, 2013, at 9:58 AM, Simon Perreault <simon.perreault@viagenie.ca>
> wrote:
> > Is there a
> > way to guess what order a name is written in? Sometimes it's not easy
> > for non-Sinophones to know which part is the given name and which part
> > is the family name.
>
> It's usually in the Chinese order in the email address.
>
>

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

<div dir=3D"ltr"><div>Right, it seems most email addresses are the=A0correc=
t order as far as my email</div><div>=A0</div><div><a href=3D"mailto:denghu=
i@chinamobile.com">denghui@chinamobile.com</a></div><div><a href=3D"mailto:=
denghui02@gmail.com">denghui02@gmail.com</a></div>
<div><a href=3D"mailto:denghui02@hotmail.com">denghui02@hotmail.com</a></di=
v><div>=A0</div><div>-Hui</div></div><div class=3D"gmail_extra"><br><br><di=
v class=3D"gmail_quote">2013/7/11 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><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 Jul 11, 2013, at 9:58 A=
M, Simon Perreault &lt;<a href=3D"mailto:simon.perreault@viagenie.ca">simon=
.perreault@viagenie.ca</a>&gt; wrote:<br>

&gt; Is there a<br>
&gt; way to guess what order a name is written in? Sometimes it&#39;s not e=
asy<br>
&gt; for non-Sinophones to know which part is the given name and which part=
<br>
&gt; is the family name.<br>
<br>
</div>It&#39;s usually in the Chinese order in the email address.<br>
<br>
</blockquote></div><br></div>

--001a11c294cab2ace704e1814824--

From denghui02@gmail.com  Sun Jul 14 16:56:20 2013
Return-Path: <denghui02@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F368021F8B35 for <ietf@ietfa.amsl.com>; Sun, 14 Jul 2013 16:56:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.555
X-Spam-Level: 
X-Spam-Status: No, score=-102.555 tagged_above=-999 required=5 tests=[AWL=0.044, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id htAPRC6eRuNH for <ietf@ietfa.amsl.com>; Sun, 14 Jul 2013 16:56:19 -0700 (PDT)
Received: from mail-qc0-x234.google.com (mail-qc0-x234.google.com [IPv6:2607:f8b0:400d:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id 1ECF921F8B51 for <ietf@ietf.org>; Sun, 14 Jul 2013 16:56:18 -0700 (PDT)
Received: by mail-qc0-f180.google.com with SMTP id a1so5908124qcx.25 for <ietf@ietf.org>; Sun, 14 Jul 2013 16:56:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ofzLT6+lx0d5/OtAr2StFno4fdDkJhaX/1mM4xS/tVo=; b=CI/OIe8pBnp8CC8ZiV84vpQBKITHgNjbRakrZ4ZZ7c8rXARu3QPC2Gm7v1Tg1Q2N3E UKVJ5KZ6HgFe6rjxP7otcmIbjfdOZ2QhCs598vmf8ms5hND0OLpDDpquV15r+kSSv6wd d+CwyD8AeuRu7NPwyeavmpxje9UJpkEeonsVcCRWltH1Alf20GGTorLyZr3ELgZt58mp TRzrRbRHbigLwBZANmeZh6ccLxrmhM6DAJLAorfrVKHjF68V51QWQ0u2pbVFwi5u5L4O cVlGbrCg6ld0fo/Cs1IcC4M6C3ph7eHEgruMnPdKEzjmn3z3cRMHeXMC4/EINFAFPsWx xfJA==
MIME-Version: 1.0
X-Received: by 10.49.82.234 with SMTP id l10mr46283100qey.17.1373846176312; Sun, 14 Jul 2013 16:56:16 -0700 (PDT)
Received: by 10.49.16.42 with HTTP; Sun, 14 Jul 2013 16:56:16 -0700 (PDT)
In-Reply-To: <51DECDE8.4080405@sprunk.org>
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com> <51DEB9F2.9040405@viagenie.ca> <51DECDE8.4080405@sprunk.org>
Date: Mon, 15 Jul 2013 07:56:16 +0800
Message-ID: <CANF0JMD2H-mHU+g3UxTu_LPeA_foEhM=4rfrE2-TN+fe-baihQ@mail.gmail.com>
Subject: Re: Regarding call Chinese names
From: Hui Deng <denghui02@gmail.com>
To: Stephen Sprunk <stephen@sprunk.org>
Content-Type: multipart/alternative; boundary=047d7b6743ea50b42904e1817d21
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Jul 2013 23:56:20 -0000

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

Hi Stephen,

all caps should be included, thanks for your pointint out.

for your 85% is one syllable, I guess that normally has two characters for
family name, then they will have two syllables?

thanks,

-Hui



2013/7/11 Stephen Sprunk <stephen@sprunk.org>

>  On 11-Jul-13 08:58, Simon Perreault wrote:
> > I have a question: I think I've seen Chinese names written in both
> > orders. That is, sometimes "Hui Deng" will be written "Deng Hui". Am
> > I right? Does this happen often? What is the most common order? Is
> > there a way to guess what order a name is written in? Sometimes it's
> > not easy for non-Sinophones to know which part is the given name and
> > which part is the family name.
>
> It is more common for the given name to come first when written in Pinyin,
> following the rule for other languages written in Latin characters, but
> exceptions are frequent enough that one can't rely on it.  A useful and
> growing convention is to write the family name in all caps.  Using the
> above example, if "Deng" were the family name, you might see:
>
> Hui DENG
> or
> DENG Hui
>
> whereas if "Hui" were the family name, you might see:
>
> Deng HUI
> or
> HUI Deng
>
> Also, most family names have a single syllable; all of the top 100 are,
> which accounts for 85% of the population of China.  So, if exactly one of
> the names has multiple syllables, it is reasonably safe to assume that is
> the given name, absent a more definitive clue.
>
> S
>
> --
> Stephen Sprunk         "God does not play dice."  --Albert Einstein
> CCIE #3723         "God is an inveterate gambler, and He throws the
> K5SSS        dice at every possible opportunity." --Stephen Hawking
>

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

<div dir=3D"ltr"><div>Hi Stephen,</div><div>=A0</div><div>all caps should b=
e included, thanks for your pointint out.</div><div>=A0</div><div>for your =
85% is one syllable, I guess that normally has two characters for family na=
me, then they will=A0have two syllables?</div>
<div>=A0</div><div>thanks,</div><div>=A0</div><div>-Hui</div><div>=A0</div>=
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">2013/7/=
11 Stephen Sprunk <span dir=3D"ltr">&lt;<a href=3D"mailto:stephen@sprunk.or=
g" target=3D"_blank">stephen@sprunk.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">
 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000"><div class=3D"im">
    On 11-Jul-13 08:58, Simon Perreault wrote:<br>
    <span style=3D"white-space:pre-wrap">&gt; I have a question: I think I&=
#39;ve
      seen Chinese names written in both <br>
      &gt; orders. That is, sometimes &quot;Hui Deng&quot; will be written =
&quot;Deng
      Hui&quot;. Am<br>
      &gt; I right? Does this happen often? What is the most common
      order? Is <br>
      &gt; there a way to guess what order a name is written in?
      Sometimes it&#39;s<br>
      &gt; not easy for non-Sinophones to know which part is the given
      name and<br>
      &gt; which part is the family name.</span><br>
    <br></div>
    It is more common for the given name to come first when written in
    Pinyin, following the rule for other languages written in Latin
    characters, but exceptions are frequent enough that one can&#39;t rely
    on it.=A0 A useful and growing convention is to write the family name
    in all caps.=A0 Using the above example, if &quot;Deng&quot; were the f=
amily
    name, you might see:<br>
    <br>
    Hui DENG<br>
    or<br>
    DENG Hui<br>
    <br>
    whereas if &quot;Hui&quot; were the family name, you might see:<br>
    <br>
    Deng HUI<br>
    or<br>
    HUI Deng<br>
    <br>
    Also, most family names have a single syllable; all of the top 100
    are, which accounts for 85% of the population of China.=A0 So, if
    exactly one of the names has multiple syllables, it is reasonably
    safe to assume that is the given name, absent a more definitive
    clue.<span class=3D"HOEnZb"><font color=3D"#888888"><br>
    <br>
    S<br>
    <br>
    -- <br>
    Stephen Sprunk=A0=A0=A0=A0=A0=A0=A0=A0 &quot;God does not play dice.&qu=
ot;=A0 --Albert Einstein<br>
    CCIE #3723=A0=A0=A0=A0=A0=A0=A0=A0 &quot;God is an inveterate gambler, =
and He throws the<br>
    K5SSS=A0=A0=A0=A0=A0=A0=A0 dice at every possible opportunity.&quot; --=
Stephen Hawking<br>
  </font></span></div>

</blockquote></div><br></div>

--047d7b6743ea50b42904e1817d21--

From denghui02@gmail.com  Sun Jul 14 17:18:21 2013
Return-Path: <denghui02@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDA7E21F9C08 for <ietf@ietfa.amsl.com>; Sun, 14 Jul 2013 17:18:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.117
X-Spam-Level: 
X-Spam-Status: No, score=-102.117 tagged_above=-999 required=5 tests=[AWL=-0.402, BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id edi8aDw6Ssqe for <ietf@ietfa.amsl.com>; Sun, 14 Jul 2013 17:18:21 -0700 (PDT)
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 4D49121F9BEF for <ietf@ietf.org>; Sun, 14 Jul 2013 17:18:21 -0700 (PDT)
Received: by mail-qa0-f47.google.com with SMTP id i13so1313784qae.13 for <ietf@ietf.org>; Sun, 14 Jul 2013 17:18:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=23BC2cBMk6fqwm26ldhM0xIOqtZ1wcaj8sVnj5XdT0g=; b=Mh2c1dEFK/hzJBWqlRo8fU4674Vo6iSCy0rKXwrZu2SCEnwTI0IHYYtSNw+0wi0RDG ZNPWD1rXRDv6H+lOmLt9a/zExyHYoNKWEeDwd6pEbDJt4mAQx8s4dqYB+NCr61WRPURM 06ov0YVmOgnOX5yQS2wxYZEL4WKM0L6IfKMfoWyj/hnGZLLdF7Zzx8ohi7LWp+4WZxXv R9xkisYDQpX0jxYUAiY6xABkIO97tbSRi1C9Zpa519KX0CLNZjQ8chgMeruv6iIi3Ync q87EM6yVS+FH5rGEwWaWaZBE61VOmCk9m7uWC8NqN2Iyq5cDekBQKWtCFkooJ6jdb4Bp 2a6g==
MIME-Version: 1.0
X-Received: by 10.224.68.6 with SMTP id t6mr50386098qai.76.1373847499724; Sun, 14 Jul 2013 17:18:19 -0700 (PDT)
Received: by 10.49.16.42 with HTTP; Sun, 14 Jul 2013 17:18:19 -0700 (PDT)
In-Reply-To: <51DED42B.8040202@sprunk.org>
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com> <51DED42B.8040202@sprunk.org>
Date: Mon, 15 Jul 2013 08:18:19 +0800
Message-ID: <CANF0JMD7VxikFgsz1K7Gts+1DMToZi9O-vYC-dZDY9_EJ55_kA@mail.gmail.com>
Subject: Re: Regarding call Chinese names
From: Hui Deng <denghui02@gmail.com>
To: Stephen Sprunk <stephen@sprunk.org>
Content-Type: multipart/alternative; boundary=001a11c2e68e325aff04e181cc5d
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Jul 2013 00:18:22 -0000

--001a11c2e68e325aff04e181cc5d
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: quoted-printable

I guess XML draft doesn't support "L=A8=A3ob=A8=A3n"
thanks for your remindness.

-Hui

2013/7/11 Stephen Sprunk <stephen@sprunk.org>

>  On 10-Jul-13 19:04, Hui Deng wrote:
>
> We submitted two drafts to help people here to correctly call chinese
> people names:
>
> http://tools.ietf.org/html/draft-deng-call-chinese-names-00
>
>    http://tools.ietf.org/html/draft-zcao-chinese-pronounce-00
>
>
> While "first name" and "last name" may be useful for many Western readers=
,
> they tend to produce confusing statements like "put his/her Last name
> first, and first name last."  I would prefer the order-neutral terms "giv=
en
> name" and "family name", which results in the more sensible "put his/her
> family name first and given name last."
>
> Also, the section on tones (which BTW belongs in the pronunciation
> document, not the names document) is a good example of how allowing UTF-8=
,
> rather than just US-ASCII, would be useful.  "Lao3ban3" (Wade-Giles)
> requires memorizing what the various tone numbers mean, whereas "L=A8=A3o=
b=A8=A3n"
> (Pinyin) provides a visual representation of the proper tone, which will =
be
> more accessible to most readers.
>
>
> S
>
> --
> Stephen Sprunk         "God does not play dice."  --Albert Einstein
> CCIE #3723         "God is an inveterate gambler, and He throws the
> K5SSS        dice at every possible opportunity." --Stephen Hawking
>
>

--001a11c2e68e325aff04e181cc5d
Content-Type: text/html; charset=GB2312
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra">I guess XML draft doesn&#39;t s=
upport &quot;L=A8=A3ob=A8=A3n&quot;</div><div class=3D"gmail_extra">thanks =
for your remindness.</div><div class=3D"gmail_extra">&nbsp;</div><div class=
=3D"gmail_extra">-Hui<br>
<br></div><div class=3D"gmail_quote">2013/7/11 Stephen Sprunk <span dir=3D"=
ltr">&lt;<a href=3D"mailto:stephen@sprunk.org" target=3D"_blank">stephen@sp=
runk.org</a>&gt;</span><br><blockquote style=3D"margin:0px 0px 0px 0.8ex;pa=
dding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;bor=
der-left-style:solid" class=3D"gmail_quote">

 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000"><div class=3D"im">
    On 10-Jul-13 19:04, Hui Deng wrote:
    <blockquote type=3D"cite">
      <div dir=3D"ltr">We submitted two drafts to help people here to
        correctly call chinese people names:
        <div><font color=3D"#000000" size=3D"3" face=3D"=CB=CE=CC=E5">
          </font>
          <p style=3D"margin:0cm 0cm 0pt"><span lang=3D"EN-US"><a href=3D"h=
ttp://tools.ietf.org/html/draft-deng-call-chinese-names-00" target=3D"_blan=
k"><span style=3D"background:white;color:rgb(17,85,204);font-family:&quot;A=
rial&quot;,&quot;sans-serif&quot;;font-size:10pt">http://tools.ietf.org/htm=
l/draft-deng-call-chinese-names-00</span></a></span><span style=3D"backgrou=
nd:white;color:rgb(34,34,34);font-family:&quot;Arial&quot;,&quot;sans-serif=
&quot;;font-size:10pt" lang=3D"EN-US">&nbsp;</span></p>

          <font color=3D"#000000" size=3D"3" face=3D"=CB=CE=CC=E5">
          </font>
          <p style=3D"margin:0cm 0cm 0pt"><span style=3D"background:white;c=
olor:rgb(34,34,34);font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;fon=
t-size:10pt" lang=3D"EN-US">&nbsp; &nbsp;</span><span lang=3D"EN-US"><a hre=
f=3D"http://tools.ietf.org/html/draft-zcao-chinese-pronounce-00" target=3D"=
_blank"><span style=3D"background:white;color:rgb(17,85,204);font-family:&q=
uot;Arial&quot;,&quot;sans-serif&quot;;font-size:10pt">http://tools.ietf.or=
g/html/draft-zcao-chinese-pronounce-00</span></a></span></p>

        </div>
      </div>
    </blockquote>
    <br></div>
    While &quot;first name&quot; and &quot;last name&quot; may be useful fo=
r many Western
    readers, they tend to produce confusing statements like &quot;put his/h=
er
    Last name first, and first name last.&quot;&nbsp; I would prefer the
    order-neutral terms &quot;given name&quot; and &quot;family name&quot;,=
 which results in
    the more sensible &quot;put his/her family name first and given name
    last.&quot;<br>
    <br>
    Also, the section on tones (which BTW belongs in the pronunciation
    document, not the names document) is a good example of how allowing
    UTF-8, rather than just US-ASCII, would be useful.&nbsp; &quot;Lao3ban3=
&quot;
    (Wade-Giles) requires memorizing what the various tone numbers mean,
    whereas &quot;L=A8=A3ob=A8=A3n&quot; (Pinyin) provides a visual represe=
ntation of the
    proper tone, which will be more accessible to most readers.<div class=
=3D"im"><br>
    <br>
    S<br>
    <pre cols=3D"72">--=20
Stephen Sprunk         &quot;God does not play dice.&quot;  --Albert Einste=
in
CCIE #3723         &quot;God is an inveterate gambler, and He throws the
K5SSS        dice at every possible opportunity.&quot; --Stephen Hawking
</pre>
  </div></div>

</blockquote></div><div class=3D"gmail_extra"><br></div></div>

--001a11c2e68e325aff04e181cc5d--

From denghui02@gmail.com  Sun Jul 14 17:26:09 2013
Return-Path: <denghui02@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0980921F8618 for <ietf@ietfa.amsl.com>; Sun, 14 Jul 2013 17:26:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.858
X-Spam-Level: 
X-Spam-Status: No, score=-100.858 tagged_above=-999 required=5 tests=[AWL=-1.593, BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, MIME_CHARSET_FARAWAY=2.45, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vya9OZB2r9NF for <ietf@ietfa.amsl.com>; Sun, 14 Jul 2013 17:26:08 -0700 (PDT)
Received: from mail-qc0-x234.google.com (mail-qc0-x234.google.com [IPv6:2607:f8b0:400d:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id 5D0FB21F8449 for <ietf@ietf.org>; Sun, 14 Jul 2013 17:26:08 -0700 (PDT)
Received: by mail-qc0-f180.google.com with SMTP id a1so5977342qcx.39 for <ietf@ietf.org>; Sun, 14 Jul 2013 17:26:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=A82uthYkqFYbE8PdgxGUO1tf9JXq2cFNayRHU2h5GM4=; b=Fp8O4EumJdwU+muybfz8V1p7Go54Z0/6Ftt0aCrYvMc3EwO2/jUsYd6ybBYKHjnuz3 gzx9/XAIek1WsVXWhThrL2ec5rhodPXQxfIZyFkXPnY8EcaNcIOusEvEdR54A3A2Z1X4 P6iyO1zMKmpv3xK36W1HSP7145toEn6q/nqKcCFx9J3HZ6H0DsVDXLTXqSrWRVAqki8T +CaxlFvs0tsX1FogjWrhMn/beTGC9VdpWLZgnXjhkj7ieUmw4bQB02koU7nP5Y9CRJdO uhM+ms8bXeOVd64l+0tVJpPl6qtg728F4R9/jIAHlqU07DyJHXzzrtZoVh0x/d/J7dEs TrmA==
MIME-Version: 1.0
X-Received: by 10.224.115.79 with SMTP id h15mr48722172qaq.41.1373847967856; Sun, 14 Jul 2013 17:26:07 -0700 (PDT)
Received: by 10.49.16.42 with HTTP; Sun, 14 Jul 2013 17:26:07 -0700 (PDT)
In-Reply-To: <CA+9kkMDZoX0Eq4TcbpP=+YMPmq-F3CAGB1dSogYJa6V2F-irbQ@mail.gmail.com>
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com> <CA+9kkMDZoX0Eq4TcbpP=+YMPmq-F3CAGB1dSogYJa6V2F-irbQ@mail.gmail.com>
Date: Mon, 15 Jul 2013 08:26:07 +0800
Message-ID: <CANF0JMCA+HQ7=xEXjDkgxLt2iqUj3Wdq_+2+KFsPg34a0m+nxQ@mail.gmail.com>
Subject: Re: Regarding call Chinese names
From: Hui Deng <denghui02@gmail.com>
To: Ted Hardie <ted.ietf@gmail.com>
Content-Type: multipart/alternative; boundary=047d7bdc78de19980f04e181e8e3
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Jul 2013 00:26:09 -0000

--047d7bdc78de19980f04e181e8e3
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: quoted-printable

Hi Ted,

I did explain them in the 1st paragraph about minorities (not mentioned
that they could have two kids in mainland)
anyway, I will revise the title by adding "Chinese "Han" people", hope that
will be ok

-Hui


2013/7/11 Ted Hardie <ted.ietf@gmail.com>

> Howdy,
>
> Thanks for your efforts.  I would suggest, however, that you re-title you=
r
> drafts so that "Chinese" is restricted to the populations which use pinyi=
n
> and have standardized on what English speakers call Mandarin (=87=F8=D5Z
> or =C6=D5=CD=A8=D4=92, depending on your background).  Those who use  rom=
anizations based
> on other dialects, in line with their familial pronunciation, would
> otherwise be treated as not "Chinese".
>
> regards,
>
> Ted Hardie
>
>
> On Wed, Jul 10, 2013 at 5:04 PM, Hui Deng <denghui02@gmail.com> wrote:
>
>> Hello all
>>
>> We submitted two drafts to help people here to correctly call chinese
>> people names:
>>
>> http://tools.ietf.org/html/draft-deng-call-chinese-names-00
>>
>>    http://tools.ietf.org/html/draft-zcao-chinese-pronounce-00
>>
>>
>>
>> Feel free to let us know if you have any other issues?
>>
>> Best regards,
>>
>>
>>
>> -Hui Deng
>>
>
>

--047d7bdc78de19980f04e181e8e3
Content-Type: text/html; charset=GB2312
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi Ted,</div><div>&nbsp;</div><div>I did explain them=
 in the 1st paragraph about minorities (not mentioned that&nbsp;they could =
have two kids in mainland)</div><div>anyway, I will revise the title by add=
ing &quot;Chinese &quot;Han&quot; people&quot;, hope that will be ok</div>
<div>&nbsp;</div><div>-Hui</div></div><div class=3D"gmail_extra"><br><br><d=
iv class=3D"gmail_quote">2013/7/11 Ted Hardie <span dir=3D"ltr">&lt;<a href=
=3D"mailto:ted.ietf@gmail.com" target=3D"_blank">ted.ietf@gmail.com</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">Howdy,<br><br>Thanks for your efforts.&nbsp;=
 I would suggest, however, that you re-title your drafts so that &quot;Chin=
ese&quot; is restricted to the populations which use pinyin and have standa=
rdized on what English speakers call Mandarin (=87=F8=D5Z<br>

or =C6=D5=CD=A8=D4=92, depending on your background).&nbsp; Those who use&n=
bsp; romanizations based on other dialects, in line with their familial pro=
nunciation, would otherwise be treated as not &quot;Chinese&quot;.&nbsp; <b=
r><br>regards,<br><br>Ted Hardie<br>

<br><br><div class=3D"gmail_quote"><div class=3D"im">On Wed, Jul 10, 2013 a=
t 5:04 PM, Hui Deng <span dir=3D"ltr">&lt;<a href=3D"mailto:denghui02@gmail=
.com" target=3D"_blank">denghui02@gmail.com</a>&gt;</span> wrote:<br></div>=
<blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-=
color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class=
=3D"gmail_quote">

<div dir=3D"ltr"><div>Hello all</div><div>&nbsp;</div><div class=3D"im"><di=
v>We submitted two drafts to help people here to correctly call chinese peo=
ple names:</div></div><div><font color=3D"#000000" size=3D"3" face=3D"=CB=
=CE=CC=E5">

</font><p style=3D"margin:0cm 0cm 0pt"><span lang=3D"EN-US"><a href=3D"http=
://tools.ietf.org/html/draft-deng-call-chinese-names-00" target=3D"_blank">=
<span style=3D"background:white;color:rgb(17,85,204);font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;;font-size:10pt">http://tools.ietf.org/html/d=
raft-deng-call-chinese-names-00</span></a></span><span style=3D"background:=
white;color:rgb(34,34,34);font-family:&quot;Arial&quot;,&quot;sans-serif&qu=
ot;;font-size:10pt" lang=3D"EN-US">&nbsp;</span></p>


<font color=3D"#000000" size=3D"3" face=3D"=CB=CE=CC=E5">

</font><p style=3D"margin:0cm 0cm 0pt"><span style=3D"background:white;colo=
r:rgb(34,34,34);font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;font-s=
ize:10pt" lang=3D"EN-US">&nbsp; &nbsp;</span><span lang=3D"EN-US"><a href=
=3D"http://tools.ietf.org/html/draft-zcao-chinese-pronounce-00" target=3D"_=
blank"><span style=3D"background:white;color:rgb(17,85,204);font-family:&qu=
ot;Arial&quot;,&quot;sans-serif&quot;;font-size:10pt">http://tools.ietf.org=
/html/draft-zcao-chinese-pronounce-00</span></a></span></p>


<p style=3D"margin:0cm 0cm 0pt"><span lang=3D"EN-US"></span>&nbsp;</p><p st=
yle=3D"margin:0cm 0cm 0pt"><span lang=3D"EN-US">Feel free to let us know if=
 you have any other issues?</span></p><p style=3D"margin:0cm 0cm 0pt"><span=
 lang=3D"EN-US">Best regards,</span></p>

<span><font color=3D"#888888">
<p style=3D"margin:0cm 0cm 0pt"><span lang=3D"EN-US"></span>&nbsp;</p><p st=
yle=3D"margin:0cm 0cm 0pt"><span lang=3D"EN-US">-Hui Deng</span></p><font c=
olor=3D"#000000" size=3D"3" face=3D"=CB=CE=CC=E5">

</font></font></span></div></div>
</blockquote></div><br>
</blockquote></div><br></div>

--047d7bdc78de19980f04e181e8e3--

From denghui02@gmail.com  Sun Jul 14 17:35:39 2013
Return-Path: <denghui02@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56A6221F9DB2 for <ietf@ietfa.amsl.com>; Sun, 14 Jul 2013 17:35:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.403
X-Spam-Level: 
X-Spam-Status: No, score=-102.403 tagged_above=-999 required=5 tests=[AWL=0.196, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MQbg3yDzH5aq for <ietf@ietfa.amsl.com>; Sun, 14 Jul 2013 17:35:38 -0700 (PDT)
Received: from mail-qe0-x234.google.com (mail-qe0-x234.google.com [IPv6:2607:f8b0:400d:c02::234]) by ietfa.amsl.com (Postfix) with ESMTP id 1658621F9DB1 for <ietf@ietf.org>; Sun, 14 Jul 2013 17:35:38 -0700 (PDT)
Received: by mail-qe0-f52.google.com with SMTP id i11so6185958qej.11 for <ietf@ietf.org>; Sun, 14 Jul 2013 17:35:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=WD9JYJbUdRdh7Fdco4Qw795qMJXxN3XoSgCkNvXuzBk=; b=SZ7gRbeBbzEibNGp3vjc0RSK1AsVV0C7SdJ38Y3SErgWubFUanhjBIwbNFPt+JFRKA c4Ek7fSwAAu28MdSAWWMiBnffF4e9CqOGbXAU5/8NiaCBRF58/bEyO6XXGThOtZz+G1k wO6GL3kn1D0duNyWre3u/b1Y3+zhSz2G5a9B+zR2JLUJdlypofRTBqNBiBI4rOdW6p17 GyIF1Npl8UGqCjHXiGIAbW8AEjqWWHBn2rKt38uELnS+zTWPZaFlAuSyOeNY/tqkp+40 5sCSYhvAl40GAuehQ4bUNngsFLtU8yxZd3PgCAbAex0caBc78HBOn1DgdAoZKR5LcrLv tHDw==
MIME-Version: 1.0
X-Received: by 10.224.172.198 with SMTP id m6mr49628024qaz.44.1373848537558; Sun, 14 Jul 2013 17:35:37 -0700 (PDT)
Received: by 10.49.16.42 with HTTP; Sun, 14 Jul 2013 17:35:37 -0700 (PDT)
In-Reply-To: <2671C6CDFBB59E47B64C10B3E0BD5923043722F56B@PRVPEXVS15.corp.twcable.com>
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com> <0B65E3C66FCF4F459F93A1A5767BB35A034AD02C@lhreml514-mbx> <alpine.DEB.2.00.1307111201190.8891@uplift.swm.pp.se> <CANF0JMAuRm2c+-L0SzD902vAt4gdsWqawVMt6=MLkkNkmza6RQ@mail.gmail.com> <51DEE55A.4050402@gmail.com> <2671C6CDFBB59E47B64C10B3E0BD5923043722F56B@PRVPEXVS15.corp.twcable.com>
Date: Mon, 15 Jul 2013 08:35:37 +0800
Message-ID: <CANF0JMBbEhW25+CEZYgWCZ7PB=8gMJy2VzvkYyJ0V-SBTe39CQ@mail.gmail.com>
Subject: Re: Regarding call Chinese names
From: Hui Deng <denghui02@gmail.com>
To: "George, Wes" <wesley.george@twcable.com>
Content-Type: multipart/alternative; boundary=047d7b5d8c7f0e8d6e04e1820aa0
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Jul 2013 00:35:39 -0000

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

I guess that George is your given name. Wes is your family name. Hope I am
not wrong.:)

-Hui


2013/7/11 George, Wes <wesley.george@twcable.com>

> > From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> > Melinda Shore
>
> > I agree
> > that this is probably not appropriate for publication as an RFC
> > but it would certainly be useful to find someplace for it in the
> > wiki.  The chairs wiki might be an option but I think it's of
> > broader interest and use.
> >
> > Melinda
>
> [WEG] I think writing language documentation isn't really a good use of
> IETF resources, even at an individual level, because neither the problem
> nor the knowledge necessary to address it is specific to the IETF, nor is
> the problem limited to Mandarin participants. As others have noted, this is
> just one of many languages represented by IETFers that we'd have to treat
> similarly.
> Further, an I-D is not a particularly useful format in which to present
> the info. Raw text in the form of "$phoneme as in $English_word" may not
> always be helpful, especially to nonnative English speakers who now have to
> work through two layers of pronunciation.  Being able to click on a button
> to hear sample pronunciations, especially in the case of words where tones
> matter, is very helpful.
>
> So if pronunciation guides end up in the Wiki or the Tao or some other yet
> to be written Diversity and Cultural guide hosted within IETF, I think it's
> more useful to simply reference things already extant instead of generating
> our own. Those representing the language in question could certainly help
> us to source and vet the information, but that's much quicker and more
> efficient than writing it themselves.
> Protocol reuse, hurray! :-)
> e.g.
>
> http://mandarin.about.com/od/pronunciation/a/How-To-Pronounce-Mandarin-Chinese.htm
> http://en.wikibooks.org/wiki/Japanese/Pronunciation
> http://en.wikipedia.org/wiki/Swedish_phonology
>
> To be clear, I'm not saying that this doesn't expose a real problem, and
> the draft certainly drew attention to it, but I also don't think that more
> documentation will solve it, especially since the information is already
> readily available in more accessible formats. I think what you'll find is
> that there are two types of folks (in IETF and generally) - those who see
> an attempt at proper pronunciation and cultural awareness as important and
> worth making extra effort to learn proactively, and those who believe that
> if it's an issue, the person on the receiving end will correct them when
> they get it wrong (and hopefully not repeat the mistake).
> Not making a value judgment on either, merely an observation.
>
> Thanks
> Wes George
>
> PS: guess which one is my given name and which my surname? Even native
> English speakers aren't immune from name confusion. :-)
>
>
> Anything below this line has been added by my company's mail server, I
> have no control over it.
> -----------------
>
> This E-mail and any of its attachments may contain Time Warner Cable
> proprietary information, which is privileged, confidential, or subject to
> copyright belonging to Time Warner Cable. This E-mail is intended solely
> for the use of the individual or entity to which it is addressed. If you
> are not the intended recipient of this E-mail, you are hereby notified that
> any dissemination, distribution, copying, or action taken in relation to
> the contents of and attachments to this E-mail is strictly prohibited and
> may be unlawful. If you have received this E-mail in error, please notify
> the sender immediately and permanently delete the original and any copy of
> this E-mail and any printout.
>

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

<div dir=3D"ltr"><div>I guess that George is your given name. Wes is your f=
amily name. Hope I am not wrong.:)</div><div>=A0</div><div>-Hui</div></div>=
<div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">2013/7/11 Geo=
rge, Wes <span dir=3D"ltr">&lt;<a href=3D"mailto:wesley.george@twcable.com"=
 target=3D"_blank">wesley.george@twcable.com</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 class=3D"im">&gt; From: <a href=3D"mail=
to:ietf-bounces@ietf.org">ietf-bounces@ietf.org</a> [mailto:<a href=3D"mail=
to:ietf-bounces@ietf.org">ietf-bounces@ietf.org</a>] On Behalf Of<br>

</div>&gt; Melinda Shore<br>
<div class=3D"im"><br>
&gt; I agree<br>
&gt; that this is probably not appropriate for publication as an RFC<br>
&gt; but it would certainly be useful to find someplace for it in the<br>
&gt; wiki. =A0The chairs wiki might be an option but I think it&#39;s of<br=
>
&gt; broader interest and use.<br>
&gt;<br>
&gt; Melinda<br>
<br>
</div>[WEG] I think writing language documentation isn&#39;t really a good =
use of IETF resources, even at an individual level, because neither the pro=
blem nor the knowledge necessary to address it is specific to the IETF, nor=
 is the problem limited to Mandarin participants. As others have noted, thi=
s is just one of many languages represented by IETFers that we&#39;d have t=
o treat similarly.<br>

Further, an I-D is not a particularly useful format in which to present the=
 info. Raw text in the form of &quot;$phoneme as in $English_word&quot; may=
 not always be helpful, especially to nonnative English speakers who now ha=
ve to work through two layers of pronunciation. =A0Being able to click on a=
 button to hear sample pronunciations, especially in the case of words wher=
e tones matter, is very helpful.<br>

<br>
So if pronunciation guides end up in the Wiki or the Tao or some other yet =
to be written Diversity and Cultural guide hosted within IETF, I think it&#=
39;s more useful to simply reference things already extant instead of gener=
ating our own. Those representing the language in question could certainly =
help us to source and vet the information, but that&#39;s much quicker and =
more efficient than writing it themselves.<br>

Protocol reuse, hurray! :-)<br>
e.g.<br>
<a href=3D"http://mandarin.about.com/od/pronunciation/a/How-To-Pronounce-Ma=
ndarin-Chinese.htm" target=3D"_blank">http://mandarin.about.com/od/pronunci=
ation/a/How-To-Pronounce-Mandarin-Chinese.htm</a><br>
<a href=3D"http://en.wikibooks.org/wiki/Japanese/Pronunciation" target=3D"_=
blank">http://en.wikibooks.org/wiki/Japanese/Pronunciation</a><br>
<a href=3D"http://en.wikipedia.org/wiki/Swedish_phonology" target=3D"_blank=
">http://en.wikipedia.org/wiki/Swedish_phonology</a><br>
<br>
To be clear, I&#39;m not saying that this doesn&#39;t expose a real problem=
, and the draft certainly drew attention to it, but I also don&#39;t think =
that more documentation will solve it, especially since the information is =
already readily available in more accessible formats. I think what you&#39;=
ll find is that there are two types of folks (in IETF and generally) - thos=
e who see an attempt at proper pronunciation and cultural awareness as impo=
rtant and worth making extra effort to learn proactively, and those who bel=
ieve that if it&#39;s an issue, the person on the receiving end will correc=
t them when they get it wrong (and hopefully not repeat the mistake).<br>

Not making a value judgment on either, merely an observation.<br>
<br>
Thanks<br>
Wes George<br>
<br>
PS: guess which one is my given name and which my surname? Even native Engl=
ish speakers aren&#39;t immune from name confusion. :-)<br>
<br>
<br>
Anything below this line has been added by my company&#39;s mail server, I =
have no control over it.<br>
-----------------<br>
<br>
This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.<br>

</blockquote></div><br></div>

--047d7b5d8c7f0e8d6e04e1820aa0--

From dougb@dougbarton.us  Sun Jul 14 20:14:07 2013
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EED121F9ADD for <ietf@ietfa.amsl.com>; Sun, 14 Jul 2013 20:14:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.475
X-Spam-Level: 
X-Spam-Status: No, score=-2.475 tagged_above=-999 required=5 tests=[AWL=0.124,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oDZPz8mJg44P for <ietf@ietfa.amsl.com>; Sun, 14 Jul 2013 20:14:03 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [208.79.90.218]) by ietfa.amsl.com (Postfix) with ESMTP id 1DADA21F9829 for <ietf@ietf.org>; Sun, 14 Jul 2013 20:14:03 -0700 (PDT)
Received: from [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b] (unknown [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b]) by dougbarton.us (Postfix) with ESMTPSA id A445122B2A for <ietf@ietf.org>; Mon, 15 Jul 2013 03:14:02 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1373858042; bh=EWzIkemy+7nDIFxXcSDzCZ1Idek7yTV9hUKbfaxUFoc=; h=Date:From:To:Subject:References:In-Reply-To; b=VNEoJTdfVE2lWFQxPv42kNJ7CVry7IWoZPKulyl1zCI8+13lTbH0T6/A5J2UtwQ+w yB9MNKzSoCuHNWXJNTFH2DKA9MvceNJBpFzI5bwEhh/mjUDLhpmcr38gWGoiFGAF7s QQHbNSar75SYnFsunZwCW20L5AXMfIc+0ekskThg=
Message-ID: <51E368F9.70404@dougbarton.us>
Date: Sun, 14 Jul 2013 20:14:01 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IAB Statement on Dotless Domains
References: <20130712162348.9441.qmail@joyce.lan> <51E06965.7010203@gmail.com> <alpine.BSF.2.00.1307121737360.13717@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1307121737360.13717@joyce.lan>
X-Enigmail-Version: 1.5.2
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Jul 2013 03:14:07 -0000

On 07/12/2013 02:40 PM, John R Levine wrote:
>
> Point your browser at http://dk/ or http://tm/ and see what happens.

As John points out, the ccTLDs are already doing this. ICANN has no 
authority to tell the ccTLDs NOT to do it, thus restricting the gTLDs 
from doing it (via their contract with ICANN) would arguably be "unfair" 
in any number of parameters, including (possibly) legal ones.

It is unarguably true that as things currently stand there will be 
"problems" with dotless domains. How widespread, and how serious those 
problems become is yet to be seen. However it is also unarguably true 
that if there is sufficient market demand for dotless domains the 
software folks, at both the OS and application levels, will make them 
work. [1]

So either this is a good idea that will gain traction, and therefore 
appropriate software support; or it is a bad idea that will go away on 
its own. Either way, making a fuss about the hoofprints after the horse 
has already left the barn doesn't help the situation.

Doug

[1] http://publicsuffix.org/ (for an arguably pathological definition of 
something that "works" in this space)

From dhc@dcrocker.net  Sun Jul 14 20:25:59 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3AA721F9DA9 for <ietf@ietfa.amsl.com>; Sun, 14 Jul 2013 20:25:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.596
X-Spam-Level: 
X-Spam-Status: No, score=-6.596 tagged_above=-999 required=5 tests=[AWL=0.003,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mwmtgRAQQnIa for <ietf@ietfa.amsl.com>; Sun, 14 Jul 2013 20:25:54 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id E3C4221F9D50 for <ietf@ietf.org>; Sun, 14 Jul 2013 20:25:53 -0700 (PDT)
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 r6F3PnBx009908 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 14 Jul 2013 20:25:52 -0700
Message-ID: <51E36B9F.2020404@dcrocker.net>
Date: Sun, 14 Jul 2013 20:25:19 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Doug Barton <dougb@dougbarton.us>
Subject: Re: IAB Statement on Dotless Domains
References: <20130712162348.9441.qmail@joyce.lan> <51E06965.7010203@gmail.com> <alpine.BSF.2.00.1307121737360.13717@joyce.lan> <51E368F9.70404@dougbarton.us>
In-Reply-To: <51E368F9.70404@dougbarton.us>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Sun, 14 Jul 2013 20:25:52 -0700 (PDT)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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, 15 Jul 2013 03:25:59 -0000

On 7/14/2013 8:14 PM, Doug Barton wrote:
> It is unarguably true that as things currently stand there will be
> "problems" with dotless domains. How widespread, and how serious those
> problems become is yet to be seen. However it is also unarguably true
> that if there is sufficient market demand for dotless domains the
> software folks, at both the OS and application levels, will make them
> work. [1]


The effects of your putting your hand into a fire are yet to be seen. 
However we have enough knowledge of things to be able to assess likely 
outcomes quite accurately.

In contrast, assertions about "market demand" ensuring that "software 
folks... will make them work" rests on a fuzzy concept of market forces 
-- for example, the market of users isn't likely to be issuing a formal 
or informal 'demand' about any of this, and a model of altering 
installed-base behavior that has, I believe, has no historical precedent.

It is, in fact, possible that Marshall Rose was wrong and that for some 
things, there is no possible thrust sufficient to make pigs fly, or at 
least not without killing an extraordinary number of other pigs.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From dougb@dougbarton.us  Sun Jul 14 20:36:43 2013
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 378A121F88FB for <ietf@ietfa.amsl.com>; Sun, 14 Jul 2013 20:36:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.496
X-Spam-Level: 
X-Spam-Status: No, score=-2.496 tagged_above=-999 required=5 tests=[AWL=0.103,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DYJXMwb6svFc for <ietf@ietfa.amsl.com>; Sun, 14 Jul 2013 20:36:39 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [208.79.90.218]) by ietfa.amsl.com (Postfix) with ESMTP id F002121F8887 for <ietf@ietf.org>; Sun, 14 Jul 2013 20:36:38 -0700 (PDT)
Received: from [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b] (unknown [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b]) by dougbarton.us (Postfix) with ESMTPSA id 12C9222B2A for <ietf@ietf.org>; Mon, 15 Jul 2013 03:36:36 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1373859396; bh=5dA9ib9mQkzl0y++YZaX9aDg8KP91vUa6tBl7XgIlZg=; h=Date:From:To:Subject:References:In-Reply-To; b=OKviMjhbSrtrbke+wMAuSEQZFAxVH8UjuKf51yYKlvO7zE4nL1vg/BU10/76tTJiz ftwCZ5vbLBfB6vJpn/KupLHDJfwgN56Dm57pjeeJzwKnYWFPn9T1nDBbCoIM4DY2+r nzLaY4nztmlzAPizBmXxRaOBJkv81PVURkYg38qY=
Message-ID: <51E36E43.4050102@dougbarton.us>
Date: Sun, 14 Jul 2013 20:36:35 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IAB Statement on Dotless Domains
References: <20130712162348.9441.qmail@joyce.lan> <51E06965.7010203@gmail.com> <alpine.BSF.2.00.1307121737360.13717@joyce.lan> <51E368F9.70404@dougbarton.us> <51E36B9F.2020404@dcrocker.net>
In-Reply-To: <51E36B9F.2020404@dcrocker.net>
X-Enigmail-Version: 1.5.2
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Jul 2013 03:36:43 -0000

On 07/14/2013 08:25 PM, Dave Crocker wrote:
> On 7/14/2013 8:14 PM, Doug Barton wrote:
>> It is unarguably true that as things currently stand there will be
>> "problems" with dotless domains. How widespread, and how serious those
>> problems become is yet to be seen. However it is also unarguably true
>> that if there is sufficient market demand for dotless domains the
>> software folks, at both the OS and application levels, will make them
>> work. [1]
>
>
> The effects of your putting your hand into a fire are yet to be seen.
> However we have enough knowledge of things to be able to assess likely
> outcomes quite accurately.

And correspondingly we have a lot of knowledge about what is likely to 
happen with dotless domains, at least in the early stages. Brian already 
pointed out that the overwhelming majority of end-user hosts have either 
a default domain, or a search string configured. Thus for the most part 
dotless domains will (again, in the early stages) be an annoyance, at 
worst.

There will be some pathological cases where various people/enterprises 
have been doing things that they have been told for years not to do 
(hijacking "unused" TLDs) who will have some pain. I have no sympathy 
for them.

Part of the annoyance will be that users will have an "inconsistent" 
experience. That's been true of the Internet for years, depending on 
your software, local configuration, etc. So again, nothing to see here.

> In contrast, assertions about "market demand" ensuring that "software
> folks... will make them work" rests on a fuzzy concept of market forces
> -- for example, the market of users isn't likely to be issuing a formal
> or informal 'demand' about any of this,

If you believe that's what I meant by "market forces" I'm not the one 
with the fuzzy concept. :)

Google is pushing for dotless-dot-search, so you can guarantee it will 
work in chromium (with or without ICANN's blessing). If sufficient 
$CURRENCY (or other currency-like motivation) is thrust in the direction 
of other browser vendors they will follow suit. The fact that it works 
in the browser will encourage other software vendors to adapt.

... or not. I don't think it's impossible that this will fail. I don't 
even think it's impossible that it will fail in a spectacular manner. 
What I know it is impossible to do is prevent it from happening.

> and a model of altering
> installed-base behavior that has, I believe, has no historical precedent.

"I find your lack of faith ... disturbing."

> It is, in fact, possible that Marshall Rose was wrong and that for some
> things, there is no possible thrust sufficient to make pigs fly, or at
> least not without killing an extraordinary number of other pigs.

For the record I am not in favor of harm coming to any bovine, 
regardless of altitude.

Doug (get it? thrust? see what I did there?)


From johnl@iecc.com  Sun Jul 14 21:41:00 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8BFD21F9A99 for <ietf@ietfa.amsl.com>; Sun, 14 Jul 2013 21:41:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.756
X-Spam-Level: 
X-Spam-Status: No, score=-110.756 tagged_above=-999 required=5 tests=[AWL=0.443, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fpg8Rtc0GQAJ for <ietf@ietfa.amsl.com>; Sun, 14 Jul 2013 21:40:56 -0700 (PDT)
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 5375521F9A2A for <ietf@ietf.org>; Sun, 14 Jul 2013 21:40:56 -0700 (PDT)
Received: (qmail 20256 invoked from network); 15 Jul 2013 04:40:55 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 15 Jul 2013 04:40:55 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=51e37d57.xn--yuvv84g.k1307; i=johnl@user.iecc.com; bh=bPReZtg3jhCoghVmusoqaEyx08GFg4L2XV7yALPyuXE=; b=vDcdWyuiEdFXlBeDLQFA05piPrmRxKV3shv0JAlMfq9BmbmtmtnjaAJ1IrtKusZ873SGqMUFjzpCB8uRRYCPZRGJ07K0AfpYBFlyAr8wiH8UjffWcgisKoaNpkT3OyX7/I7kaAoNp570YXcSca0Cj0rCR46M8C7BrjS6NbFuq1axlbfBRPSD2uhdsdZOCEyM2eBOINSYc8saZtno6JPAzGpRYdeQSfMLdZTcOg14LelQW+YLbmlVIqCJE1MHB9dE
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=51e37d57.xn--yuvv84g.k1307; olt=johnl@user.iecc.com; bh=bPReZtg3jhCoghVmusoqaEyx08GFg4L2XV7yALPyuXE=; b=NxW2j32rBQVeXzSTq4hLyZm2NEonTp0+8WagSM1tApTWIstkXlJYqEKkK04AizVelawRK8gsi70ERyGZRpkwiVjN2RT2DnZy/qDnmx5DtexdW4lanAX6QEerO+P8WGjPvlW+ZaICyA+R+Df2OgfVfw+Oqcx/TtcJeVVJlRcjVJp7LO5WIYLBGxiSZGAhfD1I5LZazvaYAJb9KNa1qggApcO4oqz/JEW+euOa3kIZPS6nu4DMQrKTVHXAr5SYzlFk
Date: 15 Jul 2013 04:40:33 -0000
Message-ID: <20130715044033.40667.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: where's the data, was IAB Statement on Dotless Domains
In-Reply-To: <51E368F9.70404@dougbarton.us>
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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Jul 2013 04:41:01 -0000

In article <51E368F9.70404@dougbarton.us> you write:
>On 07/12/2013 02:40 PM, John R Levine wrote:
>>
>> Point your browser at http://dk/ or http://tm/ and see what happens.
>
>As John points out, the ccTLDs are already doing this. ICANN has no 
>authority to tell the ccTLDs NOT to do it, thus restricting the gTLDs 
>from doing it (via their contract with ICANN) would arguably be "unfair" 
>in any number of parameters, including (possibly) legal ones.

No, you completely misunderstand my point.

If you try out the existing dotless TLDs, you will find out that they
sort of work for web pages, only because very few sites have hosts
named "dk" or "ai", and mail to them works very badly if at all.  So
there is some actual data we could cite about how badly they work, to
support the hand waving in all the anti-dotless documents to date.

It's silly to think that "fairness" between ccTLDS and gTLDs matters
at all.  For one thing, gTLDs have for over a decade followed rules
that don't apply to ccTLDs, such as accepting registrations only
indirectly, and publishing WHOIS about all registered names.  For
another, anyone who's looked through the new TLD applicant guidebook
would know that every applicant has agreed to page after page of legal
releases in ICANN's favor, and that dotless domains are specifically
forbidden without a waiver from ICANN, which ICANN can grant or not at
its discretion.

The only reason this has come up is that one (1) of the 1900 new TLD
applications has asked for a waiver to do a dotless domain, and that
applicant happens to be Google applying for .SEARCH.  ICANN can just
say no.  Or they might not even have to, since Google's is only one of
four competing applicants for .SEARCH, and there is no reason to
assume that they would necessarily be the winner at the end of the
negotiations.

R's,
John

From sm@elandsys.com  Sun Jul 14 22:09:44 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97FC421F9D5C for <ietf@ietfa.amsl.com>; Sun, 14 Jul 2013 22:09:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.588
X-Spam-Level: 
X-Spam-Status: No, score=-102.588 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cF6DMgR-zqv1 for <ietf@ietfa.amsl.com>; Sun, 14 Jul 2013 22:09:43 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id B966721F9C25 for <ietf@ietf.org>; Sun, 14 Jul 2013 22:09:43 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.153.203]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r6F57jta011018 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 14 Jul 2013 22:07:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1373864879; bh=ziefwTqbU7WlvQkACUsDr9uVS7V/xvo+MYs7O5qqZbA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=VwD3LcS9gHqMpdDR15IAYEwksPIeuu6M1hZ7RZFQE7MAhi9TozlcY8qq4w6PeOO7h 5ptsCRR3uenVS0Ix2K4/CbZ+ec6V8/rxIGONJ8zD4u36RatN+bFoMDvGCT6alL6ku4 4dTin2FAsPOay+xja87FjgoK5V3vCqBq43Ly6n9g=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1373864879; i=@elandsys.com; bh=ziefwTqbU7WlvQkACUsDr9uVS7V/xvo+MYs7O5qqZbA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=49SF+INi9zSw9nAz8HOqkMSmuqsEDrqW4qJZAhKd87v89e3TqFXml3X2UqNw/1hUQ D1W1GOp4hKvEc3zIeT89KlAzDQ3Fs6bGy2LR7tKFOgPpUvHmlfgf6lN5mDniBzN8Pe 94oqe2ri387sQWu+nJ/P+RYN0ytbnmvNlTYg9wvk=
Message-Id: <6.2.5.6.2.20130714205140.0ce1f0b8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 14 Jul 2013 22:05:17 -0700
To: ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: The case of dotless domains (was: Dotless Domain conflict with user searching and branding)
In-Reply-To: <A0984871-D92D-4110-9001-16B363B65AC0@checkpoint.com>
References: <20130713152747.8F79D18C0D0@mercury.lcs.mit.edu> <51E18737.4080903@isdg.net> <3725D4B2-65DA-45FA-AAEE-309F45CD6F18@checkpoint.com> <51E2A8EE.5010200@isdg.net> <A0984871-D92D-4110-9001-16B363B65AC0@checkpoint.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Ofer Inbar <cos@aaaaa.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Jul 2013 05:09:44 -0000

At 06:53 14-07-2013, Yoav Nir wrote:
>http://tools.ietf.org/html/draft-moonesamy-dotless-domains-00

That memo discusses about the case of the dotless domains in terms of 
the technical standards.  Comments are welcome.

At 13:11 13-07-2013, Ofer Inbar wrote:
>What this brings to mind is that we used to have implicit DNS domain
>search in the early days of DNS.  When edu.com accidentally hijacked
>a huge chunk of the Internet, most of the net very quickly got rid of
>implicit search, and we got the explicit DNS search feature that many
>people are discussing now.

Yes.

>If some new TLD gets used in a dotless fashion in a way that truly
>does cause major trouble, I expect we'll see sites all over the net
>quickly deploying DNS resolvers that discard A, AAAA, or MX records
>at the top level, to protect their users.

There is already deployed code to do that.

At 20:14 14-07-2013, Doug Barton wrote:
>It is unarguably true that as things currently stand there will be 
>"problems" with dotless domains. How widespread, and how serious 
>those problems become is yet to be seen.

I haven't seen anyone in the IETF arguing that sufficient market 
demand overrides comments about problems that will appear.

>So either this is a good idea that will gain traction, and therefore 
>appropriate software support; or it is a bad idea that will go away 
>on its own. Either way, making a fuss

It is up to those who decide to decide whether dotless domains is a 
good idea that will gain traction or a bad idea that will go away on it own.

At 20:25 14-07-2013, Dave Crocker wrote:
>In contrast, assertions about "market demand" ensuring that 
>"software folks... will make them work" rests on a fuzzy concept of 
>market forces -- for example, the market of users isn't likely to be 
>issuing a formal or informal 'demand' about any of this, and a model 
>of altering installed-base behavior that has, I believe, has no 
>historical precedent.

Yes.

>It is, in fact, possible that Marshall Rose was wrong and that for 
>some things, there is no possible thrust sufficient to make pigs 
>fly, or at least not without killing an extraordinary number of other pigs.

:-)

Regards,
S. Moonesamy 


From wesley.george@twcable.com  Mon Jul 15 05:14:00 2013
Return-Path: <wesley.george@twcable.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E9B711E80E8 for <ietf@ietfa.amsl.com>; Mon, 15 Jul 2013 05:14:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.551
X-Spam-Level: 
X-Spam-Status: No, score=-0.551 tagged_above=-999 required=5 tests=[AWL=-0.087, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WAFe0kIjBo+o for <ietf@ietfa.amsl.com>; Mon, 15 Jul 2013 05:13:50 -0700 (PDT)
Received: from cdcipgw01.twcable.com (cdcipgw01.twcable.com [165.237.91.110]) by ietfa.amsl.com (Postfix) with ESMTP id ADB0011E80C5 for <ietf@ietf.org>; Mon, 15 Jul 2013 05:13:50 -0700 (PDT)
X-SENDER-IP: 10.136.163.11
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.89,668,1367985600"; d="scan'208";a="33587950"
Received: from unknown (HELO PRVPEXHUB02.corp.twcable.com) ([10.136.163.11]) by cdcipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 15 Jul 2013 08:13:34 -0400
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.78]) by PRVPEXHUB02.corp.twcable.com ([10.136.163.11]) with mapi; Mon, 15 Jul 2013 08:13:49 -0400
From: "George, Wes" <wesley.george@twcable.com>
To: "ietf@ietf.org" <ietf@ietf.org>, "bob.hinden@gmail.com" <bob.hinden@gmail.com>
Date: Mon, 15 Jul 2013 08:13:48 -0400
Subject: RE: Sunday IAOC Overview Session at the Berlin IETF
Thread-Topic: Sunday IAOC Overview Session at the Berlin IETF
Thread-Index: Ac5/QrL+xaCrIK5iRCyRFUMPbQtetACEVJrg
Message-ID: <2671C6CDFBB59E47B64C10B3E0BD5923043882B3AE@PRVPEXVS15.corp.twcable.com>
References: <20130712205852.10265.88487.idtracker@ietfa.amsl.com>
In-Reply-To: <20130712205852.10265.88487.idtracker@ietfa.amsl.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="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Jul 2013 12:14:00 -0000

PiBUaGUgSUVURiBBZG1pbmlzdHJhdGl2ZSBPdmVyc2lnaHQgQ29tbWl0dGVlIChJQU9DKSB3aWxs
IGhvbGQgYSBzZXNzaW9uDQo+IGZyb20gMTUwMC0xNjUwIGluDQo+IFBvdHNkYW0gMSBhdCB0aGUg
QmVybGluIElFVEYgb24gU3VuZGF5IEp1bHkgMjgsIDIwMTMuICBUaGUgcHVycG9zZSBpcyB0bw0K
PiBwcm92aWRlIGFuDQo+IG92ZXJ2aWV3IG9mIHRoZSBJQU9DIHRvIGFsbG93IHRoZSBjb21tdW5p
dHkgdG8gYmV0dGVyIHVuZGVyc3RhbmQgd2hhdA0KPiB0aGUgSUFPQyBkb2VzLCBob3cNCj4gdGhl
IGZpbmFuY2VzIHdvcmssIHZlbnVlIHNlbGVjdGlvbiwgYW5kIHByb3ZpZGUgdGhlIElBT0MgZmVl
ZGJhY2sgb24gdGhlDQo+IGpvYiB0aGV5IGFyZQ0KPiBkb2luZy4NCg0KW1dFR10gQWZ0ZXIgT3Js
YW5kbywgdGhlcmUgd2FzIGZlZWRiYWNrIGZyb20gbXVsdGlwbGUgZm9sa3MgKG15c2VsZiBpbmNs
dWRlZCkgcmVxdWVzdGluZyB0aGF0IHRoaXMgc2Vzc2lvbiAqTk9UKiBiZSBzY2hlZHVsZWQgb3Bw
b3NpdGUgdGhlIE5ld2NvbWVycycgbWVldCBhbmQgZ3JlZXQsIHNpbmNlIHRoYXQgbWVhbnMgdGhh
dCBtb3N0IG9mIHRoZSBmb2xrcyB3aG8gbWlnaHQgd2FudCB0byBzZWUgdGhpcyBidXQgaGF2ZSBs
ZWFkZXJzaGlwL21lbnRvcnNoaXAgZHV0aWVzIG11c3QgbGVhdmUgdGhlIHNlc3Npb24gZWFybHku
IENvdWxkIHRoaXMgYmUgbW92ZWQgdG8gdGhlIGVhcmxpZXIgdGltZSBzbG90PyBJZiBub3QsIGNh
biB5b3UgYXQgbGVhc3QgZG8gdGhlIGNvbnRlbnQgaW4gdGhlIHJldmVyc2Ugb3JkZXIgZnJvbSB0
aGUgT3JsYW5kbyBzZXNzaW9uIHNvIHRoYXQgYmV0d2VlbiB0aGUgdHdvLCB0aG9zZSB3aG8gaGF2
ZSB0byBsZWF2ZSBhZnRlciBhbiBob3VyIGhhdmUgYSBtb3N0bHkgY29tcGxldGUgdmlldyBiZXR3
ZWVuIHRoaXMgc2Vzc2lvbiBhbmQgdGhlIHByZXZpb3VzIG9uZT8NCg0KVGhhbmtzLA0KDQpXZXMN
Cg0KDQpBbnl0aGluZyBiZWxvdyB0aGlzIGxpbmUgaGFzIGJlZW4gYWRkZWQgYnkgbXkgY29tcGFu
eeKAmXMgbWFpbCBzZXJ2ZXIsIEkgaGF2ZSBubyBjb250cm9sIG92ZXIgaXQuDQotLS0tLS0tLS0t
LS0tLS0tLQ0KDQpUaGlzIEUtbWFpbCBhbmQgYW55IG9mIGl0cyBhdHRhY2htZW50cyBtYXkgY29u
dGFpbiBUaW1lIFdhcm5lciBDYWJsZSBwcm9wcmlldGFyeSBpbmZvcm1hdGlvbiwgd2hpY2ggaXMg
cHJpdmlsZWdlZCwgY29uZmlkZW50aWFsLCBvciBzdWJqZWN0IHRvIGNvcHlyaWdodCBiZWxvbmdp
bmcgdG8gVGltZSBXYXJuZXIgQ2FibGUuIFRoaXMgRS1tYWlsIGlzIGludGVuZGVkIHNvbGVseSBm
b3IgdGhlIHVzZSBvZiB0aGUgaW5kaXZpZHVhbCBvciBlbnRpdHkgdG8gd2hpY2ggaXQgaXMgYWRk
cmVzc2VkLiBJZiB5b3UgYXJlIG5vdCB0aGUgaW50ZW5kZWQgcmVjaXBpZW50IG9mIHRoaXMgRS1t
YWlsLCB5b3UgYXJlIGhlcmVieSBub3RpZmllZCB0aGF0IGFueSBkaXNzZW1pbmF0aW9uLCBkaXN0
cmlidXRpb24sIGNvcHlpbmcsIG9yIGFjdGlvbiB0YWtlbiBpbiByZWxhdGlvbiB0byB0aGUgY29u
dGVudHMgb2YgYW5kIGF0dGFjaG1lbnRzIHRvIHRoaXMgRS1tYWlsIGlzIHN0cmljdGx5IHByb2hp
Yml0ZWQgYW5kIG1heSBiZSB1bmxhd2Z1bC4gSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyBFLW1h
aWwgaW4gZXJyb3IsIHBsZWFzZSBub3RpZnkgdGhlIHNlbmRlciBpbW1lZGlhdGVseSBhbmQgcGVy
bWFuZW50bHkgZGVsZXRlIHRoZSBvcmlnaW5hbCBhbmQgYW55IGNvcHkgb2YgdGhpcyBFLW1haWwg
YW5kIGFueSBwcmludG91dC4NCg==

From ted.ietf@gmail.com  Mon Jul 15 09:04:51 2013
Return-Path: <ted.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58AC921F8D16 for <ietf@ietfa.amsl.com>; Mon, 15 Jul 2013 09:04:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.739
X-Spam-Level: 
X-Spam-Status: No, score=-0.739 tagged_above=-999 required=5 tests=[AWL=-1.474, BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, MIME_CHARSET_FARAWAY=2.45, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UE1pT9NxWc0U for <ietf@ietfa.amsl.com>; Mon, 15 Jul 2013 09:04:50 -0700 (PDT)
Received: from mail-ie0-x233.google.com (mail-ie0-x233.google.com [IPv6:2607:f8b0:4001:c03::233]) by ietfa.amsl.com (Postfix) with ESMTP id 5DD3521F87D1 for <ietf@ietf.org>; Mon, 15 Jul 2013 09:04:50 -0700 (PDT)
Received: by mail-ie0-f179.google.com with SMTP id c10so26952707ieb.10 for <ietf@ietf.org>; Mon, 15 Jul 2013 09:04:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=2rq3eBWUWLbPZ0T2OFY/m0lQdO/e4LTuwAiIvcc6ICk=; b=gO/HSDixsM1jg+iJMiV3QFTVuLcVYeN98ccEQyPRc7h8JOrnNA0g0I1NuS0HtmNwSX wlWMa+Uv11JkCvuIjf+Ljm1I7Iq4jnmnWDhdXgwOwjxer6pjrnLIE+hh1/MbZbfXuKii Frrg2dQnaO+axRqJoljNM5mjZi6dcxfaM0fnRdCBOk4TemMNLGpsDDsPW8pbAABZEVPt hkOpy8zhMRPwD7Sx+jbOAEoNzYWQ0j18nbZsB4gMKJBtWXZB5YW4pWexOOZs+t5smqOi 5QO9bO3xUH619k8Nh2VPRHPlvsSPueY7s6SOBvJphWjJdZPQMoQzjy5LKiDDojUrWwt/ vaHw==
MIME-Version: 1.0
X-Received: by 10.50.134.9 with SMTP id pg9mr7516202igb.29.1373904289961; Mon, 15 Jul 2013 09:04:49 -0700 (PDT)
Received: by 10.42.29.202 with HTTP; Mon, 15 Jul 2013 09:04:49 -0700 (PDT)
In-Reply-To: <CANF0JMCA+HQ7=xEXjDkgxLt2iqUj3Wdq_+2+KFsPg34a0m+nxQ@mail.gmail.com>
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com> <CA+9kkMDZoX0Eq4TcbpP=+YMPmq-F3CAGB1dSogYJa6V2F-irbQ@mail.gmail.com> <CANF0JMCA+HQ7=xEXjDkgxLt2iqUj3Wdq_+2+KFsPg34a0m+nxQ@mail.gmail.com>
Date: Mon, 15 Jul 2013 09:04:49 -0700
Message-ID: <CA+9kkMCqRL5R8v5RivjRkNHQtMFiKs3Rhva+X5NogMB6_qMaSQ@mail.gmail.com>
Subject: Re: Regarding call Chinese names
From: Ted Hardie <ted.ietf@gmail.com>
To: Hui Deng <denghui02@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b41407e289f5f04e18f05f0
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Jul 2013 16:04:51 -0000

--047d7b41407e289f5f04e18f05f0
Content-Type: text/plain; charset=Big5
Content-Transfer-Encoding: quoted-printable

On Sun, Jul 14, 2013 at 5:26 PM, Hui Deng <denghui02@gmail.com> wrote:

> Hi Ted,
>
> I did explain them in the 1st paragraph about minorities (not mentioned
> that they could have two kids in mainland)
> anyway, I will revise the title by adding "Chinese "Han" people", hope
> that will be ok
>
> -Hui
>
>
>
While it is always valuable to note national minorities, I believe you
missed the point.  In some territories, there are dialects of Chinese other
than Mandarin and romanizations
other than pinyin which are common and normatively correct.  For those
Chinese people, your document does not apply.  As an example, the current
chief executive of Hong Kong is properly called Leung Chun Ying (=B1=E7=AE=
=B6=AD^); his
predecessor  in that role was Tung Chee Hwa (=B8=B3=AB=D8=B5=D8).   Similar=
 situations
arise in Taiwan and in many territories where Chinese people are themselves
national minorities.

Clarifying that your document is specific to the pinyin romanization is
likely enough (since that romanization is based on Mandarin).

best regards,

Ted Hardie





> 2013/7/11 Ted Hardie <ted.ietf@gmail.com>
>
>> Howdy,
>>
>> Thanks for your efforts.  I would suggest, however, that you re-title
>> your drafts so that "Chinese" is restricted to the populations which use
>> pinyin and have standardized on what English speakers call Mandarin (=B0=
=EA=BBy
>> or =B4=B6=B3q=B8=DC, depending on your background).  Those who use  roma=
nizations
>> based on other dialects, in line with their familial pronunciation, woul=
d
>> otherwise be treated as not "Chinese".
>>
>> regards,
>>
>> Ted Hardie
>>
>>
>> On Wed, Jul 10, 2013 at 5:04 PM, Hui Deng <denghui02@gmail.com> wrote:
>>
>>> Hello all
>>>
>>> We submitted two drafts to help people here to correctly call chinese
>>> people names:
>>>
>>> http://tools.ietf.org/html/draft-deng-call-chinese-names-00
>>>
>>>    http://tools.ietf.org/html/draft-zcao-chinese-pronounce-00
>>>
>>>
>>>
>>> Feel free to let us know if you have any other issues?
>>>
>>> Best regards,
>>>
>>>
>>>
>>> -Hui Deng
>>>
>>
>>
>

--047d7b41407e289f5f04e18f05f0
Content-Type: text/html; charset=Big5
Content-Transfer-Encoding: quoted-printable

On Sun, Jul 14, 2013 at 5:26 PM, Hui Deng <span dir=3D"ltr">&lt;<a href=3D"=
mailto:denghui02@gmail.com" target=3D"_blank">denghui02@gmail.com</a>&gt;</=
span> wrote:<br><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir=3D"ltr"><div>Hi Ted,</div><div>&nbsp;</div><div>I did explain them=
 in the 1st paragraph about minorities (not mentioned that&nbsp;they could =
have two kids in mainland)</div><div>anyway, I will revise the title by add=
ing &quot;Chinese &quot;Han&quot; people&quot;, hope that will be ok</div>
<span class=3D"HOEnZb"><font color=3D"#888888">
<div>&nbsp;</div><div>-Hui</div></font></span></div><div class=3D"HOEnZb"><=
div class=3D"h5"><div class=3D"gmail_extra"><br><br></div></div></div></blo=
ckquote><div><br>While it is always valuable to note national minorities, I=
 believe you missed the point.&nbsp; In some territories, there are dialect=
s of Chinese other than Mandarin and romanizations <br>
other than pinyin which are common and normatively correct.&nbsp; For those=
 Chinese people, your document does not apply.&nbsp; As an example, the cur=
rent chief executive of Hong Kong is properly called Leung Chun Ying (<span=
 class=3D"nickname" lang=3D"zh-hk"><span style=3D"font-weight:normal">=B1=
=E7=AE=B6=AD^)</span></span>; his predecessor&nbsp; in that role was <span =
class=3D"nickname" lang=3D"zh-hk"><span style=3D"font-weight:normal">Tung C=
hee Hwa </span></span>(<span class=3D"nickname" lang=3D"zh-hk"><span style=
=3D"font-weight:normal">=B8=B3=AB=D8=B5=D8). &nbsp; Similar situations aris=
e in Taiwan and in many territories where Chinese people are themselves nat=
ional minorities.&nbsp;&nbsp; <br>
<br>Clarifying that your document is specific to the pinyin romanization is=
 likely enough (since that romanization is based on Mandarin).<br><br>best =
regards,<br><br>Ted Hardie<br><br><br></span></span><br>&nbsp;</div><blockq=
uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex">
<div class=3D"HOEnZb"><div class=3D"h5"><div class=3D"gmail_extra"><div cla=
ss=3D"gmail_quote">2013/7/11 Ted Hardie <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:ted.ietf@gmail.com" target=3D"_blank">ted.ietf@gmail.com</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">Howdy,<br><br>Thanks for your efforts.&nbsp;=
 I would suggest, however, that you re-title your drafts so that &quot;Chin=
ese&quot; is restricted to the populations which use pinyin and have standa=
rdized on what English speakers call Mandarin (=B0=EA=BBy<br>


or =B4=B6=B3q=B8=DC, depending on your background).&nbsp; Those who use&nbs=
p; romanizations based on other dialects, in line with their familial pronu=
nciation, would otherwise be treated as not &quot;Chinese&quot;.&nbsp; <br>=
<br>regards,<br><br>Ted Hardie<br>


<br><br><div class=3D"gmail_quote"><div>On Wed, Jul 10, 2013 at 5:04 PM, Hu=
i Deng <span dir=3D"ltr">&lt;<a href=3D"mailto:denghui02@gmail.com" target=
=3D"_blank">denghui02@gmail.com</a>&gt;</span> wrote:<br></div><blockquote =
style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(20=
4,204,204);border-left-width:1px;border-left-style:solid" class=3D"gmail_qu=
ote">


<div dir=3D"ltr"><div>Hello all</div><div>&nbsp;</div><div><div>We submitte=
d two drafts to help people here to correctly call chinese people names:</d=
iv></div><div><font color=3D"#000000" face=3D"=A7=BA=CA^" size=3D"3">

</font><p style=3D"margin:0cm 0cm 0pt"><span lang=3D"EN-US"><a href=3D"http=
://tools.ietf.org/html/draft-deng-call-chinese-names-00" target=3D"_blank">=
<span style=3D"background:white;color:rgb(17,85,204);font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;;font-size:10pt">http://tools.ietf.org/html/d=
raft-deng-call-chinese-names-00</span></a></span><span style=3D"background:=
white;color:rgb(34,34,34);font-family:&quot;Arial&quot;,&quot;sans-serif&qu=
ot;;font-size:10pt" lang=3D"EN-US">&nbsp;</span></p>



<font color=3D"#000000" face=3D"=A7=BA=CA^" size=3D"3">

</font><p style=3D"margin:0cm 0cm 0pt"><span style=3D"background:white;colo=
r:rgb(34,34,34);font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;font-s=
ize:10pt" lang=3D"EN-US">&nbsp; &nbsp;</span><span lang=3D"EN-US"><a href=
=3D"http://tools.ietf.org/html/draft-zcao-chinese-pronounce-00" target=3D"_=
blank"><span style=3D"background:white;color:rgb(17,85,204);font-family:&qu=
ot;Arial&quot;,&quot;sans-serif&quot;;font-size:10pt">http://tools.ietf.org=
/html/draft-zcao-chinese-pronounce-00</span></a></span></p>



<p style=3D"margin:0cm 0cm 0pt"><span lang=3D"EN-US"></span>&nbsp;</p><p st=
yle=3D"margin:0cm 0cm 0pt"><span lang=3D"EN-US">Feel free to let us know if=
 you have any other issues?</span></p><p style=3D"margin:0cm 0cm 0pt"><span=
 lang=3D"EN-US">Best regards,</span></p>


<span><font color=3D"#888888">
<p style=3D"margin:0cm 0cm 0pt"><span lang=3D"EN-US"></span>&nbsp;</p><p st=
yle=3D"margin:0cm 0cm 0pt"><span lang=3D"EN-US">-Hui Deng</span></p><font c=
olor=3D"#000000" face=3D"=A7=BA=CA^" size=3D"3">

</font></font></span></div></div>
</blockquote></div><br>
</blockquote></div><br></div>
</div></div></blockquote></div><br>

--047d7b41407e289f5f04e18f05f0--

From ietf-secretariat@ietf.org  Mon Jul 15 10:09:23 2013
Return-Path: <ietf-secretariat@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4F4921E80FD; Mon, 15 Jul 2013 10:09:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.6
X-Spam-Level: 
X-Spam-Status: No, score=-104.6 tagged_above=-999 required=5 tests=[AWL=-2.000, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xl-Sfy3xn2t1; Mon, 15 Jul 2013 10:09:23 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 511C011E8133; Mon, 15 Jul 2013 10:09:23 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Secretariat <ietf-secretariat@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: Internet Draft Submission Cut-Off Today
X-Test-IDTracker: no
X-IETF-IDTracker: 4.51.p2
Message-ID: <20130715170923.16712.32343.idtracker@ietfa.amsl.com>
Date: Mon, 15 Jul 2013 10:09:23 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Jul 2013 17:09:23 -0000

This is a reminder that the Internet Draft Submission cut-off is today, Mon=
day, July 15, 2013. =


All submissions are due by UTC 24:00.

All drafts can be uploaded using the ID submission tool located here:
https://datatracker.ietf.org/submit/

The Internet-Draft cutoff dates as well as other significant dates for IETF=
 87 can be found at: =

https://www.ietf.org/meeting/cutoff-dates-2013.html#IETF87

Thank you for your understanding and cooperation. If you have any  question=
s or concerns, then please send a message to internet-drafts@ietf.org.

From bob.hinden@gmail.com  Mon Jul 15 11:56:11 2013
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A20A021E8126 for <ietf@ietfa.amsl.com>; Mon, 15 Jul 2013 11:56:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.425
X-Spam-Level: 
X-Spam-Status: No, score=-102.425 tagged_above=-999 required=5 tests=[AWL=0.174, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QYKTB-yeAv0s for <ietf@ietfa.amsl.com>; Mon, 15 Jul 2013 11:56:03 -0700 (PDT)
Received: from mail-qe0-x22f.google.com (mail-qe0-x22f.google.com [IPv6:2607:f8b0:400d:c02::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 928FD11E8214 for <ietf@ietf.org>; Mon, 15 Jul 2013 11:55:49 -0700 (PDT)
Received: by mail-qe0-f47.google.com with SMTP id 1so6643606qec.20 for <ietf@ietf.org>; Mon, 15 Jul 2013 11:55:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=bu7Pim6IuPIIaxM0lzK47AaGqHFZrIE8yxFH/oAI79Q=; b=NHFiKkKJ/bVb9jhzFGKgcs1tDPPYum5ydv34+RnwcMAxIpJNTj9bLzeflKa61TiELn Q/NBFB/+9DtJ/GLgHNnReE2R5KP2umkF4MJxb7Pjebea18WvnJgesWmFiir11MZqWKpk X9QK5eyipPUbp8NHVsKPgqC+2LO9XVGPVe1+DwNHN895byc9Bb3Oe76f0aubc2ne11EU B6SyZg4YuG/lt3d3sjpaslWRUwxKuX7r/VrK0SnPq49UtUZ6bbf0SmWs/PJYXjqCHkU+ 0q3Y+j/WbmvkNqPrXT4fPBXEYZnfC9HZeVg2TV5Snc+6hG4ZNl2+4+C0hRPG1XDh81y1 DRUw==
X-Received: by 10.224.165.77 with SMTP id h13mr44656172qay.58.1373914549004; Mon, 15 Jul 2013 11:55:49 -0700 (PDT)
Received: from [172.16.224.219] ([209.97.127.34]) by mx.google.com with ESMTPSA id 11sm56959740qek.1.2013.07.15.11.55.44 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 15 Jul 2013 11:55:45 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Sunday IAOC Overview Session at the Berlin IETF
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <2671C6CDFBB59E47B64C10B3E0BD5923043882B3AE@PRVPEXVS15.corp.twcable.com>
Date: Mon, 15 Jul 2013 11:55:42 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <6033B1DB-8517-4915-BBAE-35718BFC3FE4@gmail.com>
References: <20130712205852.10265.88487.idtracker@ietfa.amsl.com> <2671C6CDFBB59E47B64C10B3E0BD5923043882B3AE@PRVPEXVS15.corp.twcable.com>
To: "George, Wes" <wesley.george@twcable.com>
X-Mailer: Apple Mail (2.1508)
Cc: Bob Hinden <bob.hinden@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Jul 2013 18:56:11 -0000

Wes,

On Jul 15, 2013, at 5:13 AM, "George, Wes" <wesley.george@twcable.com> =
wrote:

>> The IETF Administrative Oversight Committee (IAOC) will hold a =
session
>> from 1500-1650 in
>> Potsdam 1 at the Berlin IETF on Sunday July 28, 2013.  The purpose is =
to
>> provide an
>> overview of the IAOC to allow the community to better understand what
>> the IAOC does, how
>> the finances work, venue selection, and provide the IAOC feedback on =
the
>> job they are
>> doing.
>=20
> [WEG] After Orlando, there was feedback from multiple folks (myself =
included) requesting that this session *NOT* be scheduled opposite the =
Newcomers' meet and greet, since that means that most of the folks who =
might want to see this but have leadership/mentorship duties must leave =
the session early. Could this be moved to the earlier time slot? If not, =
can you at least do the content in the reverse order from the Orlando =
session so that between the two, those who have to leave after an hour =
have a mostly complete view between this session and the previous one?
>=20

We checked and it appears to be possible to move it to 1pm.  This will =
conflict with the 1pm sessions (Newcomers Orientation and Tools for ID), =
but would avoid the Newcomers' meet and greet.  There isn't a perfect =
solution, unless there are objections we will move it.

Thanks,
Bob



From bob.hinden@gmail.com  Mon Jul 15 12:55:50 2013
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7E3311E822F for <ietf@ietfa.amsl.com>; Mon, 15 Jul 2013 12:55:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.46
X-Spam-Level: 
X-Spam-Status: No, score=-102.46 tagged_above=-999 required=5 tests=[AWL=0.139, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lPI-W1uiXcZ4 for <ietf@ietfa.amsl.com>; Mon, 15 Jul 2013 12:55:50 -0700 (PDT)
Received: from mail-qe0-x22f.google.com (mail-qe0-x22f.google.com [IPv6:2607:f8b0:400d:c02::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 1818411E81E8 for <ietf@ietf.org>; Mon, 15 Jul 2013 12:55:48 -0700 (PDT)
Received: by mail-qe0-f47.google.com with SMTP id 1so6683901qec.20 for <ietf@ietf.org>; Mon, 15 Jul 2013 12:55:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=Ex7ANMbsjPtKXe0V5pV4GUNsptb263TOcyTi+KZBGiA=; b=Ty2mLqZ4umGh6YXyv/MHMhVlCnoO7kHkUZ+OfOEq+efisOO6N6Qtapp+q7BMCj7NO2 SakF73xgEAGYExqO8JxB1MIc3p3uGDo1jqZEr23xvkKNX7Y8lnB+IGF0eH3717EyzBn4 aEkyOAJ3yNTIQOV7Sy7M3kYxx8Pl+B33j7W/8lCp3biNLKQ8xPJZ60pUHvX7MHENcwBD LvylUd1mxWjDHwBPi5hC6U4sMZ64zcGDONK/kMcFbzug/+OhCGxE43YhQpBF7aRF2dE1 81kkqHkg8ddXsyxPM06/gVLAkgbDg/3zCtliJkMKtcHwsts15qrNbolMNyZo3ThnvmkU mcIA==
X-Received: by 10.49.26.35 with SMTP id i3mr52603677qeg.75.1373918148392; Mon, 15 Jul 2013 12:55:48 -0700 (PDT)
Received: from [172.16.224.219] ([209.97.127.34]) by mx.google.com with ESMTPSA id ng3sm57234288qeb.0.2013.07.15.12.55.45 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 15 Jul 2013 12:55:46 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Sunday IAOC Overview Session at the Berlin IETF
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <CADnDZ8-Gx_=rL7g-0MDSLqXRDmgH5mBP1gu-3vCF_Ng66kncGA@mail.gmail.com>
Date: Mon, 15 Jul 2013 12:55:43 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <3DFDE06F-EAAA-4AA0-8DF4-AC2033C644D7@gmail.com>
References: <20130712205852.10265.88487.idtracker@ietfa.amsl.com> <CADnDZ8-Gx_=rL7g-0MDSLqXRDmgH5mBP1gu-3vCF_Ng66kncGA@mail.gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
X-Mailer: Apple Mail (2.1508)
Cc: Bob Hinden <bob.hinden@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Jul 2013 19:55:50 -0000

AB,

>=20
> IMO the questions/comments that may be ok to see added to discuss are:
>=20
> 1) Venue selection and operation of the IETF meetings
> ++++++++++++++++
> - Selection of the current venue and was there difficulties until
> getting to this meeting session time. =46rom the managing meeting
> (providing services) and the community use of the meeting. (10 minute
> discuss if needed).

I don't understand your question, please clarify.

Note that the IAOC selects the venue, provides the network, contracts =
with the hotel, etc., it is the IESG who is responsible for the agenda =
for the meeting, agenda planning, etc.

>=20
> - Is there an alternative venue if the venue was closed for any
> emergency reason at any time? or only one plan so if the plan changes
> there can be problems with the communities expected plan because they
> were not aware of the needed information per time.

No, there is not an alternative venue under contract.  It isn't =
practical to have two venues under contract, build two networks, etc.  =
It is technically feasable, but would cause the registration fee to go =
up significantly to cover the extra costs. =20

If there was, for example, a fire at a venue months before the the =
meeting we would look for an alternate, but what happens would depend on =
availability of alternative venues.  We have good relationships with the =
hotel chains we use and they would work very hard to find an alternative =
venue, as would the effected venue.

>=20
> - Is there an historic/informational RFC issued by IAOC of
> difficulties or important comments in past of venues attended?


No.  There is an extensive record of comments about venue on the =
attendees list for individual meetings and the IAOC reports to the =
community.  Also, meeting surveys with community feedback: =
http://iaoc.ietf.org/surveys.html

>=20
> - Regarding advice within emergency situations (in or out the meeting
> venue), is it considered within chosing the managing meeting
> plan/venue, and is the emergency solution an available information for
> attended participants and who will attend within a meeting day.

Assuming you mean while the meeting is taking place, the secretariat and =
venue have emergency plans in place.  The secretariat discuses safety =
and emergency medial procedures with the venue to be prepared if =
anything should happen.


>=20
> - Someone may like to know if is going to attend at a meeting, how is
> the meeting venue managed per time slots, is there a way of quick
> feedback/communication of registered-community for meetings (you may
> say IETF list but are they connected). The information availability
> can be used for others not attended and whom may attend at any time.
> (the venue ran out of coffee/water, so I may buy one while going to
> venue, or any other issue which can happen out of expected/plan).

The IETF meeting agenda is managed by the IESG. =20

Problems with the meeting venue can be reported to the Meeting Trouble =
Desk at mtd@ietf.org.  Problems with the network can be reported to the =
NOC at noc@ietf.org.


>=20
> 2) Other issue:
> +++++++++
> -Is there a future work plan milestones discussed? can be added to [*]


Not sure what your are asking about, but future meetings are posted on =
the IETF web site and the process and timeline for meeting planning is =
part of the IAOC overview presentation.



> -I am not sure if was discussed before and answered (I am sorry if
> repeated), where do I go to find important past/current Q&A for IAOC
> (to avoid efforts to be wasted, and unite best answers)? if not
> available it can be good to find it at [*].

Recent plenaries reports and the last IAOC overview session have been =
recored by Meetecho.  The last IAOC overview is on the main page at =
http://iaoc.ietf.org.  Also, plenary proceedings and jabber logs in the =
usual places, for example http://iaoc.ietf.org/plenary-reports.html

Bob


>=20
> [*] http://iaoc.ietf.org/
>=20
> AB



From yaojk@cnnic.cn  Mon Jul 15 20:52:41 2013
Return-Path: <yaojk@cnnic.cn>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A59E21E818C for <ietf@ietfa.amsl.com>; Mon, 15 Jul 2013 20:52:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.195
X-Spam-Level: 
X-Spam-Status: No, score=-100.195 tagged_above=-999 required=5 tests=[AWL=0.650, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A9Gf4VKGROMk for <ietf@ietfa.amsl.com>; Mon, 15 Jul 2013 20:52:35 -0700 (PDT)
Received: from cnnic.cn (smtp.cnnic.cn [218.241.118.7]) by ietfa.amsl.com (Postfix) with SMTP id 02C5E21E8186 for <ietf@ietf.org>; Mon, 15 Jul 2013 20:52:33 -0700 (PDT)
X-EYOUMAIL-SMTPAUTH: yaojk@cnnic.cn
Received: from unknown127.0.0.1 (HELO healthyao-think) (127.0.0.1) by 127.0.0.1 with SMTP; Tue, 16 Jul 2013 11:52:20 +0800
Date: Tue, 16 Jul 2013 11:52:20 +0800
From: "Jiankang Yao" <yaojk@cnnic.cn>
To: dcrocker <dcrocker@bbiw.net>,  ietf <ietf@ietf.org>
Subject: Re: Re: IAB Statement on Dotless Domains
References: <1984CBB8-6862-4DBB-AFAE-F8461E694083@vigilsec.com>,  <51DDD49E.5090406@dcrocker.net>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.0.1.92[cn]
Mime-Version: 1.0
Message-ID: <20130716115201041762118@cnnic.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart088867746748_=----"
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: yaojk <yaojk@cnnic.cn>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jul 2013 03:52:42 -0000

This is a multi-part message in MIME format.

------=_001_NextPart088867746748_=----
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: base64

SSBzdWJtaXR0ZWQgYSBkcmFmdCByZWxhdGVkIHRvIHRoaXMgaXNzdWUgbGFzdCB5ZWFyLg0KDQpo
dHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC15YW8tZG5zb3AtdGxkLW5hbWVzLTAwICAN
Cg0KDQpJbiB0aGlzIGRyYWZ0LCBJIGNhbGxlZCB0aGlzIGtpbmQgb2YgbmFtZXMgYXMgVExEIG5h
bWVzICBpbnN0ZWFkIG9mIGRvdGxlc3MgZG9tYWlucy4NCg0KDQoNCg0KSmlhbmthbmcgWWFvDQoN
CkZyb206IERhdmUgQ3JvY2tlcg0KRGF0ZTogMjAxMy0wNy0xMSAwNTozOQ0KVG86IGlldGYNCkND
OiBJRVRGIERpc2N1c3Npb24NClN1YmplY3Q6IFJlOiBJQUIgU3RhdGVtZW50IG9uIERvdGxlc3Mg
RG9tYWlucw0KT24gNy8xMC8yMDEzIDExOjU5IEFNLCBSdXNzIEhvdXNsZXkgd3JvdGU6DQo+IFRo
ZSBJQUIgaGFzIG1hZGUgYSBzdGF0ZW1lbnQgb24gZG90bGVzcyBkb21haW5zLiAgWW91IGNhbiBm
aW5kIHRoaXMgc3RhdGVtZW50IGhlcmU6DQo+IGh0dHA6Ly93d3cuaWFiLm9yZy9kb2N1bWVudHMv
Y29ycmVzcG9uZGVuY2UtcmVwb3J0cy1kb2N1bWVudHMvMjAxMy0yL2lhYi1zdGF0ZW1lbnQtZG90
bGVzcy1kb21haW5zLWNvbnNpZGVyZWQtaGFybWZ1bC8NCg0KDQpJdCdzIHVuZm9ydHVuYXRlIHRo
YXQgdGhlIElBQiBkaWQgbm90IGNob29zZSB0byBjaXJjdWxhdGUgYSBkcmFmdCBiZWZvcmUgDQpy
ZWxlYXNpbmcgdGhlIFN0YXRlbWVudC4gIFRoZSBTdGF0ZW1lbnQgY291bGQgaGF2ZSBiZWVuIG1h
ZGUgYSBiaXQgDQpzdHJvbmdlciBpbiB0aGUgY29uY2VybiBpdCBleHByZXNzZXMuDQoNClRoZXJl
J3MgYmVlbiBhIHNlcGFyYXRlIGRpc2N1c3Npb24gb24gdGhlIFNNVFAgbWFpbGluZyBsaXN0IGFi
b3V0IHRoZSANCklDQU5OIFNTQUMgcmVwb3J0IG9uIHRoZSB0b3BpYyBvZiBkb3RsZXNzIGRvbWFp
bnMuDQoNClRoZSByZXBvcnQgY29ycmVjdGx5IG5vdGVzIHRoYXQgdGhlcmUgYXJlIGFsc28gZW1h
aWwgYmFycmllcnMgdG8gdGhlIHVzZSANCm9mIGRvdGxlc3MgZG9tYWlucy4NCg0KVGhlIHJlcG9y
dCBpbmNvcnJlY3RseSBhdHRyaWJ1dGVzIHRoZXNlIHRvIHRoZSBlbWFpbCBzdGFuZGFyZHMsIHdo
aWNoIGRvIA0Kbm90IHByb2hpYml0IHRoZSB1c2UuICAoVG8gYmUgZmFpciB0aGUgZm9ybWF0IHN0
YW5kYXJkIFJGQyAyODIyLCB3aGljaCANCndhcyBpbiBmb3JjZSBmb3IgYSBudW1iZXIgb2YgeWVh
cnMsIGRpZCBoYXZlIHRoZSBwcm9oaWJpdGlvbiwgYnV0IA0KbmVpdGhlciBpdHMgcHJlZGVjZXNz
b3Igbm9yIGl0cyBzdWNjZXNzb3IgLS0gdGhlIGN1cnJlbnQgc3RhbmRhcmQgDQpSRkM1MzIyIC0t
IGNhcnJ5IHRoZSBsaW1pdGF0aW9uLikNCg0KUmF0aGVyLCB0aGUgU01UUCBtYWlsaW5nIGxpc3Qg
Y29uZmlybWVkIGNvbW1vbiBzb2Z0d2FyZSBpbXBsZW1lbnRhdGlvbiANCmJhcnJpZXJzLCBzb21l
dGltZXMgZHVlIHRvIHRoZSBETlMtcmVsYXRlZCBzdHJpY3R1cmUuDQoNCk1vcmUgaW50ZXJlc3Rp
bmcgd2VyZSBvdGhlciBjb25jZXJucyBhYm91dCBwb3NzaWJsZSBhdHRhY2tzIGFuZCANCmNvbmZp
Z3VyYXRpb24gZXJyb3JzLiAgVGhlIGV4YW1wbGUgb2YgbG9jYWxob3N0IHdhcyBjaXRlZC4NCg0K
ZC8NCg0KLS0gDQpEYXZlIENyb2NrZXINCkJyYW5kZW5idXJnIEludGVybmV0V29ya2luZw0KYmJp
dy5uZXQ=

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" http-equiv=3DContent-Typ=
e>
<STYLE>
BLOCKQUOTE {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; MARGIN-LEFT: 2em
}
OL {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
UL {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
BODY {
	LINE-HEIGHT: 1.5; FONT-FAMILY: verdana; COLOR: #000000; FONT-SIZE: 10pt
}
P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</STYLE>

<META name=3DGENERATOR content=3D"MSHTML 8.00.7601.18170"></HEAD>
<BODY style=3D"MARGIN: 10px">
<DIV style=3D"FONT-FAMILY: Verdana">I submitted a draft related to this is=
sue last=20
year.</DIV>
<DIV style=3D"FONT-FAMILY: Verdana">&nbsp;</DIV>
<DIV style=3D"FONT-FAMILY: Verdana"><A=20
href=3D"http://tools.ietf.org/html/draft-yao-dnsop-tld-names-00">http://to=
ols.ietf.org/html/draft-yao-dnsop-tld-names-00</A>&nbsp;=20
</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>In this draft, I called this kind of names as TLD names&nbsp; instead=
 of=20
dotless domains.</DIV>
<DIV>&nbsp;</DIV>
<HR style=3D"WIDTH: 210px; HEIGHT: 1px" align=3Dleft color=3D#b5c4df SIZE=
=3D1>

<DIV style=3D"FONT-FAMILY: Verdana"><SPAN>Jiankang Yao</SPAN></DIV>
<DIV>&nbsp;</DIV>
<DIV=20
style=3D"BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOT=
TOM: 0cm; PADDING-LEFT: 0cm; PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4df 1pt s=
olid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<DIV=20
style=3D"PADDING-BOTTOM: 8px; PADDING-LEFT: 8px; PADDING-RIGHT: 8px; BACKG=
ROUND: #efefef; COLOR: #000000; FONT-SIZE: 12px; PADDING-TOP: 8px">
<DIV><B>From:</B>&nbsp;<A href=3D"mailto:dhc@dcrocker.net">Dave Crocker</A=
></DIV>
<DIV><B>Date:</B>&nbsp;2013-07-11&nbsp;05:39</DIV>
<DIV><B>To:</B>&nbsp;<A href=3D"mailto:ietf@ietf.org">ietf</A></DIV>
<DIV><B>CC:</B>&nbsp;<A href=3D"mailto:ietf@ietf.org">IETF Discussion</A><=
/DIV>
<DIV><B>Subject:</B>&nbsp;Re: IAB Statement on Dotless Domains</DIV></DIV>=
</DIV>
<DIV>
<DIV>On&nbsp;7/10/2013&nbsp;11:59&nbsp;AM,&nbsp;Russ&nbsp;Housley&nbsp;wro=
te:</DIV>
<DIV>&gt;&nbsp;The&nbsp;IAB&nbsp;has&nbsp;made&nbsp;a&nbsp;statement&nbsp;=
on&nbsp;dotless&nbsp;domains.&nbsp;&nbsp;You&nbsp;can&nbsp;find&nbsp;this&=
nbsp;statement&nbsp;here:</DIV>
<DIV>&gt;&nbsp;http://www.iab.org/documents/correspondence-reports-documen=
ts/2013-2/iab-statement-dotless-domains-considered-harmful/</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>It's&nbsp;unfortunate&nbsp;that&nbsp;the&nbsp;IAB&nbsp;did&nbsp;not&n=
bsp;choose&nbsp;to&nbsp;circulate&nbsp;a&nbsp;draft&nbsp;before&nbsp;</DIV=
>
<DIV>releasing&nbsp;the&nbsp;Statement.&nbsp;&nbsp;The&nbsp;Statement&nbsp=
;could&nbsp;have&nbsp;been&nbsp;made&nbsp;a&nbsp;bit&nbsp;</DIV>
<DIV>stronger&nbsp;in&nbsp;the&nbsp;concern&nbsp;it&nbsp;expresses.</DIV>
<DIV>&nbsp;</DIV>
<DIV>There's&nbsp;been&nbsp;a&nbsp;separate&nbsp;discussion&nbsp;on&nbsp;t=
he&nbsp;SMTP&nbsp;mailing&nbsp;list&nbsp;about&nbsp;the&nbsp;</DIV>
<DIV>ICANN&nbsp;SSAC&nbsp;report&nbsp;on&nbsp;the&nbsp;topic&nbsp;of&nbsp;=
dotless&nbsp;domains.</DIV>
<DIV>&nbsp;</DIV>
<DIV>The&nbsp;report&nbsp;correctly&nbsp;notes&nbsp;that&nbsp;there&nbsp;a=
re&nbsp;also&nbsp;email&nbsp;barriers&nbsp;to&nbsp;the&nbsp;use&nbsp;</DIV=
>
<DIV>of&nbsp;dotless&nbsp;domains.</DIV>
<DIV>&nbsp;</DIV>
<DIV>The&nbsp;report&nbsp;incorrectly&nbsp;attributes&nbsp;these&nbsp;to&n=
bsp;the&nbsp;email&nbsp;standards,&nbsp;which&nbsp;do&nbsp;</DIV>
<DIV>not&nbsp;prohibit&nbsp;the&nbsp;use.&nbsp;&nbsp;(To&nbsp;be&nbsp;fair=
&nbsp;the&nbsp;format&nbsp;standard&nbsp;RFC&nbsp;2822,&nbsp;which&nbsp;</=
DIV>
<DIV>was&nbsp;in&nbsp;force&nbsp;for&nbsp;a&nbsp;number&nbsp;of&nbsp;years=
,&nbsp;did&nbsp;have&nbsp;the&nbsp;prohibition,&nbsp;but&nbsp;</DIV>
<DIV>neither&nbsp;its&nbsp;predecessor&nbsp;nor&nbsp;its&nbsp;successor&nb=
sp;--&nbsp;the&nbsp;current&nbsp;standard&nbsp;</DIV>
<DIV>RFC5322&nbsp;--&nbsp;carry&nbsp;the&nbsp;limitation.)</DIV>
<DIV>&nbsp;</DIV>
<DIV>Rather,&nbsp;the&nbsp;SMTP&nbsp;mailing&nbsp;list&nbsp;confirmed&nbsp=
;common&nbsp;software&nbsp;implementation&nbsp;</DIV>
<DIV>barriers,&nbsp;sometimes&nbsp;due&nbsp;to&nbsp;the&nbsp;DNS-related&n=
bsp;stricture.</DIV>
<DIV>&nbsp;</DIV>
<DIV>More&nbsp;interesting&nbsp;were&nbsp;other&nbsp;concerns&nbsp;about&n=
bsp;possible&nbsp;attacks&nbsp;and&nbsp;</DIV>
<DIV>configuration&nbsp;errors.&nbsp;&nbsp;The&nbsp;example&nbsp;of&nbsp;l=
ocalhost&nbsp;was&nbsp;cited.</DIV>
<DIV>&nbsp;</DIV>
<DIV>d/</DIV>
<DIV>&nbsp;</DIV>
<DIV>--&nbsp;</DIV>
<DIV>Dave&nbsp;Crocker</DIV>
<DIV>Brandenburg&nbsp;InternetWorking</DIV>
<DIV>bbiw.net</DIV></DIV></BODY></HTML>

------=_001_NextPart088867746748_=------


From yaojk@cnnic.cn  Mon Jul 15 20:52:41 2013
Return-Path: <yaojk@cnnic.cn>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A55521E818A for <ietf@ietfa.amsl.com>; Mon, 15 Jul 2013 20:52:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.545
X-Spam-Level: 
X-Spam-Status: No, score=-99.545 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pHEQalEmmi8M for <ietf@ietfa.amsl.com>; Mon, 15 Jul 2013 20:52:35 -0700 (PDT)
Received: from cnnic.cn (smtp.cnnic.cn [218.241.118.7]) by ietfa.amsl.com (Postfix) with SMTP id 02B3121E8168 for <ietf@ietf.org>; Mon, 15 Jul 2013 20:52:33 -0700 (PDT)
X-EYOUMAIL-SMTPAUTH: yaojk@cnnic.cn
Received: from unknown127.0.0.1 (HELO healthyao-think) (127.0.0.1) by 127.0.0.1 with SMTP; Tue, 16 Jul 2013 11:52:20 +0800
Date: Tue, 16 Jul 2013 11:52:20 +0800
From: "Jiankang Yao" <yaojk@cnnic.cn>
To: dcrocker <dcrocker@bbiw.net>,  ietf <ietf@ietf.org>
Subject: Re: Re: IAB Statement on Dotless Domains
References: <1984CBB8-6862-4DBB-AFAE-F8461E694083@vigilsec.com>,  <51DDD49E.5090406@dcrocker.net>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.0.1.92[cn]
Mime-Version: 1.0
Message-ID: <20130716115201041762118@cnnic.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart088867746748_=----"
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: yaojk <yaojk@cnnic.cn>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jul 2013 03:52:42 -0000

This is a multi-part message in MIME format.

------=_001_NextPart088867746748_=----
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: base64

SSBzdWJtaXR0ZWQgYSBkcmFmdCByZWxhdGVkIHRvIHRoaXMgaXNzdWUgbGFzdCB5ZWFyLg0KDQpo
dHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC15YW8tZG5zb3AtdGxkLW5hbWVzLTAwICAN
Cg0KDQpJbiB0aGlzIGRyYWZ0LCBJIGNhbGxlZCB0aGlzIGtpbmQgb2YgbmFtZXMgYXMgVExEIG5h
bWVzICBpbnN0ZWFkIG9mIGRvdGxlc3MgZG9tYWlucy4NCg0KDQoNCg0KSmlhbmthbmcgWWFvDQoN
CkZyb206IERhdmUgQ3JvY2tlcg0KRGF0ZTogMjAxMy0wNy0xMSAwNTozOQ0KVG86IGlldGYNCkND
OiBJRVRGIERpc2N1c3Npb24NClN1YmplY3Q6IFJlOiBJQUIgU3RhdGVtZW50IG9uIERvdGxlc3Mg
RG9tYWlucw0KT24gNy8xMC8yMDEzIDExOjU5IEFNLCBSdXNzIEhvdXNsZXkgd3JvdGU6DQo+IFRo
ZSBJQUIgaGFzIG1hZGUgYSBzdGF0ZW1lbnQgb24gZG90bGVzcyBkb21haW5zLiAgWW91IGNhbiBm
aW5kIHRoaXMgc3RhdGVtZW50IGhlcmU6DQo+IGh0dHA6Ly93d3cuaWFiLm9yZy9kb2N1bWVudHMv
Y29ycmVzcG9uZGVuY2UtcmVwb3J0cy1kb2N1bWVudHMvMjAxMy0yL2lhYi1zdGF0ZW1lbnQtZG90
bGVzcy1kb21haW5zLWNvbnNpZGVyZWQtaGFybWZ1bC8NCg0KDQpJdCdzIHVuZm9ydHVuYXRlIHRo
YXQgdGhlIElBQiBkaWQgbm90IGNob29zZSB0byBjaXJjdWxhdGUgYSBkcmFmdCBiZWZvcmUgDQpy
ZWxlYXNpbmcgdGhlIFN0YXRlbWVudC4gIFRoZSBTdGF0ZW1lbnQgY291bGQgaGF2ZSBiZWVuIG1h
ZGUgYSBiaXQgDQpzdHJvbmdlciBpbiB0aGUgY29uY2VybiBpdCBleHByZXNzZXMuDQoNClRoZXJl
J3MgYmVlbiBhIHNlcGFyYXRlIGRpc2N1c3Npb24gb24gdGhlIFNNVFAgbWFpbGluZyBsaXN0IGFi
b3V0IHRoZSANCklDQU5OIFNTQUMgcmVwb3J0IG9uIHRoZSB0b3BpYyBvZiBkb3RsZXNzIGRvbWFp
bnMuDQoNClRoZSByZXBvcnQgY29ycmVjdGx5IG5vdGVzIHRoYXQgdGhlcmUgYXJlIGFsc28gZW1h
aWwgYmFycmllcnMgdG8gdGhlIHVzZSANCm9mIGRvdGxlc3MgZG9tYWlucy4NCg0KVGhlIHJlcG9y
dCBpbmNvcnJlY3RseSBhdHRyaWJ1dGVzIHRoZXNlIHRvIHRoZSBlbWFpbCBzdGFuZGFyZHMsIHdo
aWNoIGRvIA0Kbm90IHByb2hpYml0IHRoZSB1c2UuICAoVG8gYmUgZmFpciB0aGUgZm9ybWF0IHN0
YW5kYXJkIFJGQyAyODIyLCB3aGljaCANCndhcyBpbiBmb3JjZSBmb3IgYSBudW1iZXIgb2YgeWVh
cnMsIGRpZCBoYXZlIHRoZSBwcm9oaWJpdGlvbiwgYnV0IA0KbmVpdGhlciBpdHMgcHJlZGVjZXNz
b3Igbm9yIGl0cyBzdWNjZXNzb3IgLS0gdGhlIGN1cnJlbnQgc3RhbmRhcmQgDQpSRkM1MzIyIC0t
IGNhcnJ5IHRoZSBsaW1pdGF0aW9uLikNCg0KUmF0aGVyLCB0aGUgU01UUCBtYWlsaW5nIGxpc3Qg
Y29uZmlybWVkIGNvbW1vbiBzb2Z0d2FyZSBpbXBsZW1lbnRhdGlvbiANCmJhcnJpZXJzLCBzb21l
dGltZXMgZHVlIHRvIHRoZSBETlMtcmVsYXRlZCBzdHJpY3R1cmUuDQoNCk1vcmUgaW50ZXJlc3Rp
bmcgd2VyZSBvdGhlciBjb25jZXJucyBhYm91dCBwb3NzaWJsZSBhdHRhY2tzIGFuZCANCmNvbmZp
Z3VyYXRpb24gZXJyb3JzLiAgVGhlIGV4YW1wbGUgb2YgbG9jYWxob3N0IHdhcyBjaXRlZC4NCg0K
ZC8NCg0KLS0gDQpEYXZlIENyb2NrZXINCkJyYW5kZW5idXJnIEludGVybmV0V29ya2luZw0KYmJp
dy5uZXQ=

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" http-equiv=3DContent-Typ=
e>
<STYLE>
BLOCKQUOTE {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; MARGIN-LEFT: 2em
}
OL {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
UL {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
BODY {
	LINE-HEIGHT: 1.5; FONT-FAMILY: verdana; COLOR: #000000; FONT-SIZE: 10pt
}
P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</STYLE>

<META name=3DGENERATOR content=3D"MSHTML 8.00.7601.18170"></HEAD>
<BODY style=3D"MARGIN: 10px">
<DIV style=3D"FONT-FAMILY: Verdana">I submitted a draft related to this is=
sue last=20
year.</DIV>
<DIV style=3D"FONT-FAMILY: Verdana">&nbsp;</DIV>
<DIV style=3D"FONT-FAMILY: Verdana"><A=20
href=3D"http://tools.ietf.org/html/draft-yao-dnsop-tld-names-00">http://to=
ols.ietf.org/html/draft-yao-dnsop-tld-names-00</A>&nbsp;=20
</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>In this draft, I called this kind of names as TLD names&nbsp; instead=
 of=20
dotless domains.</DIV>
<DIV>&nbsp;</DIV>
<HR style=3D"WIDTH: 210px; HEIGHT: 1px" align=3Dleft color=3D#b5c4df SIZE=
=3D1>

<DIV style=3D"FONT-FAMILY: Verdana"><SPAN>Jiankang Yao</SPAN></DIV>
<DIV>&nbsp;</DIV>
<DIV=20
style=3D"BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOT=
TOM: 0cm; PADDING-LEFT: 0cm; PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4df 1pt s=
olid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<DIV=20
style=3D"PADDING-BOTTOM: 8px; PADDING-LEFT: 8px; PADDING-RIGHT: 8px; BACKG=
ROUND: #efefef; COLOR: #000000; FONT-SIZE: 12px; PADDING-TOP: 8px">
<DIV><B>From:</B>&nbsp;<A href=3D"mailto:dhc@dcrocker.net">Dave Crocker</A=
></DIV>
<DIV><B>Date:</B>&nbsp;2013-07-11&nbsp;05:39</DIV>
<DIV><B>To:</B>&nbsp;<A href=3D"mailto:ietf@ietf.org">ietf</A></DIV>
<DIV><B>CC:</B>&nbsp;<A href=3D"mailto:ietf@ietf.org">IETF Discussion</A><=
/DIV>
<DIV><B>Subject:</B>&nbsp;Re: IAB Statement on Dotless Domains</DIV></DIV>=
</DIV>
<DIV>
<DIV>On&nbsp;7/10/2013&nbsp;11:59&nbsp;AM,&nbsp;Russ&nbsp;Housley&nbsp;wro=
te:</DIV>
<DIV>&gt;&nbsp;The&nbsp;IAB&nbsp;has&nbsp;made&nbsp;a&nbsp;statement&nbsp;=
on&nbsp;dotless&nbsp;domains.&nbsp;&nbsp;You&nbsp;can&nbsp;find&nbsp;this&=
nbsp;statement&nbsp;here:</DIV>
<DIV>&gt;&nbsp;http://www.iab.org/documents/correspondence-reports-documen=
ts/2013-2/iab-statement-dotless-domains-considered-harmful/</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>It's&nbsp;unfortunate&nbsp;that&nbsp;the&nbsp;IAB&nbsp;did&nbsp;not&n=
bsp;choose&nbsp;to&nbsp;circulate&nbsp;a&nbsp;draft&nbsp;before&nbsp;</DIV=
>
<DIV>releasing&nbsp;the&nbsp;Statement.&nbsp;&nbsp;The&nbsp;Statement&nbsp=
;could&nbsp;have&nbsp;been&nbsp;made&nbsp;a&nbsp;bit&nbsp;</DIV>
<DIV>stronger&nbsp;in&nbsp;the&nbsp;concern&nbsp;it&nbsp;expresses.</DIV>
<DIV>&nbsp;</DIV>
<DIV>There's&nbsp;been&nbsp;a&nbsp;separate&nbsp;discussion&nbsp;on&nbsp;t=
he&nbsp;SMTP&nbsp;mailing&nbsp;list&nbsp;about&nbsp;the&nbsp;</DIV>
<DIV>ICANN&nbsp;SSAC&nbsp;report&nbsp;on&nbsp;the&nbsp;topic&nbsp;of&nbsp;=
dotless&nbsp;domains.</DIV>
<DIV>&nbsp;</DIV>
<DIV>The&nbsp;report&nbsp;correctly&nbsp;notes&nbsp;that&nbsp;there&nbsp;a=
re&nbsp;also&nbsp;email&nbsp;barriers&nbsp;to&nbsp;the&nbsp;use&nbsp;</DIV=
>
<DIV>of&nbsp;dotless&nbsp;domains.</DIV>
<DIV>&nbsp;</DIV>
<DIV>The&nbsp;report&nbsp;incorrectly&nbsp;attributes&nbsp;these&nbsp;to&n=
bsp;the&nbsp;email&nbsp;standards,&nbsp;which&nbsp;do&nbsp;</DIV>
<DIV>not&nbsp;prohibit&nbsp;the&nbsp;use.&nbsp;&nbsp;(To&nbsp;be&nbsp;fair=
&nbsp;the&nbsp;format&nbsp;standard&nbsp;RFC&nbsp;2822,&nbsp;which&nbsp;</=
DIV>
<DIV>was&nbsp;in&nbsp;force&nbsp;for&nbsp;a&nbsp;number&nbsp;of&nbsp;years=
,&nbsp;did&nbsp;have&nbsp;the&nbsp;prohibition,&nbsp;but&nbsp;</DIV>
<DIV>neither&nbsp;its&nbsp;predecessor&nbsp;nor&nbsp;its&nbsp;successor&nb=
sp;--&nbsp;the&nbsp;current&nbsp;standard&nbsp;</DIV>
<DIV>RFC5322&nbsp;--&nbsp;carry&nbsp;the&nbsp;limitation.)</DIV>
<DIV>&nbsp;</DIV>
<DIV>Rather,&nbsp;the&nbsp;SMTP&nbsp;mailing&nbsp;list&nbsp;confirmed&nbsp=
;common&nbsp;software&nbsp;implementation&nbsp;</DIV>
<DIV>barriers,&nbsp;sometimes&nbsp;due&nbsp;to&nbsp;the&nbsp;DNS-related&n=
bsp;stricture.</DIV>
<DIV>&nbsp;</DIV>
<DIV>More&nbsp;interesting&nbsp;were&nbsp;other&nbsp;concerns&nbsp;about&n=
bsp;possible&nbsp;attacks&nbsp;and&nbsp;</DIV>
<DIV>configuration&nbsp;errors.&nbsp;&nbsp;The&nbsp;example&nbsp;of&nbsp;l=
ocalhost&nbsp;was&nbsp;cited.</DIV>
<DIV>&nbsp;</DIV>
<DIV>d/</DIV>
<DIV>&nbsp;</DIV>
<DIV>--&nbsp;</DIV>
<DIV>Dave&nbsp;Crocker</DIV>
<DIV>Brandenburg&nbsp;InternetWorking</DIV>
<DIV>bbiw.net</DIV></DIV></BODY></HTML>

------=_001_NextPart088867746748_=------


From dougb@dougbarton.us  Mon Jul 15 22:39:03 2013
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8611B11E8231 for <ietf@ietfa.amsl.com>; Mon, 15 Jul 2013 22:39:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.511
X-Spam-Level: 
X-Spam-Status: No, score=-2.511 tagged_above=-999 required=5 tests=[AWL=0.088,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B3yHjtwMJEhH for <ietf@ietfa.amsl.com>; Mon, 15 Jul 2013 22:38:59 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [208.79.90.218]) by ietfa.amsl.com (Postfix) with ESMTP id C11BC11E821A for <ietf@ietf.org>; Mon, 15 Jul 2013 22:38:59 -0700 (PDT)
Received: from [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b] (unknown [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b]) by dougbarton.us (Postfix) with ESMTPSA id 7C4B522B2A; Tue, 16 Jul 2013 05:38:54 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1373953135; bh=j5VkKtDRCmopoK9Vk8x1S4YCMqmJkdz4UbqTbKxlzP4=; h=Date:From:To:CC:Subject:References:In-Reply-To; b=VFfaITJjtHbgKSzP0cbUroD3RvJCmCLLHlhA9S9pvspBTlqaoMP941Z62VERBtZrJ YqJAdLxmKtjKdrVkQFQ8iQwTkUEIBlpEBw3QWKdnzcP+q4IpI2M+O11k22o2l8LYJE uJ6xeHLQebNdz85JMdJquxId24TuVLyc+FcbL/HU=
Message-ID: <51E4DC6C.3040609@dougbarton.us>
Date: Mon, 15 Jul 2013 22:38:52 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: The case of dotless domains
References: <20130713152747.8F79D18C0D0@mercury.lcs.mit.edu> <51E18737.4080903@isdg.net> <3725D4B2-65DA-45FA-AAEE-309F45CD6F18@checkpoint.com> <51E2A8EE.5010200@isdg.net> <A0984871-D92D-4110-9001-16B363B65AC0@checkpoint.com> <6.2.5.6.2.20130714205140.0ce1f0b8@resistor.net>
In-Reply-To: <6.2.5.6.2.20130714205140.0ce1f0b8@resistor.net>
X-Enigmail-Version: 1.5.2
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Ofer Inbar <cos@aaaaa.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jul 2013 05:39:03 -0000

On 07/14/2013 10:05 PM, S Moonesamy wrote:
> At 06:53 14-07-2013, Yoav Nir wrote:
>> http://tools.ietf.org/html/draft-moonesamy-dotless-domains-00
>
> That memo discusses about the case of the dotless domains in terms of
> the technical standards.  Comments are welcome.

Interesting, but pardon my being blunt, it does not seem to cover any 
new ground. You did say one useful thing:

IETF specifications usually provide guidance to ensure interoperability. 
  Whether dotless domains are harmful or not is a policy matter.

> At 13:11 13-07-2013, Ofer Inbar wrote:
>> What this brings to mind is that we used to have implicit DNS domain
>> search in the early days of DNS.  When edu.com accidentally hijacked
>> a huge chunk of the Internet, most of the net very quickly got rid of
>> implicit search, and we got the explicit DNS search feature that many
>> people are discussing now.
>
> Yes.

Can you (or Ofer) define how you're using the terms "explicit" and 
"implicit" in terms of DNS search, and what their relevance is to the 
topic of dotless domains? And no, I'm not being snarky, I think part of 
the problem here is a fundamental misunderstanding of how the vast 
majority of hosts are configured currently.

>> If some new TLD gets used in a dotless fashion in a way that truly
>> does cause major trouble, I expect we'll see sites all over the net
>> quickly deploying DNS resolvers that discard A, AAAA, or MX records
>> at the top level, to protect their users.
>
> There is already deployed code to do that.

True, for better or worse. :)  BIND's implementation also starts off 
with a reasonable default list of delegation-only domains, and allows 
you to customize the list.

... which is an excellent example of market forces influencing software 
development.

> At 20:14 14-07-2013, Doug Barton wrote:
>> It is unarguably true that as things currently stand there will be
>> "problems" with dotless domains. How widespread, and how serious those
>> problems become is yet to be seen.
>
> I haven't seen anyone in the IETF arguing that sufficient market demand
> overrides comments about problems that will appear.

I haven't seen anyone in the IETF arguing that the moon is made of green 
cheese either. What does your comment have to do with anything? Sorry 
(again) to be blunt, but the IETF pounding the "this thing is bad!" drum 
is not a particularly effective tool. [1]

We have to be realistic about how and where our influence is relevant, 
and more importantly how and where it is not. Detailing the technical 
problems with the proposal is relevant IETF work, but that job has 
already been done more thoroughly by my esteemed former colleagues on 
the SSAC.

>> So either this is a good idea that will gain traction, and therefore
>> appropriate software support; or it is a bad idea that will go away on
>> its own. Either way, making a fuss
>
> It is up to those who decide to decide whether dotless domains is a good
> idea that will gain traction or a bad idea that will go away on it own.

You vastly overestimate your own importance in the grand scheme of 
things. Don't worry, it's a common human problem. :)  Rather than 
repeating my point for the third time, see what I wrote just above.

> At 20:25 14-07-2013, Dave Crocker wrote:
>> In contrast, assertions about "market demand" ensuring that "software
>> folks... will make them work" rests on a fuzzy concept of market
>> forces -- for example, the market of users isn't likely to be issuing
>> a formal or informal 'demand' about any of this, and a model of
>> altering installed-base behavior that has, I believe, has no
>> historical precedent.
>
> Yes.

I already explained why Dave's perspective is wrong in my previous 
message, which you apparently chose to ignore. Your example of 
delegation-only domains for DNS software further proves my point.

Doug

[1] cf. NAT


From jari.arkko@piuha.net  Mon Jul 15 23:24:14 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FBFA21F9DBE; Mon, 15 Jul 2013 23:24:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.562
X-Spam-Level: 
X-Spam-Status: No, score=-102.562 tagged_above=-999 required=5 tests=[AWL=0.037, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UEABjIvSuYk0; Mon, 15 Jul 2013 23:24:09 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 02F0921F9D09; Mon, 15 Jul 2013 23:24:09 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 4ED882CC53; Tue, 16 Jul 2013 09:24:08 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cufW7r3I3BaK; Tue, 16 Jul 2013 09:24:07 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id E5A002CC3C; Tue, 16 Jul 2013 09:24:05 +0300 (EEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-abfab-eapapplicability-05
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712983F32EC@MX15A.corp.emc.com>
Date: Tue, 16 Jul 2013 08:24:04 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <6356DA73-32CE-4B32-B760-48AED3B04120@piuha.net>
References: <8D3D17ACE214DC429325B2B98F3AE71298265158@MX15A.corp.emc.com> <8D3D17ACE214DC429325B2B98F3AE712983F2C87@MX15A.corp.emc.com> <8D3D17ACE214DC429325B2B98F3AE712983F32EC@MX15A.corp.emc.com>
To: "Black, David" <david.black@emc.com>
X-Mailer: Apple Mail (2.1508)
Cc: General Area Review Team <gen-art@ietf.org>, "abfab@ietf.org" <abfab@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jul 2013 06:24:14 -0000

> And the -05 version includes the text to address that editorial nit - =
it's
> ready for publication as a Proposed Standard RFC.  Many thanks to the =
authors
> for productively addressing the review comments.

And many thanks to you, David, for your review. Based on this review and =
my own review of this document, I have balloted Yes on the document.=20

Jari


From sm@elandsys.com  Tue Jul 16 00:17:16 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2689221F8425 for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 00:17:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.59
X-Spam-Level: 
X-Spam-Status: No, score=-102.59 tagged_above=-999 required=5 tests=[AWL=0.009, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MpkxOQfn3+P6 for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 00:17:15 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5218721E81AD for <ietf@ietf.org>; Tue, 16 Jul 2013 00:17:15 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.130.81]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r6G7GdsB009889 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 16 Jul 2013 00:16:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1373959013; bh=dIPMDOO6gwaIJGaBMGm0vDLjMlQ05qUAKQIZJRMuXjg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=x7hHC3FuHzoQfKdxPYE+9lDwVoD+CFcLQglo++eqetqnHmLeBP1E2xnE0wRYUmlak zOClHPIsWqIp60jiaeYDAVIJ1Jd+dNymlTzhMW8bCKm4oJUccm1bYseijJlsNCkx/8 UTEBy2A1Mdcw6xt+sqfAjwDbAUxqXg2FN6gjcLWQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1373959013; i=@elandsys.com; bh=dIPMDOO6gwaIJGaBMGm0vDLjMlQ05qUAKQIZJRMuXjg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=z4j5EAS7ztN6u8+QQdTHAUyZZ7i4YukGcSHxCSt09lmfgdscq6YAsKTQejRKqn24N 7/5n4A8VgkgrjVWnMgk3++G+fSxhSNgCaucH/zlHWYvXTN57Semr//B/RWfMGTII6b iDj+dZRLDTXqnvo7BWDz8JbyTWoXgzMihpzZ0ATA=
Message-Id: <6.2.5.6.2.20130715225325.0bf93d18@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 16 Jul 2013 00:15:06 -0700
To: Doug Barton <dougb@dougbarton.us>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: The case of dotless domains
In-Reply-To: <51E4DC6C.3040609@dougbarton.us>
References: <20130713152747.8F79D18C0D0@mercury.lcs.mit.edu> <51E18737.4080903@isdg.net> <3725D4B2-65DA-45FA-AAEE-309F45CD6F18@checkpoint.com> <51E2A8EE.5010200@isdg.net> <A0984871-D92D-4110-9001-16B363B65AC0@checkpoint.com> <6.2.5.6.2.20130714205140.0ce1f0b8@resistor.net> <51E4DC6C.3040609@dougbarton.us>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Ofer Inbar <cos@aaaaa.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jul 2013 07:17:16 -0000

Hi Doug,
At 22:38 15-07-2013, Doug Barton wrote:
>Interesting, but pardon my being blunt, it does not seem to cover 
>any new ground. You did say one useful thing:
>
>IETF specifications usually provide guidance to ensure 
>interoperability.  Whether dotless domains are harmful or not is a 
>policy matter.

It's a -00 draft.  The above paragraph is one of the two arguments in 
the draft.

>Can you (or Ofer) define how you're using the terms "explicit" and 
>"implicit" in terms of DNS search, and what their relevance is to 
>the topic of dotless domains? And no, I'm not being snarky, I think 
>part of the problem here is a fundamental misunderstanding of how 
>the vast majority of hosts are configured currently.

Speaking for myself, I would say that "explicit" is what the user 
configured and "implicit" is what the is not used-configured.

>I haven't seen anyone in the IETF arguing that the moon is made of 
>green cheese either. What does your comment have to do with 
>anything? Sorry (again) to be blunt, but the IETF pounding the "this 
>thing is bad!" drum is not a particularly effective tool. [1]

I hope that "market forces", whatever that means, is not the main 
argument to dispel problems.

>We have to be realistic about how and where our influence is 
>relevant, and more importantly how and where it is not. Detailing 
>the technical problems with the proposal is relevant IETF work, but 
>that job has already been done more thoroughly by my esteemed former 
>colleagues on the SSAC.

I don't have any influence.  I take no position on the SSAC 
report.  What I did was to read all the IETF specifications 
referenced in the draft and write a draft.  It does not bother me to 
be unrealistic. :-)

>>It is up to those who decide to decide whether dotless domains is a good
>>idea that will gain traction or a bad idea that will go away on it own.
>
>You vastly overestimate your own importance in the grand scheme of 
>things. Don't worry, it's a common human problem. :)  Rather than 
>repeating my point for the third time, see what I wrote just above.

I left in the paragraph that was quoted for context.  The text says 
"those who decide".  I don't have anything to do with the decision 
about dotless domains.  As I am not important it is unlikely that I 
might overestimate my importance. :-)  I don't know the grand scheme 
of things and I do not need to know the grand scheme of things.

Regards,
S. Moonesamy 


From pthaler@broadcom.com  Tue Jul 16 01:33:29 2013
Return-Path: <pthaler@broadcom.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2619721F9A4C for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 01:33:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wk8Nj8iPriGv for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 01:33:24 -0700 (PDT)
Received: from mms2.broadcom.com (mms2.broadcom.com [216.31.210.18]) by ietfa.amsl.com (Postfix) with ESMTP id EF21811E8253 for <ietf@ietf.org>; Tue, 16 Jul 2013 01:33:23 -0700 (PDT)
Received: from [10.9.208.53] by mms2.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.5)); Tue, 16 Jul 2013 01:27:20 -0700
X-Server-Uuid: 4500596E-606A-40F9-852D-14843D8201B2
Received: from SJEXCHCAS03.corp.ad.broadcom.com (10.16.203.8) by IRVEXCHCAS06.corp.ad.broadcom.com (10.9.208.53) with Microsoft SMTP Server (TLS) id 14.1.438.0; Tue, 16 Jul 2013 01:33:18 -0700
Received: from SJEXCHMB09.corp.ad.broadcom.com ( [fe80::3da7:665e:cc78:181f]) by SJEXCHCAS03.corp.ad.broadcom.com ( [::1]) with mapi id 14.01.0438.000; Tue, 16 Jul 2013 01:33:17 -0700
From: "Pat Thaler" <pthaler@broadcom.com>
To: "Bob Hinden" <bob.hinden@gmail.com>, "Abdussalam Baryun" <abdussalambaryun@gmail.com>
Subject: RE: Sunday IAOC Overview Session at the Berlin IETF
Thread-Topic: Sunday IAOC Overview Session at the Berlin IETF
Thread-Index: AQHOf0KrOG+8om/p8kqHZLHdj6kDV5likOmAgAQQfoCAAFq14A==
Date: Tue, 16 Jul 2013 08:33:17 +0000
Message-ID: <EB9B93801780FD4CA165E0FBCB3C3E672AE4EDCC@SJEXCHMB09.corp.ad.broadcom.com>
References: <20130712205852.10265.88487.idtracker@ietfa.amsl.com> <CADnDZ8-Gx_=rL7g-0MDSLqXRDmgH5mBP1gu-3vCF_Ng66kncGA@mail.gmail.com> <3DFDE06F-EAAA-4AA0-8DF4-AC2033C644D7@gmail.com>
In-Reply-To: <3DFDE06F-EAAA-4AA0-8DF4-AC2033C644D7@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]
MIME-Version: 1.0
X-WSS-ID: 7DFBDC621R044711677-01-01
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jul 2013 08:33:29 -0000

One can't 100% protect against disruption from emergency situations.  I'm V=
ice Chair of IEEE 802 and there was a case where a venue became unavailable=
 due to a disaster. In that case it was enough before the meeting that it w=
orked as Bob described - the hotel chain worked with us to identify and con=
tract an acceptable alternative.=20

On the other hand, the tsunami hit Japan just before the IEEE 802 Singapore=
 meeting - close enough to it that some folks were in the air on the way to=
 the meeting when it hit. Many attendees had travel disrupted and arrived l=
ate. Some even were unable to attend due to problems getting an alternative=
 routing. Fortunately, enough were able to arrive so that we had an effecti=
ve meeting, but it was difficult.  There are also cases where a wide spread=
 weather disruption has caused problems for meeting effectiveness - e.g. a =
blizzard on the east coast of the USA.

Pat

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Bob=
 Hinden
Sent: Monday, July 15, 2013 12:56 PM
To: Abdussalam Baryun
Cc: Bob Hinden; ietf@ietf.org
Subject: Re: Sunday IAOC Overview Session at the Berlin IETF

AB,=20
<snip>
> - Is there an alternative venue if the venue was closed for any
> emergency reason at any time? or only one plan so if the plan changes
> there can be problems with the communities expected plan because they
> were not aware of the needed information per time.

No, there is not an alternative venue under contract.  It isn't practical t=
o have two venues under contract, build two networks, etc.  It is technical=
ly feasable, but would cause the registration fee to go up significantly to=
 cover the extra costs. =20

If there was, for example, a fire at a venue months before the the meeting =
we would look for an alternate, but what happens would depend on availabili=
ty of alternative venues.  We have good relationships with the hotel chains=
 we use and they would work very hard to find an alternative venue, as woul=
d the effected venue.




From zehn.cao@gmail.com  Tue Jul 16 01:35:17 2013
Return-Path: <zehn.cao@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5288111E826C for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 01:35:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.375
X-Spam-Level: 
X-Spam-Status: No, score=-1.375 tagged_above=-999 required=5 tests=[AWL=-1.225, BAYES_00=-2.599, MIME_CHARSET_FARAWAY=2.45, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i8fE61Yuea7l for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 01:35:16 -0700 (PDT)
Received: from mail-wg0-x234.google.com (mail-wg0-x234.google.com [IPv6:2a00:1450:400c:c00::234]) by ietfa.amsl.com (Postfix) with ESMTP id 6848011E8268 for <ietf@ietf.org>; Tue, 16 Jul 2013 01:35:16 -0700 (PDT)
Received: by mail-wg0-f52.google.com with SMTP id b12so331265wgh.31 for <ietf@ietf.org>; Tue, 16 Jul 2013 01:35:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=/udJIeBUG61VJwQvpTXHv+1sdMO3bi98qzjCl1k783w=; b=PPXbZ3n74RBmze742Rgrp/N0mwakJkt7jP6hMedmykNuVrg3MJ1EzsvE8i3ZxAXrZk fEPRqbSDFt/TAIZeIUU20E5AZtsz9uawupzWgTiaYmQ66W95MdO6dulAN5d67h8CXMl8 5doQaDltr9Yip5IO6I+U49N1nQxP04ag6ogcqgL7uHZ//cHFboYnLycGt6E233yju1Ms ZVDt9wFZM6OKlmjkr0uu8Q5fZkiE5QbdmiEUU8FankNNzsUqsUqgeVTvMnzhr55T6vkV hSwPeFxE6cTvuU4mghcdeX77tCh8YRL61dI1YqaPVeplt3hklRUfIUA/YqE+4iXodGRN /0mg==
MIME-Version: 1.0
X-Received: by 10.180.187.17 with SMTP id fo17mr244630wic.60.1373963715397; Tue, 16 Jul 2013 01:35:15 -0700 (PDT)
Received: by 10.216.77.131 with HTTP; Tue, 16 Jul 2013 01:35:15 -0700 (PDT)
In-Reply-To: <CA+9kkMCqRL5R8v5RivjRkNHQtMFiKs3Rhva+X5NogMB6_qMaSQ@mail.gmail.com>
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com> <CA+9kkMDZoX0Eq4TcbpP=+YMPmq-F3CAGB1dSogYJa6V2F-irbQ@mail.gmail.com> <CANF0JMCA+HQ7=xEXjDkgxLt2iqUj3Wdq_+2+KFsPg34a0m+nxQ@mail.gmail.com> <CA+9kkMCqRL5R8v5RivjRkNHQtMFiKs3Rhva+X5NogMB6_qMaSQ@mail.gmail.com>
Date: Tue, 16 Jul 2013 16:35:15 +0800
Message-ID: <CAProHASRwM8-Nnd6rPsXtXk85Vb9gNeBshppFjUQxpnLTJsjDg@mail.gmail.com>
Subject: Re: Regarding call Chinese names
From: "Cao,Zhen" <zehn.cao@gmail.com>
To: Ted Hardie <ted.ietf@gmail.com>
Content-Type: text/plain; charset=Big5
Content-Transfer-Encoding: quoted-printable
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jul 2013 08:35:17 -0000

On Tue, Jul 16, 2013 at 12:04 AM, Ted Hardie <ted.ietf@gmail.com> wrote:
> On Sun, Jul 14, 2013 at 5:26 PM, Hui Deng <denghui02@gmail.com> wrote:
>>
>> Hi Ted,
>>
>> I did explain them in the 1st paragraph about minorities (not mentioned
>> that they could have two kids in mainland)
>> anyway, I will revise the title by adding "Chinese "Han" people", hope
>> that will be ok
>>
>> -Hui
>>
>>
>
> While it is always valuable to note national minorities, I believe you
> missed the point.  In some territories, there are dialects of Chinese oth=
er
> than Mandarin and romanizations
> other than pinyin which are common and normatively correct.  For those
> Chinese people, your document does not apply.  As an example, the current
> chief executive of Hong Kong is properly called Leung Chun Ying (=B1=E7=
=AE=B6=AD^); his
> predecessor  in that role was Tung Chee Hwa (=B8=B3=AB=D8=B5=D8).   Simil=
ar situations
> arise in Taiwan and in many territories where Chinese people are themselv=
es
> national minorities.

That's not Pinyin system. I have a question for you, do you think
these spellings are self pronounciable?

>
> Clarifying that your document is specific to the pinyin romanization is
> likely enough (since that romanization is based on Mandarin).

We actually clarify that in pinyin draft,
http://tools.ietf.org/id/draft-zcao-chinese-pronounce-01

Thanks,
caozhen

From duerst@it.aoyama.ac.jp  Tue Jul 16 02:32:20 2013
Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C502B11E827D; Tue, 16 Jul 2013 02:32:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.154
X-Spam-Level: 
X-Spam-Status: No, score=-101.154 tagged_above=-999 required=5 tests=[AWL=-1.364, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cosVECMKPevo; Tue, 16 Jul 2013 02:32:15 -0700 (PDT)
Received: from scintmta01.scbb.aoyama.ac.jp (scintmta01.scbb.aoyama.ac.jp [133.2.253.33]) by ietfa.amsl.com (Postfix) with ESMTP id 29B9921F967C; Tue, 16 Jul 2013 02:32:15 -0700 (PDT)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta01.scbb.aoyama.ac.jp (secret/secret) with SMTP id r6G9WEq8021197; Tue, 16 Jul 2013 18:32:14 +0900
Received: from (unknown [133.2.206.134]) by scmse02.scbb.aoyama.ac.jp with smtp id 655c_5df8_991080ae_edfa_11e2_83a6_001e6722eec2; Tue, 16 Jul 2013 18:32:13 +0900
Received: from [IPv6:::1] (unknown [133.2.210.1]) by itmail2.it.aoyama.ac.jp (Postfix) with ESMTP id F1A21BF535; Tue, 16 Jul 2013 18:30:24 +0900 (JST)
Message-ID: <51E51310.5040400@it.aoyama.ac.jp>
Date: Tue, 16 Jul 2013 18:32:00 +0900
From: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Announcement improvement (was: Re: Last Call: RFC 2050 to historic)
References: <20130710213959.9266.65720.idtracker@ietfa.amsl.com>
In-Reply-To: <20130710213959.9266.65720.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: The IESG <iesg-secretary@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jul 2013 09:32:20 -0000

For the benefits of those (few and far between) IETF participants that 
haven't memorized all RFC numbers, it would be great if announcement 
such as the one below would contain a tiny bit more information about 
the document itself.

E.g. just having the title of the document in announcement would make it 
a lot easier to decide whether this warrants further attention or not, 
without additional lookup.

Many thanks in advance!

Regards,   Martin.

On 2013/07/11 6:39, The IESG wrote:
>
> The IESG has received a request from an individual participant to make
> the following status changes:
>
> - RFC2050 from Best Current Practice to Historic
>
> The supporting document for this request can be found here:
>
> http://datatracker.ietf.org/doc/status-change-2050-to-historic/
>
> 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 2013-08-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.
>
> The affected document can be obtained via
> http://datatracker.ietf.org/doc/rfc2050/
>
> IESG discussion of this request can be tracked via
> http://datatracker.ietf.org/doc/status-change-2050-to-historic/ballot/
>
>
>

From abdussalambaryun@gmail.com  Tue Jul 16 04:26:53 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF15311E8274 for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 04:26:53 -0700 (PDT)
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=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gNA2nfM4+L6j for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 04:26:53 -0700 (PDT)
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 2C67611E81C6 for <ietf@ietf.org>; Tue, 16 Jul 2013 04:26:53 -0700 (PDT)
Received: by mail-pd0-f178.google.com with SMTP id w11so570031pde.23 for <ietf@ietf.org>; Tue, 16 Jul 2013 04:26:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=7HKf4RsieJCggv09Hcg2L7je05Ut/Jfi7uwqsCZgxgU=; b=lLhX3shd3o3M+9ykW9i9bCj8uLcLUgZtPKa6EWItE0/yaLeZyIZLybRrPR/6+SB7Rr 7p+ZSrkxg0rViXL7E4CCcTmGTG1hzdJAGsEd1NylO465C5wDPvU3q5jCPvVXJGkNI4/y XJr0B17H+cj/bTUyqMHkhhpyvsE7zp7ETwOuPsQTh+1EIBZ9ix7TUkLO+y9kAPWehtPe 5G0z1uoJAqtMiuV4ZrMJ2pl5C9lm0T/47Qb859+XrQfJ0DQniA6IycU+n7oLE9X6aDu5 OA8NH0v4WfurRTI+qVL9qXAEVe9zG+OgLzVcoTY7PNiPlz64F6CQ8daKE02LWqNthR7z HlhA==
MIME-Version: 1.0
X-Received: by 10.66.249.135 with SMTP id yu7mr2213256pac.15.1373974012851; Tue, 16 Jul 2013 04:26:52 -0700 (PDT)
Received: by 10.68.250.133 with HTTP; Tue, 16 Jul 2013 04:26:52 -0700 (PDT)
In-Reply-To: <EB9B93801780FD4CA165E0FBCB3C3E672AE4EDCC@SJEXCHMB09.corp.ad.broadcom.com>
References: <20130712205852.10265.88487.idtracker@ietfa.amsl.com> <CADnDZ8-Gx_=rL7g-0MDSLqXRDmgH5mBP1gu-3vCF_Ng66kncGA@mail.gmail.com> <3DFDE06F-EAAA-4AA0-8DF4-AC2033C644D7@gmail.com> <EB9B93801780FD4CA165E0FBCB3C3E672AE4EDCC@SJEXCHMB09.corp.ad.broadcom.com>
Date: Tue, 16 Jul 2013 12:26:52 +0100
Message-ID: <CADnDZ8-SGocPD1Wcf=HXgFBVXiUprB22WrAxtAUVuj63te5=kw@mail.gmail.com>
Subject: Re: Sunday IAOC Overview Session at the Berlin IETF
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Pat Thaler <pthaler@broadcom.com>
Content-Type: multipart/alternative; boundary=047d7b111c33f77cb904e19f4044
Cc: Bob Hinden <bob.hinden@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jul 2013 11:26:54 -0000

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

Hi Pat,

Thanks. My concerns is that do we have a plan for disaster
recovery/management in IETF or IEEE802. Including meetings which is the
important time we come together for. Usually now organisations are looking
into defining plans so the staff/participants are aware of procedures. I
was thinking if I was to go to any organisation these days I will ask is
there a plan and alternatives. Usually communication and information is the
key to a better solution per person or per organisation. As IETF and
IEEE802 standard communication technology then it is good if we have the
best practice in the world.

AB
On Tue, Jul 16, 2013 at 9:33 AM, Pat Thaler <pthaler@broadcom.com> wrote:

> One can't 100% protect against disruption from emergency situations.  I'm
> Vice Chair of IEEE 802 and there was a case where a venue became
> unavailable due to a disaster. In that case it was enough before the
> meeting that it worked as Bob described - the hotel chain worked with us to
> identify and contract an acceptable alternative.
>
> On the other hand, the tsunami hit Japan just before the IEEE 802
> Singapore meeting - close enough to it that some folks were in the air on
> the way to the meeting when it hit. Many attendees had travel disrupted and
> arrived late. Some even were unable to attend due to problems getting an
> alternative routing. Fortunately, enough were able to arrive so that we had
> an effective meeting, but it was difficult.  There are also cases where a
> wide spread weather disruption has caused problems for meeting
> effectiveness - e.g. a blizzard on the east coast of the USA.
>
> Pat
>
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Bob Hinden
> Sent: Monday, July 15, 2013 12:56 PM
> To: Abdussalam Baryun
> Cc: Bob Hinden; ietf@ietf.org
> Subject: Re: Sunday IAOC Overview Session at the Berlin IETF
>
> AB,
> <snip>
> > - Is there an alternative venue if the venue was closed for any
> > emergency reason at any time? or only one plan so if the plan changes
> > there can be problems with the communities expected plan because they
> > were not aware of the needed information per time.
>
> No, there is not an alternative venue under contract.  It isn't practical
> to have two venues under contract, build two networks, etc.  It is
> technically feasable, but would cause the registration fee to go up
> significantly to cover the extra costs.
>
> If there was, for example, a fire at a venue months before the the meeting
> we would look for an alternate, but what happens would depend on
> availability of alternative venues.  We have good relationships with the
> hotel chains we use and they would work very hard to find an alternative
> venue, as would the effected venue.
>
>
>
>

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

<div>Hi Pat,</div><div>=A0</div><div>Thanks. My concerns is that do we have=
 a plan for disaster recovery/management in IETF or IEEE802. Including meet=
ings which is the important time we come together for. Usually now organisa=
tions are looking into defining plans so the staff/participants are aware o=
f procedures. I was thinking if I was to go to any organisation these days =
I will ask is there a plan and alternatives. Usually communication and info=
rmation is the key to a better solution per person or per organisation. As =
IETF and IEEE802 standard communication technology then it is good if we ha=
ve the best practice in the world.</div>
<div>=A0</div><div>AB<br></div><div class=3D"gmail_quote">On Tue, Jul 16, 2=
013 at 9:33 AM, Pat Thaler <span dir=3D"ltr">&lt;<a href=3D"mailto:pthaler@=
broadcom.com" target=3D"_blank">pthaler@broadcom.com</a>&gt;</span> wrote:<=
br><blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-le=
ft-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" cl=
ass=3D"gmail_quote">
One can&#39;t 100% protect against disruption from emergency situations. =
=A0I&#39;m Vice Chair of IEEE 802 and there was a case where a venue became=
 unavailable due to a disaster. In that case it was enough before the meeti=
ng that it worked as Bob described - the hotel chain worked with us to iden=
tify and contract an acceptable alternative.<br>

<br>
On the other hand, the tsunami hit Japan just before the IEEE 802 Singapore=
 meeting - close enough to it that some folks were in the air on the way to=
 the meeting when it hit. Many attendees had travel disrupted and arrived l=
ate. Some even were unable to attend due to problems getting an alternative=
 routing. Fortunately, enough were able to arrive so that we had an effecti=
ve meeting, but it was difficult. =A0There are also cases where a wide spre=
ad weather disruption has caused problems for meeting effectiveness - e.g. =
a blizzard on the east coast of the USA.<br>

<br>
Pat<br>
<br>
-----Original Message-----<br>
From: <a href=3D"mailto:ietf-bounces@ietf.org">ietf-bounces@ietf.org</a> [m=
ailto:<a href=3D"mailto:ietf-bounces@ietf.org">ietf-bounces@ietf.org</a>] O=
n Behalf Of Bob Hinden<br>
Sent: Monday, July 15, 2013 12:56 PM<br>
To: Abdussalam Baryun<br>
Cc: Bob Hinden; <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br>
Subject: Re: Sunday IAOC Overview Session at the Berlin IETF<br>
<br>
AB,<br>
&lt;snip&gt;<br>
<div class=3D"HOEnZb"><div class=3D"h5">&gt; - Is there an alternative venu=
e if the venue was closed for any<br>
&gt; emergency reason at any time? or only one plan so if the plan changes<=
br>
&gt; there can be problems with the communities expected plan because they<=
br>
&gt; were not aware of the needed information per time.<br>
<br>
No, there is not an alternative venue under contract. =A0It isn&#39;t pract=
ical to have two venues under contract, build two networks, etc. =A0It is t=
echnically feasable, but would cause the registration fee to go up signific=
antly to cover the extra costs.<br>

<br>
If there was, for example, a fire at a venue months before the the meeting =
we would look for an alternate, but what happens would depend on availabili=
ty of alternative venues. =A0We have good relationships with the hotel chai=
ns we use and they would work very hard to find an alternative venue, as wo=
uld the effected venue.<br>

<br>
<br>
<br>
</div></div></blockquote></div><br>

--047d7b111c33f77cb904e19f4044--

From l.wood@surrey.ac.uk  Tue Jul 16 04:38:19 2013
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD41511E80CC for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 04:38:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.529
X-Spam-Level: 
X-Spam-Status: No, score=-3.529 tagged_above=-999 required=5 tests=[AWL=0.069,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LjSxTTk3fv2l for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 04:38:09 -0700 (PDT)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.168]) by ietfa.amsl.com (Postfix) with ESMTP id C154521F9D46 for <ietf@ietf.org>; Tue, 16 Jul 2013 04:38:08 -0700 (PDT)
Received: from [195.245.230.131:36433] by server-8.bemta-3.messagelabs.com id B7/3A-18692-E9035E15; Tue, 16 Jul 2013 11:38:06 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-9.tower-78.messagelabs.com!1373974685!24884408!1
X-Originating-IP: [131.227.200.31]
X-StarScan-Received: 
X-StarScan-Version: 6.9.9; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 31855 invoked from network); 16 Jul 2013 11:38:06 -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; 16 Jul 2013 11:38:06 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT011P.surrey.ac.uk ([131.227.200.31]) with mapi; Tue, 16 Jul 2013 12:38:05 +0100
From: <l.wood@surrey.ac.uk>
To: <abdussalambaryun@gmail.com>, <pthaler@broadcom.com>
Date: Tue, 16 Jul 2013 12:37:00 +0100
Subject: RE: Sunday IAOC Overview Session at the Berlin IETF
Thread-Topic: Sunday IAOC Overview Session at the Berlin IETF
Thread-Index: Ac6CF3xmtZeCVEUiSGuz0BIE5+c8YAAAUywK
Message-ID: <290E20B455C66743BE178C5C84F12408223F494F01@EXMB01CMS.surrey.ac.uk>
References: <20130712205852.10265.88487.idtracker@ietfa.amsl.com> <CADnDZ8-Gx_=rL7g-0MDSLqXRDmgH5mBP1gu-3vCF_Ng66kncGA@mail.gmail.com> <3DFDE06F-EAAA-4AA0-8DF4-AC2033C644D7@gmail.com> <EB9B93801780FD4CA165E0FBCB3C3E672AE4EDCC@SJEXCHMB09.corp.ad.broadcom.com>, <CADnDZ8-SGocPD1Wcf=HXgFBVXiUprB22WrAxtAUVuj63te5=kw@mail.gmail.com>
In-Reply-To: <CADnDZ8-SGocPD1Wcf=HXgFBVXiUprB22WrAxtAUVuj63te5=kw@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: bob.hinden@gmail.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jul 2013 11:38:20 -0000

AB

How many IETFs have you attended?
How many professional meetings have you organised?

Lloyd Wood
http://sat-net.com/L.Wood/


________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Abdussalam=
 Baryun [abdussalambaryun@gmail.com]
Sent: 16 July 2013 12:26
To: Pat Thaler
Cc: Bob Hinden; ietf@ietf.org
Subject: Re: Sunday IAOC Overview Session at the Berlin IETF

Hi Pat,

Thanks. My concerns is that do we have a plan for disaster recovery/managem=
ent in IETF or IEEE802. Including meetings which is the important time we c=
ome together for. Usually now organisations are looking into defining plans=
 so the staff/participants are aware of procedures. I was thinking if I was=
 to go to any organisation these days I will ask is there a plan and altern=
atives. Usually communication and information is the key to a better soluti=
on per person or per organisation. As IETF and IEEE802 standard communicati=
on technology then it is good if we have the best practice in the world.

AB
On Tue, Jul 16, 2013 at 9:33 AM, Pat Thaler <pthaler@broadcom.com<mailto:pt=
haler@broadcom.com>> wrote:
One can't 100% protect against disruption from emergency situations.  I'm V=
ice Chair of IEEE 802 and there was a case where a venue became unavailable=
 due to a disaster. In that case it was enough before the meeting that it w=
orked as Bob described - the hotel chain worked with us to identify and con=
tract an acceptable alternative.

On the other hand, the tsunami hit Japan just before the IEEE 802 Singapore=
 meeting - close enough to it that some folks were in the air on the way to=
 the meeting when it hit. Many attendees had travel disrupted and arrived l=
ate. Some even were unable to attend due to problems getting an alternative=
 routing. Fortunately, enough were able to arrive so that we had an effecti=
ve meeting, but it was difficult.  There are also cases where a wide spread=
 weather disruption has caused problems for meeting effectiveness - e.g. a =
blizzard on the east coast of the USA.

Pat

-----Original Message-----
From: ietf-bounces@ietf.org<mailto:ietf-bounces@ietf.org> [mailto:ietf-boun=
ces@ietf.org<mailto:ietf-bounces@ietf.org>] On Behalf Of Bob Hinden
Sent: Monday, July 15, 2013 12:56 PM
To: Abdussalam Baryun
Cc: Bob Hinden; ietf@ietf.org<mailto:ietf@ietf.org>
Subject: Re: Sunday IAOC Overview Session at the Berlin IETF

AB,
<snip>
> - Is there an alternative venue if the venue was closed for any
> emergency reason at any time? or only one plan so if the plan changes
> there can be problems with the communities expected plan because they
> were not aware of the needed information per time.

No, there is not an alternative venue under contract.  It isn't practical t=
o have two venues under contract, build two networks, etc.  It is technical=
ly feasable, but would cause the registration fee to go up significantly to=
 cover the extra costs.

If there was, for example, a fire at a venue months before the the meeting =
we would look for an alternate, but what happens would depend on availabili=
ty of alternative venues.  We have good relationships with the hotel chains=
 we use and they would work very hard to find an alternative venue, as woul=
d the effected venue.





From andy@hxr.us  Tue Jul 16 07:10:28 2013
Return-Path: <andy@hxr.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1C8121E804C for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 07:10:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.477
X-Spam-Level: 
X-Spam-Status: No, score=-2.477 tagged_above=-999 required=5 tests=[AWL=0.500,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sJ-G4QNaSsoX for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 07:10:22 -0700 (PDT)
Received: from mail-pa0-f54.google.com (mail-pa0-f54.google.com [209.85.220.54]) by ietfa.amsl.com (Postfix) with ESMTP id 6D91311E80E9 for <ietf@ietf.org>; Tue, 16 Jul 2013 07:10:17 -0700 (PDT)
Received: by mail-pa0-f54.google.com with SMTP id kx10so827355pab.13 for <ietf@ietf.org>; Tue, 16 Jul 2013 07:10:17 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:date:message-id:subject:from:to:cc :content-type:x-gm-message-state; bh=JWN/0pFaXj37+4p9QFZLVz2u4nuH7FNG465ONUMYRZk=; b=PcPWokmjFqavPUjajdLPrPjhzsWKryS9AucEMWRlM8u+t1UMe96PCycADZjg4wfg+3 WbV3AmHCao58t4E5rPgb4K4xYPs6vTEWiE0SOf+ATbczvfFDc32odTcJtFIdNCF/Xrtp W1vyKxyqECxM2e9KvG2bKalD+DgXDEeC3rOIewFiyfs+/u7ariyTzA80gN2M/eGfj3cm j51l/bFWruRiKiYdKgOwipMrhVNEfuExSxsvp3eTr0wXxv/F1Jy9bloj4Dd/hi2xkeNL y8vHk+XvJkHVQnQG9oisACxWdq+IfxyNg557seVi7m2xN9T33/ZP/A77YZ9f8tTucY+p +ktQ==
MIME-Version: 1.0
X-Received: by 10.68.219.130 with SMTP id po2mr1791694pbc.54.1373983816945; Tue, 16 Jul 2013 07:10:16 -0700 (PDT)
Received: by 10.68.203.69 with HTTP; Tue, 16 Jul 2013 07:10:16 -0700 (PDT)
X-Originating-IP: [192.149.252.11]
Date: Tue, 16 Jul 2013 10:10:16 -0400
Message-ID: <CAAQiQRcjejdQgMfLn9bsaucRQgCRkt_dYPUaKLeRQPkJ7tWTQg@mail.gmail.com>
Subject: LC of draft-ietf-jcardcal-jcard-05
From: Andrew Newton <andy@hxr.us>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQkpk8rTzwTm1TpNDVCmwgvSwgCi2hZMenoJMrcZTbnoMfQuVdPn7dvE5Dhoj6kRSRHgUvyt
Cc: jcardcal@ietf.org, "weirds@ietf.org" <weirds@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jul 2013 14:10:28 -0000

In the context of writing both an RDAP client and server for the
weirds activity, I have read draft-ietf-jcardcal-jcard-05 and found no
issues.

-andy

From cos@mip.polyamory.org  Tue Jul 16 08:07:34 2013
Return-Path: <cos@mip.polyamory.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0883521F85C3 for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 08:07:34 -0700 (PDT)
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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S2YII1jvKrNi for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 08:07:29 -0700 (PDT)
Received: from mip.polyamory.org (mip.aaaaa.org [199.201.145.10]) by ietfa.amsl.com (Postfix) with ESMTP id B6ECD21F85BB for <ietf@ietf.org>; Tue, 16 Jul 2013 08:07:29 -0700 (PDT)
Received: by mip.polyamory.org (Postfix, from userid 1002) id 5FC0210760; Tue, 16 Jul 2013 11:07:21 -0400 (EDT)
Date: Tue, 16 Jul 2013 11:07:21 -0400
From: Ofer Inbar <cos@aaaaa.org>
To: Doug Barton <dougb@dougbarton.us>
Subject: Re: The case of dotless domains
Message-ID: <20130716150721.GG29401@mip.aaaaa.org>
References: <20130713152747.8F79D18C0D0@mercury.lcs.mit.edu> <51E18737.4080903@isdg.net> <3725D4B2-65DA-45FA-AAEE-309F45CD6F18@checkpoint.com> <51E2A8EE.5010200@isdg.net> <A0984871-D92D-4110-9001-16B363B65AC0@checkpoint.com> <6.2.5.6.2.20130714205140.0ce1f0b8@resistor.net> <51E4DC6C.3040609@dougbarton.us>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <51E4DC6C.3040609@dougbarton.us>
User-Agent: Mutt/1.4.2.3i
Organization: American Association Against Acronym Abuse
Cc: Ofer Inbar <cos@aaaaa.org>, S Moonesamy <sm+ietf@elandsys.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jul 2013 15:07:34 -0000

> >>What this brings to mind is that we used to have implicit DNS domain
> >>search in the early days of DNS.  When edu.com accidentally hijacked
> >>a huge chunk of the Internet, most of the net very quickly got rid of
> >>implicit search, and we got the explicit DNS search feature that many
> >>people are discussing now.
> >
> >Yes.
> 
> Can you (or Ofer) define how you're using the terms "explicit" and 
> "implicit" in terms of DNS search, and what their relevance is to the 
> topic of dotless domains? And no, I'm not being snarky, I think part of 
> the problem here is a fundamental misunderstanding of how the vast 
> majority of hosts are configured currently.

You're not being snarky, but that indicates that you seem to have
missed my point, which is not about the technical details of how
domain search got changed after the edu.com disaster.  My point is
not to make a direct parallel between how domain search changed, and
dotless domains, and you seem to be looking at it in that light.

What this brings to mind is that we had a DNS system that was
vulnerable to the addition of something to the DNS that people had
expected nobody would make the mistake of doing, but it happened and
caused damage, and the net reacted by altering how DNS software works
in order to protect against that damage.  At the time, the obvious
defensive change was "don't do implicit domain search".  If dotless
domains cause damage as many people here predict, what I'm saying is
that I think we'll react similarly, and that I guess the defensive
change people will widely deploy is to reject A/AAAA/MX records at
the top level.

You really do not need to drill into the specifics of the change from
implicit to explicit domain search in reaction to edu.com, in this
context.  So it sounds to me like you have something quite different
in mind.  I don't know what you think I was trying to say - it's not
anything I said explicitly, so perhaps you think I was trying to
subtly say something between the lines.  To be clear: I wasn't.
  -- Cos

From joseph.yee@gmail.com  Tue Jul 16 08:09:10 2013
Return-Path: <joseph.yee@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 314B911E80ED for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 08:09:10 -0700 (PDT)
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=[AWL=-0.300, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_34=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0Nu9MAm-ZOQV for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 08:09:09 -0700 (PDT)
Received: from mail-ie0-x22d.google.com (mail-ie0-x22d.google.com [IPv6:2607:f8b0:4001:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 8F12911E80E9 for <ietf@ietf.org>; Tue, 16 Jul 2013 08:09:09 -0700 (PDT)
Received: by mail-ie0-f173.google.com with SMTP id k13so1843836iea.4 for <ietf@ietf.org>; Tue, 16 Jul 2013 08:09:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=rYrhYoRR71DbquTvEdTrQUJyrg5QEJWPtupQyQzWJto=; b=W+2MMspNdFXLu3p+oYis8z4nxfbq+Wx2/3HQTmLWV4H5YSJlMUW8ku662R2OqLfEEe TnkS4bguHoj6OTcD2sHbEDF/dewi1Ly+2mhTW+EVjV8k9ADCm2AeQfMZoJIzfE9/x34j p9i1jNise8Bcdlh3GnI3udpJmKn/DoCJJQ7J0ZuNRRvh6V9gG5ERKidvRPivAaN/99mI Ay6neS6ahVcEbbMACZqiBI7+lPBlrHvY9hBtvWWFZJEqN5zCCwqJHd6leDO3TyNApG8m Ylj+mWm7aA9M9p86FlixgRCPAGXw+aMDclYwfTRJDsCnJeBm4kSe/4DjviN+ccQPU326 9N4A==
MIME-Version: 1.0
X-Received: by 10.43.14.74 with SMTP id pp10mr1170074icb.87.1373987349025; Tue, 16 Jul 2013 08:09:09 -0700 (PDT)
Received: by 10.64.49.108 with HTTP; Tue, 16 Jul 2013 08:09:08 -0700 (PDT)
In-Reply-To: <CAProHASRwM8-Nnd6rPsXtXk85Vb9gNeBshppFjUQxpnLTJsjDg@mail.gmail.com>
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com> <CA+9kkMDZoX0Eq4TcbpP=+YMPmq-F3CAGB1dSogYJa6V2F-irbQ@mail.gmail.com> <CANF0JMCA+HQ7=xEXjDkgxLt2iqUj3Wdq_+2+KFsPg34a0m+nxQ@mail.gmail.com> <CA+9kkMCqRL5R8v5RivjRkNHQtMFiKs3Rhva+X5NogMB6_qMaSQ@mail.gmail.com> <CAProHASRwM8-Nnd6rPsXtXk85Vb9gNeBshppFjUQxpnLTJsjDg@mail.gmail.com>
Date: Tue, 16 Jul 2013 11:09:08 -0400
Message-ID: <CADRqEyqMtW5rFS_az895DOroN8P7Bh5w9QuBv7549Bb_D_pjaw@mail.gmail.com>
Subject: Re: Regarding call Chinese names
From: Joseph Yee <joseph.yee@gmail.com>
To: "Cao,Zhen" <zehn.cao@gmail.com>
Content-Type: multipart/alternative; boundary=bcaec519692fdd64f104e1a25ba4
Cc: Ted Hardie <ted.ietf@gmail.com>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jul 2013 15:09:10 -0000

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

On Tue, Jul 16, 2013 at 4:35 AM, Cao,Zhen <zehn.cao@gmail.com> wrote:

> On Tue, Jul 16, 2013 at 12:04 AM, Ted Hardie <ted.ietf@gmail.com> wrote:
> > On Sun, Jul 14, 2013 at 5:26 PM, Hui Deng <denghui02@gmail.com> wrote:
> >>
> >> Hi Ted,
> >>
> >> I did explain them in the 1st paragraph about minorities (not mentione=
d
> >> that they could have two kids in mainland)
> >> anyway, I will revise the title by adding "Chinese "Han" people", hope
> >> that will be ok
> >>
> >> -Hui
> >>
> >>
> >
> > While it is always valuable to note national minorities, I believe you
> > missed the point.  In some territories, there are dialects of Chinese
> other
> > than Mandarin and romanizations
> > other than pinyin which are common and normatively correct.  For those
> > Chinese people, your document does not apply.  As an example, the curre=
nt
> > chief executive of Hong Kong is properly called Leung Chun Ying (=E6=A2=
=81=E6=8C=AF=E8=8B=B1);
> his
> > predecessor  in that role was Tung Chee Hwa (=E8=91=A3=E5=BB=BA=E8=8F=
=AF).   Similar situations
> > arise in Taiwan and in many territories where Chinese people are
> themselves
> > national minorities.
>
> That's not Pinyin system. I have a question for you, do you think
> these spellings are self pronounciable?
>

You mean how accurate they sound?  They sound right for the intended
dialect, just they are not Mandarin.

Joseph


> >
> > Clarifying that your document is specific to the pinyin romanization is
> > likely enough (since that romanization is based on Mandarin).
>
> We actually clarify that in pinyin draft,
> http://tools.ietf.org/id/draft-zcao-chinese-pronounce-01
>
> Thanks,
> caozhen
>

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><div class=3D"gmail_quote">=
On Tue, Jul 16, 2013 at 4:35 AM, Cao,Zhen <span dir=3D"ltr">&lt;<a href=3D"=
mailto:zehn.cao@gmail.com" target=3D"_blank">zehn.cao@gmail.com</a>&gt;</sp=
an> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On Tue, Jul 16, 2013 at 12=
:04 AM, Ted Hardie &lt;<a href=3D"mailto:ted.ietf@gmail.com">ted.ietf@gmail=
.com</a>&gt; wrote:<br>

&gt; On Sun, Jul 14, 2013 at 5:26 PM, Hui Deng &lt;<a href=3D"mailto:denghu=
i02@gmail.com">denghui02@gmail.com</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; Hi Ted,<br>
&gt;&gt;<br>
&gt;&gt; I did explain them in the 1st paragraph about minorities (not ment=
ioned<br>
&gt;&gt; that they could have two kids in mainland)<br>
&gt;&gt; anyway, I will revise the title by adding &quot;Chinese &quot;Han&=
quot; people&quot;, hope<br>
&gt;&gt; that will be ok<br>
&gt;&gt;<br>
&gt;&gt; -Hui<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;<br>
&gt; While it is always valuable to note national minorities, I believe you=
<br>
&gt; missed the point. =C2=A0In some territories, there are dialects of Chi=
nese other<br>
&gt; than Mandarin and romanizations<br>
&gt; other than pinyin which are common and normatively correct. =C2=A0For =
those<br>
&gt; Chinese people, your document does not apply. =C2=A0As an example, the=
 current<br>
&gt; chief executive of Hong Kong is properly called Leung Chun Ying (=E6=
=A2=81=E6=8C=AF=E8=8B=B1); his<br>
&gt; predecessor =C2=A0in that role was Tung Chee Hwa (=E8=91=A3=E5=BB=BA=
=E8=8F=AF). =C2=A0 Similar situations<br>
&gt; arise in Taiwan and in many territories where Chinese people are thems=
elves<br>
&gt; national minorities.<br>
<br>
</div>That&#39;s not Pinyin system. I have a question for you, do you think=
<br>
these spellings are self pronounciable?<br></blockquote><div><br></div><div=
>You mean how accurate they sound?=C2=A0 They sound right for the intended =
dialect, just they are not Mandarin.<br></div><div>=C2=A0<br></div><div>Jos=
eph<br>
</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class=3D"im"><br>
&gt;<br>
&gt; Clarifying that your document is specific to the pinyin romanization i=
s<br>
&gt; likely enough (since that romanization is based on Mandarin).<br>
<br>
</div>We actually clarify that in pinyin draft,<br>
<a href=3D"http://tools.ietf.org/id/draft-zcao-chinese-pronounce-01" target=
=3D"_blank">http://tools.ietf.org/id/draft-zcao-chinese-pronounce-01</a><br=
>
<br>
Thanks,<br>
caozhen<br>
</blockquote></div><br></div></div>

--bcaec519692fdd64f104e1a25ba4--

From adrian@olddog.co.uk  Tue Jul 16 10:09:54 2013
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 046B421F9970 for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 10:09:54 -0700 (PDT)
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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TxFBExLKlUJC for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 10:09:49 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id E3C2021F991E for <ietf@ietf.org>; Tue, 16 Jul 2013 10:09:48 -0700 (PDT)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r6GH9lNK022005;  Tue, 16 Jul 2013 18:09:47 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r6GH9g83021962 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 16 Jul 2013 18:09:45 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <draft-barnes-healthy-food@tools.ietf.org>
References: <20130716163157.28468.93383.idtracker@ietfa.amsl.com>
In-Reply-To: <20130716163157.28468.93383.idtracker@ietfa.amsl.com>
Subject: I-D Action: draft-barnes-healthy-food-07.txt
Date: Tue, 16 Jul 2013 18:09:41 +0100
Message-ID: <0e1501ce8247$45197bf0$cf4c73d0$@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: AQIKfiTNkPkLWdefr8jDMRdxEhClWJjvkHzg
Content-Language: en-gb
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 16 Jul 2013 17:09:54 -0000

Mary,

I appreciate your work on this document, but I don't know where or how to draw
the line.

Personally, I will strongly try to be vegetarian, but eat meat rather than
starve (a situation that arises when travelling).
But I will also try to eat fairly traded produce, and also try to reduce the
food-miles. I prefer food that can be traced to source (which is hopefully
local).

I wonder whether your draft should either go into *all* details, or try to
up-level a bit to limit itself to imperatives (such as allergies and religious
requirements).

Adrian

> -----Original Message-----
> From: i-d-announce-bounces@ietf.org [mailto:i-d-announce-bounces@ietf.org]
> On Behalf Of internet-drafts@ietf.org
> Sent: 16 July 2013 17:32
> To: i-d-announce@ietf.org
> Subject: I-D Action: draft-barnes-healthy-food-07.txt
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
directories.
> 
> 
> 	Title           : Healthy Food and Special Dietary Requirements for IETF
> meetings
> 	Author(s)       : Mary Barnes
> 	Filename        : draft-barnes-healthy-food-07.txt
> 	Pages           : 18
> 	Date            : 2013-07-15
> 
> Abstract:
>    This document describes the basic requirements for food for folks
>    that attend IETF meetings require special diets, as well as those
>    that prefer to eat healthy.  While, the variety of special diets is
>    quite broad, the most general categories are described.  There can be
>    controversy as to what constitutes healthy eating, but there are some
>    common, generally available foods that comprise the basis for healthy
>    eating and special diets.  This document provides some
>    recommendations to meeting planners, as well as participants, in
>    handling these requirements.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-barnes-healthy-food
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-barnes-healthy-food-07
> 
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-barnes-healthy-food-07
> 
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


From Ted.Lemon@nominum.com  Tue Jul 16 10:18:05 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 346D321F8616 for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 10:18:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.592
X-Spam-Level: 
X-Spam-Status: No, score=-106.592 tagged_above=-999 required=5 tests=[AWL=0.007, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m9rGmEmQwcAS for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 10:17:58 -0700 (PDT)
Received: from exprod7og118.obsmtp.com (exprod7og118.obsmtp.com [64.18.2.8]) by ietfa.amsl.com (Postfix) with ESMTP id 3E9B921F9F59 for <ietf@ietf.org>; Tue, 16 Jul 2013 10:17:58 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob118.postini.com ([64.18.6.12]) with SMTP ID DSNKUeWARb4qqCJ2s4GcfFfv3naApT4EQ1Wq@postini.com; Tue, 16 Jul 2013 10:17:58 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 6CDF11B8244 for <ietf@ietf.org>; Tue, 16 Jul 2013 10:17:57 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 2309F190052; Tue, 16 Jul 2013 10:17:56 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Tue, 16 Jul 2013 10:17:56 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "<adrian@olddog.co.uk>" <adrian@olddog.co.uk>
Subject: Re: I-D Action: draft-barnes-healthy-food-07.txt
Thread-Topic: I-D Action: draft-barnes-healthy-food-07.txt
Thread-Index: AQIKfiTNkPkLWdefr8jDMRdxEhClWJjvkHzggAB5ZIA=
Date: Tue, 16 Jul 2013 17:17:55 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307752140AD@mbx-01.win.nominum.com>
References: <20130716163157.28468.93383.idtracker@ietfa.amsl.com> <0e1501ce8247$45197bf0$cf4c73d0$@olddog.co.uk>
In-Reply-To: <0e1501ce8247$45197bf0$cf4c73d0$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <23A32D1E562F19479762ACFFBEB77169@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>, "<draft-barnes-healthy-food@tools.ietf.org>" <draft-barnes-healthy-food@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jul 2013 17:18:05 -0000

As I mentioned to Mary privately, yogurt with fish in it is very common (yo=
plait, for example) and vegetarians who know that kosher gelatin is made of=
 fish don't eat it; this can result in the food options at the cookie table=
 being, essentially, cookies, which are of course a terrible thing to eat i=
f you will be needing to concentrate during the next session.   Because of =
this I tend to consider the break food to be an attractive nuisance rather =
than a benefit.

I don't know if it's even possible to get people at venues to be sensitive =
to these issues, but I certainly support the effort Mary is making to get t=
hem to try, and I think specificity is a good thing.   I applaud your flexi=
bility, but not everyone is in a position to be as flexible; in particular,=
 given the number of graybeards who attend IETF, I think paying attention t=
o the problem of excessive sugar in break foods is really important.


From mary.ietf.barnes@gmail.com  Tue Jul 16 10:19:38 2013
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4870121E8091 for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 10:19:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.587
X-Spam-Level: 
X-Spam-Status: No, score=-102.587 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n3FlMO9uF9wB for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 10:19:36 -0700 (PDT)
Received: from mail-qa0-x231.google.com (mail-qa0-x231.google.com [IPv6:2607:f8b0:400d:c00::231]) by ietfa.amsl.com (Postfix) with ESMTP id 1143611E80D7 for <ietf@ietf.org>; Tue, 16 Jul 2013 10:19:20 -0700 (PDT)
Received: by mail-qa0-f49.google.com with SMTP id hu16so580731qab.1 for <ietf@ietf.org>; Tue, 16 Jul 2013 10:19:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=OELIhoMwmIqrLVAaKMDnSRCQpeHY0JArL+7GkhUjldQ=; b=sE3HFG5/hCer6R69V91txFVtPqcWEhegwTFuvqb/HqHz6sU/YkhRpCv5N3ZZussIff luuG3qHPHatnpGHwd5IksqSfTW8S/gR1Ds1ni6p7RpVgdSVXhYZxXoj1NEUkj5pvfZ1c 9UChVz6eNEvzoSxdlDlPoE99WGatDgmYVWrsuCvIM7OhnRbdSkVLn5IBEH1w6KW3iRTa B8df5JDmzlYB7PElMpvDOki+tuNfo7OabiV7NWDPMC8CihYo1fGtagE5BJ5ySHeUnc4x vnD0eJBm2UKfyz53xW5iYT1Lv1ICn1yfyxMgbyTGRgaLsy9MM03AUkOtee9Cc2XBVczs nLrg==
MIME-Version: 1.0
X-Received: by 10.224.72.203 with SMTP id n11mr4608248qaj.13.1373995160445; Tue, 16 Jul 2013 10:19:20 -0700 (PDT)
Received: by 10.49.76.167 with HTTP; Tue, 16 Jul 2013 10:19:20 -0700 (PDT)
In-Reply-To: <0e1501ce8247$45197bf0$cf4c73d0$@olddog.co.uk>
References: <20130716163157.28468.93383.idtracker@ietfa.amsl.com> <0e1501ce8247$45197bf0$cf4c73d0$@olddog.co.uk>
Date: Tue, 16 Jul 2013 12:19:20 -0500
Message-ID: <CAHBDyN47bRHUoFEm-+TDPJwT1LHLg_fovSc=zTOSdnARQGtEdg@mail.gmail.com>
Subject: Re: I-D Action: draft-barnes-healthy-food-07.txt
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: "<adrian@olddog.co.uk>" <adrian@olddog.co.uk>
Content-Type: multipart/alternative; boundary=20cf3074b5f6762a8004e1a42dab
X-Mailman-Approved-At: Tue, 16 Jul 2013 10:35:39 -0700
Cc: IETF-Discussion list <ietf@ietf.org>, draft-barnes-healthy-food@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jul 2013 17:19:38 -0000

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

Yes, it is hard to draw the line.  I did remove some material around the
statistics, etc that seemed to be of concern to some folks.  However, I
think for folks that don't deal with this stuff, the background can be
helpful.  It is hard for some folks to really get why some of us have to
be, or choose to be, so very particular about what we eat.  That was
extremely evident during the discussion that motivated this document after
the meeting in Dublin (countryside).

If you have suggestions on text that could be pruned, that would be
helpful.  I'll make another pass as well and see if I can trim some things.

Thanks,
Mary.


On Tue, Jul 16, 2013 at 12:09 PM, Adrian Farrel <adrian@olddog.co.uk> wrote:

> Mary,
>
> I appreciate your work on this document, but I don't know where or how to
> draw
> the line.
>
> Personally, I will strongly try to be vegetarian, but eat meat rather than
> starve (a situation that arises when travelling).
> But I will also try to eat fairly traded produce, and also try to reduce
> the
> food-miles. I prefer food that can be traced to source (which is hopefully
> local).
>
> I wonder whether your draft should either go into *all* details, or try to
> up-level a bit to limit itself to imperatives (such as allergies and
> religious
> requirements).
>
> Adrian
>
> > -----Original Message-----
> > From: i-d-announce-bounces@ietf.org [mailto:
> i-d-announce-bounces@ietf.org]
> > On Behalf Of internet-drafts@ietf.org
> > Sent: 16 July 2013 17:32
> > To: i-d-announce@ietf.org
> > Subject: I-D Action: draft-barnes-healthy-food-07.txt
> >
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> >
> >
> >       Title           : Healthy Food and Special Dietary Requirements
> for IETF
> > meetings
> >       Author(s)       : Mary Barnes
> >       Filename        : draft-barnes-healthy-food-07.txt
> >       Pages           : 18
> >       Date            : 2013-07-15
> >
> > Abstract:
> >    This document describes the basic requirements for food for folks
> >    that attend IETF meetings require special diets, as well as those
> >    that prefer to eat healthy.  While, the variety of special diets is
> >    quite broad, the most general categories are described.  There can be
> >    controversy as to what constitutes healthy eating, but there are some
> >    common, generally available foods that comprise the basis for healthy
> >    eating and special diets.  This document provides some
> >    recommendations to meeting planners, as well as participants, in
> >    handling these requirements.
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-barnes-healthy-food
> >
> > There's also a htmlized version available at:
> > http://tools.ietf.org/html/draft-barnes-healthy-food-07
> >
> > A diff from the previous version is available at:
> > http://www.ietf.org/rfcdiff?url2=draft-barnes-healthy-food-07
> >
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> > _______________________________________________
> > I-D-Announce mailing list
> > I-D-Announce@ietf.org
> > https://www.ietf.org/mailman/listinfo/i-d-announce
> > Internet-Draft directories: http://www.ietf.org/shadow.html
> > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>

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

<div dir=3D"ltr">Yes, it is hard to draw the line. =A0I did remove some mat=
erial around the statistics, etc that seemed to be of concern to some folks=
. =A0However, I think for folks that don&#39;t deal with this stuff, the ba=
ckground can be helpful. =A0It is hard for some folks to really get why som=
e of us have to be, or choose to be, so very particular about what we eat. =
=A0That was extremely evident during the discussion that motivated this doc=
ument after the meeting in Dublin (countryside). =A0<div>
<div><div><br></div><div>If you have suggestions on text that could be prun=
ed, that would be helpful. =A0I&#39;ll make another pass as well and see if=
 I can trim some things.=A0</div><div><br></div><div>Thanks,</div><div>Mary=
.=A0</div>
</div></div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_qu=
ote">On Tue, Jul 16, 2013 at 12:09 PM, Adrian Farrel <span dir=3D"ltr">&lt;=
<a href=3D"mailto:adrian@olddog.co.uk" target=3D"_blank">adrian@olddog.co.u=
k</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">Mary,<br>
<br>
I appreciate your work on this document, but I don&#39;t know where or how =
to draw<br>
the line.<br>
<br>
Personally, I will strongly try to be vegetarian, but eat meat rather than<=
br>
starve (a situation that arises when travelling).<br>
But I will also try to eat fairly traded produce, and also try to reduce th=
e<br>
food-miles. I prefer food that can be traced to source (which is hopefully<=
br>
local).<br>
<br>
I wonder whether your draft should either go into *all* details, or try to<=
br>
up-level a bit to limit itself to imperatives (such as allergies and religi=
ous<br>
requirements).<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Adrian<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
&gt; -----Original Message-----<br>
&gt; From: <a href=3D"mailto:i-d-announce-bounces@ietf.org">i-d-announce-bo=
unces@ietf.org</a> [mailto:<a href=3D"mailto:i-d-announce-bounces@ietf.org"=
>i-d-announce-bounces@ietf.org</a>]<br>
&gt; On Behalf Of <a href=3D"mailto:internet-drafts@ietf.org">internet-draf=
ts@ietf.org</a><br>
&gt; Sent: 16 July 2013 17:32<br>
&gt; To: <a href=3D"mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</a>=
<br>
&gt; Subject: I-D Action: draft-barnes-healthy-food-07.txt<br>
&gt;<br>
&gt;<br>
&gt; A New Internet-Draft is available from the on-line Internet-Drafts<br>
directories.<br>
&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 Title =A0 =A0 =A0 =A0 =A0 : Healthy Food and Special Dieta=
ry Requirements for IETF<br>
&gt; meetings<br>
&gt; =A0 =A0 =A0 Author(s) =A0 =A0 =A0 : Mary Barnes<br>
&gt; =A0 =A0 =A0 Filename =A0 =A0 =A0 =A0: draft-barnes-healthy-food-07.txt=
<br>
&gt; =A0 =A0 =A0 Pages =A0 =A0 =A0 =A0 =A0 : 18<br>
&gt; =A0 =A0 =A0 Date =A0 =A0 =A0 =A0 =A0 =A0: 2013-07-15<br>
&gt;<br>
&gt; Abstract:<br>
&gt; =A0 =A0This document describes the basic requirements for food for fol=
ks<br>
&gt; =A0 =A0that attend IETF meetings require special diets, as well as tho=
se<br>
&gt; =A0 =A0that prefer to eat healthy. =A0While, the variety of special di=
ets is<br>
&gt; =A0 =A0quite broad, the most general categories are described. =A0Ther=
e can be<br>
&gt; =A0 =A0controversy as to what constitutes healthy eating, but there ar=
e some<br>
&gt; =A0 =A0common, generally available foods that comprise the basis for h=
ealthy<br>
&gt; =A0 =A0eating and special diets. =A0This document provides some<br>
&gt; =A0 =A0recommendations to meeting planners, as well as participants, i=
n<br>
&gt; =A0 =A0handling these requirements.<br>
&gt;<br>
&gt;<br>
&gt; The IETF datatracker status page for this draft is:<br>
&gt; <a href=3D"https://datatracker.ietf.org/doc/draft-barnes-healthy-food"=
 target=3D"_blank">https://datatracker.ietf.org/doc/draft-barnes-healthy-fo=
od</a><br>
&gt;<br>
&gt; There&#39;s also a htmlized version available at:<br>
&gt; <a href=3D"http://tools.ietf.org/html/draft-barnes-healthy-food-07" ta=
rget=3D"_blank">http://tools.ietf.org/html/draft-barnes-healthy-food-07</a>=
<br>
&gt;<br>
&gt; A diff from the previous version is available at:<br>
&gt; <a href=3D"http://www.ietf.org/rfcdiff?url2=3Ddraft-barnes-healthy-foo=
d-07" target=3D"_blank">http://www.ietf.org/rfcdiff?url2=3Ddraft-barnes-hea=
lthy-food-07</a><br>
&gt;<br>
&gt;<br>
&gt; Internet-Drafts are also available by anonymous FTP at:<br>
&gt; <a href=3D"ftp://ftp.ietf.org/internet-drafts/" target=3D"_blank">ftp:=
//ftp.ietf.org/internet-drafts/</a><br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; I-D-Announce mailing list<br>
&gt; <a href=3D"mailto:I-D-Announce@ietf.org">I-D-Announce@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/i-d-announce" target=
=3D"_blank">https://www.ietf.org/mailman/listinfo/i-d-announce</a><br>
&gt; Internet-Draft directories: <a href=3D"http://www.ietf.org/shadow.html=
" target=3D"_blank">http://www.ietf.org/shadow.html</a><br>
&gt; or <a href=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt" target=3D"_bl=
ank">ftp://ftp.ietf.org/ietf/1shadow-sites.txt</a><br>
<br>
</div></div></blockquote></div><br></div>

--20cf3074b5f6762a8004e1a42dab--

From john-ietf@jck.com  Tue Jul 16 10:56:49 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D34F821F9E44 for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 10:56:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.636
X-Spam-Level: 
X-Spam-Status: No, score=-102.636 tagged_above=-999 required=5 tests=[AWL=-0.037, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hvAH8VS-vNWH for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 10:56:44 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 5C86F21F9E6A for <ietf@ietf.org>; Tue, 16 Jul 2013 10:56:44 -0700 (PDT)
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 1Uz9UE-000FKr-Qh; Tue, 16 Jul 2013 13:56:30 -0400
Date: Tue, 16 Jul 2013 13:56:25 -0400
From: John C Klensin <john-ietf@jck.com>
To: Ofer Inbar <cos@aaaaa.org>, Doug Barton <dougb@dougbarton.us>
Subject: Re: The case of dotless domains
Message-ID: <20830BF274CBFAB2009A918E@JcK-HP8200.jck.com>
In-Reply-To: <20130716150721.GG29401@mip.aaaaa.org>
References: <20130713152747.8F79D18C0D0@mercury.lcs.mit.edu> <51E18737.4080903@isdg.net> <3725D4B2-65DA-45FA-AAEE-309F45CD6F18@checkpoint.com> <51E2A8EE.5010200@isdg.net> <A0984871-D92D-4110-9001-16B363B65AC0@checkpoint.com> <6.2.5.6.2.20130714205140.0ce1f0b8@resistor.net> <51E4DC6C.3040609@dougbarton.us> <20130716150721.GG29401@mip.aaaaa.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: S Moonesamy <sm+ietf@elandsys.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jul 2013 17:56:49 -0000

--On Tuesday, July 16, 2013 11:07 -0400 Ofer Inbar
<cos@aaaaa.org> wrote:

>...
> What this brings to mind is that we had a DNS system that was
> vulnerable to the addition of something to the DNS that people
> had expected nobody would make the mistake of doing, but it
> happened and caused damage, and the net reacted by altering
> how DNS software works in order to protect against that
> damage.  At the time, the obvious defensive change was "don't
> do implicit domain search".  If dotless domains cause damage
> as many people here predict, what I'm saying is that I think
> we'll react similarly, and that I guess the defensive change
> people will widely deploy is to reject A/AAAA/MX records at
> the top level.

Two additional observations about this.   Ofer's explanation
about the edu.com example and the resultant ban on heuristic
search is consistent with RFC 1535 and what little I remember of
the history.   However...

* The RFC 1535 defensive change was far more practical in 1993
than it is today, just because of the size of the Internet, the
number of deployed DNS servers and resolvers, and the
difficulties of deploying "required" upgrades.  So the harm
level or likely duration of harm should dotless TLDs be deployed
is greater today or at least less likely to yield quickly to a
defensive change.

* A different example of searching issues caused a good deal of
disruption when it came up (several years earlier than the
EDU.COM. case) and may be relevant to ICANN's current plans and
their likely effects.   In that case, a very large number of
computer science departments in universities all over the world
quite reasonably were delegated domains like
CS.university-name.EDU, often resulting in
host1.CS.university.EDU, host2.CS.university.EDU and email
addresses like username@CS.university.EDU.  Whether by relying
on the heuristics that RFC 1535 banned or by explicit search,
institutions set up name completion so that a reference from
within that institution to username@CS (or username2@chem or
username3@art -- you get the idea) worked as everyone expected,
yielding username@CS.university.EDU, etc.   Usually, host1.CS
did too -- this is not just about "dotless" domains.

Then the TLD for Czechoslovakia was delegated under the
then-assigned ISO 3166 code of CS and unpleasant things started
happening.  Users in some institutions couldn't find Czech sites
at all; others had no problems.  In some cases in which search
rather than mere completion was used, some names would be found,
some names wouldn't, and false positives become possible.  If
there is advice for ICANN in this it is that, when DNS searching
scenarios are involved, it is not sufficient to worry about
possible conflicts between proposed new TLDs and existing
private-use pseudo-TLDs (such as "local.")   Instead, conflicts
with existing second or third-level labels (and perhaps ones
even further down the tree) have to be considered if completion
or search configurations involving those labels might give them
the same appearance as a TLD or subdomains of that TLD.

Whether the IAB should have included any of this in its
Statement is, IMO, another matter.  My personal bias is that, if
the IAB starts making Statements about the implications of a
technological choice, they should be comprehensive about the
relevant subject.  That principle would call for discussion, not
only of the email issues that started this thread, but the "CS."
case and many of the other issues that have been mentioned.  On
the other hand, there are arguments against that principle,
especially when a body like ICANN is concerned and there is
reason to believe that any statement more than a paragraph or
two long will be unread by many people in the intended audience.
Personally, I would have preferred it had the IAB been explicit
about what issues they were and were not addressing if they
decided to avoid a comprehensive discussion -- at least then,
people might be debating their choices but not whether they are
exhibiting their ignorance.  But that is just my opinion.

    john



From john-ietf@jck.com  Tue Jul 16 11:04:02 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD97C21F9C4F for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 11:04:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.634
X-Spam-Level: 
X-Spam-Status: No, score=-102.634 tagged_above=-999 required=5 tests=[AWL=-0.035, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tII9IjTeC48q for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 11:03:57 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 86DC421F9A05 for <ietf@ietf.org>; Tue, 16 Jul 2013 11:03:49 -0700 (PDT)
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 1Uz9bE-000FLw-KS; Tue, 16 Jul 2013 14:03:44 -0400
Date: Tue, 16 Jul 2013 14:03:39 -0400
From: John C Klensin <john-ietf@jck.com>
To: adrian@olddog.co.uk, draft-barnes-healthy-food@tools.ietf.org
Subject: Re: I-D Action: draft-barnes-healthy-food-07.txt
Message-ID: <B6E25FF4CE904AF154E73319@JcK-HP8200.jck.com>
In-Reply-To: <0e1501ce8247$45197bf0$cf4c73d0$@olddog.co.uk>
References: <20130716163157.28468.93383.idtracker@ietfa.amsl.com> <0e1501ce8247$45197bf0$cf4c73d0$@olddog.co.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
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jul 2013 18:04:02 -0000

--On Tuesday, July 16, 2013 18:09 +0100 Adrian Farrel
<adrian@olddog.co.uk> wrote:

>...
> Personally, I will strongly try to be vegetarian, but eat meat
> rather than starve (a situation that arises when travelling).
>...

I'm in much the same situation, but suggests that part of this
feeds back into some of the venue selection issues: if a venue
is chosen that forces you (or me or others) into a "meat or
starve" or, much worse, "eat something severely damaging to
health or beliefs or starve" situation, is that really an
acceptable venue?  And, if it is not and it is chosen anyway
(either deliberately after considering other factors or out of
ignorance), who is accountable and to whom?

    john





From Ted.Lemon@nominum.com  Tue Jul 16 11:15:12 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF4BD11E80AD for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 11:15:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.592
X-Spam-Level: 
X-Spam-Status: No, score=-106.592 tagged_above=-999 required=5 tests=[AWL=0.007, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NPm9ucKgz1Js for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 11:15:06 -0700 (PDT)
Received: from exprod7og125.obsmtp.com (exprod7og125.obsmtp.com [64.18.2.28]) by ietfa.amsl.com (Postfix) with ESMTP id 2D64811E80D5 for <ietf@ietf.org>; Tue, 16 Jul 2013 11:15:06 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob125.postini.com ([64.18.6.12]) with SMTP ID DSNKUeWNqBgJgz4TFxA7VpjDRciT9iGfUGIU@postini.com; Tue, 16 Jul 2013 11:15:06 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 831111B8228 for <ietf@ietf.org>; Tue, 16 Jul 2013 11:15:04 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 68FEC190043; Tue, 16 Jul 2013 11:15:04 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Tue, 16 Jul 2013 11:15:04 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: John C Klensin <john-ietf@jck.com>
Subject: Re: I-D Action: draft-barnes-healthy-food-07.txt
Thread-Topic: I-D Action: draft-barnes-healthy-food-07.txt
Thread-Index: AQIKfiTNkPkLWdefr8jDMRdxEhClWJjvkHzggACGLICAAAMvgA==
Date: Tue, 16 Jul 2013 18:15:03 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307752142CD@mbx-01.win.nominum.com>
References: <20130716163157.28468.93383.idtracker@ietfa.amsl.com> <0e1501ce8247$45197bf0$cf4c73d0$@olddog.co.uk> <B6E25FF4CE904AF154E73319@JcK-HP8200.jck.com>
In-Reply-To: <B6E25FF4CE904AF154E73319@JcK-HP8200.jck.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <FC2B07B49CFADE4A9784C57BF2CC773A@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<adrian@olddog.co.uk>" <adrian@olddog.co.uk>, "<ietf@ietf.org>" <ietf@ietf.org>, "<draft-barnes-healthy-food@tools.ietf.org>" <draft-barnes-healthy-food@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jul 2013 18:15:13 -0000

On Jul 16, 2013, at 11:03 AM, John C Klensin <john-ietf@jck.com> wrote:
> And, if it is not and it is chosen anyway
> (either deliberately after considering other factors or out of
> ignorance), who is accountable and to whom?

Part of the value of writing a document like this is to capture the issues =
in such a way that the venue can answer the question "can you accommodate o=
ur needs" accurately.   Dietary health issues are very important, and not e=
verybody has the level of expertise that would allow them to even know that=
 they were giving an incorrect answer to a question about them, so the bett=
er the questions you can ask, the more likely it is that we will avoid prob=
lems.   If there is someone to blame or to be accountable, it's already too=
 late, and furthermore there's absolutely no benefit to someone feeling bad=
 about getting it wrong, or getting yelled at because they got it wrong.   =
Certainly on our side of the negotiation everybody _wants_ to get it right,=
 and I seriously doubt that that would not be the case for the operators of=
 a meeting venue either.


From adrian@olddog.co.uk  Tue Jul 16 11:37:16 2013
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82F1321F9AAE for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 11:37:16 -0700 (PDT)
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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cd7+rOoqkkij for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 11:37:10 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id 7DFB921F9950 for <ietf@ietf.org>; Tue, 16 Jul 2013 11:37:10 -0700 (PDT)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r6GIb8K9027152;  Tue, 16 Jul 2013 19:37:09 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r6GIb7tV027138 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 16 Jul 2013 19:37:08 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'John C Klensin'" <john-ietf@jck.com>, <draft-barnes-healthy-food@tools.ietf.org>
References: <20130716163157.28468.93383.idtracker@ietfa.amsl.com> <0e1501ce8247$45197bf0$cf4c73d0$@olddog.co.uk> <B6E25FF4CE904AF154E73319@JcK-HP8200.jck.com>
In-Reply-To: <B6E25FF4CE904AF154E73319@JcK-HP8200.jck.com>
Subject: RE: I-D Action: draft-barnes-healthy-food-07.txt
Date: Tue, 16 Jul 2013 19:37:06 +0100
Message-ID: <0e3c01ce8253$796ebd00$6c4c3700$@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: AQIKfiTNkPkLWdefr8jDMRdxEhClWAHQKMnpAZpUTf6Y1FQJYA==
Content-Language: en-gb
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 16 Jul 2013 18:37:16 -0000

> > Personally, I will strongly try to be vegetarian, but eat meat
> > rather than starve (a situation that arises when travelling).
> 
> if a venue is chosen that forces you (or me or others) into
> a "meat or starve" or, much worse, "eat something severely
> damaging to health or beliefs or starve" situation, is that 
> really an acceptable venue? 

Yes, it is.
If a venue is inconvenient or uncomfortable for a small percentage of "regular"
IETF participants, that does not make it a poor choice of venue.

We might as well go back to the debate about location: only a venue that is a
convenient 10 minutes from my home is really a suitable venue.

I venture that "starve" is never a real outcome, but "go to a supermarket" or
"bring food in your luggage" are alternatives that need some planning and are a
small inconvenience.

Adrian


From andy@yumaworks.com  Tue Jul 16 11:44:01 2013
Return-Path: <andy@yumaworks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6B1511E80D5 for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 11:44:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.724
X-Spam-Level: 
X-Spam-Status: No, score=-2.724 tagged_above=-999 required=5 tests=[AWL=0.253,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O-jNo5D73XBZ for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 11:43:56 -0700 (PDT)
Received: from mail-pa0-f49.google.com (mail-pa0-f49.google.com [209.85.220.49]) by ietfa.amsl.com (Postfix) with ESMTP id 89BE121F9956 for <ietf@ietf.org>; Tue, 16 Jul 2013 11:43:56 -0700 (PDT)
Received: by mail-pa0-f49.google.com with SMTP id ld11so1067537pab.36 for <ietf@ietf.org>; Tue, 16 Jul 2013 11:43:53 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=lU5rcQPU4GeQjqvmTd22XqYJVe5lMmzybNGEEJd6U/4=; b=it0fTgFoN69mIO5UfD//RvBOYDTFaVcesB16CFgTMRB4SvMb3CnpTQMQJvq8TedFQM 3uR0GL6AKadX/w32nQKvVbHXFtj2d1LmLu4JUkC8XOsa5N1pwyeXV1ldqoTq8dm4G6h4 1mgFbdNhgiMNWhN1BVPaozwxwXpFfZCWaZeFWWypC9hx6JEiiPVA8vkE4d/3ifC6wfNG g0BdNRBKGBWQP9kzV5r1IOumjcPkcaz+ZFreE+DwOadouQ4zRk/5jB+3CpiJDkylTdhn WzGF1pK+hrHqaWFNTG73PuSX+vFp3VmzOPV9H6v66evdpo4uVfl7WRmWDQvWusQuX/zm Nz7g==
MIME-Version: 1.0
X-Received: by 10.66.234.71 with SMTP id uc7mr3989309pac.10.1374000233895; Tue, 16 Jul 2013 11:43:53 -0700 (PDT)
Received: by 10.70.12.161 with HTTP; Tue, 16 Jul 2013 11:43:53 -0700 (PDT)
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307752140AD@mbx-01.win.nominum.com>
References: <20130716163157.28468.93383.idtracker@ietfa.amsl.com> <0e1501ce8247$45197bf0$cf4c73d0$@olddog.co.uk> <8D23D4052ABE7A4490E77B1A012B6307752140AD@mbx-01.win.nominum.com>
Date: Tue, 16 Jul 2013 11:43:53 -0700
Message-ID: <CABCOCHRhYJ5HJ+n0kCOt84LfF4MT0f5jgxu42BSgvY8SfHJFRQ@mail.gmail.com>
Subject: Re: I-D Action: draft-barnes-healthy-food-07.txt
From: Andy Bierman <andy@yumaworks.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQkpp8e5YxInn7gBPncDsEjOp+8XAUvRidIu76A8mNxYq228zJDIXivoH7Sd4x2fmXYOCEAm
Cc: "<adrian@olddog.co.uk>" <adrian@olddog.co.uk>, "<ietf@ietf.org>" <ietf@ietf.org>, "<draft-barnes-healthy-food@tools.ietf.org>" <draft-barnes-healthy-food@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jul 2013 18:44:01 -0000

Hi,

On Tue, Jul 16, 2013 at 10:17 AM, Ted Lemon <Ted.Lemon@nominum.com> wrote:
>...
> given the number of graybeards who attend IETF,
> I think paying attention to the problem of excessive sugar in break foods is really important.
>

I'm not supposed to have sugar, so the massive quantities of cookies,
brownies, ice cream, etc. in the breaks are an unwanted distraction.
But that doesn't mean I want celery and carrots instead. :-)
I suggest more cheese and crackers, sandwiches, etc.
and perhaps less cookies.

Andy

From randy@psg.com  Tue Jul 16 11:46:58 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA80C11E80ED for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 11:46:58 -0700 (PDT)
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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kpEg8PnBYYd8 for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 11:46:58 -0700 (PDT)
Received: from ran.psg.com (unknown [IPv6:2001:418:8006::19]) by ietfa.amsl.com (Postfix) with ESMTP id 6D5F111E80D5 for <ietf@ietf.org>; Tue, 16 Jul 2013 11:46:55 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1UzAGz-0004IS-0l; Tue, 16 Jul 2013 18:46:53 +0000
Date: Tue, 16 Jul 2013 11:46:52 -0700
Message-ID: <m2ppuipckj.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: John C Klensin <john-ietf@jck.com>
Subject: Re: I-D Action: draft-barnes-healthy-food-07.txt
In-Reply-To: <B6E25FF4CE904AF154E73319@JcK-HP8200.jck.com>
References: <20130716163157.28468.93383.idtracker@ietfa.amsl.com> <0e1501ce8247$45197bf0$cf4c73d0$@olddog.co.uk> <B6E25FF4CE904AF154E73319@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
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jul 2013 18:46:58 -0000

two hypotheses:
  o there is no venue which is easy/acceptable to all ietf participants
  o there is no ietf participant for whom all venues are easy/acceptable

randy, who is happy not to be on the meetings committee

From Ted.Lemon@nominum.com  Tue Jul 16 11:48:02 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C6DD21F9A35 for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 11:48:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.592
X-Spam-Level: 
X-Spam-Status: No, score=-106.592 tagged_above=-999 required=5 tests=[AWL=0.007, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rckaS94StTFh for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 11:47:55 -0700 (PDT)
Received: from exprod7og117.obsmtp.com (exprod7og117.obsmtp.com [64.18.2.6]) by ietfa.amsl.com (Postfix) with ESMTP id 50BC921F8267 for <ietf@ietf.org>; Tue, 16 Jul 2013 11:47:55 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob117.postini.com ([64.18.6.12]) with SMTP ID DSNKUeWVWybEQFyaWviwDFlaMsM0FKvuXyXh@postini.com; Tue, 16 Jul 2013 11:47:55 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id D468B1B8248 for <ietf@ietf.org>; Tue, 16 Jul 2013 11:47:54 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 878B4190043; Tue, 16 Jul 2013 11:47:53 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Tue, 16 Jul 2013 11:47:53 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "<adrian@olddog.co.uk>" <adrian@olddog.co.uk>
Subject: Re: I-D Action: draft-barnes-healthy-food-07.txt
Thread-Topic: I-D Action: draft-barnes-healthy-food-07.txt
Thread-Index: AQIKfiTNkPkLWdefr8jDMRdxEhClWJjvkHzggACGLICAAAlYAIAAAwIA
Date: Tue, 16 Jul 2013 18:47:53 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077521448F@mbx-01.win.nominum.com>
References: <20130716163157.28468.93383.idtracker@ietfa.amsl.com> <0e1501ce8247$45197bf0$cf4c73d0$@olddog.co.uk> <B6E25FF4CE904AF154E73319@JcK-HP8200.jck.com> <0e3c01ce8253$796ebd00$6c4c3700$@olddog.co.uk>
In-Reply-To: <0e3c01ce8253$796ebd00$6c4c3700$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2C7E3124F599A5429E12F4E0777BA1CA@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: John C Klensin <john-ietf@jck.com>, "<ietf@ietf.org>" <ietf@ietf.org>, "<draft-barnes-healthy-food@tools.ietf.org>" <draft-barnes-healthy-food@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jul 2013 18:48:02 -0000

On Jul 16, 2013, at 11:37 AM, Adrian Farrel <adrian@olddog.co.uk> wrote:
> I venture that "starve" is never a real outcome, but "go to a supermarket=
" or
> "bring food in your luggage" are alternatives that need some planning and=
 are a
> small inconvenience.

Try it sometime, then get back to us.   :)

I rented a car in Orlando, which just about doubled the cost of my stay.   =
This is a pretty strong negative for a venue.   And I suspect that "needs s=
ome kind of nonstandard food" is not quite as small a minority as you imagi=
ne it is.   Particularly when "nonstandard"=3D=3D"what is served in the hot=
el restaurant," which, in large hotels, tends to actually be a very constra=
ined, unhealthy diet even for those who can eat it.   I was feeling so crap=
py after several days of the hotel food at the most recent venue we shared =
together that  I had to flee the meeting and search Dublin for some probiot=
ics and roughage.   I am happy for you that you don't have this problem.


From Ted.Lemon@nominum.com  Tue Jul 16 11:48:35 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D6B121F994B for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 11:48:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.593
X-Spam-Level: 
X-Spam-Status: No, score=-106.593 tagged_above=-999 required=5 tests=[AWL=0.006, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J7adTa1eC0vo for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 11:48:28 -0700 (PDT)
Received: from exprod7og113.obsmtp.com (exprod7og113.obsmtp.com [64.18.2.179]) by ietfa.amsl.com (Postfix) with ESMTP id 62C9E11E8101 for <ietf@ietf.org>; Tue, 16 Jul 2013 11:48:26 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob113.postini.com ([64.18.6.12]) with SMTP ID DSNKUeWVeufl7QWLGknWsazRtqWDuPaY3shg@postini.com; Tue, 16 Jul 2013 11:48:26 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 042051B8244 for <ietf@ietf.org>; Tue, 16 Jul 2013 11:48:26 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id F1621190043; Tue, 16 Jul 2013 11:48:25 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Tue, 16 Jul 2013 11:48:26 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Andy Bierman <andy@yumaworks.com>
Subject: Re: I-D Action: draft-barnes-healthy-food-07.txt
Thread-Topic: I-D Action: draft-barnes-healthy-food-07.txt
Thread-Index: AQIKfiTNkPkLWdefr8jDMRdxEhClWJjvkHzggAB5ZICAABgFgIAAAUMA
Date: Tue, 16 Jul 2013 18:48:24 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077521449E@mbx-01.win.nominum.com>
References: <20130716163157.28468.93383.idtracker@ietfa.amsl.com> <0e1501ce8247$45197bf0$cf4c73d0$@olddog.co.uk> <8D23D4052ABE7A4490E77B1A012B6307752140AD@mbx-01.win.nominum.com> <CABCOCHRhYJ5HJ+n0kCOt84LfF4MT0f5jgxu42BSgvY8SfHJFRQ@mail.gmail.com>
In-Reply-To: <CABCOCHRhYJ5HJ+n0kCOt84LfF4MT0f5jgxu42BSgvY8SfHJFRQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <B912A707FE6094468D474A108716B6D9@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<adrian@olddog.co.uk>" <adrian@olddog.co.uk>, "<ietf@ietf.org>" <ietf@ietf.org>, "<draft-barnes-healthy-food@tools.ietf.org>" <draft-barnes-healthy-food@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jul 2013 18:48:35 -0000

On Jul 16, 2013, at 11:43 AM, Andy Bierman <andy@yumaworks.com> wrote:
> I suggest more cheese and crackers, sandwiches, etc.
> and perhaps less cookies.

+1

Celery will not prevent a blood sugar crash.


From abdussalambaryun@gmail.com  Tue Jul 16 12:18:21 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 379E021F9A2E for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 12:18:18 -0700 (PDT)
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=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UBUKWFcM2Gx0 for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 12:18:17 -0700 (PDT)
Received: from mail-pb0-x236.google.com (mail-pb0-x236.google.com [IPv6:2607:f8b0:400e:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id 4423B21F96A7 for <ietf@ietf.org>; Tue, 16 Jul 2013 12:18:16 -0700 (PDT)
Received: by mail-pb0-f54.google.com with SMTP id ro2so1028160pbb.41 for <ietf@ietf.org>; Tue, 16 Jul 2013 12:18:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=adGeufd97kRg53TONKHbate0gzZBt+6ksf338G/RgV0=; b=DGTthJxUhPuRVCpJZxuSpwcuCGkLa3tJdRYiHSugBoDKeQAuRUC5SJB5CXJPGY2DqY zc52qqibih4IP2lmIYKPoSRQDSV+Ldl0AQrEc/oI2RmufF7PTFCQAMY9q2Zv4YTQ3o21 P3t5c6IGsrOi65hksnf7DOv9M71ZQEa00yd7nGTqZUgPytORcSmJWFMDzpXESnZIqy+L bEPlekkQRtVEBrpJJS7LiguQzZjXTJfkTOgCv54ncHtVQ2jLDClGgTaqbbD0iuA1PNWR HRQ+0fcIxjYZKYQ7K2hfWIl8r/3aIfd6PcBaDWn1MNU8gcdLAPD8uT76JnbmkA8tkh4k dxaQ==
MIME-Version: 1.0
X-Received: by 10.68.221.102 with SMTP id qd6mr3055267pbc.30.1374002295956; Tue, 16 Jul 2013 12:18:15 -0700 (PDT)
Received: by 10.68.250.133 with HTTP; Tue, 16 Jul 2013 12:18:15 -0700 (PDT)
In-Reply-To: <3DFDE06F-EAAA-4AA0-8DF4-AC2033C644D7@gmail.com>
References: <20130712205852.10265.88487.idtracker@ietfa.amsl.com> <CADnDZ8-Gx_=rL7g-0MDSLqXRDmgH5mBP1gu-3vCF_Ng66kncGA@mail.gmail.com> <3DFDE06F-EAAA-4AA0-8DF4-AC2033C644D7@gmail.com>
Date: Tue, 16 Jul 2013 20:18:15 +0100
Message-ID: <CADnDZ8-wXi3_7XN8GA8hygeZjTArYkbWymCm+rWTPrAYZRXpoA@mail.gmail.com>
Subject: Re: Sunday IAOC Overview Session at the Berlin IETF
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Bob Hinden <bob.hinden@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b2ed53dc5699f04e1a5d6ba
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jul 2013 19:18:22 -0000

--047d7b2ed53dc5699f04e1a5d6ba
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi Bob,

thanks and respond below,

On Mon, Jul 15, 2013 at 8:55 PM, Bob Hinden <bob.hinden@gmail.com> wrote:

> AB,
>
> >
> > IMO the questions/comments that may be ok to see added to discuss are:
> >
> > 1) Venue selection and operation of the IETF meetings
> > ++++++++++++++++
> > - Selection of the current venue and was there difficulties until
> > getting to this meeting session time. From the managing meeting
> > (providing services) and the community use of the meeting. (10 minute
> > discuss if needed).
>
> I don't understand your question, please clarify.
>

sorry, I ment meetings in the past were they all using the selected venue
successfully, if there was difficulty (in attending, in using the avenue,
in venue resources).

>
> Note that the IAOC selects the venue, provides the network, contracts wit=
h
> the hotel, etc., it is the IESG who is responsible for the agenda for the
> meeting, agenda planning, etc.
>
> >
> > - Is there an alternative venue if the venue was closed for any
> > emergency reason at any time? or only one plan so if the plan changes
> > there can be problems with the communities expected plan because they
> > were not aware of the needed information per time.
>
> No, there is not an alternative venue under contract.  It isn't practical
> to have two venues under contract, build two networks, etc.  It is
> technically feasable, but would cause the registration fee to go up
> significantly to cover the extra costs.
>
I ment that does the contract mention if there was difficulty in using the
venue then an alternative may be an option. Does the finance of the venue
contract is non-refundable ( a plan for service and maintenance).

>
> If there was, for example, a fire at a venue months before the the meetin=
g
> we would look for an alternate, but what happens would depend on
> availability of alternative venues.  We have good relationships with the
> hotel chains we use and they would work very hard to find an alternative
> venue, as would the effected venue.
>

So I understand there is no plan, we only think about alternative when a
problem appears. I wanted if possible a discuss on this issue.

>
> >
> > - Is there an historic/informational RFC issued by IAOC of
> > difficulties or important comments in past of venues attended?
>
>
> No.  There is an extensive record of comments about venue on the attendee=
s
> list for individual meetings and the IAOC reports to the community.  Also=
,
> meeting surveys with community feedback: http://iaoc.ietf.org/surveys.htm=
l
>
Ok

>
> >
> > - Regarding advice within emergency situations (in or out the meeting
> > venue), is it considered within chosing the managing meeting
> > plan/venue, and is the emergency solution an available information for
> > attended participants and who will attend within a meeting day.
>
> Assuming you mean while the meeting is taking place, the secretariat and
> venue have emergency plans in place.  The secretariat discuses safety and
> emergency medial procedures with the venue to be prepared if anything
> should happen.
>
Ok, so I understand that the safety procedure is discussed but not
emailed/sended to registered participants.

>
>
> >
> > - Someone may like to know if is going to attend at a meeting, how is
> > the meeting venue managed per time slots, is there a way of quick
> > feedback/communication of registered-community for meetings (you may
> > say IETF list but are they connected). The information availability
> > can be used for others not attended and whom may attend at any time.
> > (the venue ran out of coffee/water, so I may buy one while going to
> > venue, or any other issue which can happen out of expected/plan).
>
> The IETF meeting agenda is managed by the IESG.
>
> Problems with the meeting venue can be reported to the Meeting Trouble
> Desk at mtd@ietf.org.  Problems with the network can be reported to the
> NOC at noc@ietf.org.
>
> ok thanks,

>
> >
> > 2) Other issue:
> > +++++++++
> > -Is there a future work plan milestones discussed? can be added to [*]
>
>
> Not sure what your are asking about, but future meetings are posted on th=
e
> IETF web site and the process and timeline for meeting planning is part o=
f
> the IAOC overview presentation.
>
> sorry, I ment what to discuss, is the community work plan of discuss, so
IAOC knows what it is discussing each time, but does the community just
follow presented issues, or we can come together and plan how we
discuss/influence with IAOC. (this point was trigered when I read your call
to community to suggest what to discuss). Each WG in IETF has milestones,
but I not sure of the general area milestones related to meetings
selections.

>
>
> > -I am not sure if was discussed before and answered (I am sorry if
> > repeated), where do I go to find important past/current Q&A for IAOC
> > (to avoid efforts to be wasted, and unite best answers)? if not
> > available it can be good to find it at [*].
>
> Recent plenaries reports and the last IAOC overview session have been
> recored by Meetecho.  The last IAOC overview is on the main page at
> http://iaoc.ietf.org.  Also, plenary proceedings and jabber logs in the
> usual places, for example http://iaoc.ietf.org/plenary-reports.html
>

The reason of my comments/questions I wanted a discuss related to venue as
more safe, because being prepared for disasters is important for all
organisations including IETF (see below references). I beleive the
selection of venue with best-evacuate-options/emergency-plan should be
considered as factor of better option (considering variable number of
participants per room/day). Once some one mentioned that we don't do
meeting in some countries because of high possibility of disaster, so now I
comment if we already agreed on one country, does the IAOC consider
planning of recovery (e.g. even in North America there was disasters, which
is mostly where IETF meet)

Krock, R., E., =91Lack of Emergency Recovery Planning Is a Disaster Waiting
to Happen=92, IEEE Commun. Mag., Vol.49, No.1, pp 48-51, Jan 2011.

Oberg, J., C., Whitt, A., G., and Mills, R., M., =91Disasters Will Happen =
=96
Are You Ready?=92, IEEE Commun. Mag., Vol.49, No.1, pp 36-42, Jan 2011.

Thanks

AB

--047d7b2ed53dc5699f04e1a5d6ba
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi Bob,</div><div>=A0</div><div>thanks=A0and respond =
below,<br><br></div><div class=3D"gmail_quote">On Mon, Jul 15, 2013 at 8:55=
 PM, Bob Hinden <span dir=3D"ltr">&lt;<a href=3D"mailto:bob.hinden@gmail.co=
m" target=3D"_blank">bob.hinden@gmail.com</a>&gt;</span> wrote:<br>


<blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-=
color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class=
=3D"gmail_quote">AB,<br>
<div><br>
&gt;<br>
&gt; IMO the questions/comments that may be ok to see added to discuss are:=
<br>
&gt;<br>
&gt; 1) Venue selection and operation of the IETF meetings<br>
&gt; ++++++++++++++++<br>
&gt; - Selection of the current venue and was there difficulties until<br>
&gt; getting to this meeting session time. From the managing meeting<br>
&gt; (providing services) and the community use of the meeting. (10 minute<=
br>
&gt; discuss if needed).<br>
<br>
</div>I don&#39;t understand your question, please clarify.<br></blockquote=
><div>=A0</div><div>sorry, I ment meetings in the past were they all using =
the selected venue successfully, if there was difficulty (in attending, in =
using the avenue, in venue resources).</div>
<blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-=
color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class=
=3D"gmail_quote">


<br>
Note that the IAOC selects the venue, provides the network, contracts with =
the hotel, etc., it is the IESG who is responsible for the agenda for the m=
eeting, agenda planning, etc.<br>
<div><br>
&gt;<br>
&gt; - Is there an alternative venue if the venue was closed for any<br>
&gt; emergency reason at any time? or only one plan so if the plan changes<=
br>
&gt; there can be problems with the communities expected plan because they<=
br>
&gt; were not aware of the needed information per time.<br>
<br>
</div>No, there is not an alternative venue under contract. =A0It isn&#39;t=
 practical to have two venues under contract, build two networks, etc. =A0I=
t is technically feasable, but would cause the registration fee to go up si=
gnificantly to cover the extra costs.<br>
</blockquote><div>I ment that does the contract mention if there was diffic=
ulty in using the venue then an alternative may be an option. Does the fina=
nce of the venue contract=A0is non-refundable ( a plan for service and main=
tenance).=A0</div>
<blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-=
color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class=
=3D"gmail_quote">


<br>
If there was, for example, a fire at a venue months before the the meeting =
we would look for an alternate, but what happens would depend on availabili=
ty of alternative venues. =A0We have good relationships with the hotel chai=
ns we use and they would work very hard to find an alternative venue, as wo=
uld the effected venue.<br>
</blockquote><div>=A0</div><div>So I understand there is no plan, we only t=
hink about alternative when a problem appears. I wanted if possible a discu=
ss on this issue.=A0</div><blockquote style=3D"margin:0px 0px 0px 0.8ex;pad=
ding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;bord=
er-left-style:solid" class=3D"gmail_quote">



<div><br>
&gt;<br>
&gt; - Is there an historic/informational RFC issued by IAOC of<br>
&gt; difficulties or important comments in past of venues attended?<br>
<br>
<br>
</div>No. =A0There is an extensive record of comments about venue on the at=
tendees list for individual meetings and the IAOC reports to the community.=
 =A0Also, meeting surveys with community feedback: <a href=3D"http://iaoc.i=
etf.org/surveys.html" target=3D"_blank">http://iaoc.ietf.org/surveys.html</=
a><br>
</blockquote><div>Ok=A0</div><blockquote style=3D"margin:0px 0px 0px 0.8ex;=
padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;b=
order-left-style:solid" class=3D"gmail_quote">


<div><br>
&gt;<br>
&gt; - Regarding advice within emergency situations (in or out the meeting<=
br>
&gt; venue), is it considered within chosing the managing meeting<br>
&gt; plan/venue, and is the emergency solution an available information for=
<br>
&gt; attended participants and who will attend within a meeting day.<br>
<br>
</div>Assuming you mean while the meeting is taking place, the secretariat =
and venue have emergency plans in place. =A0The secretariat discuses safety=
 and emergency medial procedures with the venue to be prepared if anything =
should happen.<br>
</blockquote><div>Ok, so I understand that the safety procedure is discusse=
d but not emailed/sended to registered participants.=A0</div><blockquote st=
yle=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,=
204,204);border-left-width:1px;border-left-style:solid" class=3D"gmail_quot=
e">



<div><br>
<br>
&gt;<br>
&gt; - Someone may like to know if is going to attend at a meeting, how is<=
br>
&gt; the meeting venue managed per time slots, is there a way of quick<br>
&gt; feedback/communication of registered-community for meetings (you may<b=
r>
&gt; say IETF list but are they connected). The information availability<br=
>
&gt; can be used for others not attended and whom may attend at any time.<b=
r>
&gt; (the venue ran out of coffee/water, so I may buy one while going to<br=
>
&gt; venue, or any other issue which can happen out of expected/plan).<br>
<br>
</div>The IETF meeting agenda is managed by the IESG.<br>
<br>
Problems with the meeting venue can be reported to the Meeting Trouble Desk=
 at <a href=3D"mailto:mtd@ietf.org" target=3D"_blank">mtd@ietf.org</a>. =A0=
Problems with the network can be reported to the NOC at <a href=3D"mailto:n=
oc@ietf.org" target=3D"_blank">noc@ietf.org</a>.<br>



<div><br></div></blockquote><div>ok thanks,=A0</div><blockquote style=3D"ma=
rgin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);=
border-left-width:1px;border-left-style:solid" class=3D"gmail_quote"><div>
<br>
&gt;<br>
&gt; 2) Other issue:<br>
&gt; +++++++++<br>
&gt; -Is there a future work plan milestones discussed? can be added to [*]=
<br>
<br>
<br>
</div>Not sure what your are asking about, but future meetings are posted o=
n the IETF web site and the process and timeline for meeting planning is pa=
rt of the IAOC overview presentation.<br>
<div><br></div></blockquote><div>sorry, I ment=A0what to discuss, is the co=
mmunity work plan of discuss, so IAOC knows what it is discussing each time=
, but does the community just follow presented issues, or we can come toget=
her and plan how we discuss/influence with IAOC. (this point was trigered w=
hen I read your call to community to suggest what to discuss). Each WG in I=
ETF has milestones, but I not sure of the general area milestones related t=
o meetings selections.</div>
<blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-=
color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class=
=3D"gmail_quote"><div>
<br>
<br>
&gt; -I am not sure if was discussed before and answered (I am sorry if<br>
&gt; repeated), where do I go to find important past/current Q&amp;A for IA=
OC<br>
&gt; (to avoid efforts to be wasted, and unite best answers)? if not<br>
&gt; available it can be good to find it at [*].<br>
<br>
</div>Recent plenaries reports and the last IAOC overview session have been=
 recored by Meetecho. =A0The last IAOC overview is on the main page at <a h=
ref=3D"http://iaoc.ietf.org" target=3D"_blank">http://iaoc.ietf.org</a>. =
=A0Also, plenary proceedings and jabber logs in the usual places, for examp=
le <a href=3D"http://iaoc.ietf.org/plenary-reports.html" target=3D"_blank">=
http://iaoc.ietf.org/plenary-reports.html</a><br>
</blockquote><div>=A0</div><div>The reason of my comments/questions I=A0wan=
ted a discuss related to venue as more safe, because being prepared for dis=
asters is important for all organisations including IETF (see below referen=
ces). I beleive the selection of venue with best-evacuate-options/emergency=
-plan=A0should be considered as factor of better option (considering variab=
le number of participants per room/day). Once some one mentioned that we do=
n&#39;t do meeting in some countries because of high possibility of disaste=
r, so now I comment if we already agreed on one country, does the IAOC cons=
ider planning of recovery (e.g. even in North America=A0there was disasters=
, which is mostly where IETF meet)</div>
<div><span style=3D"font-family:&quot;Times New Roman&quot;,&quot;serif&quo=
t;;font-size:10pt" lang=3D"EN-US"><font color=3D"#000000"></font></span>=A0=
</div><div><span style=3D"font-family:&quot;Times New Roman&quot;,&quot;ser=
if&quot;;font-size:10pt" lang=3D"EN-US"><font color=3D"#000000">Krock, R., =
E., =91Lack
of Emergency Recovery Planning Is a Disaster Waiting to Happen=92, IEEE Com=
mun.
Mag., Vol.49, No.1, pp 48-51, Jan 2011.</font></span></div><div><span style=
=3D"font-family:&quot;Times New Roman&quot;,&quot;serif&quot;;font-size:10p=
t" lang=3D"EN-US"><font color=3D"#000000"></font></span>=A0</div><div><span=
 style=3D"font-family:&quot;Times New Roman&quot;,&quot;serif&quot;;font-si=
ze:10pt" lang=3D"EN-US"><span style=3D"font-family:&quot;Times New Roman&qu=
ot;,&quot;serif&quot;;font-size:10pt" lang=3D"EN-US"><font color=3D"#000000=
">Oberg, J., C., Whitt,
A., G., and Mills, R., M., =91Disasters Will Happen =96 Are You Ready?=92, =
IEEE
Commun. Mag., Vol.49, No.1, pp 36-42, Jan 2011.</font></span></span></div><=
div><span style=3D"font-family:&quot;Times New Roman&quot;,&quot;serif&quot=
;;font-size:10pt" lang=3D"EN-US"></span>=A0</div><div>Thanks</div><div>=A0<=
/div>
<div>AB</div></div></div>

--047d7b2ed53dc5699f04e1a5d6ba--

From mary.h.barnes@gmail.com  Tue Jul 16 12:34:13 2013
Return-Path: <mary.h.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A0CB21F9D6B for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 12:34:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Epy3HnvYTXvi for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 12:34:12 -0700 (PDT)
Received: from mail-ve0-x231.google.com (mail-ve0-x231.google.com [IPv6:2607:f8b0:400c:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id 97CFB21F9DBB for <ietf@ietf.org>; Tue, 16 Jul 2013 12:34:04 -0700 (PDT)
Received: by mail-ve0-f177.google.com with SMTP id cz10so822463veb.22 for <ietf@ietf.org>; Tue, 16 Jul 2013 12:34:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=KO6/oLZnGHLgDTfOagv1jTcwSCCd7WUUGgYEY559CWw=; b=GAfJwizdwT3HgdhKJrcg+kIgdtxn0VvatxKVtTvxpJU9zJzfHw5n/nA381xtine+ZL e7zNiPeX6Q4FBLneLlAEwvfcpzj7VKLy0Ql3IDb5qkLsJqxCT1MYFzG8BL3FpHq7/kYe YDzaNk5q3kZIFMIqCqwub78YdkAzY58yVaP58sSWjBoz6FhQ1dIdS7aCx1a4fGne3DA/ 9v4S82vC1GQ7t/9+sIAbroWA8c9nGjHj3+uH3VYuyp3PUoSTttyM8zwGkcKFCJI/dsE+ ZUXENwHCFXgIMg/3FdJy+R9xo7/Iz8SW1qxY6kxQtJfFA4YMHnPIs5wmqDRpKz/aHLdA sLaQ==
MIME-Version: 1.0
X-Received: by 10.52.232.165 with SMTP id tp5mr784589vdc.11.1374003243952; Tue, 16 Jul 2013 12:34:03 -0700 (PDT)
Received: by 10.58.74.97 with HTTP; Tue, 16 Jul 2013 12:34:03 -0700 (PDT)
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B63077521448F@mbx-01.win.nominum.com>
References: <20130716163157.28468.93383.idtracker@ietfa.amsl.com> <0e1501ce8247$45197bf0$cf4c73d0$@olddog.co.uk> <B6E25FF4CE904AF154E73319@JcK-HP8200.jck.com> <0e3c01ce8253$796ebd00$6c4c3700$@olddog.co.uk> <8D23D4052ABE7A4490E77B1A012B63077521448F@mbx-01.win.nominum.com>
Date: Tue, 16 Jul 2013 14:34:03 -0500
Message-ID: <CABmDk8nA4iXPaLx=NZC-LGySbJnXNZTerRg-CYLG3GTHtjV-nA@mail.gmail.com>
Subject: Re: I-D Action: draft-barnes-healthy-food-07.txt
From: Mary Barnes <mary.h.barnes@gmail.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Content-Type: multipart/alternative; boundary=089e0122f48046b63904e1a60f63
Cc: John C Klensin <john-ietf@jck.com>, "<adrian@olddog.co.uk>" <adrian@olddog.co.uk>, "<ietf@ietf.org>" <ietf@ietf.org>, "<draft-barnes-healthy-food@tools.ietf.org>" <draft-barnes-healthy-food@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jul 2013 19:34:13 -0000

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

On Tue, Jul 16, 2013 at 1:47 PM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> On Jul 16, 2013, at 11:37 AM, Adrian Farrel <adrian@olddog.co.uk> wrote:
> > I venture that "starve" is never a real outcome, but "go to a
> supermarket" or
> > "bring food in your luggage" are alternatives that need some planning
> and are a
> > small inconvenience.
>
> Try it sometime, then get back to us.   :)
>

[MB] Exactly.  This was the same sort of response that we had when we
raised these concerns after the meeting in Dublin (and later in
Maastricht).   Many countries limit the food that you can bring in your
luggage. And, in the case of Dublin (and Maastricht on Sunday) there were
no markets to go to in order to buy food.  Yes, I can subsist on the
pumpkin seeds and raisins that I carry in my pocket and backpack but to do
so for 36-48 hours is really unpleasant and isn't healthy for me personally
who needs more fresh foods to feel well.  [/MB]

>
> I rented a car in Orlando, which just about doubled the cost of my stay.
> This is a pretty strong negative for a venue.   And I suspect that "needs
> some kind of nonstandard food" is not quite as small a minority as you
> imagine it is.   Particularly when "nonstandard"=="what is served in the
> hotel restaurant," which, in large hotels, tends to actually be a very
> constrained, unhealthy diet even for those who can eat it.   I was feeling
> so crappy after several days of the hotel food at the most recent venue we
> shared together that  I had to flee the meeting and search Dublin for some
> probiotics and roughage.   I am happy for you that you don't have this
> problem.
>

[MB] I did the same in Orlando and will do so in cases where we may end up
in the boondocks or tiny cities in Europe again, but my company covers that
cost and not everyone has the financial support that I do when I go to
meetings.  [/MB]

--089e0122f48046b63904e1a60f63
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, Jul 16, 2013 at 1:47 PM, Ted Lemon <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:Ted.Lemon@nominum.com" target=3D"_blank">Ted.Lemon@nominum.=
com</a>&gt;</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 Jul 16, 2013, at 11:37 =
AM, Adrian Farrel &lt;<a href=3D"mailto:adrian@olddog.co.uk">adrian@olddog.=
co.uk</a>&gt; wrote:<br>

&gt; I venture that &quot;starve&quot; is never a real outcome, but &quot;g=
o to a supermarket&quot; or<br>
&gt; &quot;bring food in your luggage&quot; are alternatives that need some=
 planning and are a<br>
&gt; small inconvenience.<br>
<br>
</div>Try it sometime, then get back to us. =A0 :)<br></blockquote><div><br=
></div><div>[MB] Exactly. =A0This was the same sort of response that we had=
 when we raised these concerns after the meeting in Dublin (and later in Ma=
astricht). =A0 Many countries limit the food that you can bring in your lug=
gage. And, in the case of Dublin (and Maastricht on Sunday) there were no m=
arkets to go to in order to buy food. =A0Yes, I can subsist on the pumpkin =
seeds and raisins that I carry in my pocket and backpack but to do so for 3=
6-48 hours is really unpleasant and isn&#39;t healthy for me personally who=
 needs more fresh foods to feel well. =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>
I rented a car in Orlando, which just about doubled the cost of my stay. =
=A0 This is a pretty strong negative for a venue. =A0 And I suspect that &q=
uot;needs some kind of nonstandard food&quot; is not quite as small a minor=
ity as you imagine it is. =A0 Particularly when &quot;nonstandard&quot;=3D=
=3D&quot;what is served in the hotel restaurant,&quot; which, in large hote=
ls, tends to actually be a very constrained, unhealthy diet even for those =
who can eat it. =A0 I was feeling so crappy after several days of the hotel=
 food at the most recent venue we shared together that =A0I had to flee the=
 meeting and search Dublin for some probiotics and roughage. =A0 I am happy=
 for you that you don&#39;t have this problem.<br>
</blockquote><div>=A0</div><div>[MB] I did the same in Orlando and will do =
so in cases where we may end up in the boondocks or tiny cities in Europe a=
gain, but my company covers that cost and not everyone has the financial su=
pport that I do when I go to meetings. =A0[/MB]</div>
</div><br></div></div>

--089e0122f48046b63904e1a60f63--

From bernard_aboba@hotmail.com  Tue Jul 16 12:42:36 2013
Return-Path: <bernard_aboba@hotmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A21921F968B; Tue, 16 Jul 2013 12:42:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.498
X-Spam-Level: 
X-Spam-Status: No, score=-102.498 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dFPhAE4Zfnbz; Tue, 16 Jul 2013 12:42:30 -0700 (PDT)
Received: from blu0-omc2-s35.blu0.hotmail.com (blu0-omc2-s35.blu0.hotmail.com [65.55.111.110]) by ietfa.amsl.com (Postfix) with ESMTP id 6874921F9263; Tue, 16 Jul 2013 12:42:30 -0700 (PDT)
Received: from BLU169-W33 ([65.55.111.71]) by blu0-omc2-s35.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 16 Jul 2013 12:42:29 -0700
X-TMN: [KI5dqS1W+CcsDLj47fFf8uqClLbzwar3SzKI1DvdEGQ=]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU169-W3386A689EE5BFC8D2272A093600@phx.gbl>
Content-Type: multipart/alternative; boundary="_fe55e381-6deb-4a0d-98e4-8acf61d98135_"
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Internationalization and draft-ietf-abfab-eapapplicability
Date: Tue, 16 Jul 2013 12:42:29 -0700
Importance: Normal
MIME-Version: 1.0
X-OriginalArrivalTime: 16 Jul 2013 19:42:29.0532 (UTC) FILETIME=[9B5A6DC0:01CE825C]
Cc: "draft-ietf-abfab-eapapplicability@tools.ietf.org" <draft-ietf-abfab-eapapplicability@tools.ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jul 2013 19:42:36 -0000

--_fe55e381-6deb-4a0d-98e4-8acf61d98135_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

After reading this document=2C I believe that this document omits discussio=
n of an important aspect=2C which is  internationalization.  Since the cont=
ents of the EAP Identity and RADIUS User-Name attributes are specified to b=
e encoded in UTF-8=2C application protocols that utilize encodings other th=
an UTF-8 for user identities and passwords could have issues utilizing EAP =
(and RADIUS).  Currently RFC 4282bis proposes that all EAP implementations =
normalize identities and passwords before utilizing them=2C and therefore a=
pplication protocols that do not do this will be at variance with RFC 4282b=
is. =20
IMHO the document needs to state what the internationalization requirements=
 are for application-layer protocol use of EAP.  There are potential workar=
ounds=2C such as requiring that application protocols convert identities an=
d passwords to UTF-8 prior to use of EAP=2C or modifying RFC 4282bis so as =
to require normalization in RADIUS proxies or servers.   However=2C without=
 fixes being applied and/or changes to RFC 4282bis=2C use of EAP by applica=
tions may not be compatible with either existing specifications or implemen=
tations.=20
Background

EAP and protocols that carry it (e.g. RADIUS) assume that the EAP-Response/=
Identity is encoded in UTF-8.  For example=2C RFC 3748 Section 1.2 defines =
"displayable message" as follows:=20
   Displayable Message=0A=
      This is interpreted to be a human readable string of characters.=0A=
      The message encoding MUST follow the UTF-8 transformation format=0A=
      [RFC2279].
Therefore EAP messages including EAP Identity and Notification that are des=
cribed as "displayable messages" have a UTF-8 encoding requirement applied =
to them.=20
Since RFC 3579 Section 2.1 specifies that the EAP-Response/Identity is copi=
ed into the RADIUS User-Name Attribute:    In order to permit non-EAP aware=
 RADIUS proxies to forward the=0A=
   Access-Request packet=2C if the NAS initially sends an=0A=
   EAP-Request/Identity message to the peer=2C the NAS MUST copy the=0A=
   contents of the Type-Data field of the EAP-Response/Identity received=0A=
   from the peer into the User-Name attribute and MUST include the=0A=
   Type-Data field of the EAP-Response/Identity in the User-Name=0A=
   attribute in every subsequent Access-Request.
Therefore for use with EAP=2C the User-Name Attribute also inherits a UTF-8=
 encoding requirement=2C restricting the potential encodings permitted by R=
FC 2865 Section 5.1 (User-Name Attribute): =0A=
      The format of the username MAY be one of several forms:=0A=
=0A=
      text      Consisting only of UTF-8 encoded 10646 [7] characters.=0A=
=0A=
      network access identifier=0A=
                A Network Access Identifier as described in RFC 2486=0A=
                [8].=0A=
=0A=
      distinguished name=0A=
                A name in ASN.1 form used in Public Key authentication=0A=
                systems.




      		 	   		  =

--_fe55e381-6deb-4a0d-98e4-8acf61d98135_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 12pt=3B
font-family:Calibri
}
--></style></head>
<body class=3D'hmmessage'><div dir=3D'ltr'>After reading this document=2C I=
 believe that this document omits discussion of an important aspect=2C whic=
h is &nbsp=3Binternationalization. &nbsp=3BSince the contents of the EAP Id=
entity and RADIUS User-Name attributes are specified to be encoded in UTF-8=
=2C&nbsp=3B<span style=3D"font-size: 12pt=3B ">application protocols that u=
tilize encodings other than UTF-8 for user identities and passwords could h=
ave issues utilizing EAP (and RADIUS). &nbsp=3B</span><span style=3D"font-s=
ize: 12pt=3B ">Currently RFC 4282bis proposes that all EAP implementations =
normalize identities and passwords before utilizing them=2C and therefore a=
pplication protocols that do not do this will be at variance with RFC 4282b=
is. &nbsp=3B</span><div><div><div><br></div><div>IMHO the document needs to=
 state what the internationalization requirements are for application-layer=
 protocol use of EAP. &nbsp=3BThere are potential workarounds=2C such as re=
quiring that application protocols convert identities and passwords to UTF-=
8 prior to use of EAP=2C or modifying RFC 4282bis so as to require normaliz=
ation in RADIUS proxies or servers. &nbsp=3B However=2C without fixes being=
 applied and/or changes to RFC 4282bis=2C use of EAP by applications may no=
t be compatible with either existing specifications or implementations.&nbs=
p=3B</div><div><br></div><div>Background<br><div><br></div><div>EAP and pro=
tocols that carry it (e.g. RADIUS) assume that the EAP-Response/Identity is=
 encoded in UTF-8. &nbsp=3BFor example=2C RFC 3748 Section 1.2 defines "dis=
playable message" as follows:&nbsp=3B</div><div><br></div><div><pre style=
=3D"word-wrap: break-word=3B white-space: pre-wrap=3B ">   Displayable Mess=
age=0A=
      This is interpreted to be a human readable string of characters.=0A=
      The message encoding MUST follow the UTF-8 transformation format=0A=
      [RFC2279].</pre></div><div><br></div><div>Therefore EAP messages incl=
uding EAP Identity and Notification that are described as "displayable mess=
ages" have a UTF-8 encoding requirement applied to them.&nbsp=3B</div></div=
><div><br></div><div>Since RFC 3579 Section 2.1 specifies that the EAP-Resp=
onse/Identity is copied into the RADIUS User-Name Attribute:&nbsp=3B</div><=
div><pre style=3D"word-wrap: break-word=3B white-space: pre-wrap=3B ">   In=
 order to permit non-EAP aware RADIUS proxies to forward the=0A=
   Access-Request packet=2C if the NAS initially sends an=0A=
   EAP-Request/Identity message to the peer=2C the NAS MUST copy the=0A=
   contents of the Type-Data field of the EAP-Response/Identity received=0A=
   from the peer into the User-Name attribute and MUST include the=0A=
   Type-Data field of the EAP-Response/Identity in the User-Name=0A=
   attribute in every subsequent Access-Request.</pre></div><div><br></div>=
<div>Therefore for use with EAP=2C the User-Name Attribute also inherits a =
UTF-8 encoding requirement=2C restricting the potential encodings permitted=
 by RFC 2865 Section 5.1 (User-Name Attribute):&nbsp=3B</div><div><pre styl=
e=3D"word-wrap: break-word=3B white-space: pre-wrap=3B ">=0A=
      The format of the username MAY be one of several forms:=0A=
=0A=
      text      Consisting only of UTF-8 encoded 10646 [7] characters.=0A=
=0A=
      network access identifier=0A=
                A Network Access Identifier as described in RFC 2486=0A=
                [8].=0A=
=0A=
      distinguished name=0A=
                A name in ASN.1 form used in Public Key authentication=0A=
                systems.</pre></div><div><br></div><div><br></div><div><br>=
</div><div><br></div><div><br></div><div><pre style=3D"word-wrap: break-wor=
d=3B white-space: pre-wrap=3B ">     </pre></div></div></div> 		 	   		  </=
div></body>
</html>=

--_fe55e381-6deb-4a0d-98e4-8acf61d98135_--

From mary.h.barnes@gmail.com  Tue Jul 16 12:48:53 2013
Return-Path: <mary.h.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F0BF21F99AE for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 12:48:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uJnD9Jv+hZ6k for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 12:48:52 -0700 (PDT)
Received: from mail-ve0-x231.google.com (mail-ve0-x231.google.com [IPv6:2607:f8b0:400c:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id 6E58621F99A2 for <ietf@ietf.org>; Tue, 16 Jul 2013 12:48:52 -0700 (PDT)
Received: by mail-ve0-f177.google.com with SMTP id cz10so845145veb.36 for <ietf@ietf.org>; Tue, 16 Jul 2013 12:48:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=+o7D8GqQMby9Z9jkf7wWwIQ/O8zHccyg7rj1tAZHoxk=; b=P8VFdsuVbmQwLOrmvJRCZjFZF5QUn55o8denMzUU431YN+KTRb2efk7ZLL50bRVSXO AUAAlqf4dGyePj6beCd7UQyJ+2D8nlUHDWw77Wd4A6jbVOHscNmkns2PXXXlQkCvs5eu NQS4JHPL2p8A7Di+XV0LYVurlUEGFte4VNzHPRV258Yoty1FvVe34X/cXAIf8/LyvUWV vgE8I1OWsElfm+bvYjVNT2GkIL81hkvnFma2CoQNEEXkDCRRZG54c3izTo6vIK/AHSsT Jr/jjHuxw+wC6rrZA5cNRIhFl3fVTaCs0wJYFksUSyrlGE94LHnRj/+Ygl634YJVuOqb zWTQ==
MIME-Version: 1.0
X-Received: by 10.58.80.38 with SMTP id o6mr936771vex.69.1374004131977; Tue, 16 Jul 2013 12:48:51 -0700 (PDT)
Received: by 10.58.74.97 with HTTP; Tue, 16 Jul 2013 12:48:51 -0700 (PDT)
In-Reply-To: <0e3c01ce8253$796ebd00$6c4c3700$@olddog.co.uk>
References: <20130716163157.28468.93383.idtracker@ietfa.amsl.com> <0e1501ce8247$45197bf0$cf4c73d0$@olddog.co.uk> <B6E25FF4CE904AF154E73319@JcK-HP8200.jck.com> <0e3c01ce8253$796ebd00$6c4c3700$@olddog.co.uk>
Date: Tue, 16 Jul 2013 14:48:51 -0500
Message-ID: <CABmDk8knWphtjiS-oPNkj0BW-AKGSj3cdnrZjwuUau5v2yyUyA@mail.gmail.com>
Subject: Re: I-D Action: draft-barnes-healthy-food-07.txt
From: Mary Barnes <mary.h.barnes@gmail.com>
To: "<adrian@olddog.co.uk>" <adrian@olddog.co.uk>
Content-Type: multipart/alternative; boundary=047d7b5d48a634e09704e1a64475
Cc: John C Klensin <john-ietf@jck.com>, "<ietf@ietf.org>" <ietf@ietf.org>, "<draft-barnes-healthy-food@tools.ietf.org>" <draft-barnes-healthy-food@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jul 2013 19:48:53 -0000

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

On Tue, Jul 16, 2013 at 1:37 PM, Adrian Farrel <adrian@olddog.co.uk> wrote:

> > > Personally, I will strongly try to be vegetarian, but eat meat
> > > rather than starve (a situation that arises when travelling).
> >
> > if a venue is chosen that forces you (or me or others) into
> > a "meat or starve" or, much worse, "eat something severely
> > damaging to health or beliefs or starve" situation, is that
> > really an acceptable venue?
>
> Yes, it is.
> If a venue is inconvenient or uncomfortable for a small percentage of
> "regular"
> IETF participants, that does not make it a poor choice of venue.
>

[MB] This is the exact reason I had some stats in the doc previously as
it's not as small a percentage as you think.  Also, as the document
highlights, in cases of medical conditions, one might consider this to
violate the American Disability Act in the US.  Celiac disease, for
example, is considered an "invisible" disability in the US.  One can debate
whether or not IETF/ISOC must comply with the American Disability Act, but
as I have posited IETF claims to be an open organization so I would think
they would want the meetings to be accessible to all, which means ensuring
there is food readily available to accommodate those with dietary
restrictions.

The example of your situation is a matter of personal choice.  For some of
us it can be a matter of life or death (e.g., peanut allergies).  [/MB]


> We might as well go back to the debate about location: only a venue that
> is a
> convenient 10 minutes from my home is really a suitable venue.
>
> I venture that "starve" is never a real outcome, but "go to a supermarket"
> or
> "bring food in your luggage" are alternatives that need some planning and
> are a
> small inconvenience.
>
[MB] I already responded to this one, but I'll go ahead again, because this
attitude is the reason why I wrote this document after Dublin.  There was
no supermarket near the venue at all, thus that wasn't possible.  I did the
right thing and checked out the hotel restaurants on the Sunday before the
meeting started and found they could easily accommodate my GF diet.
However, at Monday lunchtime we could not order off the menu and were given
something like 3 choices of entrees.  The staff serving the food had no
idea about preparation.  Folks that are vegan/vegetarian/kosher couldn't
even eat the french fries because they couldn't be certain whether they
were cooked in a meat based oil or vegetable oil.    I have celiac and thus
I cannot eat anything unless I have a very high level of confidence that it
is gluten free - my reaction can be extremely severe and at it's mildest,
it's like having a miserable 24 hour flu.  [/MB]

>
> Adrian
>
>

--047d7b5d48a634e09704e1a64475
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, Jul 16, 2013 at 1:37 PM, Adrian Farrel <span dir=3D"ltr">&l=
t;<a href=3D"mailto:adrian@olddog.co.uk" target=3D"_blank">adrian@olddog.co=
.uk</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">&gt; &gt; Personally, I wi=
ll strongly try to be vegetarian, but eat meat<br>
&gt; &gt; rather than starve (a situation that arises when travelling).<br>
&gt;<br>
</div><div class=3D"im">&gt; if a venue is chosen that forces you (or me or=
 others) into<br>
&gt; a &quot;meat or starve&quot; or, much worse, &quot;eat something sever=
ely<br>
&gt; damaging to health or beliefs or starve&quot; situation, is that<br>
&gt; really an acceptable venue?<br>
<br>
</div>Yes, it is.<br>
If a venue is inconvenient or uncomfortable for a small percentage of &quot=
;regular&quot;<br>
IETF participants, that does not make it a poor choice of venue.<br></block=
quote><div>=A0</div><div>[MB] This is the exact reason I had some stats in =
the doc previously as it&#39;s not as small a percentage as you think. =A0A=
lso, as the document highlights, in cases of medical conditions, one might =
consider this to violate the American Disability Act in the US. =A0Celiac d=
isease, for example, is considered an &quot;invisible&quot; disability in t=
he US. =A0One can debate whether or not IETF/ISOC must comply with the Amer=
ican Disability Act, but as I have posited IETF claims to be an open organi=
zation so I would think they would want the meetings to be accessible to al=
l, which means ensuring there is food readily available to accommodate thos=
e with dietary restrictions.</div>
<div><br></div><div>The example of your situation is a matter of personal c=
hoice. =A0For some of us it can be a matter of life or death (e.g., peanut =
allergies). =A0[/MB]</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>
We might as well go back to the debate about location: only a venue that is=
 a<br>
convenient 10 minutes from my home is really a suitable venue.<br>
<br>
I venture that &quot;starve&quot; is never a real outcome, but &quot;go to =
a supermarket&quot; or<br>
&quot;bring food in your luggage&quot; are alternatives that need some plan=
ning and are a<br>
small inconvenience.<br></blockquote><div>[MB] I already responded to this =
one, but I&#39;ll go ahead again, because this attitude is the reason why I=
 wrote this document after Dublin. =A0There was no supermarket near the ven=
ue at all, thus that wasn&#39;t possible. =A0I did the right thing and chec=
ked out the hotel restaurants on the Sunday before the meeting started and =
found they could easily accommodate my GF diet. However, at Monday lunchtim=
e we could not order off the menu and were given something like 3 choices o=
f entrees. =A0The staff serving the food had no idea about preparation. =A0=
Folks that are vegan/vegetarian/kosher couldn&#39;t even eat the french fri=
es because they couldn&#39;t be certain whether they were cooked in a meat =
based oil or vegetable oil. =A0 =A0I have celiac and thus I cannot eat anyt=
hing unless I have a very high level of confidence that it is gluten free -=
 my reaction can be extremely severe and at it&#39;s mildest, it&#39;s like=
 having a miserable 24 hour flu. =A0[/MB]</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Adrian<br>
<br>
</font></span></blockquote></div><br></div></div>

--047d7b5d48a634e09704e1a64475--

From dhc@dcrocker.net  Tue Jul 16 12:54:14 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44EF321F9815 for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 12:54:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.588
X-Spam-Level: 
X-Spam-Status: No, score=-6.588 tagged_above=-999 required=5 tests=[AWL=0.011,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 63-a8W8qDfsj for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 12:54:08 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 3908621F977A for <ietf@ietf.org>; Tue, 16 Jul 2013 12:53:48 -0700 (PDT)
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 r6GJrSkm029604 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 16 Jul 2013 12:53:32 -0700
Message-ID: <51E5A497.5000305@dcrocker.net>
Date: Tue, 16 Jul 2013 12:52:55 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: I-D Action: draft-barnes-healthy-food-07.txt
References: <20130716163157.28468.93383.idtracker@ietfa.amsl.com> <0e1501ce8247$45197bf0$cf4c73d0$@olddog.co.uk> <B6E25FF4CE904AF154E73319@JcK-HP8200.jck.com> <0e3c01ce8253$796ebd00$6c4c3700$@olddog.co.uk>
In-Reply-To: <0e3c01ce8253$796ebd00$6c4c3700$@olddog.co.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]); Tue, 16 Jul 2013 12:53:32 -0700 (PDT)
Cc: draft-barnes-healthy-food@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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, 16 Jul 2013 19:54:14 -0000

On 7/16/2013 11:37 AM, Adrian Farrel wrote:
> If a venue is inconvenient or uncomfortable for a small percentage of "regular"
> IETF participants, that does not make it a poor choice of venue.


How about "unworkable" or "only marginally tolerable"?

For example imposing a 'meat or die' model onto almost any kind of 
vegetarian seems to me frankly offensive (and I'm not a member of that 
demographic).  In this day and age, ensuring good vegan options -- which 
therefore work for most vegetarians -- should not be viewed as unusual 
or difficult; but it does need to be an explicit goal.

Then there's the question of how small a percentage is acceptable?

If someone is allergic to literally everything, we can't do much to help 
them.  On the other hand, if someone has special needs that can 
reasonably be accommodated by a typical, modern, urban grocery store, 
then we can help them by choosing a venue near such a place and 
publishing information about access to it.  This is the ultimate fallback.

Similarly, there are snack foods that are basic an healthy and run into 
relatively few allergy, belief or religious limitations.  Providing such 
choices during IETF breaks is a version of being more inclusive, to 
encourage more diversity.

I've intentionally invoked the current buzzword, because ultimately 
these various accommodations have to do with making the IETF more (or 
less) friendly to the widest range of participants we can manage.

Some organizational empathy that is applied to event logistics will go a 
long way here.

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From adrian@olddog.co.uk  Tue Jul 16 13:10:20 2013
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5FB321E8064 for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 13:10:20 -0700 (PDT)
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=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IqfsEXT1lSTN for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 13:10:15 -0700 (PDT)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by ietfa.amsl.com (Postfix) with ESMTP id 0E5BE21E8054 for <ietf@ietf.org>; Tue, 16 Jul 2013 13:10:13 -0700 (PDT)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id r6GKABhk027796;  Tue, 16 Jul 2013 21:10:11 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id r6GKAAj0027784 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 16 Jul 2013 21:10:10 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Mary Barnes'" <mary.h.barnes@gmail.com>
References: <20130716163157.28468.93383.idtracker@ietfa.amsl.com>	<0e1501ce8247$45197bf0$cf4c73d0$@olddog.co.uk>	<B6E25FF4CE904AF154E73319@JcK-HP8200.jck.com>	<0e3c01ce8253$796ebd00$6c4c3700$@olddog.co.uk> <CABmDk8knWphtjiS-oPNkj0BW-AKGSj3cdnrZjwuUau5v2yyUyA@mail.gmail.com>
In-Reply-To: <CABmDk8knWphtjiS-oPNkj0BW-AKGSj3cdnrZjwuUau5v2yyUyA@mail.gmail.com>
Subject: RE: I-D Action: draft-barnes-healthy-food-07.txt
Date: Tue, 16 Jul 2013 21:10:08 +0100
Message-ID: <0e8e01ce8260$78b56c30$6a204490$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0E8F_01CE8268.DA8DD160"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIKfiTNkPkLWdefr8jDMRdxEhClWAHQKMnpAZpUTf4CdH5ZowINe93ymLBexhA=
Content-Language: en-gb
Cc: 'John C Klensin' <john-ietf@jck.com>, ietf@ietf.org, draft-barnes-healthy-food@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 16 Jul 2013 20:10:21 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0E8F_01CE8268.DA8DD160
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

My point, of course, is not to disparage those with medical conditions, or even
those with philosophical/religious convictions.
 
Google shows me a supermarket within 1km of the venue in Dublin. I walked to one
while I was there. I also caught the free shuttle to down-town Dublin where I
saw several shops.
 
I know folk who travel with suitcases of special food. 
 
It is hard.
We should do what we can to be accommodating.
It should be one of the factors we consider in selecting/briefing a venue.
 
It should not be an over-riding consideration.
 
Adrian
 
From: Mary Barnes [mailto:mary.h.barnes@gmail.com] 
Sent: 16 July 2013 20:49
To: <adrian@olddog.co.uk>
Cc: John C Klensin; <draft-barnes-healthy-food@tools.ietf.org>; <ietf@ietf.org>
Subject: Re: I-D Action: draft-barnes-healthy-food-07.txt
 
On Tue, Jul 16, 2013 at 1:37 PM, Adrian Farrel <adrian@olddog.co.uk> wrote:
> > Personally, I will strongly try to be vegetarian, but eat meat
> > rather than starve (a situation that arises when travelling).
>
> if a venue is chosen that forces you (or me or others) into
> a "meat or starve" or, much worse, "eat something severely
> damaging to health or beliefs or starve" situation, is that
> really an acceptable venue?
Yes, it is.
If a venue is inconvenient or uncomfortable for a small percentage of "regular"
IETF participants, that does not make it a poor choice of venue.
 
[MB] This is the exact reason I had some stats in the doc previously as it's not
as small a percentage as you think.  Also, as the document highlights, in cases
of medical conditions, one might consider this to violate the American
Disability Act in the US.  Celiac disease, for example, is considered an
"invisible" disability in the US.  One can debate whether or not IETF/ISOC must
comply with the American Disability Act, but as I have posited IETF claims to be
an open organization so I would think they would want the meetings to be
accessible to all, which means ensuring there is food readily available to
accommodate those with dietary restrictions.
 
The example of your situation is a matter of personal choice.  For some of us it
can be a matter of life or death (e.g., peanut allergies).  [/MB]
 

We might as well go back to the debate about location: only a venue that is a
convenient 10 minutes from my home is really a suitable venue.

I venture that "starve" is never a real outcome, but "go to a supermarket" or
"bring food in your luggage" are alternatives that need some planning and are a
small inconvenience.
[MB] I already responded to this one, but I'll go ahead again, because this
attitude is the reason why I wrote this document after Dublin.  There was no
supermarket near the venue at all, thus that wasn't possible.  I did the right
thing and checked out the hotel restaurants on the Sunday before the meeting
started and found they could easily accommodate my GF diet. However, at Monday
lunchtime we could not order off the menu and were given something like 3
choices of entrees.  The staff serving the food had no idea about preparation.
Folks that are vegan/vegetarian/kosher couldn't even eat the french fries
because they couldn't be certain whether they were cooked in a meat based oil or
vegetable oil.    I have celiac and thus I cannot eat anything unless I have a
very high level of confidence that it is gluten free - my reaction can be
extremely severe and at it's mildest, it's like having a miserable 24 hour flu.
[/MB]

Adrian

------=_NextPart_000_0E8F_01CE8268.DA8DD160
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DProgId content=3DWord.Document><meta =
name=3DGenerator content=3D"Microsoft Word 14"><meta name=3DOriginator =
content=3D"Microsoft Word 14"><link rel=3DFile-List =
href=3D"cid:filelist.xml@01CE8268.5A351140"><!--[if gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:AllowPNG/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:SpellingState>Clean</w:SpellingState>
<w:TrackMoves/>
<w:TrackFormatting/>
<w:EnvelopeVis/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF/>
<w:LidThemeOther>EN-GB</w:LidThemeOther>
<w:LidThemeAsian>X-NONE</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:DoNotExpandShiftReturn/>
<w:BreakWrappedTables/>
<w:SplitPgBreakAndParaMark/>
<w:EnableOpenTypeKerning/>
</w:Compatibility>
<m:mathPr>
<m:mathFont m:val=3D"Cambria Math"/>
<m:brkBin m:val=3D"before"/>
<m:brkBinSub m:val=3D"&#45;-"/>
<m:smallFrac m:val=3D"off"/>
<m:dispDef/>
<m:lMargin m:val=3D"0"/>
<m:rMargin m:val=3D"0"/>
<m:defJc m:val=3D"centerGroup"/>
<m:wrapIndent m:val=3D"1440"/>
<m:intLim m:val=3D"subSup"/>
<m:naryLim m:val=3D"undOvr"/>
</m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState=3D"false" DefUnhideWhenUsed=3D"true" =
DefSemiHidden=3D"true" DefQFormat=3D"false" DefPriority=3D"99" =
LatentStyleCount=3D"267">
<w:LsdException Locked=3D"false" Priority=3D"0" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Normal"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"heading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 3"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 4"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 5"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 6"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 7"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 8"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 9"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 1"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 2"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 3"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 4"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 5"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 6"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 7"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 8"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 9"/>
<w:LsdException Locked=3D"false" Priority=3D"35" QFormat=3D"true" =
Name=3D"caption"/>
<w:LsdException Locked=3D"false" Priority=3D"10" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Title"/>
<w:LsdException Locked=3D"false" Priority=3D"1" Name=3D"Default =
Paragraph Font"/>
<w:LsdException Locked=3D"false" Priority=3D"11" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtitle"/>
<w:LsdException Locked=3D"false" Priority=3D"22" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Strong"/>
<w:LsdException Locked=3D"false" Priority=3D"20" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"59" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Table Grid"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Placeholder Text"/>
<w:LsdException Locked=3D"false" Priority=3D"1" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"No Spacing"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 1"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Revision"/>
<w:LsdException Locked=3D"false" Priority=3D"34" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"List Paragraph"/>
<w:LsdException Locked=3D"false" Priority=3D"29" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"30" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"19" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"21" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"31" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"32" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"33" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Book Title"/>
<w:LsdException Locked=3D"false" Priority=3D"37" Name=3D"Bibliography"/>
<w:LsdException Locked=3D"false" Priority=3D"39" QFormat=3D"true" =
Name=3D"TOC Heading"/>
</w:LatentStyles>
</xml><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-536870145 1073786111 1 0 415 0;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-520081665 -1073717157 41 0 66047 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	mso-fareast-font-family:Calibri;}
a:link, span.MsoHyperlink
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:purple;
	text-decoration:underline;
	text-underline:single;}
span.hoenzb
	{mso-style-name:hoenzb;
	mso-style-unhide:no;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	mso-style-noshow:yes;
	mso-style-unhide:no;
	mso-ansi-font-size:11.0pt;
	mso-bidi-font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-default-props:yes;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;
	mso-header-margin:36.0pt;
	mso-footer-margin:36.0pt;
	mso-paper-source:0;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 10]><style>/* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin:0cm;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-fareast-language:EN-US;}
</style><![endif]--><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-GB link=3Dblue =
vlink=3Dpurple style=3D'tab-interval:36.0pt'><div =
class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>My point, of course, is not to =
disparage those with medical conditions, or even those with =
philosophical/religious convictions.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>Google shows me a supermarket =
within 1km of the venue in Dublin. I walked to one while I was there. I =
also caught the free shuttle to down-town Dublin where I saw several =
shops.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>I know folk who travel with =
suitcases of special food. <o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>It is =
hard.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>We should do what we can to be =
accommodating.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>It should be one of the =
factors we consider in selecting/briefing a =
venue.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>It should not be an =
over-riding consideration.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>Adrian<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New =
Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-f=
ont-family:"Times New =
Roman";mso-ansi-language:EN-US'>From:</span></b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-f=
ont-family:"Times New Roman";mso-ansi-language:EN-US'> Mary Barnes =
[mailto:mary.h.barnes@gmail.com] <br><b>Sent:</b> 16 July 2013 =
20:49<br><b>To:</b> &lt;adrian@olddog.co.uk&gt;<br><b>Cc:</b> John C =
Klensin; &lt;draft-barnes-healthy-food@tools.ietf.org&gt;; =
&lt;ietf@ietf.org&gt;<br><b>Subject:</b> Re: I-D Action: =
draft-barnes-healthy-food-07.txt<o:p></o:p></span></p></div></div><div><d=
iv><div><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal>On Tue, Jul 16, 2013 at 1:37 PM, Adrian Farrel &lt;<a =
href=3D"mailto:adrian@olddog.co.uk" =
target=3D"_blank">adrian@olddog.co.uk</a>&gt; =
wrote:<o:p></o:p></p><div><p class=3DMsoNormal>&gt; &gt; Personally, I =
will strongly try to be vegetarian, but eat meat<br>&gt; &gt; rather =
than starve (a situation that arises when =
travelling).<br>&gt;<o:p></o:p></p></div><div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'>&gt; if a venue is chosen that forces you =
(or me or others) into<br>&gt; a &quot;meat or starve&quot; or, much =
worse, &quot;eat something severely<br>&gt; damaging to health or =
beliefs or starve&quot; situation, is that<br>&gt; really an acceptable =
venue?<o:p></o:p></p></div><p class=3DMsoNormal>Yes, it is.<br>If a =
venue is inconvenient or uncomfortable for a small percentage of =
&quot;regular&quot;<br>IETF participants, that does not make it a poor =
choice of venue.<o:p></o:p></p><div><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p></div><div><p =
class=3DMsoNormal>[MB] This is the exact reason I had some stats in the =
doc previously as it's not as small a percentage as you think. =
&nbsp;Also, as the document highlights, in cases of medical conditions, =
one might consider this to violate the American Disability Act in the =
US. &nbsp;Celiac disease, for example, is considered an =
&quot;invisible&quot; disability in the US. &nbsp;One can debate whether =
or not IETF/ISOC must comply with the American Disability Act, but as I =
have posited IETF claims to be an open organization so I would think =
they would want the meetings to be accessible to all, which means =
ensuring there is food readily available to accommodate those with =
dietary restrictions.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>The example of your situation is a matter of personal =
choice. &nbsp;For some of us it can be a matter of life or death (e.g., =
peanut allergies). &nbsp;[/MB]<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><blockquote =
style=3D'border:none;border-left:solid #CCCCCC =
1.0pt;mso-border-left-alt:solid #CCCCCC .75pt;padding:0cm 0cm 0cm =
6.0pt;margin-left:4.8pt;margin-right:0cm'><p class=3DMsoNormal><br>We =
might as well go back to the debate about location: only a venue that is =
a<br>convenient 10 minutes from my home is really a suitable =
venue.<br><br>I venture that &quot;starve&quot; is never a real outcome, =
but &quot;go to a supermarket&quot; or<br>&quot;bring food in your =
luggage&quot; are alternatives that need some planning and are =
a<br>small inconvenience.<o:p></o:p></p></blockquote><div><p =
class=3DMsoNormal>[MB] I already responded to this one, but I'll go =
ahead again, because this attitude is the reason why I wrote this =
document after Dublin. &nbsp;There was no supermarket near the venue at =
all, thus that wasn't possible. &nbsp;I did the right thing and checked =
out the hotel restaurants on the Sunday before the meeting started and =
found they could easily accommodate my GF diet. However, at Monday =
lunchtime we could not order off the menu and were given something like =
3 choices of entrees. &nbsp;The staff serving the food had no idea about =
preparation. &nbsp;Folks that are vegan/vegetarian/kosher couldn't even =
eat the french fries because they couldn't be certain whether they were =
cooked in a meat based oil or vegetable oil. &nbsp; &nbsp;I have celiac =
and thus I cannot eat anything unless I have a very high level of =
confidence that it is gluten free - my reaction can be extremely severe =
and at it's mildest, it's like having a miserable 24 hour flu. =
&nbsp;[/MB]<o:p></o:p></p></div><blockquote =
style=3D'border:none;border-left:solid #CCCCCC =
1.0pt;mso-border-left-alt:solid #CCCCCC .75pt;padding:0cm 0cm 0cm =
6.0pt;margin-left:4.8pt;margin-right:0cm'><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;mar=
gin-left:16.8pt'><span style=3D'color:#888888'><br><span =
class=3Dhoenzb>Adrian</span></span><span =
style=3D'color:#1F497D'><o:p></o:p></span></p></blockquote></div></div></=
div></div></div></body></html>
------=_NextPart_000_0E8F_01CE8268.DA8DD160--


From mary.h.barnes@gmail.com  Tue Jul 16 13:29:21 2013
Return-Path: <mary.h.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 294A421F9A8F for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 13:29:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h+JoMMO2RTfy for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 13:29:20 -0700 (PDT)
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 BE6B321F9A05 for <ietf@ietf.org>; Tue, 16 Jul 2013 13:29:19 -0700 (PDT)
Received: by mail-ve0-f170.google.com with SMTP id 14so889295vea.15 for <ietf@ietf.org>; Tue, 16 Jul 2013 13:29:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=5RCvnbRTuALVVPLQX/NuAHbruq9np55HP3Vou7219wQ=; b=n+RdvUIM+XR3brcq2pXvLomvGBdESPAen894Tpn40ao4+pYF/4nJrUbOSX/vRbLD5a GuBDAA8j3WFtik48rTc6QjUWFlaJbhuoY2tgMPggdoUK1u1JjIe/8Ox36V+87k9wJIFk 4f3HrEshJ3c5HSnsOGImA43f/EtjLHsI1IwryIh1OvG+95gAqavVc7dYlI01VI5JLm+J bzFbOoGyxlekoF4+gDTfIewAeKEuxcV8zIIjXDQHfqRjA8jpBWJi5dq6VrlETpkw0y9k Lzm6gqANAludODZj7pH4Ho2Q7LcgZoErE42Kn/hibKJmGLb1fL30YuJQ03uTFfx2DmDF 6kFw==
MIME-Version: 1.0
X-Received: by 10.52.232.165 with SMTP id tp5mr841140vdc.11.1374006558114; Tue, 16 Jul 2013 13:29:18 -0700 (PDT)
Received: by 10.58.74.97 with HTTP; Tue, 16 Jul 2013 13:29:18 -0700 (PDT)
In-Reply-To: <0e8e01ce8260$78b56c30$6a204490$@olddog.co.uk>
References: <20130716163157.28468.93383.idtracker@ietfa.amsl.com> <0e1501ce8247$45197bf0$cf4c73d0$@olddog.co.uk> <B6E25FF4CE904AF154E73319@JcK-HP8200.jck.com> <0e3c01ce8253$796ebd00$6c4c3700$@olddog.co.uk> <CABmDk8knWphtjiS-oPNkj0BW-AKGSj3cdnrZjwuUau5v2yyUyA@mail.gmail.com> <0e8e01ce8260$78b56c30$6a204490$@olddog.co.uk>
Date: Tue, 16 Jul 2013 15:29:18 -0500
Message-ID: <CABmDk8mMjVQ9dOLgvx-W_cvc+d6+LMa9xiQgEZPMA8PuGgb8eQ@mail.gmail.com>
Subject: Re: I-D Action: draft-barnes-healthy-food-07.txt
From: Mary Barnes <mary.h.barnes@gmail.com>
To: "<adrian@olddog.co.uk>" <adrian@olddog.co.uk>
Content-Type: multipart/alternative; boundary=089e0122f480d0cc1704e1a6d412
Cc: John C Klensin <john-ietf@jck.com>, "<ietf@ietf.org>" <ietf@ietf.org>, "<draft-barnes-healthy-food@tools.ietf.org>" <draft-barnes-healthy-food@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jul 2013 20:29:21 -0000

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

On Tue, Jul 16, 2013 at 3:10 PM, Adrian Farrel <adrian@olddog.co.uk> wrote:

> My point, of course, is not to disparage those with medical conditions, or
> even those with philosophical/religious convictions.****
>
> ** **
>
> Google shows me a supermarket within 1km of the venue in Dublin. I walked
> to one while I was there. I also caught the free shuttle to down-town
> Dublin where I saw several shops.
>
[MB] The market within walking distance was poorly stocked when I went
there.  The only thing I found that I could possibly eat was canned
vegetables.    Yes, I did take the shuttle to the city at night for dinner,
but that didn't solve the lunch issue at all and the speciality food
markets weren't open that late.   Did you subsist on the food that you
bought at the supermarket or did you partake of the food that you could eat
that was offered at the hotel buffet?    [/MB]

> ****
>
> ** **
>
> I know folk who travel with suitcases of special food.
>
[MB] Sure. And, in many cases we are violating local laws by bringing food
into the country.  Most of the food I carry with me is nuts, pumpkin seeds,
dried fruit and some snack bars.  All of those things would be confiscated
if I declared them as they have been when I have been searched and they
have found them.   I asked someone to bring a packaged food product from
Stockholm to me when we were meeting in the US. It got confiscated.  [/MB]

> ****
>
> ** **
>
> It is hard.****
>
> We should do what we can to be accommodating.****
>
> It should be one of the factors we consider in selecting/briefing a venue.
> ****
>
> ** **
>
> It should not be an over-riding consideration.
>
[MB] This is the very reason I wrote this document - being able to eat
SHOULD be an over-riding consideration for meetings.  That's a basic human
requirement for survival.    Certainly, most of us won't die if we have to
subsist on nuts, seeds and dried fruit, canned veggies, etc during an IETF
meeting.  But, most of us will not function well without proper nutrition,
somewhat equivalent to what we are used to on a daily basis.  While, at
this point, I might benefit from some fasting, I would never choose a week
where I am working 12-16 hours a day to do so. [/MB]

> ****
>
> ** **
>
> Adrian****
>
> ** **
>
> *From:* Mary Barnes [mailto:mary.h.barnes@gmail.com]
> *Sent:* 16 July 2013 20:49
> *To:* <adrian@olddog.co.uk>
> *Cc:* John C Klensin; <draft-barnes-healthy-food@tools.ietf.org>; <
> ietf@ietf.org>
> *Subject:* Re: I-D Action: draft-barnes-healthy-food-07.txt****
>
> ** **
>
> On Tue, Jul 16, 2013 at 1:37 PM, Adrian Farrel <adrian@olddog.co.uk>
> wrote:****
>
> > > Personally, I will strongly try to be vegetarian, but eat meat
> > > rather than starve (a situation that arises when travelling).
> >****
>
> > if a venue is chosen that forces you (or me or others) into
> > a "meat or starve" or, much worse, "eat something severely
> > damaging to health or beliefs or starve" situation, is that
> > really an acceptable venue?****
>
> Yes, it is.
> If a venue is inconvenient or uncomfortable for a small percentage of
> "regular"
> IETF participants, that does not make it a poor choice of venue.****
>
>  ****
>
> [MB] This is the exact reason I had some stats in the doc previously as
> it's not as small a percentage as you think.  Also, as the document
> highlights, in cases of medical conditions, one might consider this to
> violate the American Disability Act in the US.  Celiac disease, for
> example, is considered an "invisible" disability in the US.  One can debate
> whether or not IETF/ISOC must comply with the American Disability Act, but
> as I have posited IETF claims to be an open organization so I would think
> they would want the meetings to be accessible to all, which means ensuring
> there is food readily available to accommodate those with dietary
> restrictions.****
>
> ** **
>
> The example of your situation is a matter of personal choice.  For some of
> us it can be a matter of life or death (e.g., peanut allergies).  [/MB]***
> *
>
> ** **
>
>
> We might as well go back to the debate about location: only a venue that
> is a
> convenient 10 minutes from my home is really a suitable venue.
>
> I venture that "starve" is never a real outcome, but "go to a supermarket"
> or
> "bring food in your luggage" are alternatives that need some planning and
> are a
> small inconvenience.****
>
> [MB] I already responded to this one, but I'll go ahead again, because
> this attitude is the reason why I wrote this document after Dublin.  There
> was no supermarket near the venue at all, thus that wasn't possible.  I did
> the right thing and checked out the hotel restaurants on the Sunday before
> the meeting started and found they could easily accommodate my GF diet.
> However, at Monday lunchtime we could not order off the menu and were given
> something like 3 choices of entrees.  The staff serving the food had no
> idea about preparation.  Folks that are vegan/vegetarian/kosher couldn't
> even eat the french fries because they couldn't be certain whether they
> were cooked in a meat based oil or vegetable oil.    I have celiac and thus
> I cannot eat anything unless I have a very high level of confidence that it
> is gluten free - my reaction can be extremely severe and at it's mildest,
> it's like having a miserable 24 hour flu.  [/MB]****
>
>
> Adrian****
>
>

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra">On Tue, Jul 16, 2013 at 3:1=
0 PM, Adrian Farrel <span dir=3D"ltr">&lt;<a href=3D"mailto:adrian@olddog.c=
o.uk" target=3D"_blank">adrian@olddog.co.uk</a>&gt;</span> wrote:<br><div c=
lass=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div lang=3D"EN-GB" link=3D"blue" vlink=3D"p=
urple"><div><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">My point, of =
course, is not to disparage those with medical conditions, or even those wi=
th philosophical/religious convictions.<u></u><u></u></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"><u></u>=A0<u></u></span><=
/p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Google shows me a supe=
rmarket within 1km of the venue in Dublin. I walked to one while I was ther=
e. I also caught the free shuttle to down-town Dublin where I saw several s=
hops.</span></p>
</div></div></blockquote><div>[MB] The market within walking distance was p=
oorly stocked when I went there. =A0The only thing I found that I could pos=
sibly eat was canned vegetables. =A0 =A0Yes, I did take the shuttle to the =
city at night for dinner, but that didn&#39;t solve the lunch issue at all =
and the speciality food markets weren&#39;t open that late. =A0 Did you sub=
sist on the food that you bought at the supermarket or did you partake of t=
he food that you could eat that was offered at the hotel buffet? =A0 =A0[/M=
B]</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div lang=3D"EN-GB" link=3D"blue" vlink=3D"p=
urple"><div><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u><u></u=
></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"><u></u>=A0<u></u></span><=
/p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">I know folk who travel=
 with suitcases of special food.</span></p>
</div></div></blockquote><div>[MB] Sure. And, in many cases we are violatin=
g local laws by bringing food into the country. =A0Most of the food I carry=
 with me is nuts, pumpkin seeds, dried fruit and some snack bars. =A0All of=
 those things would be confiscated if I declared them as they have been whe=
n I have been searched and they have found them. =A0 I asked someone to bri=
ng a packaged food product from Stockholm to me when we were meeting in the=
 US. It got confiscated. =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 lang=3D"EN-GB" link=3D"blue" vlink=3D"p=
urple"><div><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"> <u></u><u></=
u></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"><u></u>=A0<u></u></span><=
/p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">It is hard.<u></u><u><=
/u></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">We should do what we can =
to be accommodating.<u></u><u></u></span></p><p class=3D"MsoNormal"><span s=
tyle=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&q=
uot;;color:#1f497d">It should be one of the factors we consider in selectin=
g/briefing a venue.<u></u><u></u></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"><u></u>=A0<u></u></span><=
/p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">It should not be an ov=
er-riding consideration.</span></p>
</div></div></blockquote><div>[MB] This is the very reason I wrote this doc=
ument - being able to eat SHOULD be an over-riding consideration for meetin=
gs. =A0That&#39;s a basic human requirement for survival. =A0 =A0Certainly,=
 most of us won&#39;t die if we have to subsist on nuts, seeds and dried fr=
uit, canned veggies, etc during an IETF meeting. =A0But, most of us will no=
t function well without proper nutrition, somewhat equivalent to what we ar=
e used to on a daily basis. =A0While, at this point, I might benefit from s=
ome fasting, I would never choose a week where I am working 12-16 hours a d=
ay to do so. [/MB] =A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div lang=3D"EN-GB" link=3D"blue" vlink=3D"p=
urple"><div><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u><u></u=
></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"><u></u>=A0<u></u></span><=
/p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Adrian<u></u><u></u></=
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"><u></u>=A0<u></u></span><=
/p><div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0=
cm 4.0pt">
<div><div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt=
 0cm 0cm 0cm"><p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-=
size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</s=
pan></b><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;"> Mary Barnes [mailto:<a href=3D"mailto:m=
ary.h.barnes@gmail.com" target=3D"_blank">mary.h.barnes@gmail.com</a>] <br>
<b>Sent:</b> 16 July 2013 20:49<br><b>To:</b> &lt;<a href=3D"mailto:adrian@=
olddog.co.uk" target=3D"_blank">adrian@olddog.co.uk</a>&gt;<br><b>Cc:</b> J=
ohn C Klensin; &lt;<a href=3D"mailto:draft-barnes-healthy-food@tools.ietf.o=
rg" target=3D"_blank">draft-barnes-healthy-food@tools.ietf.org</a>&gt;; &lt=
;<a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ietf.org</a>&gt;<b=
r>
<b>Subject:</b> Re: I-D Action: draft-barnes-healthy-food-07.txt<u></u><u><=
/u></span></p></div></div><div><div class=3D"h5"><div><div><div><p class=3D=
"MsoNormal"><span style=3D"color:#1f497d"><u></u>=A0<u></u></span></p><p cl=
ass=3D"MsoNormal">
On Tue, Jul 16, 2013 at 1:37 PM, Adrian Farrel &lt;<a href=3D"mailto:adrian=
@olddog.co.uk" target=3D"_blank">adrian@olddog.co.uk</a>&gt; wrote:<u></u><=
u></u></p><div><p class=3D"MsoNormal">&gt; &gt; Personally, I will strongly=
 try to be vegetarian, but eat meat<br>
&gt; &gt; rather than starve (a situation that arises when travelling).<br>=
&gt;<u></u><u></u></p></div><div><p class=3D"MsoNormal" style=3D"margin-bot=
tom:12.0pt">&gt; if a venue is chosen that forces you (or me or others) int=
o<br>
&gt; a &quot;meat or starve&quot; or, much worse, &quot;eat something sever=
ely<br>&gt; damaging to health or beliefs or starve&quot; situation, is tha=
t<br>&gt; really an acceptable venue?<u></u><u></u></p></div><p class=3D"Ms=
oNormal">
Yes, it is.<br>If a venue is inconvenient or uncomfortable for a small perc=
entage of &quot;regular&quot;<br>IETF participants, that does not make it a=
 poor choice of venue.<u></u><u></u></p><div><p class=3D"MsoNormal">=A0<u><=
/u><u></u></p>
</div><div><p class=3D"MsoNormal">[MB] This is the exact reason I had some =
stats in the doc previously as it&#39;s not as small a percentage as you th=
ink. =A0Also, as the document highlights, in cases of medical conditions, o=
ne might consider this to violate the American Disability Act in the US. =
=A0Celiac disease, for example, is considered an &quot;invisible&quot; disa=
bility in the US. =A0One can debate whether or not IETF/ISOC must comply wi=
th the American Disability Act, but as I have posited IETF claims to be an =
open organization so I would think they would want the meetings to be acces=
sible to all, which means ensuring there is food readily available to accom=
modate those with dietary restrictions.<u></u><u></u></p>
</div><div><p class=3D"MsoNormal"><u></u>=A0<u></u></p></div><div><p class=
=3D"MsoNormal">The example of your situation is a matter of personal choice=
. =A0For some of us it can be a matter of life or death (e.g., peanut aller=
gies). =A0[/MB]<u></u><u></u></p>
</div><div><p class=3D"MsoNormal"><u></u>=A0<u></u></p></div><blockquote st=
yle=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0p=
t;margin-left:4.8pt;margin-right:0cm"><p class=3D"MsoNormal"><br>We might a=
s well go back to the debate about location: only a venue that is a<br>
convenient 10 minutes from my home is really a suitable venue.<br><br>I ven=
ture that &quot;starve&quot; is never a real outcome, but &quot;go to a sup=
ermarket&quot; or<br>&quot;bring food in your luggage&quot; are alternative=
s that need some planning and are a<br>
small inconvenience.<u></u><u></u></p></blockquote><div><p class=3D"MsoNorm=
al">[MB] I already responded to this one, but I&#39;ll go ahead again, beca=
use this attitude is the reason why I wrote this document after Dublin. =A0=
There was no supermarket near the venue at all, thus that wasn&#39;t possib=
le. =A0I did the right thing and checked out the hotel restaurants on the S=
unday before the meeting started and found they could easily accommodate my=
 GF diet. However, at Monday lunchtime we could not order off the menu and =
were given something like 3 choices of entrees. =A0The staff serving the fo=
od had no idea about preparation. =A0Folks that are vegan/vegetarian/kosher=
 couldn&#39;t even eat the french fries because they couldn&#39;t be certai=
n whether they were cooked in a meat based oil or vegetable oil. =A0 =A0I h=
ave celiac and thus I cannot eat anything unless I have a very high level o=
f confidence that it is gluten free - my reaction can be extremely severe a=
nd at it&#39;s mildest, it&#39;s like having a miserable 24 hour flu. =A0[/=
MB]<u></u><u></u></p>
</div><blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padd=
ing:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm"><p class=3D"MsoNo=
rmal" style=3D"margin-right:0cm;margin-bottom:12.0pt;margin-left:16.8pt"><s=
pan style=3D"color:#888888"><br>
<span>Adrian</span></span><span style=3D"color:#1f497d"><u></u><u></u></spa=
n></p></blockquote></div></div></div></div></div></div></div></div></blockq=
uote></div><br></div></div>

--089e0122f480d0cc1704e1a6d412--

From bob.hinden@gmail.com  Tue Jul 16 13:42:52 2013
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66C6A21F99AC; Tue, 16 Jul 2013 13:42:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pll5rMSddrDg; Tue, 16 Jul 2013 13:42:52 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EF47A21F97E6; Tue, 16 Jul 2013 13:42:51 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: The IAOC <bob.hinden@gmail.com>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: Time Change [Sunday IAOC Overview Session at the Berlin IETF]
X-Test-IDTracker: no
X-IETF-IDTracker: 4.53
Message-ID: <20130716204251.21682.72791.idtracker@ietfa.amsl.com>
Date: Tue, 16 Jul 2013 13:42:51 -0700
Cc: ietf@ietf.org, 87all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 16 Jul 2013 20:42:52 -0000

The time of the IAOC overview session has changed to 1300-1450 (still in Po=
tsdam 1) to
avoid overlapping with the Newcomers's Meet and Greet.

Bob

On Jul 12, 2013, at 1:58 PM, The IAOC <bob.hinden@gmail.com> wrote:

The IETF Administrative Oversight Committee (IAOC) will hold a session from=
 1500-1650 in
Potsdam 1 at the Berlin IETF on Sunday July 28, 2013.  The purpose is to pr=
ovide an
overview of the IAOC to allow the community to better understand what the I=
AOC does, how
the finances work, venue selection, and provide the IAOC feedback on the jo=
b they are
doing.  =


Remote participation support for this session will be provided by Meetecho.

This will be similar to the session held at IETF86 in Orlando.

The IAOC's responsibilities include:

- Managing the IETF finances
- Oversight of the IETF Administrative Director (IAD)
- Selection and oversight of contracted services
- Venue selection and operation of the IETF meetings
- Support for the IETF's IT services (data tracker, web sites,
  tools, etc.)

The topics that will be discussed include:

- BCP101 - Structure of the IETF Administrative Support Activity (IASA)
- Operation of the IAOC
- Financial model and relationship with ISOC
- Venue selection
- Q & A

We hope this will improve the community understanding of how the IAOC works=
 and provide
the community an opportunity to provide feedback to the IAOC. =


Please let us know ahead of time if you have specific questions you would l=
ike
to see discussed.

Bob Hinden
IAOC Chair

From sob@harvard.edu  Tue Jul 16 13:44:55 2013
Return-Path: <sob@harvard.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FDC621F99CF for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 13:44:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fSb9Fe9lbMi6 for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 13:44:37 -0700 (PDT)
Received: from ackroyd.harvard.edu (ackroyd.harvard.edu [128.103.208.29]) by ietfa.amsl.com (Postfix) with ESMTP id C9CCE21E8083 for <ietf@ietf.org>; Tue, 16 Jul 2013 13:44:30 -0700 (PDT)
Received: from exchange.university.harvard.edu (entwedge0000004.university.harvard.edu [10.35.202.51]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ackroyd.harvard.edu (Postfix) with ESMTP id 55B5FE9882 for <ietf@ietf.org>; Tue, 16 Jul 2013 16:44:30 -0400 (EDT)
Received: from ENTWHUBT0000001.university.harvard.edu (10.32.8.202) by entwedge0000004.university.harvard.edu (10.35.202.51) with Microsoft SMTP Server (TLS) id 14.2.342.3; Tue, 16 Jul 2013 16:44:29 -0400
Received: from ENTWEXMB0000008.university.harvard.edu ([169.254.1.137]) by ENTWHUBT0000001.university.harvard.edu ([10.32.8.202]) with mapi id 14.02.0342.003; Tue, 16 Jul 2013 16:44:30 -0400
From: "Bradner, Scott" <sob@harvard.edu>
To: "<ietf@ietf.org>" <ietf@ietf.org>
Subject: Re: Time Change [Sunday IAOC Overview Session at the Berlin IETF]
Thread-Topic: Time Change [Sunday IAOC Overview Session at the Berlin IETF]
Thread-Index: AQHOgmUMIYyi+JwNqU+2DqycofK/JZloCPEA
Date: Tue, 16 Jul 2013 20:44:29 +0000
Message-ID: <57F6D45C-6F25-4E3A-9C3F-1EE33AE2E437@harvard.edu>
References: <20130716204251.21682.72791.idtracker@ietfa.amsl.com>
In-Reply-To: <20130716204251.21682.72791.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [173.166.5.69]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <55C574E67BF437418441F872846D301A@Exchange.university.harvard.edu>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jul 2013 20:44:55 -0000

but now it overlaps with the newcomers tutorial so I will not be there

Scott


On Jul 16, 2013, at 4:42 PM, The IAOC <bob.hinden@gmail.com>
 wrote:

> The time of the IAOC overview session has changed to 1300-1450 (still in =
Potsdam 1) to
> avoid overlapping with the Newcomers's Meet and Greet.
>=20
> Bob
>=20
> On Jul 12, 2013, at 1:58 PM, The IAOC <bob.hinden@gmail.com> wrote:
>=20
> The IETF Administrative Oversight Committee (IAOC) will hold a session fr=
om 1500-1650 in
> Potsdam 1 at the Berlin IETF on Sunday July 28, 2013.  The purpose is to =
provide an
> overview of the IAOC to allow the community to better understand what the=
 IAOC does, how
> the finances work, venue selection, and provide the IAOC feedback on the =
job they are
> doing. =20
>=20
> Remote participation support for this session will be provided by Meetech=
o.
>=20
> This will be similar to the session held at IETF86 in Orlando.
>=20
> The IAOC's responsibilities include:
>=20
> - Managing the IETF finances
> - Oversight of the IETF Administrative Director (IAD)
> - Selection and oversight of contracted services
> - Venue selection and operation of the IETF meetings
> - Support for the IETF's IT services (data tracker, web sites,
>  tools, etc.)
>=20
> The topics that will be discussed include:
>=20
> - BCP101 - Structure of the IETF Administrative Support Activity (IASA)
> - Operation of the IAOC
> - Financial model and relationship with ISOC
> - Venue selection
> - Q & A
>=20
> We hope this will improve the community understanding of how the IAOC wor=
ks and provide
> the community an opportunity to provide feedback to the IAOC.=20
>=20
> Please let us know ahead of time if you have specific questions you would=
 like
> to see discussed.
>=20
> Bob Hinden
> IAOC Chair


From faber@isi.edu  Tue Jul 16 13:48:20 2013
Return-Path: <faber@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C4A721F9F21 for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 13:48:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HVlSCzOwIrgd for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 13:48:15 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 6FF6221F9A8F for <ietf@ietf.org>; Tue, 16 Jul 2013 13:48:15 -0700 (PDT)
Received: from vim.isi.edu (vim.isi.edu [128.9.168.184]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r6GKkln5018706 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 16 Jul 2013 13:46:47 -0700 (PDT)
Message-ID: <51E5B136.20901@isi.edu>
Date: Tue, 16 Jul 2013 13:46:46 -0700
From: Ted Faber <faber@isi.edu>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130715 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: I-D Action: draft-barnes-healthy-food-07.txt
References: <20130716163157.28468.93383.idtracker@ietfa.amsl.com> <0e1501ce8247$45197bf0$cf4c73d0$@olddog.co.uk> <B6E25FF4CE904AF154E73319@JcK-HP8200.jck.com> <m2ppuipckj.wl%randy@psg.com>
In-Reply-To: <m2ppuipckj.wl%randy@psg.com>
X-Enigmail-Version: 1.5.1
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="----enig2RHSWKNMFQHACUFVAMKIB"
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: faber@isi.edu
Cc: faber@isi.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jul 2013 20:48:20 -0000

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

On 07/16/2013 11:46, Randy Bush wrote:
> two hypotheses:
>   o there is no venue which is easy/acceptable to all ietf participants=

>   o there is no ietf participant for whom all venues are easy/acceptabl=
e

    o there is some ietf participant for whom no venue is easy/acceptable=


Yet, we persevere.

--=20
Ted Faber
http://www.isi.edu/~faber           PGP:
http://www.isi.edu/~faber/pubkeys.asc
Unexpected attachment on this mail? See
http://www.isi.edu/~faber/FAQ.html#SIG


------enig2RHSWKNMFQHACUFVAMKIB
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.13 (FreeBSD)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlHlsTYACgkQaUz3f+Zf+Xs/AgCgkp6p1ym7FumPsBeBbQhb0F3w
wfIAniBCGgCXlZ3x/7NCWHRAw56muYe0
=6QgD
-----END PGP SIGNATURE-----

------enig2RHSWKNMFQHACUFVAMKIB--

From Ted.Lemon@nominum.com  Tue Jul 16 14:36:42 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A76BB11E80F3 for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 14:36:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.593
X-Spam-Level: 
X-Spam-Status: No, score=-106.593 tagged_above=-999 required=5 tests=[AWL=0.006, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T7Q0TgcUWoRC for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 14:36:36 -0700 (PDT)
Received: from exprod7og105.obsmtp.com (exprod7og105.obsmtp.com [64.18.2.163]) by ietfa.amsl.com (Postfix) with ESMTP id DF9E021F99DA for <ietf@ietf.org>; Tue, 16 Jul 2013 14:36:35 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob105.postini.com ([64.18.6.12]) with SMTP ID DSNKUeW84xzUgbIgGjN20Lqkgsd06Y7eJDUN@postini.com; Tue, 16 Jul 2013 14:36:35 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 5D48F1B81C7 for <ietf@ietf.org>; Tue, 16 Jul 2013 14:36:35 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 14984190052; Tue, 16 Jul 2013 14:36:34 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Tue, 16 Jul 2013 14:36:34 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "<adrian@olddog.co.uk>" <adrian@olddog.co.uk>
Subject: Re: I-D Action: draft-barnes-healthy-food-07.txt
Thread-Topic: I-D Action: draft-barnes-healthy-food-07.txt
Thread-Index: AQIKfiTNkPkLWdefr8jDMRdxEhClWJjvkHzggACGLICAAAlYAIAAFAyAgAAF8gCAABglgA==
Date: Tue, 16 Jul 2013 21:36:33 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775214BCB@mbx-01.win.nominum.com>
References: <20130716163157.28468.93383.idtracker@ietfa.amsl.com> <0e1501ce8247$45197bf0$cf4c73d0$@olddog.co.uk> <B6E25FF4CE904AF154E73319@JcK-HP8200.jck.com> <0e3c01ce8253$796ebd00$6c4c3700$@olddog.co.uk> <CABmDk8knWphtjiS-oPNkj0BW-AKGSj3cdnrZjwuUau5v2yyUyA@mail.gmail.com> <0e8e01ce8260$78b56c30$6a204490$@olddog.co.uk>
In-Reply-To: <0e8e01ce8260$78b56c30$6a204490$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <52BB5AE3FB0A6B4D97E5C2DA4B4077FF@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: John C Klensin <john-ietf@jck.com>, "<ietf@ietf.org>" <ietf@ietf.org>, "<draft-barnes-healthy-food@tools.ietf.org>" <draft-barnes-healthy-food@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jul 2013 21:36:42 -0000

On Jul 16, 2013, at 1:10 PM, Adrian Farrel <adrian@olddog.co.uk> wrote:
> It should not be an over-riding consideration.

If not, then what _would_ be an over-riding consideration?

I did the research on the venue for the Dublin IETF and concluded that I co=
uld not stay at the hotel, so I stayed elsewhere and commuted to the venue.=
   This made my IETF visit quite a bit less effective than it would otherwi=
se have been, because I was about an hour from the venue by reasonably pric=
ed transportation. =20

In Orlando, as an AD, I was still driving fifteen to twenty minutes each wa=
y at least once a day to get food, which was a huge waste of time that left=
 me badly sleep-deprived one morning.   I still managed to get to the point=
 where I had to eat a cookie or faint at one point, and that pretty much wr=
ecked me for the rest of the day.   Expecting there to be healthy food at a=
n IETF venue is _not_ unreasonable, and the lack of it _does_ impact produc=
tivity.

(When I mentioned Dublin previously, I was referring to our recent mutual v=
isit to downtown Dublin, not to the Dublin IETF.)

BTW, on the topic of diversity, I'd just like to point out that understandi=
ng really matters.   Dave Crocker's message on this topic was really touchi=
ng, and much appreciated.   I think this is something that we could stand t=
o see more of in the IETF, not just on the topic of food, but various other=
 diversity topics that we discuss from time to time (or perhaps even now, i=
n another thread).


From mary.h.barnes@gmail.com  Tue Jul 16 14:44:04 2013
Return-Path: <mary.h.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93F8921F9DFB for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 14:44:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v20TG8hXtNSZ for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 14:44:04 -0700 (PDT)
Received: from mail-la0-x22c.google.com (mail-la0-x22c.google.com [IPv6:2a00:1450:4010:c03::22c]) by ietfa.amsl.com (Postfix) with ESMTP id EA61721F9E46 for <ietf@ietf.org>; Tue, 16 Jul 2013 14:44:02 -0700 (PDT)
Received: by mail-la0-f44.google.com with SMTP id er20so966462lab.31 for <ietf@ietf.org>; Tue, 16 Jul 2013 14:44:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=78oG/ULN2VHkSCxPmYFTdtgoatDN8Ke3WGy2X54OmHM=; b=jYN8Qet6suQQ/Hdo7qi+eOasXCjQTIlaNXDTR1pOf0Dd2vRT7NkkB9CN8FpucpuIcR Jp5K1+WSy2lePkB/hkfPl6zZ9PzbKhQVaITyhTJGUNlQV/BOC0V5iizpOXlqptmoJYU2 HqXM+lTtlJDc1JoiyioWUZ36XIkNhoKOt7V7Qf5XR+/uhhZ3Q1m8uCi+gwutPMxIUbeG soOW1QBVPHXe1C7yk5adWll4CqbF0RjJWzbVFRmgnlhUGVsCAAwAjiqrmdqGEVznCNKq oBAlSg2qpB7cv2Wy9Us5vIF2cFmAi4n0k2CsCcVlfCxar0Y/Ikd5g7C+M0nxVaQc6f5C pN3w==
MIME-Version: 1.0
X-Received: by 10.152.87.15 with SMTP id t15mr1514467laz.85.1374011041829; Tue, 16 Jul 2013 14:44:01 -0700 (PDT)
Received: by 10.114.184.14 with HTTP; Tue, 16 Jul 2013 14:44:01 -0700 (PDT)
In-Reply-To: <57F6D45C-6F25-4E3A-9C3F-1EE33AE2E437@harvard.edu>
References: <20130716204251.21682.72791.idtracker@ietfa.amsl.com> <57F6D45C-6F25-4E3A-9C3F-1EE33AE2E437@harvard.edu>
Date: Tue, 16 Jul 2013 16:44:01 -0500
Message-ID: <CABmDk8kVZ8Lu9nV9=piDxjGc5LVR80_z2r3y=rqG3BsN-Xpq_g@mail.gmail.com>
Subject: Re: Time Change [Sunday IAOC Overview Session at the Berlin IETF]
From: Mary Barnes <mary.h.barnes@gmail.com>
To: "Bradner, Scott" <sob@harvard.edu>
Content-Type: multipart/alternative; boundary=001a11c3663e10d5ed04e1a7e066
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jul 2013 21:44:04 -0000

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

I had previously asked if the tutorials couldn't be shortened and start 30
minutes earlier so that none of them conflict the with newcomer's meet and
greet. It makes little sense to me to have tutorials conflict with an event
targeted at newcomers.  While those of us that have been around for a while
benefit from some of these other tutorials, I would think that the majority
of newcomers would have an even higher level of interest in attending them.

Mary.


On Tue, Jul 16, 2013 at 3:44 PM, Bradner, Scott <sob@harvard.edu> wrote:

> but now it overlaps with the newcomers tutorial so I will not be there
>
> Scott
>
>
> On Jul 16, 2013, at 4:42 PM, The IAOC <bob.hinden@gmail.com>
>  wrote:
>
> > The time of the IAOC overview session has changed to 1300-1450 (still in
> Potsdam 1) to
> > avoid overlapping with the Newcomers's Meet and Greet.
> >
> > Bob
> >
> > On Jul 12, 2013, at 1:58 PM, The IAOC <bob.hinden@gmail.com> wrote:
> >
> > The IETF Administrative Oversight Committee (IAOC) will hold a session
> from 1500-1650 in
> > Potsdam 1 at the Berlin IETF on Sunday July 28, 2013.  The purpose is to
> provide an
> > overview of the IAOC to allow the community to better understand what
> the IAOC does, how
> > the finances work, venue selection, and provide the IAOC feedback on the
> job they are
> > doing.
> >
> > Remote participation support for this session will be provided by
> Meetecho.
> >
> > This will be similar to the session held at IETF86 in Orlando.
> >
> > The IAOC's responsibilities include:
> >
> > - Managing the IETF finances
> > - Oversight of the IETF Administrative Director (IAD)
> > - Selection and oversight of contracted services
> > - Venue selection and operation of the IETF meetings
> > - Support for the IETF's IT services (data tracker, web sites,
> >  tools, etc.)
> >
> > The topics that will be discussed include:
> >
> > - BCP101 - Structure of the IETF Administrative Support Activity (IASA)
> > - Operation of the IAOC
> > - Financial model and relationship with ISOC
> > - Venue selection
> > - Q & A
> >
> > We hope this will improve the community understanding of how the IAOC
> works and provide
> > the community an opportunity to provide feedback to the IAOC.
> >
> > Please let us know ahead of time if you have specific questions you
> would like
> > to see discussed.
> >
> > Bob Hinden
> > IAOC Chair
>
>

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

<div dir=3D"ltr">I had previously asked if the tutorials couldn&#39;t be sh=
ortened and start 30 minutes earlier so that none of them conflict the with=
 newcomer&#39;s meet and greet. It makes little sense to me to have tutoria=
ls conflict with an event targeted at newcomers. =A0While those of us that =
have been around for a while benefit from some of these other tutorials, I =
would think that the majority of newcomers would have an even higher level =
of interest in attending them.<div>
<br></div><div>Mary.=A0</div></div><div class=3D"gmail_extra"><br><br><div =
class=3D"gmail_quote">On Tue, Jul 16, 2013 at 3:44 PM, Bradner, Scott <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:sob@harvard.edu" target=3D"_blank">sob@h=
arvard.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">but now it overlaps with the newcomers tutor=
ial so I will not be there<br>
<br>
Scott<br>
<br>
<br>
On Jul 16, 2013, at 4:42 PM, The IAOC &lt;<a href=3D"mailto:bob.hinden@gmai=
l.com">bob.hinden@gmail.com</a>&gt;<br>
<div class=3D"HOEnZb"><div class=3D"h5">=A0wrote:<br>
<br>
&gt; The time of the IAOC overview session has changed to 1300-1450 (still =
in Potsdam 1) to<br>
&gt; avoid overlapping with the Newcomers&#39;s Meet and Greet.<br>
&gt;<br>
&gt; Bob<br>
&gt;<br>
&gt; On Jul 12, 2013, at 1:58 PM, The IAOC &lt;<a href=3D"mailto:bob.hinden=
@gmail.com">bob.hinden@gmail.com</a>&gt; wrote:<br>
&gt;<br>
&gt; The IETF Administrative Oversight Committee (IAOC) will hold a session=
 from 1500-1650 in<br>
&gt; Potsdam 1 at the Berlin IETF on Sunday July 28, 2013. =A0The purpose i=
s to provide an<br>
&gt; overview of the IAOC to allow the community to better understand what =
the IAOC does, how<br>
&gt; the finances work, venue selection, and provide the IAOC feedback on t=
he job they are<br>
&gt; doing.<br>
&gt;<br>
&gt; Remote participation support for this session will be provided by Meet=
echo.<br>
&gt;<br>
&gt; This will be similar to the session held at IETF86 in Orlando.<br>
&gt;<br>
&gt; The IAOC&#39;s responsibilities include:<br>
&gt;<br>
&gt; - Managing the IETF finances<br>
&gt; - Oversight of the IETF Administrative Director (IAD)<br>
&gt; - Selection and oversight of contracted services<br>
&gt; - Venue selection and operation of the IETF meetings<br>
&gt; - Support for the IETF&#39;s IT services (data tracker, web sites,<br>
&gt; =A0tools, etc.)<br>
&gt;<br>
&gt; The topics that will be discussed include:<br>
&gt;<br>
&gt; - BCP101 - Structure of the IETF Administrative Support Activity (IASA=
)<br>
&gt; - Operation of the IAOC<br>
&gt; - Financial model and relationship with ISOC<br>
&gt; - Venue selection<br>
&gt; - Q &amp; A<br>
&gt;<br>
&gt; We hope this will improve the community understanding of how the IAOC =
works and provide<br>
&gt; the community an opportunity to provide feedback to the IAOC.<br>
&gt;<br>
&gt; Please let us know ahead of time if you have specific questions you wo=
uld like<br>
&gt; to see discussed.<br>
&gt;<br>
&gt; Bob Hinden<br>
&gt; IAOC Chair<br>
<br>
</div></div></blockquote></div><br></div>

--001a11c3663e10d5ed04e1a7e066--

From ben@nostrum.com  Tue Jul 16 15:27:33 2013
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3148921F91B7; Tue, 16 Jul 2013 15:27:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.488
X-Spam-Level: 
X-Spam-Status: No, score=-102.488 tagged_above=-999 required=5 tests=[AWL=0.112, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E7XvFlbvVhe5; Tue, 16 Jul 2013 15:27:32 -0700 (PDT)
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 7566921F9011; Tue, 16 Jul 2013 15:27:32 -0700 (PDT)
Received: from [10.0.1.12] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r6GMRV0X020855 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 16 Jul 2013 17:27:31 -0500 (CDT) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Gen-ART LC/Telechat Review of draft-ietf-jcardcal-jcard-04
Date: Tue, 16 Jul 2013 17:27:31 -0500
Message-Id: <E8A52EC5-BF67-4F5B-A810-0D69D01377AA@nostrum.com>
To: draft-ietf-jcardcal-jcard.all@tools.ietf.org
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
Received-SPF: pass (shaman.nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jul 2013 22:27:33 -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 wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document:  draft-ietf-jcardcal-jcard-04
Reviewer:  Ben Campbell
Review Date:  2013-07-16
IETF LC End Date: 2013-07-18
IESG Telechat date: 2013-07-18

Note: This draft is on the IESG Telechat agenda on the same date as it =
completes IETF Last Call. Therefore, this review serves both purposes.

Summary: This draft is almost ready for publication as a proposed =
standard. There are a few minor issues and editorial nits that should be =
considered prior to publication.

Major issues:

-- None

Minor issues:

-- Section 1, design considerations:

You mention that the semantic results should survive round-tripping, but =
the order of fields might not. I gather there are other changes that =
might occur from the literal text, right? (e.g. Case changes, some =
optional parameter usage). If so, it might be worth clarifying that.

-- 3.1, 2nd paragraph:

I assume the removal of escaping means that one renders the escaped =
text, not simply removes it, right? Is that as simple as removing the =
escape characters in vCards? I assume this doesn't apply to any =
content-specific escaping inside vCard fields, e.g. URI escaping, right? =
If so, it might be worth mentioning.

-- 3.2.1.1:

What happens for future versions of vCard? Do you simply use the new =
version number, or would we need a new version of this spec? I suspect =
the latter. If true, it might be worth mentioning that, or somewhere =
early in the draft mention that this spec is for vCard 4.0 only.

-- sections 3.4.3 and 3.4.4:

Is the included ABNF a quotation of that in the referenced RFCs, or is =
it new and authoritative? If the former, it would be helpful to mention =
that in the text. (I note you did say that about the ABNF in the =
appendix).

-- 3.4.11:

If RFC6350 says that use of the timezone offset is NOT RECOMMENDED, can =
you elaborate on why it's included here? (I can guess it's because =
people may still use it in vCards since it was a "MUST NOT", but it =
would be good to say something to that effect in the text.)

Nits/editorial comments:

-- Section 1, paragraph 1:

Please expand JSON on first mention.

-- Section 1, paragraph 3:

This paragraph seems redundant to paragraph 1.

-- 1, paragraph 7: " Preserve the semantics of the vCard data."

Imperative form sentence is confusing in context, and inconsistent with =
surrounding text.

-- 1, paragraph 8:

Sentence Fragment.

-- 3.2, Last Paragraph: "... for a parser check the data type..."

Missing "to"?

-- 3.2.1.2, last paragraph before example:

Should the "iCalendar" reference be "vCard" instead?

-- 3.2.1.3, Last Paragraph:

RFCTODO? I gather in the IANA section, that may be a placeholder for =
"this RFC", but that doesn't seem to fit here.

-- 3.3.2: "Example 1:"

Other examples are not numbered.

-- 5:

More occurrences of RFCTODO









From ben@nostrum.com  Tue Jul 16 15:51:47 2013
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C451B21F9AA3; Tue, 16 Jul 2013 15:51:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.498
X-Spam-Level: 
X-Spam-Status: No, score=-102.498 tagged_above=-999 required=5 tests=[AWL=0.102, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ioqTdRRbvSqz; Tue, 16 Jul 2013 15:51:47 -0700 (PDT)
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 B8DBB21F9A98; Tue, 16 Jul 2013 15:51:46 -0700 (PDT)
Received: from [10.0.1.12] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r6GMpjYJ023427 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 16 Jul 2013 17:51:46 -0500 (CDT) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Gen-ART LC Review of draft-yusef-dispatch-ccmp-indication-04
Date: Tue, 16 Jul 2013 17:51:45 -0500
Message-Id: <15C587F4-4A93-4EAC-A241-D0E5E8FF5F3B@nostrum.com>
To: draft-yusef-dispatch-ccmp-indication.all@tools.ietf.org
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
Received-SPF: pass (shaman.nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jul 2013 22:51:47 -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-yusef-dispatch-ccmp-indication-04
Reviewer: Ben Campbell=09
Review Date: 2013-07-16
IETF LC End Date: 2013-07-16

Summary: This draft is almost ready for publication as a proposed =
standard, but I think there are some clarifications needed first.

Major issues:

-- None

Minor issues:

-- Abstract:

Is the abstract current? It says you will discuss pros and cons of a few =
options, and recommend two. I guess you did recommend two, but the =
others have been relegated to the appendix. There are no pros and cons =
listed for the two recommended choices, which seems rather odd.=20

It also mentions that these are mechanisms to be used by SIP clients. =
That's not repeated in the introduction. Is this entire draft intended =
exclusively for SIP clients?

-- 2.

It would be helpful to give more guidance on when one would use one =
method over the other. 2.1 mentions that it might be an "easier way for =
a UA that is not interested in the URI". I'm not sure what it means for =
a UA to be interested or not interested in a URI--maybe you mean "A UA =
that does not otherwise need to parse the URI"?

-- 2.1:=20

I assume this section is intended to be SIP specific. It would help to =
say that somewhere, and include a 3261 citation for Call-Info. There are =
hints that the entire draft is SIP specific in the abstract, but that =
doesn't get repeated elsewhere. (In fact, the only non-abstract citation =
to 3261 is in the IANA considerations.)

Also, the section seems underspecified. It says the ccmp value can go in =
any INVITE, INVITE response, or OPTIONS response. It would help to =
describe how UAs would actually use it. Simply naming the actors would =
help; as it is, they are obscured by the passive voice in "... can be =
used...", and the reader is left to infer the intent based on his =
knowledge of SIP.

--2.2:

I assume this section is _not_ necessarily SIP specific. If that's the =
intent, it would be helpful to say so.

-- Appendices:

There's more detail and discussion around the discarded methods than the =
recommended ones in sections 2.X. It would be helpful to have those =
sections have at least this much explanation.

-- section 3:

You say this draft introduces no additional security considerations. =
Statements like that turn out false more often than not. For example, is =
there no security consideration created by having a SIP UA identify =
itself as a conference focus in an INVITE? (Even if the answer is no, =
it's helpful to have text along the line of "we thought about this and =
decided it was not a consideration due <reasons>"

Further, you say "... beyond those applicable to the mechanisms =
described within". The mechanisms in sections 2.X are "described =
within". I assume those aren't the ones you mean here.


Nits/editorial comments:

-- Abstract:

The abstract should not contain citations. It will be published in =
multiple places without the rest of the document, orphaning the =
citations.=

From marka@isc.org  Tue Jul 16 17:32:51 2013
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5875D21F8475 for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 17:32:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.455
X-Spam-Level: 
X-Spam-Status: No, score=-2.455 tagged_above=-999 required=5 tests=[AWL=0.144,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P0GxNKEjiWOO for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 17:32:46 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 89CBB21F90FD for <ietf@ietf.org>; Tue, 16 Jul 2013 17:32:46 -0700 (PDT)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id CA80CC94C2; Wed, 17 Jul 2013 00:32:31 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1374021165; bh=LAyQFOo0/Ad9VdOSDmSSms/XMkvWK2CTciDdJCTlaeg=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=HjyldORjCxoxrvx/UcxnxG0iD/UGngeCAqWSk9i7GEOfD6zUalQaNOZeuM46dcsAP /j3VRDkVrPJYP1PpHefA/KR2KSsdOxZrZgO3Bi3VR4oNrueoiGqYaEGusL/sahs52j y/bwD1DYiSfjTCAyJDcsXXmjBK/r7O6Y0RfCFuGs=
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.pao1.isc.org (Postfix) with ESMTP; Wed, 17 Jul 2013 00:32:31 +0000 (UTC) (envelope-from marka@isc.org)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 77E901601E7; Wed, 17 Jul 2013 00:35:13 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id VFdl85Guq-sN; Wed, 17 Jul 2013 00:35:12 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id D756D1601E6; Wed, 17 Jul 2013 00:35:12 +0000 (UTC)
X-Virus-Scanned: amavisd-new at zmx1.isc.org
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id D_kUKyvZdtzS; Wed, 17 Jul 2013 00:35:12 +0000 (UTC)
Received: from drugs.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id 829D21601E5; Wed, 17 Jul 2013 00:35:12 +0000 (UTC)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id B2E5037662F4; Wed, 17 Jul 2013 10:32:27 +1000 (EST)
To: Ofer Inbar <cos@aaaaa.org>
From: Mark Andrews <marka@isc.org>
References: <20130713152747.8F79D18C0D0@mercury.lcs.mit.edu> <51E18737.4080903@isdg.net> <3725D4B2-65DA-45FA-AAEE-309F45CD6F18@checkpoint.com> <51E2A8EE.5010200@isdg.net> <A0984871-D92D-4110-9001-16B363B65AC0@checkpoint.com> <6.2.5.6.2.20130714205140.0ce1f0b8@resistor.net> <51E4DC6C.3040609@dougbarton.us> <20130716150721.GG29401@mip.aaaaa.org>
Subject: Re: The case of dotless domains
In-reply-to: Your message of "Tue, 16 Jul 2013 11:07:21 -0400." <20130716150721.GG29401@mip.aaaaa.org>
Date: Wed, 17 Jul 2013 10:32:27 +1000
Message-Id: <20130717003227.B2E5037662F4@drugs.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
Cc: ietf@ietf.org, S Moonesamy <sm+ietf@elandsys.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Jul 2013 00:32:51 -0000

In message <20130716150721.GG29401@mip.aaaaa.org>, Ofer Inbar writes:
> > >>What this brings to mind is that we used to have implicit DNS domain
> > >>search in the early days of DNS.  When edu.com accidentally hijacked
> > >>a huge chunk of the Internet, most of the net very quickly got rid of
> > >>implicit search, and we got the explicit DNS search feature that many
> > >>people are discussing now.
> > >
> > >Yes.
> > 
> > Can you (or Ofer) define how you're using the terms "explicit" and 
> > "implicit" in terms of DNS search, and what their relevance is to the 
> > topic of dotless domains? And no, I'm not being snarky, I think part of 
> > the problem here is a fundamental misunderstanding of how the vast 
> > majority of hosts are configured currently.
> 
> You're not being snarky, but that indicates that you seem to have
> missed my point, which is not about the technical details of how
> domain search got changed after the edu.com disaster.  My point is
> not to make a direct parallel between how domain search changed, and
> dotless domains, and you seem to be looking at it in that light.
> 
> What this brings to mind is that we had a DNS system that was
> vulnerable to the addition of something to the DNS that people had
> expected nobody would make the mistake of doing, but it happened and
> caused damage, and the net reacted by altering how DNS software works
> in order to protect against that damage.  At the time, the obvious
> defensive change was "don't do implicit domain search".  If dotless
> domains cause damage as many people here predict, what I'm saying is
> that I think we'll react similarly, and that I guess the defensive
> change people will widely deploy is to reject A/AAAA/MX records at
> the top level.
> 
> You really do not need to drill into the specifics of the change from
> implicit to explicit domain search in reaction to edu.com, in this
> context.  So it sounds to me like you have something quite different
> in mind.  I don't know what you think I was trying to say - it's not
> anything I said explicitly, so perhaps you think I was trying to
> subtly say something between the lines.  To be clear: I wasn't.
>   -- Cos

It was more than implicit to explicit.  It was also trying domains
with dots "as is" first.  Domains with perids were treated as fully
qualified until proved otherwise.  Unqualified domains were qualified
then tried "as is" if a match was not found.

It is bad to treat domains with periods as partially qualified.
It is bad to treat domains without periods as qualified.

Note it is also more than A, AAAA and MX record at the tld label.
It is also SRV records where they are used with a base name in
a host context.

_http._tcp.tld/SRV is equally bad as tld/A where as
_whois._tcp.tld/SRV would not be a issue as it would point to
the whois service for names that end in .tld.

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From medel@globetel.com.ph  Tue Jul 16 18:07:27 2013
Return-Path: <medel@globetel.com.ph>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F60A21F9CF5; Tue, 16 Jul 2013 18:07:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.448
X-Spam-Level: 
X-Spam-Status: No, score=0.448 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id niwy9g9d3A7d; Tue, 16 Jul 2013 18:07:23 -0700 (PDT)
Received: from smtp01.globetel.com.ph (smtp01.globetel.com.ph [203.177.192.181]) by ietfa.amsl.com (Postfix) with ESMTP id 1077C21F9C68; Tue, 16 Jul 2013 18:07:19 -0700 (PDT)
Received: from exgtbh01.globetel.com ([10.225.208.17]) by smtp01.globetel.com.ph (8.14.4/8.14.4) with ESMTP id r6H1557w003895;  Wed, 17 Jul 2013 09:07:09 +0800
Received: from EXVSGT02.globetel.com ([10.225.208.146]) by exgtbh01.globetel.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 17 Jul 2013 09:13:23 +0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;	charset="euc-jp"
Content-Transfer-Encoding: base64
Subject: RE: Announcement improvement (was: Re: Last Call: RFC 2050 to historic)
Date: Wed, 17 Jul 2013 09:13:22 +0800
Message-ID: <A5AD67DA1ACB9648831FD753485B2BFE2297FFB0@EXVSGT02.globetel.com>
In-Reply-To: <51E51310.5040400@it.aoyama.ac.jp>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Announcement improvement (was: Re: Last Call: RFC 2050 to historic)
Thread-Index: Ac6CCGPYVTKGn3P2TFCNSQQLjsrCjAAfgFKg
References: <20130710213959.9266.65720.idtracker@ietfa.amsl.com> <51E51310.5040400@it.aoyama.ac.jp>
From: "GT RAMIREZ, Medel G." <medel@globetel.com.ph>
To: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>, <ietf@ietf.org>
X-OriginalArrivalTime: 17 Jul 2013 01:13:23.0664 (UTC) FILETIME=[D5568D00:01CE828A]
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-07-16_09:2013-07-16, 2013-07-16, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1305240000 definitions=main-1307160246
Cc: The IESG <iesg-secretary@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Jul 2013 01:07:27 -0000

KzEuDQpMaWtld2lzZSwgaWYgSSBtYXkgYWRkOyB0aGUgc3VtbWFyeSBvZiB0aGUgcHJvZ3Jlc3Mg
c3BlY2lmaWNhbGx5IG9uIHRoZSBNUExTLVRQDQooaS5lLiBSYXRpZmllZCAvIFBlbmRpbmcgLyBP
bi1nb2luZyAvIEV4cGlyZWQpLg0KDQpUaGFua3MNCk1lZGVsDQorKysrKysrKysrKysrKysrKysr
KysrKysrDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBpZXRmLWJvdW5jZXNA
aWV0Zi5vcmcgW21haWx0bzppZXRmLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiAiTWFy
dGluIEouIETDvHJzdCINClNlbnQ6IFR1ZXNkYXksIEp1bHkgMTYsIDIwMTMgNTozMiBQTQ0KVG86
IGlldGZAaWV0Zi5vcmcNCkNjOiBUaGUgSUVTRzsgSUVURi1Bbm5vdW5jZQ0KU3ViamVjdDogQW5u
b3VuY2VtZW50IGltcHJvdmVtZW50ICh3YXM6IFJlOiBMYXN0IENhbGw6IFJGQyAyMDUwIHRvIGhp
c3RvcmljKQ0KDQpGb3IgdGhlIGJlbmVmaXRzIG9mIHRob3NlIChmZXcgYW5kIGZhciBiZXR3ZWVu
KSBJRVRGIHBhcnRpY2lwYW50cyB0aGF0IGhhdmVuJ3QgbWVtb3JpemVkIGFsbCBSRkMgbnVtYmVy
cywgaXQgd291bGQgYmUgZ3JlYXQgaWYgYW5ub3VuY2VtZW50IHN1Y2ggYXMgdGhlIG9uZSBiZWxv
dyB3b3VsZCBjb250YWluIGEgdGlueSBiaXQgbW9yZSBpbmZvcm1hdGlvbiBhYm91dCB0aGUgZG9j
dW1lbnQgaXRzZWxmLg0KDQpFLmcuIGp1c3QgaGF2aW5nIHRoZSB0aXRsZSBvZiB0aGUgZG9jdW1l
bnQgaW4gYW5ub3VuY2VtZW50IHdvdWxkIG1ha2UgaXQgYSBsb3QgZWFzaWVyIHRvIGRlY2lkZSB3
aGV0aGVyIHRoaXMgd2FycmFudHMgZnVydGhlciBhdHRlbnRpb24gb3Igbm90LCB3aXRob3V0IGFk
ZGl0aW9uYWwgbG9va3VwLg0KDQpNYW55IHRoYW5rcyBpbiBhZHZhbmNlIQ0KDQpSZWdhcmRzLCAg
IE1hcnRpbi4NCg0KT24gMjAxMy8wNy8xMSA2OjM5LCBUaGUgSUVTRyB3cm90ZToNCj4NCj4gVGhl
IElFU0cgaGFzIHJlY2VpdmVkIGEgcmVxdWVzdCBmcm9tIGFuIGluZGl2aWR1YWwgcGFydGljaXBh
bnQgdG8gbWFrZSANCj4gdGhlIGZvbGxvd2luZyBzdGF0dXMgY2hhbmdlczoNCj4NCj4gLSBSRkMy
MDUwIGZyb20gQmVzdCBDdXJyZW50IFByYWN0aWNlIHRvIEhpc3RvcmljDQo+DQo+IFRoZSBzdXBw
b3J0aW5nIGRvY3VtZW50IGZvciB0aGlzIHJlcXVlc3QgY2FuIGJlIGZvdW5kIGhlcmU6DQo+DQo+
IGh0dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2Mvc3RhdHVzLWNoYW5nZS0yMDUwLXRvLWhp
c3RvcmljLw0KPg0KPiBUaGUgSUVTRyBwbGFucyB0byBtYWtlIGEgZGVjaXNpb24gaW4gdGhlIG5l
eHQgZmV3IHdlZWtzLCBhbmQgc29saWNpdHMgDQo+IGZpbmFsIGNvbW1lbnRzIG9uIHRoaXMgYWN0
aW9uLiBQbGVhc2Ugc2VuZCBzdWJzdGFudGl2ZSBjb21tZW50cyB0byB0aGUgDQo+IGlldGZAaWV0
Zi5vcmcgbWFpbGluZyBsaXN0cyBieSAyMDEzLTA4LTA3LiBFeGNlcHRpb25hbGx5LCBjb21tZW50
cyBtYXkgDQo+IGJlIHNlbnQgdG8gaWVzZ0BpZXRmLm9yZyBpbnN0ZWFkLiBJbiBlaXRoZXIgY2Fz
ZSwgcGxlYXNlIHJldGFpbiB0aGUgDQo+IGJlZ2lubmluZyBvZiB0aGUgU3ViamVjdCBsaW5lIHRv
IGFsbG93IGF1dG9tYXRlZCBzb3J0aW5nLg0KPg0KPiBUaGUgYWZmZWN0ZWQgZG9jdW1lbnQgY2Fu
IGJlIG9idGFpbmVkIHZpYSANCj4gaHR0cDovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9yZmMy
MDUwLw0KPg0KPiBJRVNHIGRpc2N1c3Npb24gb2YgdGhpcyByZXF1ZXN0IGNhbiBiZSB0cmFja2Vk
IHZpYSANCj4gaHR0cDovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9zdGF0dXMtY2hhbmdlLTIw
NTAtdG8taGlzdG9yaWMvYmFsbG90Lw0KPg0KPg0KPg0KClRoaXMgZS1tYWlsIG1lc3NhZ2UgKGlu
Y2x1ZGluZyBhdHRhY2htZW50cywgaWYgYW55KSBpcyBpbnRlbmRlZCBmb3IgdGhlIHVzZSBvZiB0
aGUgaW5kaXZpZHVhbCBvciB0aGUgZW50aXR5IHRvIHdob20gaXQgaXMgYWRkcmVzc2VkIGFuZCBt
YXkgY29udGFpbiBpbmZvcm1hdGlvbiB0aGF0IGlzIHByaXZpbGVnZWQsIHByb3ByaWV0YXJ5LCBj
b25maWRlbnRpYWwgYW5kIGV4ZW1wdCBmcm9tIGRpc2Nsb3N1cmUuIElmIHlvdSBhcmUgbm90IHRo
ZSBpbnRlbmRlZCByZWNpcGllbnQsIHlvdSBhcmUgbm90aWZpZWQgdGhhdCBhbnkgZGlzc2VtaW5h
dGlvbiwgZGlzdHJpYnV0aW9uIG9yIGNvcHlpbmcgb2YgdGhpcyBjb21tdW5pY2F0aW9uIGlzIHN0
cmljdGx5IHByb2hpYml0ZWQuIElmIHlvdSBoYXZlIHJlY2VpdmVkIHRoaXMgY29tbXVuaWNhdGlv
biBpbiBlcnJvciwgcGxlYXNlIG5vdGlmeSB0aGUgc2VuZGVyIGFuZCBkZWxldGUgdGhpcyBFLW1h
aWwgbWVzc2FnZSBpbW1lZGlhdGVseS4K

From sm@resistor.net  Tue Jul 16 21:16:37 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A76421F9B97 for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 21:16:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.598
X-Spam-Level: 
X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xFEhcctoJ+NG for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 21:16:36 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id E40EF21F9B5D for <ietf@ietf.org>; Tue, 16 Jul 2013 21:16:33 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r6H4GSmZ025416 for <ietf@ietf.org>; Tue, 16 Jul 2013 21:16:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1374034593; bh=CtnkUS66ZaQhRS5nhkj1RxoY3AjcuFMBxTc75EqRPY8=; h=Date:To:From:Subject:In-Reply-To:References; b=a7VITXSKPvohkT3HfJ/bTcZV5DaYRhjnTcOQ80mxmjewT15nwzlHfDZsctxOpLq3y Jklrytu2JIna8/GOkRsckJx/gzYDlO7mtRCHwOw0eiyg5hIh+TZh/cQDqxBBv0aJ2Y V96QkciQnBLM0hy/afI5Par2UseGe0EpN3OXLiMw=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1374034593; i=@resistor.net; bh=CtnkUS66ZaQhRS5nhkj1RxoY3AjcuFMBxTc75EqRPY8=; h=Date:To:From:Subject:In-Reply-To:References; b=fRcuQDnCsk15MmpW5JCqCy5WeDgjNJYWrfZT039mY1TnlsCvGiuIGyyzxJaKhxT1T ilWr7zc0RRMTMczWJynSR6zTn/pMrrd6OHyrTLPD2tNFwGTI9IhVHURekpGNmLeajk 6Y8EGUXB9BfQ+wMFYsyyuUhorxjVdDp0a0dKV1bw=
Message-Id: <6.2.5.6.2.20130716195548.0d5b1db0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 16 Jul 2013 21:15:34 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-weirds-using-http-07.txt> (HTTP usage in the Registration Data Access Protocol (RDAP)) to Proposed Standard
In-Reply-To: <20130715230536.14139.1854.idtracker@ietfa.amsl.com>
References: <20130715230536.14139.1854.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Jul 2013 04:16:37 -0000

At 16:05 15-07-2013, The IESG wrote:
>The IESG has received a request from the Web Extensible Internet
>Registration Data Service WG (weirds) to consider the following document:
>- 'HTTP usage in the Registration Data Access Protocol (RDAP)'
>   <draft-ietf-weirds-using-http-07.txt> as Proposed Standard

The Abstract mentions that:

   "This document is one of a collection that together describe the
    Registration Data Access Protocol (RDAP).  It describes how RDAP is
    transported using the Hypertext Transfer Protocol (HTTP)."

In Section 2 it is mentioned that:

  "RDAP query and response formats are described in other documents
   in the collection of RDAP specifications, while this document
   describes how RDAP clients and servers use HTTP to exchange
   queries and responses."

I read the document and I did not find any other=20
information about collection of RDAP specifications.

According to Section 1:

   "This document describes the usage of HTTP for Registration Data
    Directory Services."

 From Section 2:

   "In accordance with [SAC-051], this document describes the base
    behavior for a Registration Data Access Protocol (RDAP).
    [SAC-051] describes a protocol profile of RDAP for Domain Name
    Registries (DNRs), the Domain Name Registration Data
    Access Protocol (DNRD-AP)."

The recommendation in SAC051 is to adopt the following terminology:

   "Domain Name Registration Data Access Protocol (DNRD-AP).
    The components of a (standard) communications exchange=ADqueries
    and responses=ADthat specify the access to DNRD"

I did not find any other information about the=20
Registration Data Access Protocol.  It is weird=20
that the IETF is standardizing a collection of=20
documents which is undocumented.  It is also=20
weird that the IETF is standardizing the=20
Registration Data Access Protocol when there=20
isn't any information about the said protocol=20
except for the terminology mentioned above.

 From Section 1:

   "A replacement protocol is expected to retain the simple transactional
    nature of WHOIS, while providing a specification for queries and
    responses, redirection to authoritative sources, support for
    Internationalized Domain Names (IDNs, [RFC5890]), and support for
    localized registration data such as addresses and organisation or
    person names."

I read the draft again and I still did not know=20
what the replacement protocol is.  I suggest=20
clarifying where the Registration Data Access=20
Protocol actually exists and where is it specified.

In Section 1:

   "This is the basic usage pattern for this protocol:

    1.  A client issues an HTTP query using GET.  As an example, a query
        for the network registration 192.0.2.0 might be http://
        example.com/ip/192.0.2.0.

    2.  If the receiving server has the information for the query, it
        examines the Accept header field of the query and returns a 200
        response with a response entity appropriate for the requested
        format.

    3.  If the receiving server does not have the information for the
        query but does have knowledge of where the information can be
        found, it will return a redirection response (3xx) with the
        Location: header field containing an HTTP(S) URL (Uniform
        Resource Locator) pointing to the information or another server
        known to have knowledge of the location of the information.  The
        client is expected to re-query using that HTTP URL.

    4.  If the receiving server does not have the information being
        requested and does not have knowledge of where the information
        can be found, it returns a 404 response.

    5.  If the receiving server will not answer a request for policy
        reasons, it will return an error response (4xx) indicating the
        reason for giving no answer."

The above is basically HTTP being given another=20
name.  Section 3 of the draft says that:

   "HTTP also benefits from widespread investment in scalability,
    reliability, and performance, and widespread programmer understanding
    of client behaviours for RESTful web services, reducing the cost to
    deploy Registration Data Directory Services and clients."

It seems that someone decided to choose port 80=20
and then went to find the reasons for that=20
choice.  Can I ask for some references for the=20
above?  I am okay if I am told that I have to=20
believe that it is true because it is written in a RFC.

 From Section 4.2:

   "Servers MUST ignore unknown query parameters.  Use of unknown query
    parameters for cache-busting is described in Appendix B."

If I understood the requirement it is that the=20
servers must ignore unknown query parameters=20
while the draft documents usage of unknown query=20
parameters in Appendix B.  This doesn't make sense to me.

 From Section 5:

   "While no standard HTTP response code is forbidden in usage, at a
    minimum clients SHOULD understand the response codes described in
    this section as they will be in common use by servers."

I don't understand the "SHOULD understand".

 From the Security Considerations section:

   "This document does not pose strong security requirements to the RDAP
    protocol."

I read the about as meaning that the unspecified=20
RDAP protocol does not need strong security requirements.

   "Additional security considerations to the RDAP protocol will be
    covered in future RFCs documenting specific security mechanisms and
    schemes."

I assumed that security considerations was about=20
considering security concerns and discussing=20
about them.  The above leaves that to future RFCs.

In Section 9.1:

   "Clients can use IRIs [RFC3987] for internal use as they see fit, but
    MUST transform them to URIs [RFC3986] for interaction with RDAP
    servers."

That means that servers do not support internationalization.

 From Section 9.2:

   "On the other hand, when servers return data and have knowledge
    that the data is in a language or script, the data SHOULD be
    annotated with language identifiers whenever they are available,
    thus allowing clients to process and display the data accordingly.

    The mechanism for including a language identifier in a response will
    be defined in subsequent documents describing specific response
    formats."

The approach adopted in this future Proposed=20
Standard is that everything will be defined in=20
some future document.  This future Proposed=20
Standard is under-specified to the such an extent=20
that it would be extremely difficult to implement without insider=
 information.

By the way, the RFC 4627 and RFC 5234 references should be normative.

Regards,
-sm=20


From paf@frobbit.se  Tue Jul 16 21:30:02 2013
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DC4621F9B90; Tue, 16 Jul 2013 21:30:02 -0700 (PDT)
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=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8qrOzXjA4zTV; Tue, 16 Jul 2013 21:30:01 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id 2972B21F9B2F; Tue, 16 Jul 2013 21:30:00 -0700 (PDT)
Received: from [10.21.11.46] (unknown [196.38.31.134]) by mail.frobbit.se (Postfix) with ESMTPSA id 8C36E23FA0; Wed, 17 Jul 2013 06:29:58 +0200 (CEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Internationalization and draft-ietf-abfab-eapapplicability
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <BLU169-W3386A689EE5BFC8D2272A093600@phx.gbl>
Date: Wed, 17 Jul 2013 06:29:55 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <71FEE03C-7A07-4CF3-BC25-0F22F306DE71@frobbit.se>
References: <BLU169-W3386A689EE5BFC8D2272A093600@phx.gbl>
To: Bernard Aboba <bernard_aboba@hotmail.com>
X-Mailer: Apple Mail (2.1508)
Cc: "draft-ietf-abfab-eapapplicability@tools.ietf.org" <draft-ietf-abfab-eapapplicability@tools.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Jul 2013 04:30:02 -0000

On 16 jul 2013, at 21:42, Bernard Aboba <bernard_aboba@hotmail.com> =
wrote:

> After reading this document, I believe that this document omits =
discussion of an important aspect, which is  internationalization.  =
Since the contents of the EAP Identity and RADIUS User-Name attributes =
are specified to be encoded in UTF-8, application protocols that utilize =
encodings other than UTF-8 for user identities and passwords could have =
issues utilizing EAP (and RADIUS).  Currently RFC 4282bis proposes that =
all EAP implementations normalize identities and passwords before =
utilizing them, and therefore application protocols that do not do this =
will be at variance with RFC 4282bis. =20
>=20
> IMHO the document needs to state what the internationalization =
requirements are for application-layer protocol use of EAP.  There are =
potential workarounds, such as requiring that application protocols =
convert identities and passwords to UTF-8 prior to use of EAP, or =
modifying RFC 4282bis so as to require normalization in RADIUS proxies =
or servers.   However, without fixes being applied and/or changes to RFC =
4282bis, use of EAP by applications may not be compatible with either =
existing specifications or implementations.=20

In addition to this, if the string is to be compared with other strings =
(directly or indirectly) just specifying encoding is not enough. You =
must also specify the matching algorithm used, and one such can be for =
example to normalize the string(s) before doing character by character =
comparison and specifying what the normalization algorithm is.

   Patrik F=E4ltstr=F6m

> Background
>=20
> EAP and protocols that carry it (e.g. RADIUS) assume that the =
EAP-Response/Identity is encoded in UTF-8.  For example, RFC 3748 =
Section 1.2 defines "displayable message" as follows:=20
>=20
>    Displayable Message
>       This is interpreted to be a human readable string of characters.
>       The message encoding MUST follow the UTF-8 transformation format
>       [RFC2279].
>=20
>=20
> Therefore EAP messages including EAP Identity and Notification that =
are described as "displayable messages" have a UTF-8 encoding =
requirement applied to them.=20
>=20
> Since RFC 3579 Section 2.1 specifies that the EAP-Response/Identity is =
copied into the RADIUS User-Name Attribute:=20
>    In order to permit non-EAP aware RADIUS proxies to forward the
>    Access-Request packet, if the NAS initially sends an
>    EAP-Request/Identity message to the peer, the NAS MUST copy the
>    contents of the Type-Data field of the EAP-Response/Identity =
received
>    from the peer into the User-Name attribute and MUST include the
>    Type-Data field of the EAP-Response/Identity in the User-Name
>    attribute in every subsequent Access-Request.
>=20
>=20
> Therefore for use with EAP, the User-Name Attribute also inherits a =
UTF-8 encoding requirement, restricting the potential encodings =
permitted by RFC 2865 Section 5.1 (User-Name Attribute):=20
>       The format of the username MAY be one of several forms:
>=20
>       text      Consisting only of UTF-8 encoded 10646 [7] characters.
>=20
>       network access identifier
>                 A Network Access Identifier as described in RFC 2486
>                 [8].
>=20
>       distinguished name
>                 A name in ASN.1 form used in Public Key authentication
>                 systems.
>=20
>=20
>=20
>=20
>=20
>=20
>     =20


From stefan.winter@restena.lu  Tue Jul 16 23:52:10 2013
Return-Path: <stefan.winter@restena.lu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F90B21F9C82 for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 23:52:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.193
X-Spam-Level: 
X-Spam-Status: No, score=-2.193 tagged_above=-999 required=5 tests=[AWL=0.406,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZCyAnZNi+NWB for <ietf@ietfa.amsl.com>; Tue, 16 Jul 2013 23:52:09 -0700 (PDT)
Received: from smtprelay.restena.lu (smtprelay.restena.lu [IPv6:2001:a18:1::62]) by ietfa.amsl.com (Postfix) with ESMTP id 0728221F8438 for <ietf@ietf.org>; Tue, 16 Jul 2013 23:52:08 -0700 (PDT)
Received: from smtprelay.restena.lu (localhost [127.0.0.1]) by smtprelay.restena.lu (Postfix) with ESMTP id 7183510584; Wed, 17 Jul 2013 08:52:07 +0200 (CEST)
Received: from aragorn.restena.lu (aragorn.restena.lu [IPv6:2001:a18:1:8::155]) by smtprelay.restena.lu (Postfix) with ESMTPS id 60CD910583; Wed, 17 Jul 2013 08:52:07 +0200 (CEST)
Message-ID: <51E63F12.3070302@restena.lu>
Date: Wed, 17 Jul 2013 08:52:02 +0200
From: Stefan Winter <stefan.winter@restena.lu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
Subject: Re: Internationalization and draft-ietf-abfab-eapapplicability
References: <BLU169-W3386A689EE5BFC8D2272A093600@phx.gbl>
In-Reply-To: <BLU169-W3386A689EE5BFC8D2272A093600@phx.gbl>
X-Enigmail-Version: 1.5.1
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="----enig2FSFOVRNFABGFOIBFPLBC"
X-Virus-Scanned: ClamAV
Cc: "draft-ietf-abfab-eapapplicability@tools.ietf.org" <draft-ietf-abfab-eapapplicability@tools.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Jul 2013 06:52:10 -0000

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

Hi,

> After reading this document, I believe that this document omits
> discussion of an important aspect, which is  internationalization.
>  Since the contents of the EAP Identity and RADIUS User-Name attributes=

> are specified to be encoded in UTF-8, application protocols that utiliz=
e
> encodings other than UTF-8 for user identities and passwords could have=

> issues utilizing EAP (and RADIUS).  Currently RFC 4282bis proposes that=

> all EAP implementations normalize identities and passwords before
> utilizing them, and therefore application protocols that do not do this=

> will be at variance with RFC 4282bis. =20
>=20
> IMHO the document needs to state what the internationalization
> requirements are for application-layer protocol use of EAP.  There are
> potential workarounds, such as requiring that application protocols
> convert identities and passwords to UTF-8 prior to use of EAP, or
> modifying RFC 4282bis so as to require normalization in RADIUS proxies
> or servers.   However, without fixes being applied and/or changes to RF=
C
> 4282bis, use of EAP by applications may not be compatible with either
> existing specifications or implementations.=20

The discussion in radext on RFC4282bis was very long and much thought
has gone into "fixing" internationalisation aspects. The fix is still
partial only, because of the said uncertainties about the input encoding
and normalization. RADIUS servers or proxies touching and manipulating
the Identity/User-Name was seen as the bigger of two evils; the lesser
one being the requirement on EAP supplicants to perform normalization on
their own.

If a change is needed in the eapapplicability draft, I'd prefer to
change eapapplicability to be in line with 4282bis, not the other way
around.

> Background
>=20
> EAP and protocols that carry it (e.g. RADIUS) assume that the
> EAP-Response/Identity is encoded in UTF-8.
>
>  For example, RFC 3748
> Section 1.2 defines "displayable message" as follows:=20
>=20
>    Displayable Message
>       This is interpreted to be a human readable string of characters.
>       The message encoding MUST follow the UTF-8 transformation format
>       [RFC2279].
>=20
>=20
> Therefore EAP messages including EAP Identity and Notification that are=

> described as "displayable messages" have a UTF-8 encoding requirement
> applied to them.=20

I disagree with your reading of RFC3748.

It's true that "displayable messages" need to be encoded in UTF-8; but
the document does not state that an EAP-Response/Identity is a
"displayable message". Section 5.1 of RFC3748 uses the term "displayable
message" several times, but never in conjunction with the Identity
*response*:

"An optional displayable message MAY be included to
      prompt the peer in the case where there is an expectation of
      interaction with a user. "

(which is for the request, and it is optional)

and later on:

"Type-Data

      This field MAY contain a displayable message in the Request,
      containing UTF-8 encoded ISO 10646 characters [RFC2279]."

This is the normative language for the previous text.

I keep staring at section 5.1 of that RFC and see nothing that would
require the EAP-Response/Identity to be UTF-8.

I also believe that the lack of being clear at that particular point is
"the root of all evil" because it allows EAP supplicant implementers to
choose arbitrary encodings for conveying the identities.

It is somewhat understandable that EAP-Response/Identity was not tagged
as "displayable message" back in the day - its purpose is not to be
displayed anywhere; it's input to the authentication algorithm and is
meant to be processed by an EAP server. So, if there's nothing to
display, it's not a displayable message.

RFC3748 would have achieved more clarity and better interop if it would
have explicitly demanded the EAP-Response/Identity to be UTF-8 even
though it's not a displayable message.

Now, that would suggest an update to RFC3748, introducing a UTF-8
requirement at that spot. And guess what - we're writing a document that
updates RFC3748!

The question is: this document is about an applicability update, not a
change of the on-the-wire behaviour of EAP. If we were to try and apply
a proper fix to RFC3748 to make Identities UTF-8 everywhere, then the
impact is way beyond ABFAB. We previously tried to make the
applicability statement "for all of EAP", but later decided to restrict
ourselves to ABFAB-specific updates.

The next best solution then would be to require that only ABFAB-using
EAP supplicants are required to use UTF-8 (and possibly also require a
normalisation). That would indeed solve ABFAB's i18n'ed use of EAP, but
not everybody else's. That's a bit selfish, but it would certainly be
better than nothing.

I wonder what the other authors think about nailing down a
UTF-8/NFC-normalised Identity into the draft.

Greetings,

Stefan Winter

> Since RFC 3579 Section 2.1 specifies that the EAP-Response/Identity is
> copied into the RADIUS User-Name Attribute:=20
>=20
>    In order to permit non-EAP aware RADIUS proxies to forward the
>    Access-Request packet, if the NAS initially sends an
>    EAP-Request/Identity message to the peer, the NAS MUST copy the
>    contents of the Type-Data field of the EAP-Response/Identity receive=
d
>    from the peer into the User-Name attribute and MUST include the
>    Type-Data field of the EAP-Response/Identity in the User-Name
>    attribute in every subsequent Access-Request.
>=20
>=20
> Therefore for use with EAP, the User-Name Attribute also inherits a
> UTF-8 encoding requirement, restricting the potential encodings
> permitted by RFC 2865 Section 5.1 (User-Name Attribute):=20
>=20
>       The format of the username MAY be one of several forms:
>=20
>       text      Consisting only of UTF-8 encoded 10646 [7] characters.
>=20
>       network access identifier
>                 A Network Access Identifier as described in RFC 2486
>                 [8].
>=20
>       distinguished name
>                 A name in ASN.1 form used in Public Key authentication
>                 systems.
>=20
>=20
>=20
>=20
>=20
>=20
>     =20
>=20


--=20
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education National=
e et
de la Recherche
6, rue Richard Coudenhove-Kalergi
L-1359 Luxembourg

Tel: +352 424409 1
Fax: +352 422473


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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlHmPxcACgkQ+jm90f8eFWYw6ACdGxKpaqgrvJIIwFlJ7W9btgno
AFoAmgO9ZZ5n0l6UvuL8lrpOJ/9vSjeC
=cYMj
-----END PGP SIGNATURE-----

------enig2FSFOVRNFABGFOIBFPLBC--

From stephen.farrell@cs.tcd.ie  Wed Jul 17 03:36:03 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 474C521F9A5F; Wed, 17 Jul 2013 03:36:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level: 
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hit2iJ7fzZkt; Wed, 17 Jul 2013 03:35:58 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id EBF2021F99C0; Wed, 17 Jul 2013 03:35:57 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 2AF6ABEAF; Wed, 17 Jul 2013 11:35:34 +0100 (IST)
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pdToWOYTMjQm; Wed, 17 Jul 2013 11:35:34 +0100 (IST)
Received: from [IPv6:2001:770:10:203:588a:ac19:318b:469b] (unknown [IPv6:2001:770:10:203:588a:ac19:318b:469b]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id F2589BE8A; Wed, 17 Jul 2013 11:35:33 +0100 (IST)
Message-ID: <51E67375.20802@cs.tcd.ie>
Date: Wed, 17 Jul 2013 11:35:33 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
Subject: Re: Internationalization and draft-ietf-abfab-eapapplicability
References: <BLU169-W3386A689EE5BFC8D2272A093600@phx.gbl> <71FEE03C-7A07-4CF3-BC25-0F22F306DE71@frobbit.se>
In-Reply-To: <71FEE03C-7A07-4CF3-BC25-0F22F306DE71@frobbit.se>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: Bernard Aboba <bernard_aboba@hotmail.com>, "draft-ietf-abfab-eapapplicability@tools.ietf.org" <draft-ietf-abfab-eapapplicability@tools.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Jul 2013 10:36:03 -0000

Hi Bernard, Patrik,

Thanks for the comment. Checking that out now and will
get back.

Cheers,
S.

On 07/17/2013 05:29 AM, Patrik F鋖tstr鰉 wrote:
> 
> On 16 jul 2013, at 21:42, Bernard Aboba <bernard_aboba@hotmail.com> wrote:
> 
>> After reading this document, I believe that this document omits discussion of an important aspect, which is  internationalization.  Since the contents of the EAP Identity and RADIUS User-Name attributes are specified to be encoded in UTF-8, application protocols that utilize encodings other than UTF-8 for user identities and passwords could have issues utilizing EAP (and RADIUS).  Currently RFC 4282bis proposes that all EAP implementations normalize identities and passwords before utilizing them, and therefore application protocols that do not do this will be at variance with RFC 4282bis.  
>>
>> IMHO the document needs to state what the internationalization requirements are for application-layer protocol use of EAP.  There are potential workarounds, such as requiring that application protocols convert identities and passwords to UTF-8 prior to use of EAP, or modifying RFC 4282bis so as to require normalization in RADIUS proxies or servers.   However, without fixes being applied and/or changes to RFC 4282bis, use of EAP by applications may not be compatible with either existing specifications or implementations. 
> 
> In addition to this, if the string is to be compared with other strings (directly or indirectly) just specifying encoding is not enough. You must also specify the matching algorithm used, and one such can be for example to normalize the string(s) before doing character by character comparison and specifying what the normalization algorithm is.
> 
>    Patrik F鋖tstr鰉
> 
>> Background
>>
>> EAP and protocols that carry it (e.g. RADIUS) assume that the EAP-Response/Identity is encoded in UTF-8.  For example, RFC 3748 Section 1.2 defines "displayable message" as follows: 
>>
>>    Displayable Message
>>       This is interpreted to be a human readable string of characters.
>>       The message encoding MUST follow the UTF-8 transformation format
>>       [RFC2279].
>>
>>
>> Therefore EAP messages including EAP Identity and Notification that are described as "displayable messages" have a UTF-8 encoding requirement applied to them. 
>>
>> Since RFC 3579 Section 2.1 specifies that the EAP-Response/Identity is copied into the RADIUS User-Name Attribute: 
>>    In order to permit non-EAP aware RADIUS proxies to forward the
>>    Access-Request packet, if the NAS initially sends an
>>    EAP-Request/Identity message to the peer, the NAS MUST copy the
>>    contents of the Type-Data field of the EAP-Response/Identity received
>>    from the peer into the User-Name attribute and MUST include the
>>    Type-Data field of the EAP-Response/Identity in the User-Name
>>    attribute in every subsequent Access-Request.
>>
>>
>> Therefore for use with EAP, the User-Name Attribute also inherits a UTF-8 encoding requirement, restricting the potential encodings permitted by RFC 2865 Section 5.1 (User-Name Attribute): 
>>       The format of the username MAY be one of several forms:
>>
>>       text      Consisting only of UTF-8 encoded 10646 [7] characters.
>>
>>       network access identifier
>>                 A Network Access Identifier as described in RFC 2486
>>                 [8].
>>
>>       distinguished name
>>                 A name in ASN.1 form used in Public Key authentication
>>                 systems.
>>
>>
>>
>>
>>
>>
>>      
> 

From hartmans@mit.edu  Wed Jul 17 04:04:29 2013
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88B1F21F965B; Wed, 17 Jul 2013 04:04:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.569
X-Spam-Level: 
X-Spam-Status: No, score=-102.569 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tvq8EJY+wVmo; Wed, 17 Jul 2013 04:04:23 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id A06A221F8A53; Wed, 17 Jul 2013 04:04:23 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id EEB6D20141; Wed, 17 Jul 2013 07:04:17 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O43Qn8HRDtF0; Wed, 17 Jul 2013 07:04:17 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (c-98-216-0-82.hsd1.ma.comcast.net [98.216.0.82]) (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, 17 Jul 2013 07:04:17 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 7B45981758; Wed, 17 Jul 2013 07:04:20 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Internationalization and draft-ietf-abfab-eapapplicability
References: <BLU169-W3386A689EE5BFC8D2272A093600@phx.gbl> <71FEE03C-7A07-4CF3-BC25-0F22F306DE71@frobbit.se> <51E67375.20802@cs.tcd.ie>
Date: Wed, 17 Jul 2013 07:04:20 -0400
In-Reply-To: <51E67375.20802@cs.tcd.ie> (Stephen Farrell's message of "Wed, 17 Jul 2013 11:35:33 +0100")
Message-ID: <tslhaftv45n.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
Cc: Bernard Aboba <bernard_aboba@hotmail.com>, "draft-ietf-abfab-eapapplicability@tools.ietf.org" <draft-ietf-abfab-eapapplicability@tools.ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@frobbit.se>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Jul 2013 11:04:29 -0000

>>>>> "Stephen" == Stephen Farrell <stephen.farrell@cs.tcd.ie> writes:

    Stephen> Hi Bernard, Patrik,

    Stephen> Thanks for the comment. Checking that out now and will get
    Stephen> back.


Bernard, thanks for the comment.  I expected to feel really frustrated
at how late the comment was sent but after reading your message I agree
it was appropriate to send at this stage (although sooner is always
better).

I think assuming that 4282bis has reached consensus on
internationalization is wildly wishful thinking at this stage.  I
continue to be dubious that the right parties are involved in the
discussion and even if we have consensus in radext expect significant
discussion at ietf last call, appsdir review and IESG review.

However, I absolutely agree that if an application is going to use EAP
it needs to  follow EAP's i18n conventions whatever those may be.  A
rrequirement on anti-causal investigation for current implementation
efforts has never stopped us before.
I also agree the current document does not speak to this.

My recommendation is that we point out the issue.  And say that strings
used within a specific EAP method MUST follow the rules for that method.
If AAA is used, strings used within AAA MUST follow the rules for the
AAA protocol in use.  We can add an informative citation to 4282bis as a
snapshot of current thinking.

I would not support a normative reference to 4282bis.

From stefan.winter@restena.lu  Wed Jul 17 04:41:07 2013
Return-Path: <stefan.winter@restena.lu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1FB821F9E6A for <ietf@ietfa.amsl.com>; Wed, 17 Jul 2013 04:41:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.209
X-Spam-Level: 
X-Spam-Status: No, score=-2.209 tagged_above=-999 required=5 tests=[AWL=0.390,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6N6rvyJZpl3x for <ietf@ietfa.amsl.com>; Wed, 17 Jul 2013 04:41:07 -0700 (PDT)
Received: from smtprelay.restena.lu (smtprelay.restena.lu [IPv6:2001:a18:1::62]) by ietfa.amsl.com (Postfix) with ESMTP id D6B0D21F9C19 for <ietf@ietf.org>; Wed, 17 Jul 2013 04:41:06 -0700 (PDT)
Received: from smtprelay.restena.lu (localhost [127.0.0.1]) by smtprelay.restena.lu (Postfix) with ESMTP id 7B4851058A; Wed, 17 Jul 2013 13:41:05 +0200 (CEST)
Received: from aragorn.restena.lu (aragorn.restena.lu [IPv6:2001:a18:1:8::155]) by smtprelay.restena.lu (Postfix) with ESMTPS id 62B8310584; Wed, 17 Jul 2013 13:41:05 +0200 (CEST)
Message-ID: <51E682CC.8030603@restena.lu>
Date: Wed, 17 Jul 2013 13:41:00 +0200
From: Stefan Winter <stefan.winter@restena.lu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: Internationalization and draft-ietf-abfab-eapapplicability
References: <BLU169-W3386A689EE5BFC8D2272A093600@phx.gbl> <71FEE03C-7A07-4CF3-BC25-0F22F306DE71@frobbit.se> <51E67375.20802@cs.tcd.ie> <tslhaftv45n.fsf@mit.edu>
In-Reply-To: <tslhaftv45n.fsf@mit.edu>
X-Enigmail-Version: 1.5.1
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="----enig2UGVHIMDIGUENTKUUHTLF"
X-Virus-Scanned: ClamAV
Cc: Bernard Aboba <bernard_aboba@hotmail.com>, "draft-ietf-abfab-eapapplicability@tools.ietf.org" <draft-ietf-abfab-eapapplicability@tools.ietf.org>, =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Jul 2013 11:41:07 -0000

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

Hi,

> I think assuming that 4282bis has reached consensus on
> internationalization is wildly wishful thinking at this stage.  I
> continue to be dubious that the right parties are involved in the
> discussion and even if we have consensus in radext expect significant
> discussion at ietf last call, appsdir review and IESG review.

I had the impression we are getting somewhere, but that's just a
personal opinion of course.

> However, I absolutely agree that if an application is going to use EAP
> it needs to  follow EAP's i18n conventions whatever those may be.  A
> rrequirement on anti-causal investigation for current implementation
> efforts has never stopped us before.
> I also agree the current document does not speak to this.
>=20
> My recommendation is that we point out the issue.  And say that strings=

> used within a specific EAP method MUST follow the rules for that method=
=2E
> If AAA is used, strings used within AAA MUST follow the rules for the
> AAA protocol in use.  We can add an informative citation to 4282bis as =
a
> snapshot of current thinking.

Pushing the requirement down to the EAP method won't work IMHO. Take as
example EAP-TTLS in RFC5281. A full-text search for "UTF" in it yields 0
hits; and a look at section 7.3 ("EAP Identity Information") does not
speak of any encodings.

IMHO, not being explicit in the EAP spec itself has brought us to the
i18n problems we are seeing. An EAP supplicant supporting EAP-TTLS can
use latin-1 or foobar as encoding for the EAP identity; he'll send that
bytestream on the wire without the encoding information being known,
meaning a UTF-8 sanitisation isn't possible anywhere further down the
route. The supplicant also doesn't know that the authenticator will wrap
this in RADIUS, so can't be aware of the next-hop's requirement to use
UTF-8.

The poor pass-through authenticator now gets a blob with not valid
UTF-8, and is forced to either violate RFC2865 by putting non-UTF-8 into
a RADIUS User-Name, or by rejecting the entire EAP authentication for a
reason the EAP supplicant can do nothing about because it doesn't know
about it. In the IEEE 802.1X network access case, there's also no
signalling what exactly was the reason for EAP to break; EAPoL is not
very verbose. I don't know about ABFAB; GSSAPI could well have a way to
signal that it choked on encoding - or not.

In the end, all participants in the conversation can claim they did the
"right thing", and yet nothing worked.

> I would not support a normative reference to 4282bis.

That I agree with; 4282bis is about NAIs exclusively. I could well
imagine ABFAB being deployed inside an enterprise where EAP identities
do not follow the NAI provisions; any restrictions on the encoding or
normalization should apply to those deployments nontheless.

Greetings,

Stefan Winter

--=20
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education National=
e et
de la Recherche
6, rue Richard Coudenhove-Kalergi
L-1359 Luxembourg

Tel: +352 424409 1
Fax: +352 422473


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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlHmgtAACgkQ+jm90f8eFWZPIQCfamyGBNIPX1MLF041SpZvOpBQ
5wAAn0T5diE4I96ebZk0CUndKGu0YHHw
=tCaN
-----END PGP SIGNATURE-----

------enig2UGVHIMDIGUENTKUUHTLF--

From stefan.winter@restena.lu  Wed Jul 17 04:53:48 2013
Return-Path: <stefan.winter@restena.lu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87DDF21F9D2C for <ietf@ietfa.amsl.com>; Wed, 17 Jul 2013 04:53:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.224
X-Spam-Level: 
X-Spam-Status: No, score=-2.224 tagged_above=-999 required=5 tests=[AWL=0.375,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vsPdzpdp-X8M for <ietf@ietfa.amsl.com>; Wed, 17 Jul 2013 04:53:48 -0700 (PDT)
Received: from smtprelay.restena.lu (smtprelay.restena.lu [IPv6:2001:a18:1::62]) by ietfa.amsl.com (Postfix) with ESMTP id E8AA321F9A1C for <ietf@ietf.org>; Wed, 17 Jul 2013 04:53:47 -0700 (PDT)
Received: from smtprelay.restena.lu (localhost [127.0.0.1]) by smtprelay.restena.lu (Postfix) with ESMTP id 4A7381058A; Wed, 17 Jul 2013 13:53:47 +0200 (CEST)
Received: from aragorn.restena.lu (aragorn.restena.lu [IPv6:2001:a18:1:8::155]) by smtprelay.restena.lu (Postfix) with ESMTPS id 3993610584; Wed, 17 Jul 2013 13:53:47 +0200 (CEST)
Message-ID: <51E685C7.8090401@restena.lu>
Date: Wed, 17 Jul 2013 13:53:43 +0200
From: Stefan Winter <stefan.winter@restena.lu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: Internationalization and draft-ietf-abfab-eapapplicability
References: <BLU169-W3386A689EE5BFC8D2272A093600@phx.gbl> <71FEE03C-7A07-4CF3-BC25-0F22F306DE71@frobbit.se> <51E67375.20802@cs.tcd.ie> <tslhaftv45n.fsf@mit.edu> <51E682CC.8030603@restena.lu>
In-Reply-To: <51E682CC.8030603@restena.lu>
X-Enigmail-Version: 1.5.1
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="----enig2DEMBHOPRULRGUHSMLEQX"
X-Virus-Scanned: ClamAV
Cc: Bernard Aboba <bernard_aboba@hotmail.com>, "draft-ietf-abfab-eapapplicability@tools.ietf.org" <draft-ietf-abfab-eapapplicability@tools.ietf.org>, =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Jul 2013 11:53:48 -0000

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

Hi,

> Pushing the requirement down to the EAP method won't work IMHO.

Further to this: now that I have EAP-TTLS on screen, its words of wisdom
about EAP type selection show that it won't work quite clearly. And they
are valid beyond EAP-TTLS. Section 7.3 of RFC5281 states:

"Note that at the time the initial EAP-Response/Identity packet is
   sent the EAP method is yet to be negotiated.  If, in addition to EAP-
   TTLS, the client is willing to negotiate use of EAP methods that do
   not support user anonymity, then the client MAY include the name of
   the user in the EAP-Response/Identity to meet the requirements of the
   other candidate EAP methods."

This was written for anonymisation reasons; but it applies to i18n as
well. If EAP-Type A uses encoding X, and EAP-Type B uses encoding Y, in
which encoding should the initial EAP-Response/Identity be sent?

One can only hope that all the EAP types which are configured on the
supplicant share one common encoding that is allowed in all of them, and
that the supplicant chooses wisely. Otherwise the question above can
turn into a "does not compute".

Sure, a half-baked answer is that the real identity is in a tunnel
anyway, and the EAP type is known at that time; but that doesn't cover
all cases. EAP-pwd has no tunnel, and needs to rely on the "outer"
identity being in a format it can process. There are more untunneled EAP
types.

Greetings,

Stefan Winter

--=20
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education National=
e et
de la Recherche
6, rue Richard Coudenhove-Kalergi
L-1359 Luxembourg

Tel: +352 424409 1
Fax: +352 422473


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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlHmhcsACgkQ+jm90f8eFWZjeQCfUGBoF/yH3Y4JPdIKaMSNxgO8
frsAnjlGsc2K3WtH0fiTbluCkRhcP4o6
=2K9t
-----END PGP SIGNATURE-----

------enig2DEMBHOPRULRGUHSMLEQX--

From hartmans@mit.edu  Wed Jul 17 05:18:10 2013
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E28C721F9E33 for <ietf@ietfa.amsl.com>; Wed, 17 Jul 2013 05:18:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.574
X-Spam-Level: 
X-Spam-Status: No, score=-102.574 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cUCQpZUXRZLP for <ietf@ietfa.amsl.com>; Wed, 17 Jul 2013 05:18:04 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 955DC21F997B for <ietf@ietf.org>; Wed, 17 Jul 2013 05:18:04 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 9E70520141; Wed, 17 Jul 2013 08:17:57 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wLONIyg3EDKv; Wed, 17 Jul 2013 08:17:56 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (c-98-216-0-82.hsd1.ma.comcast.net [98.216.0.82]) (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, 17 Jul 2013 08:17:56 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id DDC0E81758; Wed, 17 Jul 2013 08:17:59 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Stefan Winter <stefan.winter@restena.lu>
Subject: Re: Internationalization and draft-ietf-abfab-eapapplicability
References: <BLU169-W3386A689EE5BFC8D2272A093600@phx.gbl> <71FEE03C-7A07-4CF3-BC25-0F22F306DE71@frobbit.se> <51E67375.20802@cs.tcd.ie> <tslhaftv45n.fsf@mit.edu> <51E682CC.8030603@restena.lu>
Date: Wed, 17 Jul 2013 08:17:59 -0400
In-Reply-To: <51E682CC.8030603@restena.lu> (Stefan Winter's message of "Wed, 17 Jul 2013 13:41:00 +0200")
Message-ID: <tsl61w9tm6g.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
Cc: "draft-ietf-abfab-eapapplicability@tools.ietf.org" <draft-ietf-abfab-eapapplicability@tools.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Bernard Aboba <bernard_aboba@hotmail.com>, Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@frobbit.se>, Sam Hartman <hartmans-ietf@mit.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Jul 2013 12:18:11 -0000

>>>>> "Stefan" == Stefan Winter <stefan.winter@restena.lu> writes:

    >> However, I absolutely agree that if an application is going to
    >> use EAP it needs to follow EAP's i18n conventions whatever those
    >> may be.  A rrequirement on anti-causal investigation for current
    >> implementation efforts has never stopped us before.  I also agree
    >> the current document does not speak to this.
    >> 
    >> My recommendation is that we point out the issue.  And say that
    >> strings used within a specific EAP method MUST follow the rules
    >> for that method.  If AAA is used, strings used within AAA MUST
    >> follow the rules for the AAA protocol in use.  We can add an
    >> informative citation to 4282bis as a snapshot of current
    >> thinking.

    Stefan> Pushing the requirement down to the EAP method won't work
    Stefan> IMHO. Take as example EAP-TTLS in RFC5281. A full-text
    Stefan> search for "UTF" in it yields 0 hits; and a look at section
    Stefan> 7.3 ("EAP Identity Information") does not speak of any
    Stefan> encodings.

    Stefan> IMHO, not being explicit in the EAP spec itself has brought
    Stefan> us to the i18n problems we are seeing. 


Nah, you'd just be living in a different hell if you'd been explicit in
the EAP spec.  I know: other parts of the IETF are in that hell.  The
protocols are clear and everything is fine until you realize that the
backend authentication systems you're dealing with are using a totally
different set of rules than the protocols.
That hell sucks too.


Some EAP methods are going to care a lot. They'll care more about
passwords than they will usernames.  Usernames are complex because they
can be carried in AAA, EAP identity and within a method.

However, if someone ever does EAP-Kerberos, it's going to have to
specify its own string rules so it can send valid Kerberos PDUs.
MSCHAPV2 had to be compatible with the NTLM hash.

Only the method is in a position to know what strings to send.
We have an unfortunate situation where some methods don't  specify.  As
you point out TTLS is delightfully ambiguous here.  I can point to
similarly annoying deficiencies in the TTLS spec in other areas.

we can write a guidance document for non-standards-track methods that
are ambiguous giving the best advice we can.  We can give good
requirements in standards-track methods.  TEAP is in last-call now; I'm
fairly sure it gets this reasonably OK, but we should probably check
that.

However, none of the above matters for this document.
We're not tasked with documenting EAP.  We're certainly not tasked with
fixing EAP.  We're tasked with giving applications requirements for
working with EAP.
I'm fairly sure the requirement is that applications need to do whatever
EAP expects, understanding that there could be more clarity about that.
Applications need to follow the requirements of EAP, of the AAA
protocols they use and of the EAP methods they use.
There's probably disagreement about what those requirements are; we
should not allow this document to be blocked on resolving that
disagreement.

From bernard_aboba@hotmail.com  Wed Jul 17 05:33:49 2013
Return-Path: <bernard_aboba@hotmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43D2521F9EA9 for <ietf@ietfa.amsl.com>; Wed, 17 Jul 2013 05:33:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.525
X-Spam-Level: 
X-Spam-Status: No, score=-102.525 tagged_above=-999 required=5 tests=[AWL=0.073, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hpSbfPAlDpWk for <ietf@ietfa.amsl.com>; Wed, 17 Jul 2013 05:33:41 -0700 (PDT)
Received: from blu0-omc3-s15.blu0.hotmail.com (blu0-omc3-s15.blu0.hotmail.com [65.55.116.90]) by ietfa.amsl.com (Postfix) with ESMTP id 4D58F21F9E94 for <ietf@ietf.org>; Wed, 17 Jul 2013 05:33:41 -0700 (PDT)
Received: from BLU169-W90 ([65.55.116.73]) by blu0-omc3-s15.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 17 Jul 2013 05:33:41 -0700
X-TMN: [ExpMt7zUbui6k1U+gn3+VqGjtAeY8kW+]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU169-W90B729C7BAB4BA50C5F53E93610@phx.gbl>
Content-Type: multipart/alternative; boundary="_ab3058e1-1830-49b1-91e2-cc49141e9d83_"
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: Stefan Winter <stefan.winter@restena.lu>
Subject: RE: Internationalization and draft-ietf-abfab-eapapplicability
Date: Wed, 17 Jul 2013 05:33:40 -0700
Importance: Normal
In-Reply-To: <51E63F12.3070302@restena.lu>
References: <BLU169-W3386A689EE5BFC8D2272A093600@phx.gbl>, <51E63F12.3070302@restena.lu>
MIME-Version: 1.0
X-OriginalArrivalTime: 17 Jul 2013 12:33:41.0108 (UTC) FILETIME=[DE6E3B40:01CE82E9]
Cc: "draft-ietf-abfab-eapapplicability@tools.ietf.org" <draft-ietf-abfab-eapapplicability@tools.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Jul 2013 12:33:49 -0000

--_ab3058e1-1830-49b1-91e2-cc49141e9d83_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

> The question is: this document is about an applicability update=2C not a>=
 change of the on-the-wire behaviour of EAP.=20
[BA] That's right -- which is why I see no need for the applicability updat=
e to depend on RFC 4282bis.  It just needs to discuss the applicability asp=
ects.=20
> If we were to try and apply a proper fix to RFC3748 to make Identities UT=
F-8 everywhere
[BA]  We are just talking about core EAP and RADIUS RFCs here.  Internation=
alization of method-specific identities (and passwords) is defined by the E=
AP method specifications=2C so the "Identities UTF-8 everywhere" is a much =
broader topic (and one which I'd argue is not relevant to an ABFAB applicab=
ility statement).=20
> The next best solution then would be to require that only ABFAB-using
> EAP supplicants are required to use UTF-8 (and possibly also require a
> normalisation).=20
[BA] I would agree with a UTF-8 requirement for EAP-Response/Identities.  T=
hat is necessary in practice=2C because RFC 3579 requires that the EAP-Resp=
onse/Identity be copied into the RADIUS User-Name attribute=2C and  RFC 286=
5 Section 5.1 states that:
      The format of the username MAY be one of several forms:=0A=
=0A=
      text      Consisting only of UTF-8 encoded 10646 [7] characters.=0A=
=0A=
      network access identifier=0A=
                A Network Access Identifier as described in RFC 2486=0A=
                [8].=0A=
=0A=
      distinguished name=0A=
                A name in ASN.1 form used in Public Key authentication=0A=
                systems.
Internationalization of method-specific identities and passwords are up to =
the methods=2C so the document can just point this out and say "see applica=
ble RFCs."
Personally=2C I don't think that the ABFAB applicability statement has to m=
andate normalization in NAIs -  that would make it depend on RFC 4282bis=2C=
 and that doesn't seem necessary to me.  Instead=2C it can just make the re=
ader aware of RFC 4282bis and say that uses need to conform to internationa=
lization requirements which are a work in progress.=20





That would indeed solve ABFAB's i18n'ed use of EAP=2C but
> not everybody else's. That's a bit selfish=2C but it would certainly be
> better than nothing.
>=20
> I wonder what the other authors think about nailing down a
> UTF-8/NFC-normalised Identity into the draft.
>=20
> Greetings=2C
>=20
> Stefan Winter
>=20
> > Since RFC 3579 Section 2.1 specifies that the EAP-Response/Identity is
> > copied into the RADIUS User-Name Attribute:=20
> >=20
> >    In order to permit non-EAP aware RADIUS proxies to forward the
> >    Access-Request packet=2C if the NAS initially sends an
> >    EAP-Request/Identity message to the peer=2C the NAS MUST copy the
> >    contents of the Type-Data field of the EAP-Response/Identity receive=
d
> >    from the peer into the User-Name attribute and MUST include the
> >    Type-Data field of the EAP-Response/Identity in the User-Name
> >    attribute in every subsequent Access-Request.
> >=20
> >=20
> > Therefore for use with EAP=2C the User-Name Attribute also inherits a
> > UTF-8 encoding requirement=2C restricting the potential encodings
> > permitted by RFC 2865 Section 5.1 (User-Name Attribute):=20
> >=20
> >       The format of the username MAY be one of several forms:
> >=20
> >       text      Consisting only of UTF-8 encoded 10646 [7] characters.
> >=20
> >       network access identifier
> >                 A Network Access Identifier as described in RFC 2486
> >                 [8].
> >=20
> >       distinguished name
> >                 A name in ASN.1 form used in Public Key authentication
> >                 systems.
> >=20
> >=20
> >=20
> >=20
> >=20
> >=20
> >     =20
> >=20
>=20
>=20
> --=20
> Stefan WINTER
> Ingenieur de Recherche
> Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education National=
e et
> de la Recherche
> 6=2C rue Richard Coudenhove-Kalergi
> L-1359 Luxembourg
>=20
> Tel: +352 424409 1
> Fax: +352 422473
>=20
 		 	   		  =

--_ab3058e1-1830-49b1-91e2-cc49141e9d83_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 12pt=3B
font-family:Calibri
}
--></style></head>
<body class=3D'hmmessage'><div dir=3D'ltr'><div><span style=3D"font-size: 1=
2pt=3B ">&gt=3B The question is: this document is about an applicability up=
date=2C not a</span></div><div>&gt=3B change of the on-the-wire behaviour o=
f EAP.&nbsp=3B</div><div><br></div><div>[BA] That's right -- which is why I=
 see no need for the applicability update to depend on RFC 4282bis. &nbsp=
=3BIt just needs to discuss the applicability aspects.&nbsp=3B</div><div><b=
r></div><div>&gt=3B If we were to try and apply&nbsp=3Ba proper fix to RFC3=
748 to make Identities UTF-8 everywhere</div><div><br></div><div>[BA] &nbsp=
=3BWe are just talking about core EAP and RADIUS RFCs here. &nbsp=3B<span s=
tyle=3D"font-size: 12pt=3B ">Internationalization of method-specific identi=
ties (and passwords) is defined by the EAP method specifications=2C so the =
"Identities UTF-8 everywhere" is a much broader topic (and one which I'd ar=
gue is not relevant to an ABFAB applicability statement).&nbsp=3B</span></d=
iv><div><br></div><div>&gt=3B The next best solution then would be to requi=
re that only ABFAB-using<br>&gt=3B EAP supplicants are required to use UTF-=
8 (and possibly also require a<br>&gt=3B normalisation).&nbsp=3B</div><div>=
<br></div><div>[BA] I would agree with a UTF-8 requirement for EAP-Response=
/Identities. &nbsp=3BThat is necessary in practice=2C because&nbsp=3B<span =
style=3D"font-size: 12pt=3B ">RFC 3579 requires that the EAP-Response/Ident=
ity be copied into the RADIUS User-Name attribute=2C and &nbsp=3BRFC 2865 S=
ection 5.1 states that:</span></div><div><br></div><div><pre style=3D"word-=
wrap: break-word=3B white-space: pre-wrap=3B ">      The format of the user=
name MAY be one of several forms:=0A=
=0A=
      text      Consisting only of UTF-8 encoded 10646 [7] characters.=0A=
=0A=
      network access identifier=0A=
                A Network Access Identifier as described in RFC 2486=0A=
                [8].=0A=
=0A=
      distinguished name=0A=
                A name in ASN.1 form used in Public Key authentication=0A=
                systems.</pre></div><div><br></div><div>Internationalizatio=
n of method-specific identities and passwords are up to the methods=2C so t=
he document can just point this out and say "see applicable RFCs."</div><di=
v><br></div><div>Personally=2C I don't think that the ABFAB applicability s=
tatement has to mandate normalization in NAIs - &nbsp=3Bthat would make it =
depend on RFC 4282bis=2C and that doesn't seem necessary to me. &nbsp=3BIns=
tead=2C it can just make the reader aware of RFC 4282bis and say that uses =
need to conform to internationalization requirements which are a work in pr=
ogress.&nbsp=3B</div><div><br></div><div><br></div><div><br></div><div><br>=
</div><div><br></div><div><br></div><div>That would indeed solve ABFAB's i1=
8n'ed use of EAP=2C but<br>&gt=3B not everybody else's. That's a bit selfis=
h=2C but it would certainly be<br>&gt=3B better than nothing.<br>&gt=3B <br=
>&gt=3B I wonder what the other authors think about nailing down a<br>&gt=
=3B UTF-8/NFC-normalised Identity into the draft.<br>&gt=3B <br>&gt=3B Gree=
tings=2C<br>&gt=3B <br>&gt=3B Stefan Winter<br>&gt=3B <br>&gt=3B &gt=3B Sin=
ce RFC 3579 Section 2.1 specifies that the EAP-Response/Identity is<br>&gt=
=3B &gt=3B copied into the RADIUS User-Name Attribute: <br>&gt=3B &gt=3B <b=
r>&gt=3B &gt=3B    In order to permit non-EAP aware RADIUS proxies to forwa=
rd the<br>&gt=3B &gt=3B    Access-Request packet=2C if the NAS initially se=
nds an<br>&gt=3B &gt=3B    EAP-Request/Identity message to the peer=2C the =
NAS MUST copy the<br>&gt=3B &gt=3B    contents of the Type-Data field of th=
e EAP-Response/Identity received<br>&gt=3B &gt=3B    from the peer into the=
 User-Name attribute and MUST include the<br>&gt=3B &gt=3B    Type-Data fie=
ld of the EAP-Response/Identity in the User-Name<br>&gt=3B &gt=3B    attrib=
ute in every subsequent Access-Request.<br>&gt=3B &gt=3B <br>&gt=3B &gt=3B =
<br>&gt=3B &gt=3B Therefore for use with EAP=2C the User-Name Attribute als=
o inherits a<br>&gt=3B &gt=3B UTF-8 encoding requirement=2C restricting the=
 potential encodings<br>&gt=3B &gt=3B permitted by RFC 2865 Section 5.1 (Us=
er-Name Attribute): <br>&gt=3B &gt=3B <br>&gt=3B &gt=3B       The format of=
 the username MAY be one of several forms:<br>&gt=3B &gt=3B <br>&gt=3B &gt=
=3B       text      Consisting only of UTF-8 encoded 10646 [7] characters.<=
br>&gt=3B &gt=3B <br>&gt=3B &gt=3B       network access identifier<br>&gt=
=3B &gt=3B                 A Network Access Identifier as described in RFC =
2486<br>&gt=3B &gt=3B                 [8].<br>&gt=3B &gt=3B <br>&gt=3B &gt=
=3B       distinguished name<br>&gt=3B &gt=3B                 A name in ASN=
.1 form used in Public Key authentication<br>&gt=3B &gt=3B                 =
systems.<br>&gt=3B &gt=3B <br>&gt=3B &gt=3B <br>&gt=3B &gt=3B <br>&gt=3B &g=
t=3B <br>&gt=3B &gt=3B <br>&gt=3B &gt=3B <br>&gt=3B &gt=3B      <br>&gt=3B =
&gt=3B <br>&gt=3B <br>&gt=3B <br>&gt=3B -- <br>&gt=3B Stefan WINTER<br>&gt=
=3B Ingenieur de Recherche<br>&gt=3B Fondation RESTENA - R=E9seau T=E9l=E9i=
nformatique de l'Education Nationale et<br>&gt=3B de la Recherche<br>&gt=3B=
 6=2C rue Richard Coudenhove-Kalergi<br>&gt=3B L-1359 Luxembourg<br>&gt=3B =
<br>&gt=3B Tel: +352 424409 1<br>&gt=3B Fax: +352 422473<br>&gt=3B <br></di=
v> 		 	   		  </div></body>
</html>=

--_ab3058e1-1830-49b1-91e2-cc49141e9d83_--

From bernard_aboba@hotmail.com  Wed Jul 17 05:48:35 2013
Return-Path: <bernard_aboba@hotmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C45AD21F9F3A for <ietf@ietfa.amsl.com>; Wed, 17 Jul 2013 05:48:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.528
X-Spam-Level: 
X-Spam-Status: No, score=-102.528 tagged_above=-999 required=5 tests=[AWL=0.070, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ok+yNwiP-g6W for <ietf@ietfa.amsl.com>; Wed, 17 Jul 2013 05:48:30 -0700 (PDT)
Received: from blu0-omc3-s20.blu0.hotmail.com (blu0-omc3-s20.blu0.hotmail.com [65.55.116.95]) by ietfa.amsl.com (Postfix) with ESMTP id A9DDC21F9E47 for <ietf@ietf.org>; Wed, 17 Jul 2013 05:48:29 -0700 (PDT)
Received: from BLU169-W30 ([65.55.116.73]) by blu0-omc3-s20.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 17 Jul 2013 05:48:29 -0700
X-TMN: [3/YG+tvsRMR4IgZW9VofKdfVFw1b0Q7G]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU169-W303D6471137BAEDD9FD70693610@phx.gbl>
Content-Type: multipart/alternative; boundary="_49ec5b41-f08e-40b2-be7f-dd8b1aaf8692_"
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: Sam Hartman <hartmans-ietf@mit.edu>, Stefan Winter <stefan.winter@restena.lu>
Subject: RE: Internationalization and draft-ietf-abfab-eapapplicability
Date: Wed, 17 Jul 2013 05:48:29 -0700
Importance: Normal
In-Reply-To: <tsl61w9tm6g.fsf@mit.edu>
References: <BLU169-W3386A689EE5BFC8D2272A093600@phx.gbl>, <71FEE03C-7A07-4CF3-BC25-0F22F306DE71@frobbit.se>, <51E67375.20802@cs.tcd.ie> <tslhaftv45n.fsf@mit.edu>, <51E682CC.8030603@restena.lu>, <tsl61w9tm6g.fsf@mit.edu>
MIME-Version: 1.0
X-OriginalArrivalTime: 17 Jul 2013 12:48:29.0105 (UTC) FILETIME=[EFB7D210:01CE82EB]
Cc: "draft-ietf-abfab-eapapplicability@tools.ietf.org" <draft-ietf-abfab-eapapplicability@tools.ietf.org>, =?iso-8859-1?B?UGF0cmlrIEbkbHRzdHL2bQ==?= <paf@frobbit.se>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Jul 2013 12:48:35 -0000

--_49ec5b41-f08e-40b2-be7f-dd8b1aaf8692_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Sam said:=20
> My recommendation is that we point out the issue.  And say that
> strings used within a specific EAP method MUST follow the rules
> for that method.  If AAA is used=2C strings used within AAA MUST
> follow the rules for the AAA protocol in use.  We can add an
> informative citation to 4282bis as a snapshot of current
> thinking.
[BA] That works for me.=20
>     Stefan> Pushing the requirement down to the EAP method won't work
>     Stefan> IMHO. Take as example EAP-TTLS in RFC5281. A full-text
>     Stefan> search for "UTF" in it yields 0 hits=3B and a look at section
>     Stefan> 7.3 ("EAP Identity Information") does not speak of any
>     Stefan> encodings.
[BA] You are right that a number of method specifications are deficient in =
the internationalization area.  However=2C I don't think that's an issue th=
at an ABFAB applicability statement can solve.   Sam's proposed approach se=
ems like the only feasible one.=20
Sam said:  > Nah=2C you'd just be living in a different hell if you'd been =
explicit in
> the EAP spec.  I know: other parts of the IETF are in that hell.  The
> protocols are clear and everything is fine until you realize that the
> backend authentication systems you're dealing with are using a totally
> different set of rules than the protocols.
> That hell sucks too.
[BA] I totally agree.=20
> Some EAP methods are going to care a lot. They'll care more about
> passwords than they will usernames.  Usernames are complex because they
> can be carried in AAA=2C EAP identity and within a method.

[BA] Yes=2C but at least the method-specific identities and passwords are o=
paque to the EAP core implementation and the AAA protocol.=20
> we can write a guidance document for non-standards-track methods that> ar=
e ambiguous giving the best advice we can.  We can give good
> requirements in standards-track methods.  TEAP is in last-call now=3B I'm
> fairly sure it gets this reasonably OK=2C but we should probably check
> that.>> However=2C none of the above matters for this document.
[BA] Exactly.  It's just an applicability statement=2C not a prescription f=
or world peace :)

 		 	   		  =

--_49ec5b41-f08e-40b2-be7f-dd8b1aaf8692_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 12pt=3B
font-family:Calibri
}
--></style></head>
<body class=3D'hmmessage'><div dir=3D'ltr'><div>Sam said:&nbsp=3B</div><div=
><br>&gt=3B My recommendation is that we point out the issue.  And say that=
<br>&gt=3B strings used within a specific EAP method MUST follow the rules<=
br>&gt=3B for that method.  If AAA is used=2C strings used within AAA MUST<=
br>&gt=3B follow the rules for the AAA protocol in use.  We can add an<br>&=
gt=3B informative citation to 4282bis as a snapshot of current<br>&gt=3B th=
inking.</div><div><br></div><div>[BA] That works for me.&nbsp=3B</div><div>=
<br></div><div>&gt=3B     Stefan&gt=3B Pushing the requirement down to the =
EAP method won't work<br>&gt=3B     Stefan&gt=3B IMHO. Take as example EAP-=
TTLS in RFC5281. A full-text<br>&gt=3B     Stefan&gt=3B search for "UTF" in=
 it yields 0 hits=3B and a look at section<br>&gt=3B     Stefan&gt=3B 7.3 (=
"EAP Identity Information") does not speak of any<br>&gt=3B     Stefan&gt=
=3B encodings.</div><div><br></div><div>[BA] You are right that a number of=
 method specifications are deficient in the internationalization area. &nbs=
p=3B</div><div>However=2C I don't think that's an issue that an ABFAB appli=
cability statement can solve. &nbsp=3B&nbsp=3B</div><div>Sam's proposed app=
roach seems like the only feasible one.&nbsp=3B</div><div><br></div><div><s=
pan style=3D"font-size: 12pt=3B ">Sam said:&nbsp=3B</span></div><div><span =
style=3D"font-size: 12pt=3B ">&nbsp=3B</span></div><div>&gt=3B Nah=2C you'd=
 just be living in a different hell if you'd been explicit in<br>&gt=3B the=
 EAP spec.  I know: other parts of the IETF are in that hell.  The<br>&gt=
=3B protocols are clear and everything is fine until you realize that the<b=
r>&gt=3B backend authentication systems you're dealing with are using a tot=
ally<br>&gt=3B different set of rules than the protocols.<br>&gt=3B That he=
ll sucks too.</div><div><br></div><div>[BA] I totally agree.&nbsp=3B</div><=
div><br></div><div>&gt=3B Some EAP methods are going to care a lot. They'll=
 care more about<br>&gt=3B passwords than they will usernames.  Usernames a=
re complex because they<br>&gt=3B can be carried in AAA=2C EAP identity and=
 within a method.<br><br></div><div>[BA] Yes=2C but at least the method-spe=
cific identities and passwords are opaque to the EAP core implementation an=
d the AAA protocol.&nbsp=3B</div><div><br></div><div><span style=3D"font-si=
ze: 12pt=3B ">&gt=3B we can write a guidance document for non-standards-tra=
ck methods that</span></div><div>&gt=3B are ambiguous giving the best advic=
e we can.  We can give good<br>&gt=3B requirements in standards-track metho=
ds.  TEAP is in last-call now=3B I'm<br>&gt=3B fairly sure it gets this rea=
sonably OK=2C but we should probably check<br>&gt=3B that.</div><div>&gt=3B=
</div><div>&gt=3B However=2C none of the above matters for this document.</=
div><div><br></div><div>[BA] Exactly. &nbsp=3BIt's just an applicability st=
atement=2C not a prescription for world peace :)</div><div><br></div><div><=
br></div> 		 	   		  </div></body>
</html>=

--_49ec5b41-f08e-40b2-be7f-dd8b1aaf8692_--

From stefan.winter@restena.lu  Wed Jul 17 06:16:48 2013
Return-Path: <stefan.winter@restena.lu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D578D21F9B19 for <ietf@ietfa.amsl.com>; Wed, 17 Jul 2013 06:16:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.238
X-Spam-Level: 
X-Spam-Status: No, score=-2.238 tagged_above=-999 required=5 tests=[AWL=0.361,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vybuaUmKM72p for <ietf@ietfa.amsl.com>; Wed, 17 Jul 2013 06:16:48 -0700 (PDT)
Received: from smtprelay.restena.lu (smtprelay.restena.lu [IPv6:2001:a18:1::62]) by ietfa.amsl.com (Postfix) with ESMTP id 4AF3021F9AE9 for <ietf@ietf.org>; Wed, 17 Jul 2013 06:16:47 -0700 (PDT)
Received: from smtprelay.restena.lu (localhost [127.0.0.1]) by smtprelay.restena.lu (Postfix) with ESMTP id BD3811058A; Wed, 17 Jul 2013 15:16:46 +0200 (CEST)
Received: from aragorn.restena.lu (aragorn.restena.lu [IPv6:2001:a18:1:8::155]) by smtprelay.restena.lu (Postfix) with ESMTPS id 9B9F810584; Wed, 17 Jul 2013 15:16:46 +0200 (CEST)
Message-ID: <51E6993A.7010600@restena.lu>
Date: Wed, 17 Jul 2013 15:16:42 +0200
From: Stefan Winter <stefan.winter@restena.lu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
Subject: Re: Internationalization and draft-ietf-abfab-eapapplicability
References: <BLU169-W3386A689EE5BFC8D2272A093600@phx.gbl>, <71FEE03C-7A07-4CF3-BC25-0F22F306DE71@frobbit.se>, <51E67375.20802@cs.tcd.ie> <tslhaftv45n.fsf@mit.edu>, <51E682CC.8030603@restena.lu>, <tsl61w9tm6g.fsf@mit.edu> <BLU169-W303D6471137BAEDD9FD70693610@phx.gbl>
In-Reply-To: <BLU169-W303D6471137BAEDD9FD70693610@phx.gbl>
X-Enigmail-Version: 1.5.1
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="----enig2HOMPIMSBFBHKDRMGABXB"
X-Virus-Scanned: ClamAV
Cc: "draft-ietf-abfab-eapapplicability@tools.ietf.org" <draft-ietf-abfab-eapapplicability@tools.ietf.org>, =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>, Sam Hartman <hartmans-ietf@mit.edu>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Jul 2013 13:16:49 -0000

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

Hi,

> Sam said:=20
> =20
>> Nah, you'd just be living in a different hell if you'd been explicit i=
n
>> the EAP spec. I know: other parts of the IETF are in that hell. The
>> protocols are clear and everything is fine until you realize that the
>> backend authentication systems you're dealing with are using a totally=

>> different set of rules than the protocols.
>> That hell sucks too.
>=20
> [BA] I totally agree.=20

I'm joyfully na=EFve here.

Right now, the receiving end has no guarantees about the encoding and
normalisation of the incoming string. If it doesn't match its
expectations in that regard, then that's unrecoverable.

In the other hell, it can be sure to receive UTF-8 in NFC, and if that
doesn't match what it needs, it can convert it.

In my na=EFve thinking, that second hell is a lot less hot and much more
habitable.

Could you point out where my thinking goes wrong?

Also: we're dealing with writing specifications here. If our
specifications are correct, and some implementations do it wrong anyway
- that's their problem, right?


>> However, none of the above matters for this document.
>=20
> [BA] Exactly.  It's just an applicability statement, not a prescription=

> for world peace :)

Sure: we need more than an applicability statement update to achieve
peace in the EAP world. But if an applicability statement update is all
we can work with, we could try and do our best in that one.

Greetings,

Stefan Winter



--=20
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education National=
e et
de la Recherche
6, rue Richard Coudenhove-Kalergi
L-1359 Luxembourg

Tel: +352 424409 1
Fax: +352 422473


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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlHmmT4ACgkQ+jm90f8eFWZLUQCcDzTEyQQvv6GT2RGXLxH4lZij
anEAnA9RAu1IpSlstI+VxxsnjPnysgBB
=rPNS
-----END PGP SIGNATURE-----

------enig2HOMPIMSBFBHKDRMGABXB--

From stefan.winter@restena.lu  Wed Jul 17 06:31:02 2013
Return-Path: <stefan.winter@restena.lu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B0DB21F9EA7 for <ietf@ietfa.amsl.com>; Wed, 17 Jul 2013 06:31:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.251
X-Spam-Level: 
X-Spam-Status: No, score=-2.251 tagged_above=-999 required=5 tests=[AWL=0.348,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DBDv--ADXW6e for <ietf@ietfa.amsl.com>; Wed, 17 Jul 2013 06:31:01 -0700 (PDT)
Received: from smtprelay.restena.lu (smtprelay.restena.lu [IPv6:2001:a18:1::62]) by ietfa.amsl.com (Postfix) with ESMTP id 5AB7821F9E33 for <ietf@ietf.org>; Wed, 17 Jul 2013 06:31:01 -0700 (PDT)
Received: from smtprelay.restena.lu (localhost [127.0.0.1]) by smtprelay.restena.lu (Postfix) with ESMTP id 7DAE81058A; Wed, 17 Jul 2013 15:31:00 +0200 (CEST)
Received: from aragorn.restena.lu (aragorn.restena.lu [IPv6:2001:a18:1:8::155]) by smtprelay.restena.lu (Postfix) with ESMTPS id 6837810583; Wed, 17 Jul 2013 15:31:00 +0200 (CEST)
Message-ID: <51E69C8F.805@restena.lu>
Date: Wed, 17 Jul 2013 15:30:55 +0200
From: Stefan Winter <stefan.winter@restena.lu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
Subject: Re: Internationalization and draft-ietf-abfab-eapapplicability
References: <BLU169-W3386A689EE5BFC8D2272A093600@phx.gbl>, <51E63F12.3070302@restena.lu> <BLU169-W90B729C7BAB4BA50C5F53E93610@phx.gbl>
In-Reply-To: <BLU169-W90B729C7BAB4BA50C5F53E93610@phx.gbl>
X-Enigmail-Version: 1.5.1
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="----enig2QQXBFVBDDADQAERSJBIJ"
X-Virus-Scanned: ClamAV
Cc: "draft-ietf-abfab-eapapplicability@tools.ietf.org" <draft-ietf-abfab-eapapplicability@tools.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Jul 2013 13:31:02 -0000

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

Hi,

> [BA]  We are just talking about core EAP and RADIUS RFCs here.
>  Internationalization of method-specific identities (and passwords) is
> defined by the EAP method specifications, so the "Identities UTF-8
> everywhere" is a much broader topic (and one which I'd argue is not
> relevant to an ABFAB applicability statement).=20

Indeed; sorry for the imprecise use of "everywhere". What needs to be
tackled is EAP's "outer" or "only" identity (for methods that don't have
the luxury of sending a different identity in their method-specific
payload).

>> The next best solution then would be to require that only ABFAB-using
>> EAP supplicants are required to use UTF-8 (and possibly also require a=

>> normalisation).=20
>=20
> [BA] I would agree with a UTF-8 requirement for EAP-Response/Identities=
=2E
>  That is necessary in practice, because RFC 3579 requires that the
> EAP-Response/Identity be copied into the RADIUS User-Name attribute, an=
d
>  RFC 2865 Section 5.1 states that:

You are conflating AAA with RADIUS. EAP-Response/Identity can be used in
other contexts; I heard that some use Diameter instead of RADIUS, so any
reference to RFC2865 would not apply there. And if I write
MyOwnAAAProtocol and require EAP Identities in EBCDIC encoding in my
equivalent of User-Name, then that's my thing alone and RFC2865 has
nothing to say to me.

The EAP supplicant doesn't know which AAA is going to be used behind the
authenticator; so how would it know whether to use EBCDIC or UTF-8?

Unless, of course, there is a place outside of RFC2865 which forces me
to accept/use exclusively UTF-8. An update to RFC3748 stating that comes
to mind.

> Internationalization of method-specific identities and passwords are up=

> to the methods, so the document can just point this out and say "see
> applicable RFCs."

As stated elsewhere in the thread, the initial EAP-Identity needs to be
sent before the EAP method is negotiated.

> Personally, I don't think that the ABFAB applicability statement has to=

> mandate normalization in NAIs -  that would make it depend on RFC
> 4282bis, and that doesn't seem necessary to me.  Instead, it can just
> make the reader aware of RFC 4282bis and say that uses need to conform
> to internationalization requirements which are a work in progress.=20

This is a cliffhanger text with a forward-reference into the future. I
could live with a statement like that, but ...

=2E.. just listing 4282bis is not enough; EAP identities don't have to be=

NAIs - if we state that applications need to conform to that future RFC,
and they read things in it like "This document only defines NAIs, if you
don't use NAIs, there's nothing in it for you" - then implementations
have a way too easy loophole to not care about i18n; they can just say:
oh, we don't use NAIs. It's all unstructured identities; any presence of
an @ in there is just coincidence.

I could live with it very well if there is a promise to continue the
cliffhanger situation with an all-encompassing update that covers all
EAP Identities; be they NAIs or not and be they transported over RADIUS
or not.

I.e. if we can agree that updating RFC3748 with stricter i18n rules is
going to be chartered work and will happen, then I can live with a
cliffhanger statement of "stay tuned for that update" in the
eapapplicability draft.

Greetings,

Stefan Winter

>=20
>=20
>=20
>=20
>=20
> That would indeed solve ABFAB's i18n'ed use of EAP, but
>> not everybody else's. That's a bit selfish, but it would certainly be
>> better than nothing.
>>
>> I wonder what the other authors think about nailing down a
>> UTF-8/NFC-normalised Identity into the draft.
>>
>> Greetings,
>>
>> Stefan Winter
>>
>> > Since RFC 3579 Section 2.1 specifies that the EAP-Response/Identity =
is
>> > copied into the RADIUS User-Name Attribute:
>> >
>> > In order to permit non-EAP aware RADIUS proxies to forward the
>> > Access-Request packet, if the NAS initially sends an
>> > EAP-Request/Identity message to the peer, the NAS MUST copy the
>> > contents of the Type-Data field of the EAP-Response/Identity receive=
d
>> > from the peer into the User-Name attribute and MUST include the
>> > Type-Data field of the EAP-Response/Identity in the User-Name
>> > attribute in every subsequent Access-Request.
>> >
>> >
>> > Therefore for use with EAP, the User-Name Attribute also inherits a
>> > UTF-8 encoding requirement, restricting the potential encodings
>> > permitted by RFC 2865 Section 5.1 (User-Name Attribute):
>> >
>> > The format of the username MAY be one of several forms:
>> >
>> > text Consisting only of UTF-8 encoded 10646 [7] characters.
>> >
>> > network access identifier
>> > A Network Access Identifier as described in RFC 2486
>> > [8].
>> >
>> > distinguished name
>> > A name in ASN.1 form used in Public Key authentication
>> > systems.
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>>
>>
>> --
>> Stefan WINTER
>> Ingenieur de Recherche
>> Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education Natio=
nale et
>> de la Recherche
>> 6, rue Richard Coudenhove-Kalergi
>> L-1359 Luxembourg
>>
>> Tel: +352 424409 1
>> Fax: +352 422473
>>


--=20
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education National=
e et
de la Recherche
6, rue Richard Coudenhove-Kalergi
L-1359 Luxembourg

Tel: +352 424409 1
Fax: +352 422473


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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlHmnJQACgkQ+jm90f8eFWbqGwCfR/G4+mCdPKgtXwuim7eWYeEv
ZcQAniEnr/uNUFsKDvJ9Rz5cDwOM8lgn
=feL9
-----END PGP SIGNATURE-----

------enig2QQXBFVBDDADQAERSJBIJ--

From bernard_aboba@hotmail.com  Wed Jul 17 06:38:35 2013
Return-Path: <bernard_aboba@hotmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C765C21F9E47 for <ietf@ietfa.amsl.com>; Wed, 17 Jul 2013 06:38:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.531
X-Spam-Level: 
X-Spam-Status: No, score=-102.531 tagged_above=-999 required=5 tests=[AWL=0.067, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vwmAHdfCrfWx for <ietf@ietfa.amsl.com>; Wed, 17 Jul 2013 06:38:25 -0700 (PDT)
Received: from blu0-omc3-s17.blu0.hotmail.com (blu0-omc3-s17.blu0.hotmail.com [65.55.116.92]) by ietfa.amsl.com (Postfix) with ESMTP id C547821F9034 for <ietf@ietf.org>; Wed, 17 Jul 2013 06:38:25 -0700 (PDT)
Received: from BLU169-W53 ([65.55.116.74]) by blu0-omc3-s17.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 17 Jul 2013 06:38:25 -0700
X-TMN: [p5XXDjSqguZeMB2q6gvjp4TOTEBgvrg1]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU169-W534988EF80D6E7BFAC3FC193610@phx.gbl>
Content-Type: multipart/alternative; boundary="_35a9f045-56b3-47b0-b4ef-65c81e4664b5_"
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: Stefan Winter <stefan.winter@restena.lu>
Subject: RE: Internationalization and draft-ietf-abfab-eapapplicability
Date: Wed, 17 Jul 2013 06:38:24 -0700
Importance: Normal
In-Reply-To: <51E6993A.7010600@restena.lu>
References: <BLU169-W3386A689EE5BFC8D2272A093600@phx.gbl>, <71FEE03C-7A07-4CF3-BC25-0F22F306DE71@frobbit.se>, <51E67375.20802@cs.tcd.ie> <tslhaftv45n.fsf@mit.edu>, <51E682CC.8030603@restena.lu>, <tsl61w9tm6g.fsf@mit.edu> <BLU169-W303D6471137BAEDD9FD70693610@phx.gbl>, <51E6993A.7010600@restena.lu>
MIME-Version: 1.0
X-OriginalArrivalTime: 17 Jul 2013 13:38:25.0809 (UTC) FILETIME=[E9E49010:01CE82F2]
Cc: "draft-ietf-abfab-eapapplicability@tools.ietf.org" <draft-ietf-abfab-eapapplicability@tools.ietf.org>, =?iso-8859-1?B?UGF0cmlrIEbkbHRzdHL2bQ==?= <paf@frobbit.se>, Sam Hartman <hartmans-ietf@mit.edu>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Jul 2013 13:38:35 -0000

--_35a9f045-56b3-47b0-b4ef-65c81e4664b5_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

> > [BA] Exactly.  It's just an applicability statement=2C not a prescripti=
on
> > for world peace :)
>=20
> Sure: we need more than an applicability statement update to achieve
> peace in the EAP world. But if an applicability statement update is all
> we can work with=2C we could try and do our best in that one.

[BA] The goal of an applicability statement to provide guidance as to the a=
pplicability of a particular standard.=20
Using a marine analogy=2C it can say "it is ok to take a boat of this size =
out into the ocean"=2C but it doesn't have to provide a detailed map of eve=
ry harbor.=20
So it seems like there is a need to address application-layer protocols tha=
t don't encode their identities in UTF-8 over the wire today.  Is EAP appli=
cable to these protocols?  If so=2C is there something they need to be awar=
e of?  Going beyond that is probably for other documents=2C not this one.  =
		 	   		  =

--_35a9f045-56b3-47b0-b4ef-65c81e4664b5_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 12pt=3B
font-family:Calibri
}
--></style></head>
<body class=3D'hmmessage'><div dir=3D'ltr'><div>&gt=3B &gt=3B [BA] Exactly.=
  It's just an applicability statement=2C not a prescription<br>&gt=3B &gt=
=3B for world peace :)<br>&gt=3B <br>&gt=3B Sure: we need more than an appl=
icability statement update to achieve<br>&gt=3B peace in the EAP world. But=
 if an applicability statement update is all<br>&gt=3B we can work with=2C =
we could try and do our best in that one.<br><br></div><div>[BA] The goal o=
f an applicability statement to provide guidance as to the applicability of=
 a particular standard.&nbsp=3B</div><div><br></div><div>Using a marine ana=
logy=2C it can say "it is ok to take a boat of this size out into the ocean=
"=2C but it doesn't have to provide a detailed map of every harbor.&nbsp=3B=
</div><div><br></div><div>So it seems like there is a need to address appli=
cation-layer protocols that don't encode their identities in UTF-8 over the=
 wire today. &nbsp=3BIs EAP applicable to these protocols? &nbsp=3BIf so=2C=
 is there something they need to be aware of? &nbsp=3BGoing beyond that is =
probably for other documents=2C not this one.&nbsp=3B</div> 		 	   		  </di=
v></body>
</html>=

--_35a9f045-56b3-47b0-b4ef-65c81e4664b5_--

From hartmans@mit.edu  Wed Jul 17 07:32:01 2013
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D22421F9D1C for <ietf@ietfa.amsl.com>; Wed, 17 Jul 2013 07:32:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IIXDRnNPd+DK for <ietf@ietfa.amsl.com>; Wed, 17 Jul 2013 07:31:56 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 349EC21F9FCA for <ietf@ietf.org>; Wed, 17 Jul 2013 07:31:55 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 056F020141; Wed, 17 Jul 2013 10:31:50 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aYNbqm671ote; Wed, 17 Jul 2013 10:31:49 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (unknown [10.1.10.116]) (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, 17 Jul 2013 10:31:49 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id F410E81758; Wed, 17 Jul 2013 10:31:53 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Stefan Winter <stefan.winter@restena.lu>
Subject: Re: Internationalization and draft-ietf-abfab-eapapplicability
References: <BLU169-W3386A689EE5BFC8D2272A093600@phx.gbl> <71FEE03C-7A07-4CF3-BC25-0F22F306DE71@frobbit.se> <51E67375.20802@cs.tcd.ie> <tslhaftv45n.fsf@mit.edu> <51E682CC.8030603@restena.lu> <tsl61w9tm6g.fsf@mit.edu> <BLU169-W303D6471137BAEDD9FD70693610@phx.gbl> <51E6993A.7010600@restena.lu>
Date: Wed, 17 Jul 2013 10:31:53 -0400
In-Reply-To: <51E6993A.7010600@restena.lu> (Stefan Winter's message of "Wed, 17 Jul 2013 15:16:42 +0200")
Message-ID: <tsl38rds1eu.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=iso-8859-1
Content-Transfer-Encoding: 8bit
Cc: Bernard Aboba <bernard_aboba@hotmail.com>, "draft-ietf-abfab-eapapplicability@tools.ietf.org" <draft-ietf-abfab-eapapplicability@tools.ietf.org>, Sam Hartman <hartmans-ietf@mit.edu>, "ietf@ietf.org" <ietf@ietf.org>, Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@frobbit.se>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Jul 2013 14:32:01 -0000

>>>>> "Stefan" == Stefan Winter <stefan.winter@restena.lu> writes:

    Stefan> In the other hell, it can be sure to receive UTF-8 in NFC,
    Stefan> and if that doesn't match what it needs, it can convert it.

    Stefan> In my na飗e thinking, that second hell is a lot less hot
    Stefan> and much more habitable.


This discussion has also moved to the abfab list.
I'm responding there because ultimately we'll need WG consensus for any
change.

however there's one point I'll respond in my last message on this
thread..

you have: a UTF-8 NFC hashed password response to your password
challenge.

You want: the same input to the hash except the input should be UTF-16
encoded with the normalization implicit in the Windows input method.

Or
you have: a UTF-8 NFC encoded username

you want: whatever PAM wants.  Your PAM stack is complex and may involve
network protocols with their own encodings.

The second example is intended to illustrate why OS folks like Nico
Williams tend to favor normalizing usernames as late as possible.  In
this case the original client and PAM probably have more information
about what is required than the goo in the middle, and you can win in
cases where you preserve the form the user gave their system but not in
other cases.
Full interop in this second case is probably impossible.

From hartmans@mit.edu  Wed Jul 17 07:44:42 2013
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B93921F9D2C for <ietf@ietfa.amsl.com>; Wed, 17 Jul 2013 07:44:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OA3qw2Tnmnez for <ietf@ietfa.amsl.com>; Wed, 17 Jul 2013 07:44:36 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 4EB7121F9294 for <ietf@ietf.org>; Wed, 17 Jul 2013 07:44:35 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 7767220141; Wed, 17 Jul 2013 10:44:29 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xcrk0kVnnkKi; Wed, 17 Jul 2013 10:44:29 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (unknown [10.1.10.116]) (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, 17 Jul 2013 10:44:29 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id BD1BA81758; Wed, 17 Jul 2013 10:44:33 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Sam Hartman <hartmans-ietf@MIT.EDU>
Subject: Re: Internationalization and draft-ietf-abfab-eapapplicability
References: <BLU169-W3386A689EE5BFC8D2272A093600@phx.gbl> <71FEE03C-7A07-4CF3-BC25-0F22F306DE71@frobbit.se> <51E67375.20802@cs.tcd.ie> <tslhaftv45n.fsf@mit.edu> <51E682CC.8030603@restena.lu> <tsl61w9tm6g.fsf@mit.edu> <BLU169-W303D6471137BAEDD9FD70693610@phx.gbl> <51E6993A.7010600@restena.lu> <tsl38rds1eu.fsf@mit.edu>
Date: Wed, 17 Jul 2013 10:44:33 -0400
In-Reply-To: <tsl38rds1eu.fsf@mit.edu> (Sam Hartman's message of "Wed, 17 Jul 2013 10:31:53 -0400")
Message-ID: <tsl8v15qm9a.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
Cc: Bernard Aboba <bernard_aboba@hotmail.com>, Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@frobbit.se>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-abfab-eapapplicability@tools.ietf.org" <draft-ietf-abfab-eapapplicability@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Jul 2013 14:44:42 -0000

Also, note that the important thing is not that applications use UTF-8
for usernames.
It's that they know what character set they are using  and follow EAP's
(lack of) rules when using EAP.

In general, I would not expect an application to encode a username
that's also used in EAP authentication as part of the authentication.

The same username may be encoded in the app protocol in response to
whoami style oppcodes or in response to ACL operations.
But the situation is somewhat complicated by things like SASL
authorization identities and other forms of proxy authorization.

We don't get to place requirements on applications except to say what
they need to do to use EAP.  The protocol requirement for that is that
applications using EAP need to know what character set they have so that
EAP can convert the identity to UTF-8 and so that EAP methods can do any
needed conversions.

From bernard_aboba@hotmail.com  Wed Jul 17 07:56:51 2013
Return-Path: <bernard_aboba@hotmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D02A21E804B for <ietf@ietfa.amsl.com>; Wed, 17 Jul 2013 07:56:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.534
X-Spam-Level: 
X-Spam-Status: No, score=-102.534 tagged_above=-999 required=5 tests=[AWL=0.064, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aqIJsswnNNW9 for <ietf@ietfa.amsl.com>; Wed, 17 Jul 2013 07:56:45 -0700 (PDT)
Received: from blu0-omc3-s19.blu0.hotmail.com (blu0-omc3-s19.blu0.hotmail.com [65.55.116.94]) by ietfa.amsl.com (Postfix) with ESMTP id CF9C711E80CC for <ietf@ietf.org>; Wed, 17 Jul 2013 07:56:42 -0700 (PDT)
Received: from BLU169-W111 ([65.55.116.74]) by blu0-omc3-s19.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 17 Jul 2013 07:56:42 -0700
X-TMN: [p13KLI/pPuf3/K+LlnL4w8qcjOzaM1HM]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU169-W1110E775721ABEC5C3E4F1393610@phx.gbl>
Content-Type: multipart/alternative; boundary="_e7836ec1-728d-4ec2-a927-66a78bf602b5_"
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: Sam Hartman <hartmans-ietf@mit.edu>
Subject: RE: Internationalization and draft-ietf-abfab-eapapplicability
Date: Wed, 17 Jul 2013 07:56:42 -0700
Importance: Normal
In-Reply-To: <tsl8v15qm9a.fsf@mit.edu>
References: <BLU169-W3386A689EE5BFC8D2272A093600@phx.gbl>, <71FEE03C-7A07-4CF3-BC25-0F22F306DE71@frobbit.se>, <51E67375.20802@cs.tcd.ie> <tslhaftv45n.fsf@mit.edu>,<51E682CC.8030603@restena.lu> <tsl61w9tm6g.fsf@mit.edu>, <BLU169-W303D6471137BAEDD9FD70693610@phx.gbl>, <51E6993A.7010600@restena.lu> <tsl38rds1eu.fsf@mit.edu>,<tsl8v15qm9a.fsf@mit.edu>
MIME-Version: 1.0
X-OriginalArrivalTime: 17 Jul 2013 14:56:42.0964 (UTC) FILETIME=[D99D8940:01CE82FD]
Cc: "draft-ietf-abfab-eapapplicability@tools.ietf.org" <draft-ietf-abfab-eapapplicability@tools.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, =?iso-8859-1?B?UGF0cmlrIEbkbHRzdHL2bQ==?= <paf@frobbit.se>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Jul 2013 14:56:51 -0000

--_e7836ec1-728d-4ec2-a927-66a78bf602b5_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Sam said:=20
> We don't get to place requirements on applications except to say what
> they need to do to use EAP.  The protocol requirement for that is that
> applications using EAP need to know what character set they have so that
> EAP can convert the identity to UTF-8 and so that EAP methods can do any
> needed conversions.
=20
[BA] That sounds right.=20

 		 	   		  =

--_e7836ec1-728d-4ec2-a927-66a78bf602b5_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 12pt=3B
font-family:Calibri
}
--></style></head>
<body class=3D'hmmessage'><div dir=3D'ltr'>Sam said: <br>&gt=3B We don't ge=
t to place requirements on applications except to say what<br>&gt=3B they n=
eed to do to use EAP.  The protocol requirement for that is that<br>&gt=3B =
applications using EAP need to know what character set they have so that<br=
>&gt=3B EAP can convert the identity to UTF-8 and so that EAP methods can d=
o any<br>&gt=3B needed conversions.<BR>&nbsp=3B<BR>[BA] That sounds right. =
<br><BR> 		 	   		  </div></body>
</html>=

--_e7836ec1-728d-4ec2-a927-66a78bf602b5_--

From iab-chair@iab.org  Wed Jul 17 08:11:26 2013
Return-Path: <iab-chair@iab.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FA3721E8087; Wed, 17 Jul 2013 08:11:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.321
X-Spam-Level: 
X-Spam-Status: No, score=-102.321 tagged_above=-999 required=5 tests=[AWL=0.278, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uiSV260a1WgO; Wed, 17 Jul 2013 08:11:25 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:15]) by ietfa.amsl.com (Postfix) with ESMTP id 52B7221E8086; Wed, 17 Jul 2013 08:11:25 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id 7A14DA8A1C; Wed, 17 Jul 2013 08:10:42 -0700 (PDT)
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 JT5949twica8; Wed, 17 Jul 2013 08:10:42 -0700 (PDT)
Received: from [192.168.2.109] (pool-96-241-212-98.washdc.fios.verizon.net [96.241.212.98]) by c9a.amsl.com (Postfix) with ESMTPSA id CE5EAA8A1A; Wed, 17 Jul 2013 08:10:41 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Subject: IAB Response to the Appeal Regarding RFC 6852 by JFC Morfin
Mime-Version: 1.0 (Apple Message framework v1085)
From: IAB Chair <iab-chair@iab.org>
Date: Wed, 17 Jul 2013 11:11:23 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <2BAB5B56-5F1F-4AC1-9A16-C78115D94F02@iab.org>
To: JFC Morfin <jefsey@jefsey.com>
X-Mailer: Apple Mail (2.1085)
Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>, IETF Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: IETF <ietf@ietf.org>, 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, 17 Jul 2013 15:11:26 -0000

The appeal from Mr. Morfin was received on 8 July 2013; it can be found =
here:
=
http://www.iab.org/wp-content/IAB-uploads/2013/07/appeal-morfin-2013-07-08=
.pdf.

Mr. Morfin's appeal concerns RFC 6852.  While the appeal does not state
any objection to any of the content of RFC 6852, Mr. Morfin wishes that
RFC 6852 included additional principles and a global framework.  In
addition, Mr. Morfin calls for a way for additional organizations to
"sign on" to the expanded principle list and the desired global
framework.

RFC 6852 contains five principles that are strongly supported by five
organizations.  The principles were the result of significant
coordination among these organizations.

Mr. Morfin's preferred remedy has two points.

First, Mr. Morfin calls for publication of a statement or RFC that
expands on RFC 6852, preferably in conjunction with other organizations
and governments.  Mr. Morfin believes that there are currently two
models for the evolution of the Internet.  One is based on the World
Summit on the Information Society (WSIS), and the other is based on the
principles in RFC 6852.  Mr. Morfin would like to see these two merged.

Second, Mr. Morfin calls for the creation of an inter-SDO procedure to
maintain the RFC 6852 principles and allow civil society, governments,
and international organizations to "sign on" to these principles.

The IAB believes that a formal appeal is the wrong mechanism to achieve
these goals.  Appeals are to bring to light and correct errors in
process and/or substance.  Here neither is alleged.  Thus, no action is
needed by the IAB as a formal response to this appeal.  Future
suggestions from the community are welcome through mail to the
IAB <iab at iab.org> or through the RFC publication process.=

From ietf-secretariat@ietf.org  Wed Jul 17 15:55:54 2013
Return-Path: <ietf-secretariat@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03B1121F9EC4; Wed, 17 Jul 2013 15:55:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.267
X-Spam-Level: 
X-Spam-Status: No, score=-103.267 tagged_above=-999 required=5 tests=[AWL=-0.667, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ks5lSICZCg4j; Wed, 17 Jul 2013 15:55:51 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 121A621F9D87; Wed, 17 Jul 2013 15:55:51 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Secretariat <ietf-secretariat@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: IETF Mentor Program
X-Test-IDTracker: no
X-IETF-IDTracker: 4.53
Message-ID: <20130717225551.32629.89382.idtracker@ietfa.amsl.com>
Date: Wed, 17 Jul 2013 15:55:51 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 17 Jul 2013 22:55:54 -0000

Hi all,

   This is a reminder that, based on discussions during IETF 86, we are tri=
aling an IETF mentoring program.  During this trial period, we would like t=
o pair newcomers (people who have attended 3 or fewer meetings or have regi=
stered as students) with existing IETF participants.  The goal is to provid=
e a resource for the newcomer who can assist them with integrating into the=
 IETF community.  Mentors and newcomers will be paired prior to IETF 87.

   What we need is for people to volunteer to be mentors. As a mentor, we w=
ould ask that you be willing to assist your mentoring participant before, d=
uring, and (hopefully) after IETF 87.  The actual level of interaction will=
 be driven by an agreement between the mentor and the mentoring participant=
. Additionally, we would need a brief description of your areas of expertis=
e, technical interests, and conversational languages.

   A description of the Mentor Program (including a FAQ describing
how to volunteer to be a mentor) is available:

http://www.ietf.org/resources/mentoring-program.html.

   Anyone interested in being a mentor should follow the sign-up
instructions contained in the above URL.  The more volunteers we have,
the stronger the program will be!

Regards,
IETF Chair

From chair@ietf.org  Wed Jul 17 15:58:49 2013
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99E5621F9AFE; Wed, 17 Jul 2013 15:58:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.6
X-Spam-Level: 
X-Spam-Status: No, score=-104.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_INVITATION=-2, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 30-LtRVQL4zf; Wed, 17 Jul 2013 15:58:49 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E330421F9D87; Wed, 17 Jul 2013 15:58:41 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Chair <chair@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: Invitation to request an IETF mentor
X-Test-IDTracker: no
X-IETF-IDTracker: 4.53
Message-ID: <20130717225841.14002.89245.idtracker@ietfa.amsl.com>
Date: Wed, 17 Jul 2013 15:58:41 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 17 Jul 2013 22:58:49 -0000

All,

During IETF 87 in Berlin, we will be running a trial of the IETF Mentoring =
Program. The goal of the IETF Mentoring Program is to match people new to t=
he IETF (people who have participated in three or fewer face-to-face meetin=
gs or anyone registering as a student) with experienced IETF mentors. As a =
mentoring participant, your mentor will personally introduce you to the IET=
F community, help you find your way around the IETF & the meeting, explain =
things, and introduce you to other attendees you might like to meet. Basica=
lly, your mentor will be your personal buddy during the meeting week, and p=
ossibly afterwards.

The IETF Mentoring Program was created to help new IETF participants to get=
 up to speed rapidly and help them begin to contribute to the IETF quickly =
and easily.  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 then introduce you to each =
other by email, and invite you to meet up in person at the IETF Meet & Gree=
t event on Sunday afternoon in Berlin. From there on, you and your mentor d=
ecide 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 t=
he IETF Mentoring Program will be a great way for new participants to get i=
ntroduced to the IETF by an experienced participant with matching interest.

Regards,
Jari Arkko
IETF Chair

From john-ietf@jck.com  Wed Jul 17 23:02:17 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80DDA21F9FCC for <ietf@ietfa.amsl.com>; Wed, 17 Jul 2013 23:02:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.632
X-Spam-Level: 
X-Spam-Status: No, score=-102.632 tagged_above=-999 required=5 tests=[AWL=-0.033, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UfHGS5mbb0zW for <ietf@ietfa.amsl.com>; Wed, 17 Jul 2013 23:02:11 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 08A0121F9F00 for <ietf@ietf.org>; Wed, 17 Jul 2013 23:02:11 -0700 (PDT)
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 1UzhHz-000Iiw-VG; Thu, 18 Jul 2013 02:02:07 -0400
Date: Thu, 18 Jul 2013 02:02:02 -0400
From: John C Klensin <john-ietf@jck.com>
To: Bernard Aboba <bernard_aboba@hotmail.com>, Sam Hartman <hartmans-ietf@mit.edu>
Subject: RE: Internationalization and draft-ietf-abfab-eapapplicability
Message-ID: <C344105FFF7E8A2696D562F8@JcK-HP8200.jck.com>
In-Reply-To: <BLU169-W1110E775721ABEC5C3E4F1393610@phx.gbl>
References: <BLU169-W3386A689EE5BFC8D2272A093600@phx.gbl> ,	<71FEE03C-7A07-4CF3-BC25-0F22F306DE71@frobbit.se> ,	<51E67375.20802@cs.tcd.ie>	<tslhaftv45n.fsf@mit.edu> ,<51E682CC.8030603@restena.lu>	<tsl61w9tm6g.fsf@mit.edu>, <BLU169-W303D6471137BAEDD9FD70693610@phx.gbl> ,	<51E6993A.7010600@restena.lu>	<tsl38rds1eu.fsf@mit.edu> ,<tsl8v15qm9a.fsf@mit.edu> <BLU169-W1110E775721ABEC5C3E4F1393610@phx.gbl>
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: draft-ietf-abfab-eapapplicability@tools.ietf.org, ietf@ietf.org, =?UTF-8?Q?Patrik_F=C3=A4ltstr=C3=B6m?= <paf@frobbit.se>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Jul 2013 06:02:17 -0000

--On Wednesday, July 17, 2013 07:56 -0700 Bernard Aboba
<bernard_aboba@hotmail.com> wrote:

> Sam said: 
>> We don't get to place requirements on applications except to
>> say what they need to do to use EAP.  The protocol
>> requirement for that is that applications using EAP need to
>> know what character set they have so that EAP can convert the
>> identity to UTF-8 and so that EAP methods can do any needed
>> conversions.
>  
> [BA] That sounds right. 

I think it is right, with one qualification that might
reasonably be reflected in the document (perhaps as a Security
Consideration).  In the complex world of multiple coded
character sets and models for designing them, there is no
guarantee of a unique, reversible, mapping from any given one of
them to and from Unicode.  There is obviously no problem with
ASCII (or, more precisely, ISO 646 IRV) or ISO 8859-1 because
the Unicode ranges 0020..007F and 00A0..00FF are defined in
terms of those specs.  But, if the CCS used in an application,
is some odd code page, mappings onto Unicode may be a matter of
conventions and judgment, not a standard or universally-accepted
rule.  That problem is further complicated by issues of
normalization and precomposed characters versus composing
sequences, but would exist even without it.

As Sam more or less points out, this is an application problem,
not an EAP one, but the conversion process may lead to
surprising EAP results, particularly including false negatives.

best,
   john


From stefan.winter@restena.lu  Thu Jul 18 05:29:01 2013
Return-Path: <stefan.winter@restena.lu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 870D821E80E7 for <ietf@ietfa.amsl.com>; Thu, 18 Jul 2013 05:29:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.263
X-Spam-Level: 
X-Spam-Status: No, score=-2.263 tagged_above=-999 required=5 tests=[AWL=0.336,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9WrlRu3oX1l3 for <ietf@ietfa.amsl.com>; Thu, 18 Jul 2013 05:29:01 -0700 (PDT)
Received: from smtprelay.restena.lu (smtprelay.restena.lu [IPv6:2001:a18:1::62]) by ietfa.amsl.com (Postfix) with ESMTP id ABDDC21E80C5 for <ietf@ietf.org>; Thu, 18 Jul 2013 05:29:00 -0700 (PDT)
Received: from smtprelay.restena.lu (localhost [127.0.0.1]) by smtprelay.restena.lu (Postfix) with ESMTP id 765F71058A; Thu, 18 Jul 2013 14:28:59 +0200 (CEST)
Received: from aragorn.restena.lu (aragorn.restena.lu [IPv6:2001:a18:1:8::155]) by smtprelay.restena.lu (Postfix) with ESMTPS id 68D4B10584; Thu, 18 Jul 2013 14:28:59 +0200 (CEST)
Message-ID: <51E7DF87.6010908@restena.lu>
Date: Thu, 18 Jul 2013 14:28:55 +0200
From: Stefan Winter <stefan.winter@restena.lu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: Internationalization and draft-ietf-abfab-eapapplicability
References: <BLU169-W3386A689EE5BFC8D2272A093600@phx.gbl> <71FEE03C-7A07-4CF3-BC25-0F22F306DE71@frobbit.se> <51E67375.20802@cs.tcd.ie> <tslhaftv45n.fsf@mit.edu> <51E682CC.8030603@restena.lu> <tsl61w9tm6g.fsf@mit.edu> <BLU169-W303D6471137BAEDD9FD70693610@phx.gbl> <51E6993A.7010600@restena.lu> <tsl38rds1eu.fsf@mit.edu> <tsl8v15qm9a.fsf@mit.edu>
In-Reply-To: <tsl8v15qm9a.fsf@mit.edu>
X-Enigmail-Version: 1.5.1
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="----enig2XPAGQIOISPKJECICWJQN"
X-Virus-Scanned: ClamAV
Cc: Bernard Aboba <bernard_aboba@hotmail.com>, "draft-ietf-abfab-eapapplicability@tools.ietf.org" <draft-ietf-abfab-eapapplicability@tools.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Jul 2013 12:29:01 -0000

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

Hi,

> We don't get to place requirements on applications except to say what
> they need to do to use EAP.  The protocol requirement for that is that
> applications using EAP need to know what character set they have so tha=
t
> EAP can convert the identity to UTF-8 and so that EAP methods can do an=
y
> needed conversions.

That text sounds pretty good, and is probably all ABFAB needs to say
about this.

I'm still not happy with the i18n situation in EAP; especially that EAP
itself doesn't always know its requirements regarding encoding and
normalization.

I think the basic problem is that identities and other credentials are
eap-type specific and one might expect that neither core EAP nor the AAA
transport have to care about what an EAP method thinks it wants as encodi=
ng.
But that isn't true, since at least the Identity part (not the
passwords; I'm not saying these would need to be normalised at all) may
be needed by the EAP method, but they transpire through to the
EAP-Identity and RADIUS/other-AAA User-Names. It's a spill-over effect,
where an EAP method's decisions re encoding and normalisation impose
something on other protocols.

Due to that, an EAP method's way of constructing *identities* needs to
be regulated so that the method, core EAP, and AAA transports can get alo=
ng.

Nothing of this needs to happen in ABFAB, but I think work needs to be do=
ne.

Either by modifying EAP itself to impose a common encoding and maybe
normalisation on EAP-Identity (which in turn forces EAP methods to use
that same encoding and/or normalisation in their "outer" or "only"
phase), or by making sure all EAP methods use an encoding that does not
create problems on EAP core and the AAA layer.

I think this really has "force use of UTF-8" written all over it. The
question for me is which path to take, and where/who does the work.

Greetings,

Stefan Winter


--=20
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education National=
e et
de la Recherche
6, rue Richard Coudenhove-Kalergi
L-1359 Luxembourg

Tel: +352 424409 1
Fax: +352 422473


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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlHn34sACgkQ+jm90f8eFWau/ACcDr1hALUOIVDkCZh7UtSK1Xzs
CZcAn0rO8dCqNWLBrD+YiSQjvnuD7CTQ
=PqIH
-----END PGP SIGNATURE-----

------enig2XPAGQIOISPKJECICWJQN--

From bdickson@verisign.com  Wed Jul 17 11:14:12 2013
Return-Path: <bdickson@verisign.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65B8121F9B0D for <ietf@ietfa.amsl.com>; Wed, 17 Jul 2013 11:14:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.561
X-Spam-Level: 
X-Spam-Status: No, score=-6.561 tagged_above=-999 required=5 tests=[AWL=0.037,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H82CdKcjMpvE for <ietf@ietfa.amsl.com>; Wed, 17 Jul 2013 11:14:06 -0700 (PDT)
Received: from exprod6og127.obsmtp.com (exprod6og127.obsmtp.com [64.18.1.78]) by ietfa.amsl.com (Postfix) with ESMTP id EC74621F9D01 for <ietf@ietf.org>; Wed, 17 Jul 2013 11:14:04 -0700 (PDT)
Received: from osprey.verisign.com ([216.168.239.75]) (using TLSv1) by exprod6ob127.postini.com ([64.18.5.12]) with SMTP ID DSNKUebe7MC++H1TD3SU9cS6HPy7IPxzvEsu@postini.com; Wed, 17 Jul 2013 11:14:05 PDT
Received: from BRN1WNEXCHM01.vcorp.ad.vrsn.com (brn1wnexchm01.vcorp.ad.vrsn.com [10.173.152.255]) by osprey.verisign.com (8.13.6/8.13.4) with ESMTP id r6HIE1Bj011034 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <ietf@ietf.org>; Wed, 17 Jul 2013 14:14:03 -0400
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by BRN1WNEXCHM01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.02.0342.003; Wed, 17 Jul 2013 14:14:00 -0400
From: "Dickson, Brian" <bdickson@verisign.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Last Call: <draft-ietf-geopriv-res-gw-lis-discovery-05.txt> (Location Information Server (LIS) Discovery using IP address and Reverse DNS) to Informational RFC
Thread-Topic: Last Call: <draft-ietf-geopriv-res-gw-lis-discovery-05.txt> (Location Information Server (LIS) Discovery using IP address and Reverse DNS) to Informational RFC
Thread-Index: AQHOgxlpQiMYsEVaTESAVwQYVllumA==
Date: Wed, 17 Jul 2013 18:14:00 +0000
Message-ID: <CE0C5727.C4BC%bdickson@verisign.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.5.130515
x-originating-ip: [10.173.152.4]
Content-Type: multipart/alternative; boundary="_000_CE0C5727C4BCbdicksonverisigncom_"
MIME-Version: 1.0
X-Mailman-Approved-At: Thu, 18 Jul 2013 08:15:11 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Jul 2013 18:14:12 -0000

--_000_CE0C5727C4BCbdicksonverisigncom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I have a question about the use of STUN, as a way of discovering IP address=
(es), in draft-ietf-geopriv-res-gw-lis-discovery.

Section 4.1 refers to STUN by way of RFC 5389, but reading both the present=
 draft and 5389 leaves one critical item unspecified:

  o    What domain name is to be used, in the SRV query ("_stun._udp.domain=
" or "_stuns._tcp.domain" -- what value of "domain" is to be used in the qu=
ery)?

Without that being specified, implementers/users have nothing specific to t=
ry, and without that, I do not see how STUN could be used at all.

Similarly, recommending that STUN be provisioned (section 4.6) leaves the q=
uestion of "under which domain", unanswered and ambiguous.

Section 4.4 suggests that STUN servers be able to see the public IP used, b=
ut again, how should the STUN server be found?

This may have been an oversight by the authors, and they may already have e=
nvisioned answers to these questions.

Even section 7 (IAB considerations) is IMHO incomplete without the necessar=
y "domain" specification for STUN usage.

I think resolving this issue is critical  for the document to serve its sta=
ted purpose.

(Is there perhaps a companion STUN RFC that does discuss this? If so, addin=
g that as a normative reference may suffice, and linking to that in section=
s 4.1, 4.4, 4.6, and 8.

Modulo this oversight, I believe this is a well-written document and fills =
in an important gap in LIS deployment and use.

Brian Dickson

--_000_CE0C5727C4BCbdicksonverisigncom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <4028EC885306E34BB89DE430B8D23CBC@verisign.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif; ">
<div>I have a question about the use of STUN, as a way of discovering IP ad=
dress(es), in draft-ietf-geopriv-res-gw-lis-discovery.</div>
<div><br>
</div>
<div>Section 4.1 refers to STUN by way of RFC 5389, but reading both the pr=
esent draft and 5389 leaves one critical item unspecified:</div>
<div><br>
</div>
<div>&nbsp; o &nbsp; &nbsp;What domain name is to be used, in the SRV query=
 (&quot;_stun._udp.domain&quot; or &quot;_stuns._tcp.domain&quot; -- what v=
alue of &quot;domain&quot; is to be used in the query)?</div>
<div><br>
</div>
<div>Without that being specified, implementers/users have nothing specific=
 to try, and without that, I do not see how STUN could be used at all.</div=
>
<div><br>
</div>
<div>Similarly, recommending that STUN be provisioned (section 4.6) leaves =
the question of &quot;under which domain&quot;, unanswered and ambiguous.</=
div>
<div><br>
</div>
<div>Section 4.4 suggests that STUN servers be able to see the public IP us=
ed, but again, how should the STUN server be found?</div>
<div><br>
</div>
<div>This may have been an oversight by the authors, and they may already h=
ave envisioned answers to these questions.</div>
<div><br>
</div>
<div>Even section 7 (IAB considerations) is IMHO incomplete without the nec=
essary &quot;domain&quot; specification for STUN usage.</div>
<div><br>
</div>
<div>I think resolving this issue is critical &nbsp;for the document to ser=
ve its stated purpose.</div>
<div><br>
</div>
<div>(Is there perhaps a companion STUN RFC that does discuss this? If so, =
adding that as a normative reference may suffice, and linking to that in se=
ctions 4.1, 4.4, 4.6, and 8.</div>
<div><br>
</div>
<div>Modulo this oversight, I believe this is a well-written document and f=
ills in an important gap in LIS deployment and use.</div>
<div><br>
</div>
<div>Brian Dickson</div>
</body>
</html>

--_000_CE0C5727C4BCbdicksonverisigncom_--

From david.black@emc.com  Wed Jul 17 16:55:08 2013
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 427AE21F88D2; Wed, 17 Jul 2013 16:55:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.196
X-Spam-Level: 
X-Spam-Status: No, score=-102.196 tagged_above=-999 required=5 tests=[AWL=-0.197, BAYES_00=-2.599, J_CHICKENPOX_34=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ehLTLOl-G-SI; Wed, 17 Jul 2013 16:54:52 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 6612C21F99C3; Wed, 17 Jul 2013 16:54:48 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r6HNsf66028956 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Jul 2013 19:54:41 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd03.lss.emc.com [10.254.221.145]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Wed, 17 Jul 2013 19:54:30 -0400
Received: from mxhub20.corp.emc.com (mxhub20.corp.emc.com [10.254.93.49]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r6HNsTmm024844; Wed, 17 Jul 2013 19:54:29 -0400
Received: from mx15a.corp.emc.com ([169.254.1.184]) by mxhub20.corp.emc.com ([10.254.93.49]) with mapi; Wed, 17 Jul 2013 19:54:28 -0400
From: "Black, David" <david.black@emc.com>
To: "ldunbar@huawei.com" <ldunbar@huawei.com>, Donald Eastlake <d3e3e3@gmail.com>, "Radia@alum.mit.edu" <Radia@alum.mit.edu>, "igor@yahoo-inc.com" <igor@yahoo-inc.com>, General Area Review Team <gen-art@ietf.org>
Date: Wed, 17 Jul 2013 19:54:27 -0400
Subject: Gen-ART review of draft-ietf-trill-directory-framework-05
Thread-Topic: Gen-ART review of draft-ietf-trill-directory-framework-05
Thread-Index: Ac6DSPiBG6FbLQSdQg+o47Dp8whwIw==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712984AC753@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-EMM-MHVC: 1
X-Mailman-Approved-At: Thu, 18 Jul 2013 08:15:28 -0700
Cc: "Black, David" <david.black@emc.com>, "ietf@ietf.org" <ietf@ietf.org>, "trill@ietf.org" <trill@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Jul 2013 23:55:09 -0000

Document: draft-ietf-trill-directory-framework-05
Reviewer: David L. Black
Review Date: July 17, 2013
IETF LC End Date: July 18, 2013

Summary:
This draft is on the right track but has open issues, described in the revi=
ew.

This draft describes a framework for using directory servers to provide
address mappings (address -> destination RBridge) to TRILL Rbridges as an
alternative to data plane learning and use of the TRILL ESADI protocol.

The draft's generally well written and clear.  I found a couple of minor
issues.

Major issues: None.

Minor issues:

[1] The last bullet in Section 3.1 says:

       - In an environment where VMs migrate, there is a higher chance
         of cached information becoming invalid, causing traffic to be
         black-holed by the ingress RBridge, that is, persistently sent
         to the wrong egress RBridge. If VMs do not flood gratuitous
         ARP/ND or VDP [802.1Qbg] messages upon arriving at new
         locations, the ingress nodes might not have MAC entries for the
         MAC of the newly arrived VMs, causing unknown address flooding.

This is incorrect in multiple ways and should just be removed:

- Persistent black-holing is rare in practice because all common
	VM migration implementations issue the gratuitous messages.
- VMs don't send the gratuitous messages, hypervisors do.
- VDP is not flooded.  The receiver's always a bridge.
- At least one common VM migration implementation actually uses a gratuitou=
s
	RARP, not ARP.
- Flooding is done by the bridges and Rbridges, not the VMs.

[2] There are some unfortunate notation problems in Section 5.1 that carry
into the following sections, based on the logical data structure:

   [{IP, MAC/VLAN, {list of attached RBridge nicknames}, {list of
   interested RBridges}]

- The first open curly brace ('{') is unmatched.
- Subsequent text uses [IP or MAC/VLAN], IP/MAC/VLAN and MAC&VLAN,
	none of which appear in that structure.

Nits/editorial comments:

Section 1 - item 1 in the numbered list does not explain why it makes
a directory approach attractive.  This should be added, as it is
present for the other three items .

Section 2 - Say that IS-IS is a routing protocol.
The definition of Station should say that the node or virtual node
is on a network.  Also, please define or explain "virtual node".

Section 3.2 - Add the number of entries to be learned to scenario #1
in order to parallel the scenario # 2 discussion.

Section 4 - remove "(distributed model)" from first paragraph,
as it's not explained.

Section 5.3, top of p.13:

   therefore, there needs to be some mechanism by which RBridges that
   have pulled information that has not expired can be informed when
   that information changes or the like.

"or the like" is vague.  I suggest "or becomes invalid for other
 reasons".

idnits 2.12.17 didn't find any nits that need attention.

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 sanjay.mishra@verizon.com  Thu Jul 18 13:14:09 2013
Return-Path: <sanjay.mishra@verizon.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68EF211E8158 for <ietf@ietfa.amsl.com>; Thu, 18 Jul 2013 13:14:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.495
X-Spam-Level: 
X-Spam-Status: No, score=-3.495 tagged_above=-999 required=5 tests=[AWL=0.104,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7KS74NcP413g for <ietf@ietfa.amsl.com>; Thu, 18 Jul 2013 13:14:04 -0700 (PDT)
Received: from fldsmtpe02.verizon.com (fldsmtpe02.verizon.com [140.108.26.141]) by ietfa.amsl.com (Postfix) with ESMTP id E065411E813F for <ietf@ietf.org>; Thu, 18 Jul 2013 13:14:03 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: false
Received: from unknown (HELO fldsmtpi02.verizon.com) ([166.68.71.144]) by fldsmtpe02.verizon.com with ESMTP; 18 Jul 2013 20:14:03 +0000
From: "Mishra, Sanjay" <sanjay.mishra@verizon.com>
X-IronPort-AV: E=Sophos;i="4.89,696,1367971200"; d="scan'208";a="510357798"
Received: from fhdp1lumxc7hb04.verizon.com (HELO FHDP1LUMXC7HB04.us.one.verizon.com) ([166.68.59.191]) by fldsmtpi02.verizon.com with ESMTP; 18 Jul 2013 20:14:03 +0000
Received: from fhdp1lumxc7v23.us.one.verizon.com ([166.68.59.159]) by FHDP1LUMXC7HB04.us.one.verizon.com ([166.68.59.191]) with mapi; Thu, 18 Jul 2013 16:14:03 -0400
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Thu, 18 Jul 2013 16:14:01 -0400
Subject: RE: Ietf Digest, Vol 62, Issue 57
Thread-Topic: Ietf Digest, Vol 62, Issue 57
Thread-Index: Ac6ChUC3ygL7F7KhQsGxZXdyIV07BwBbTHBA
Message-ID: <900A1E2059ADB149B905E3C8FA0046A62C77D926D4@FHDP1LUMXC7V23.us.one.verizon.com>
References: <mailman.4397.1374021172.3516.ietf@ietf.org>
In-Reply-To: <mailman.4397.1374021172.3516.ietf@ietf.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Jul 2013 20:14:09 -0000

Moving IAOC Overview session now conflicts with Newcomer's orientation. The=
 original schedule for IAOC conflicted only for the 2nd hour with newcomer =
meet and greet and I had figured to attend at least the first hour but now =
the IAOC session overlaps fully with Newcomer's orientation so those first =
time attendees like me will have to likely pick newcomer orientation over I=
AOC overview which if not conflicting would have been helpful.

Is it possible to start sooner on Sunday?

Thanks
Sanjay

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of iet=
f-request@ietf.org
Sent: Tuesday, July 16, 2013 8:33 PM
To: ietf@ietf.org
Subject: Ietf Digest, Vol 62, Issue 57

If you have received this digest without all the individual message attachm=
ents you will need to update your digest options in your list subscription.=
  To do so, go to=20

https://www.ietf.org/mailman/listinfo/ietf

Click the 'Unsubscribe or edit options' button, log in, and set "Get MIME o=
r Plain Text Digests?" to MIME.  You can set this option globally for all t=
he list digests you receive at this point.



Send Ietf mailing list submissions to
	ietf@ietf.org

To subscribe or unsubscribe via the World Wide Web, visit
	https://www.ietf.org/mailman/listinfo/ietf
or, via email, send a message with subject or body 'help' to
	ietf-request@ietf.org

You can reach the person managing the list at
	ietf-owner@ietf.org

When replying, please edit your Subject line so it is more specific than "R=
e: Contents of Ietf digest..."

From brian.e.carpenter@gmail.com  Thu Jul 18 13:34:12 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E64611E81E6 for <ietf@ietfa.amsl.com>; Thu, 18 Jul 2013 13:34:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.494
X-Spam-Level: 
X-Spam-Status: No, score=-102.494 tagged_above=-999 required=5 tests=[AWL=0.105, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4oAK6dFrworu for <ietf@ietfa.amsl.com>; Thu, 18 Jul 2013 13:34:10 -0700 (PDT)
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 C1EEF11E81C8 for <ietf@ietf.org>; Thu, 18 Jul 2013 13:34:10 -0700 (PDT)
Received: by mail-pd0-f179.google.com with SMTP id q10so3496273pdj.10 for <ietf@ietf.org>; Thu, 18 Jul 2013 13:34:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=qXGXeyZ3i3UDV5K1dJBUJydahXYb2HUnZp3XyY9+vjY=; b=viNZWDQrUCu4f1roR10HycJUczYUClGL/CIDUD6/ESfA5EGp8E0hXwbyFJJQcIzGV/ DVEr94W6f2bS7x7JaT8DXx77jO0qfcroWYeV91RUFHMNaZaQmaxwbNKxIIMo0XcDfRjT b37bZcT/dQY7fjdxe1ZXBkO/J72zlSiiKlDmhFJsbeW7YHmfcryY2bDv44feKonHCpdB M2HiyHDb7E4KvUayZAlggSrfsTR8fH4OMj5FCDaUP9P1VFyDqlJrjfoCNc3ze1PqxY7p U0iov2xsP/hEBO5IoczHlLGKP62Uzt/++AP7UX8dQ0QXalyMp6dFBlLvG6UuGT5UrN3t nZkw==
X-Received: by 10.68.204.194 with SMTP id la2mr13915689pbc.71.1374179650527; Thu, 18 Jul 2013 13:34:10 -0700 (PDT)
Received: from [192.168.178.23] (127.199.69.111.dynamic.snap.net.nz. [111.69.199.127]) by mx.google.com with ESMTPSA id vo8sm15520042pbc.5.2013.07.18.13.34.08 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 18 Jul 2013 13:34:09 -0700 (PDT)
Message-ID: <51E85149.400@gmail.com>
Date: Fri, 19 Jul 2013 08:34:17 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "Mishra, Sanjay" <sanjay.mishra@verizon.com>
Subject: IAOC overview clash
References: <mailman.4397.1374021172.3516.ietf@ietf.org> <900A1E2059ADB149B905E3C8FA0046A62C77D926D4@FHDP1LUMXC7V23.us.one.verizon.com>
In-Reply-To: <900A1E2059ADB149B905E3C8FA0046A62C77D926D4@FHDP1LUMXC7V23.us.one.verizon.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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Jul 2013 20:34:12 -0000

Sanjay,

A comment from an old-timer: if you want to understand the IETF as a whole,
put your priority on the Newcomer's orientation. There's plenty of time
in the future to understand details of the IETF's administration.

Unfortunately, clashes between interesting sessions are unavoidable
at the IETF, because there is just too much going on. If they move the
IAOC overview again, it will clash with something else, even on Sunday.

Regards
   Brian Carpenter

On 19/07/2013 08:14, Mishra, Sanjay wrote:
> Moving IAOC Overview session now conflicts with Newcomer's orientation. The original schedule for IAOC conflicted only for the 2nd hour with newcomer meet and greet and I had figured to attend at least the first hour but now the IAOC session overlaps fully with Newcomer's orientation so those first time attendees like me will have to likely pick newcomer orientation over IAOC overview which if not conflicting would have been helpful.
> 
> Is it possible to start sooner on Sunday?
> 
> Thanks
> Sanjay
> 
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of ietf-request@ietf.org
> Sent: Tuesday, July 16, 2013 8:33 PM
> To: ietf@ietf.org
> Subject: Ietf Digest, Vol 62, Issue 57
> 
> If you have received this digest without all the individual message attachments you will need to update your digest options in your list subscription.  To do so, go to 
> 
> https://www.ietf.org/mailman/listinfo/ietf
> 
> Click the 'Unsubscribe or edit options' button, log in, and set "Get MIME or Plain Text Digests?" to MIME.  You can set this option globally for all the list digests you receive at this point.
> 
> 
> 
> Send Ietf mailing list submissions to
> 	ietf@ietf.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://www.ietf.org/mailman/listinfo/ietf
> or, via email, send a message with subject or body 'help' to
> 	ietf-request@ietf.org
> 
> You can reach the person managing the list at
> 	ietf-owner@ietf.org
> 
> When replying, please edit your Subject line so it is more specific than "Re: Contents of Ietf digest..."
> 

From randy@psg.com  Thu Jul 18 13:48:23 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2774011E8199 for <ietf@ietfa.amsl.com>; Thu, 18 Jul 2013 13:48:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.558
X-Spam-Level: 
X-Spam-Status: No, score=-2.558 tagged_above=-999 required=5 tests=[AWL=0.041,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 06bh5E1x5xNm for <ietf@ietfa.amsl.com>; Thu, 18 Jul 2013 13:48:22 -0700 (PDT)
Received: from ran.psg.com (unknown [IPv6:2001:418:8006::19]) by ietfa.amsl.com (Postfix) with ESMTP id BFDD711E813D for <ietf@ietf.org>; Thu, 18 Jul 2013 13:48:22 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1Uzv7W-0001KO-MO for ietf@ietf.org; Thu, 18 Jul 2013 20:48:15 +0000
Date: Thu, 18 Jul 2013 13:48:14 -0700
Message-ID: <m261w78ui9.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: IETF Disgust <ietf@ietf.org>
Subject: Re: IAOC overview clash
In-Reply-To: <51E85149.400@gmail.com>
References: <mailman.4397.1374021172.3516.ietf@ietf.org> <900A1E2059ADB149B905E3C8FA0046A62C77D926D4@FHDP1LUMXC7V23.us.one.verizon.com> <51E85149.400@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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Jul 2013 20:48:23 -0000

global bgp never converges (and how would you know if it did?)
all devices fail, and two will fail at once
there is no more ipv4 free pool, get over it
there is not enough time on sunday for everything without conflict
there are never enough social tickets (but there is heavy last minute trading)
the cookies are bad and bad for you, and they are too small (~= w allen)

welcome to the internet and the ietf!

From sanjay.mishra@verizon.com  Thu Jul 18 13:55:34 2013
Return-Path: <sanjay.mishra@verizon.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0251C11E8220 for <ietf@ietfa.amsl.com>; Thu, 18 Jul 2013 13:55:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.529
X-Spam-Level: 
X-Spam-Status: No, score=-3.529 tagged_above=-999 required=5 tests=[AWL=0.069,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id huJhhkd9d1HA for <ietf@ietfa.amsl.com>; Thu, 18 Jul 2013 13:55:07 -0700 (PDT)
Received: from omzsmtpe02.verizonbusiness.com (omzsmtpe02.verizonbusiness.com [199.249.25.209]) by ietfa.amsl.com (Postfix) with ESMTP id 8012921E80F9 for <ietf@ietf.org>; Thu, 18 Jul 2013 13:54:31 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: false
Received: from unknown (HELO fldsmtpi01.verizon.com) ([166.68.71.143]) by omzsmtpe02.verizonbusiness.com with ESMTP; 18 Jul 2013 20:54:30 +0000
From: "Mishra, Sanjay" <sanjay.mishra@verizon.com>
X-IronPort-AV: E=Sophos;i="4.89,696,1367971200";  d="scan'208,217";a="519944146"
Received: from fhdp1lumxc7hb04.verizon.com (HELO FHDP1LUMXC7HB04.us.one.verizon.com) ([166.68.59.191]) by fldsmtpi01.verizon.com with ESMTP; 18 Jul 2013 20:54:30 +0000
Received: from fhdp1lumxc7v23.us.one.verizon.com ([166.68.59.159]) by FHDP1LUMXC7HB04.us.one.verizon.com ([166.68.59.191]) with mapi; Thu, 18 Jul 2013 16:54:29 -0400
To: 'Brian E Carpenter' <brian.e.carpenter@gmail.com>
Date: Thu, 18 Jul 2013 16:54:29 -0400
Subject: RE: IAOC overview clash
Thread-Topic: IAOC overview clash
Thread-Index: Ac6D9imVj2Pa+f0hTNOalhq0YLt2agAAtWE8
Message-ID: <900A1E2059ADB149B905E3C8FA0046A62C77E2500B@FHDP1LUMXC7V23.us.one.verizon.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_900A1E2059ADB149B905E3C8FA0046A62C77E2500BFHDP1LUMXC7V2_"
MIME-Version: 1.0
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Jul 2013 20:55:36 -0000

--_000_900A1E2059ADB149B905E3C8FA0046A62C77E2500BFHDP1LUMXC7V2_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

QnJpYW4gLSB0aGFuayB5b3UuIFllcywgSSBjZXJ0YWlubHkgcGxhbiB0byB0byBhdHRlbmQgdGhl
IG5ld2NvbWVyIG9yaWVudGF0aW9uLiBNeSBwb2ludCB3YXMgdGhhdCBtb3ZpbmcgdG8gdGhlIHRp
bWUgc2xvdCBzdGlsbCBkaWQgbm90IGF2b2lkIHRoZSBjb25mbGljdC4gQnV0IGkgYWdyZWUgd2l0
aCB5b3UgdGhhdCBuZXcgY29tZXIgb3JpZW50YXRpb24gaXMgaGVscGZ1bCBub3cgYW5kIHRoZXJl
IHdpbGwgYmUgcGxlbnR5IG9mIG9wcG9ydHVuaXR5IGxhdGVyIHRvIHBpY2sgdXAgb24gSU9BQyBh
ZG1pbmlzdHJhdGl2ZSBmdW5jdGlvbnMuDQoNClRoYW5rcw0KU2FuamF5DQoNCg0KDQpUaGFua3MN
ClNhbmpheSBNaXNocmENCkNlbGw6MzAxLTQ1Mi0yNTk1DQpTZW50IHdpdGggR29vZCAod3d3Lmdv
b2QuY29tKQ0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogQnJpYW4gRSBDYXJw
ZW50ZXIgW2JyaWFuLmUuY2FycGVudGVyQGdtYWlsLmNvbTxtYWlsdG86YnJpYW4uZS5jYXJwZW50
ZXJAZ21haWwuY29tPl0NClNlbnQ6IFRodXJzZGF5LCBKdWx5IDE4LCAyMDEzIDA0OjM0IFBNIEVh
c3Rlcm4gU3RhbmRhcmQgVGltZQ0KVG86IE1pc2hyYSwgU2FuamF5DQpDYzogaWV0ZkBpZXRmLm9y
Zw0KU3ViamVjdDogSUFPQyBvdmVydmlldyBjbGFzaA0KDQoNClNhbmpheSwNCg0KQSBjb21tZW50
IGZyb20gYW4gb2xkLXRpbWVyOiBpZiB5b3Ugd2FudCB0byB1bmRlcnN0YW5kIHRoZSBJRVRGIGFz
IGEgd2hvbGUsDQpwdXQgeW91ciBwcmlvcml0eSBvbiB0aGUgTmV3Y29tZXIncyBvcmllbnRhdGlv
bi4gVGhlcmUncyBwbGVudHkgb2YgdGltZQ0KaW4gdGhlIGZ1dHVyZSB0byB1bmRlcnN0YW5kIGRl
dGFpbHMgb2YgdGhlIElFVEYncyBhZG1pbmlzdHJhdGlvbi4NCg0KVW5mb3J0dW5hdGVseSwgY2xh
c2hlcyBiZXR3ZWVuIGludGVyZXN0aW5nIHNlc3Npb25zIGFyZSB1bmF2b2lkYWJsZQ0KYXQgdGhl
IElFVEYsIGJlY2F1c2UgdGhlcmUgaXMganVzdCB0b28gbXVjaCBnb2luZyBvbi4gSWYgdGhleSBt
b3ZlIHRoZQ0KSUFPQyBvdmVydmlldyBhZ2FpbiwgaXQgd2lsbCBjbGFzaCB3aXRoIHNvbWV0aGlu
ZyBlbHNlLCBldmVuIG9uIFN1bmRheS4NCg0KUmVnYXJkcw0KICAgQnJpYW4gQ2FycGVudGVyDQoN
Ck9uIDE5LzA3LzIwMTMgMDg6MTQsIE1pc2hyYSwgU2FuamF5IHdyb3RlOg0KPiBNb3ZpbmcgSUFP
QyBPdmVydmlldyBzZXNzaW9uIG5vdyBjb25mbGljdHMgd2l0aCBOZXdjb21lcidzIG9yaWVudGF0
aW9uLiBUaGUgb3JpZ2luYWwgc2NoZWR1bGUgZm9yIElBT0MgY29uZmxpY3RlZCBvbmx5IGZvciB0
aGUgMm5kIGhvdXIgd2l0aCBuZXdjb21lciBtZWV0IGFuZCBncmVldCBhbmQgSSBoYWQgZmlndXJl
ZCB0byBhdHRlbmQgYXQgbGVhc3QgdGhlIGZpcnN0IGhvdXIgYnV0IG5vdyB0aGUgSUFPQyBzZXNz
aW9uIG92ZXJsYXBzIGZ1bGx5IHdpdGggTmV3Y29tZXIncyBvcmllbnRhdGlvbiBzbyB0aG9zZSBm
aXJzdCB0aW1lIGF0dGVuZGVlcyBsaWtlIG1lIHdpbGwgaGF2ZSB0byBsaWtlbHkgcGljayBuZXdj
b21lciBvcmllbnRhdGlvbiBvdmVyIElBT0Mgb3ZlcnZpZXcgd2hpY2ggaWYgbm90IGNvbmZsaWN0
aW5nIHdvdWxkIGhhdmUgYmVlbiBoZWxwZnVsLg0KPg0KPiBJcyBpdCBwb3NzaWJsZSB0byBzdGFy
dCBzb29uZXIgb24gU3VuZGF5Pw0KPg0KPiBUaGFua3MNCj4gU2FuamF5DQo+DQo+IC0tLS0tT3Jp
Z2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IGlldGYtYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRv
OmlldGYtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIGlldGYtcmVxdWVzdEBpZXRmLm9y
Zw0KPiBTZW50OiBUdWVzZGF5LCBKdWx5IDE2LCAyMDEzIDg6MzMgUE0NCj4gVG86IGlldGZAaWV0
Zi5vcmcNCj4gU3ViamVjdDogSWV0ZiBEaWdlc3QsIFZvbCA2MiwgSXNzdWUgNTcNCj4NCj4gSWYg
eW91IGhhdmUgcmVjZWl2ZWQgdGhpcyBkaWdlc3Qgd2l0aG91dCBhbGwgdGhlIGluZGl2aWR1YWwg
bWVzc2FnZSBhdHRhY2htZW50cyB5b3Ugd2lsbCBuZWVkIHRvIHVwZGF0ZSB5b3VyIGRpZ2VzdCBv
cHRpb25zIGluIHlvdXIgbGlzdCBzdWJzY3JpcHRpb24uICBUbyBkbyBzbywgZ28gdG8NCj4NCj4g
aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pZXRmDQo+DQo+IENsaWNrIHRo
ZSAnVW5zdWJzY3JpYmUgb3IgZWRpdCBvcHRpb25zJyBidXR0b24sIGxvZyBpbiwgYW5kIHNldCAi
R2V0IE1JTUUgb3IgUGxhaW4gVGV4dCBEaWdlc3RzPyIgdG8gTUlNRS4gIFlvdSBjYW4gc2V0IHRo
aXMgb3B0aW9uIGdsb2JhbGx5IGZvciBhbGwgdGhlIGxpc3QgZGlnZXN0cyB5b3UgcmVjZWl2ZSBh
dCB0aGlzIHBvaW50Lg0KPg0KPg0KPg0KPiBTZW5kIElldGYgbWFpbGluZyBsaXN0IHN1Ym1pc3Np
b25zIHRvDQo+ICAgICAgIGlldGZAaWV0Zi5vcmcNCj4NCj4gVG8gc3Vic2NyaWJlIG9yIHVuc3Vi
c2NyaWJlIHZpYSB0aGUgV29ybGQgV2lkZSBXZWIsIHZpc2l0DQo+ICAgICAgIGh0dHBzOi8vd3d3
LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vaWV0Zg0KPiBvciwgdmlhIGVtYWlsLCBzZW5kIGEg
bWVzc2FnZSB3aXRoIHN1YmplY3Qgb3IgYm9keSAnaGVscCcgdG8NCj4gICAgICAgaWV0Zi1yZXF1
ZXN0QGlldGYub3JnDQo+DQo+IFlvdSBjYW4gcmVhY2ggdGhlIHBlcnNvbiBtYW5hZ2luZyB0aGUg
bGlzdCBhdA0KPiAgICAgICBpZXRmLW93bmVyQGlldGYub3JnDQo+DQo+IFdoZW4gcmVwbHlpbmcs
IHBsZWFzZSBlZGl0IHlvdXIgU3ViamVjdCBsaW5lIHNvIGl0IGlzIG1vcmUgc3BlY2lmaWMgdGhh
biAiUmU6IENvbnRlbnRzIG9mIElldGYgZGlnZXN0Li4uIg0KPg0K

--_000_900A1E2059ADB149B905E3C8FA0046A62C77E2500BFHDP1LUMXC7V2_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDMuMi8vRU4iPg0KPGh0bWw+
DQo8aGVhZD4NCjxtZXRhIG5hbWU9ImdlbmVyYXRvciIgY29udGVudD0iSFRNTCBUaWR5IGZvciBX
aW5kb3dzICh2ZXJzIDI1IE1hcmNoIDIwMDkpLCBzZWUgd3d3LnczLm9yZyI+DQo8bWV0YSBodHRw
LWVxdWl2PSJDb250ZW50LVR5cGUiIGNvbnRlbnQ9InRleHQvaHRtbDsgY2hhcnNldD11dGYtOCI+
DQo8bWV0YSBuYW1lPSJHZW5lcmF0b3IiIGNvbnRlbnQ9Ik1TIEV4Y2hhbmdlIFNlcnZlciB2ZXJz
aW9uIDA4LjAzLjAyNzkuMDAwIj4NCjx0aXRsZT5JQU9DIG92ZXJ2aWV3IGNsYXNoPC90aXRsZT4N
CjwvaGVhZD4NCjxib2R5Pg0KQnJpYW4gLSB0aGFuayB5b3UuIFllcywgSSBjZXJ0YWlubHkgcGxh
biB0byB0byBhdHRlbmQgdGhlIG5ld2NvbWVyIG9yaWVudGF0aW9uLiBNeSBwb2ludCB3YXMgdGhh
dCBtb3ZpbmcgdG8gdGhlIHRpbWUgc2xvdCBzdGlsbCBkaWQgbm90IGF2b2lkIHRoZSBjb25mbGlj
dC4gQnV0IGkgYWdyZWUgd2l0aCB5b3UgdGhhdCBuZXcgY29tZXIgb3JpZW50YXRpb24gaXMgaGVs
cGZ1bCBub3cgYW5kIHRoZXJlIHdpbGwgYmUgcGxlbnR5IG9mIG9wcG9ydHVuaXR5IGxhdGVyIHRv
IHBpY2sgdXAgb24gSU9BQyBhZG1pbmlzdHJhdGl2ZSBmdW5jdGlvbnMuPGJyPg0KPGJyPg0KVGhh
bmtzPGJyPg0KU2FuamF5PGJyPg0KPGJyPg0KPGJyPg0KPGJyPg0KVGhhbmtzPGJyPg0KU2FuamF5
IE1pc2hyYTxicj4NCkNlbGw6MzAxLTQ1Mi0yNTk1PGJyPg0KU2VudCB3aXRoIEdvb2QgKHd3dy5n
b29kLmNvbSk8YnI+DQo8YnI+DQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLTxicj4NCjxiPkZy
b206Jm5ic3A7PC9iPkJyaWFuIEUgQ2FycGVudGVyIFs8YSBocmVmPSJtYWlsdG86YnJpYW4uZS5j
YXJwZW50ZXJAZ21haWwuY29tIj5icmlhbi5lLmNhcnBlbnRlckBnbWFpbC5jb208L2E+XTxicj4N
CjxiPlNlbnQ6Jm5ic3A7PC9iPlRodXJzZGF5LCBKdWx5IDE4LCAyMDEzIDA0OjM0IFBNIEVhc3Rl
cm4gU3RhbmRhcmQgVGltZTxicj4NCjxiPlRvOiZuYnNwOzwvYj5NaXNocmEsIFNhbmpheTxicj4N
CjxiPkNjOiZuYnNwOzwvYj5pZXRmQGlldGYub3JnPGJyPg0KPGI+U3ViamVjdDombmJzcDs8L2I+
SUFPQyBvdmVydmlldyBjbGFzaDxicj4NCjxicj4NCjwhLS0gQ29udmVydGVkIGZyb20gdGV4dC9w
bGFpbiBmb3JtYXQgLS0+DQo8cD48Zm9udCBzaXplPSIyIj5TYW5qYXksPGJyPg0KPGJyPg0KQSBj
b21tZW50IGZyb20gYW4gb2xkLXRpbWVyOiBpZiB5b3Ugd2FudCB0byB1bmRlcnN0YW5kIHRoZSBJ
RVRGIGFzIGEgd2hvbGUsPGJyPg0KcHV0IHlvdXIgcHJpb3JpdHkgb24gdGhlIE5ld2NvbWVyJ3Mg
b3JpZW50YXRpb24uIFRoZXJlJ3MgcGxlbnR5IG9mIHRpbWU8YnI+DQppbiB0aGUgZnV0dXJlIHRv
IHVuZGVyc3RhbmQgZGV0YWlscyBvZiB0aGUgSUVURidzIGFkbWluaXN0cmF0aW9uLjxicj4NCjxi
cj4NClVuZm9ydHVuYXRlbHksIGNsYXNoZXMgYmV0d2VlbiBpbnRlcmVzdGluZyBzZXNzaW9ucyBh
cmUgdW5hdm9pZGFibGU8YnI+DQphdCB0aGUgSUVURiwgYmVjYXVzZSB0aGVyZSBpcyBqdXN0IHRv
byBtdWNoIGdvaW5nIG9uLiBJZiB0aGV5IG1vdmUgdGhlPGJyPg0KSUFPQyBvdmVydmlldyBhZ2Fp
biwgaXQgd2lsbCBjbGFzaCB3aXRoIHNvbWV0aGluZyBlbHNlLCBldmVuIG9uIFN1bmRheS48YnI+
DQo8YnI+DQpSZWdhcmRzPGJyPg0KJm5ic3A7Jm5ic3A7IEJyaWFuIENhcnBlbnRlcjxicj4NCjxi
cj4NCk9uIDE5LzA3LzIwMTMgMDg6MTQsIE1pc2hyYSwgU2FuamF5IHdyb3RlOjxicj4NCiZndDsg
TW92aW5nIElBT0MgT3ZlcnZpZXcgc2Vzc2lvbiBub3cgY29uZmxpY3RzIHdpdGggTmV3Y29tZXIn
cyBvcmllbnRhdGlvbi4gVGhlIG9yaWdpbmFsIHNjaGVkdWxlIGZvciBJQU9DIGNvbmZsaWN0ZWQg
b25seSBmb3IgdGhlIDJuZCBob3VyIHdpdGggbmV3Y29tZXIgbWVldCBhbmQgZ3JlZXQgYW5kIEkg
aGFkIGZpZ3VyZWQgdG8gYXR0ZW5kIGF0IGxlYXN0IHRoZSBmaXJzdCBob3VyIGJ1dCBub3cgdGhl
IElBT0Mgc2Vzc2lvbiBvdmVybGFwcyBmdWxseSB3aXRoIE5ld2NvbWVyJ3Mgb3JpZW50YXRpb24g
c28gdGhvc2UgZmlyc3QgdGltZSBhdHRlbmRlZXMgbGlrZSBtZSB3aWxsIGhhdmUgdG8gbGlrZWx5
IHBpY2sgbmV3Y29tZXIgb3JpZW50YXRpb24gb3ZlciBJQU9DIG92ZXJ2aWV3IHdoaWNoIGlmIG5v
dCBjb25mbGljdGluZyB3b3VsZCBoYXZlIGJlZW4gaGVscGZ1bC48YnI+DQomZ3Q7PGJyPg0KJmd0
OyBJcyBpdCBwb3NzaWJsZSB0byBzdGFydCBzb29uZXIgb24gU3VuZGF5Pzxicj4NCiZndDs8YnI+
DQomZ3Q7IFRoYW5rczxicj4NCiZndDsgU2FuamF5PGJyPg0KJmd0Ozxicj4NCiZndDsgLS0tLS1P
cmlnaW5hbCBNZXNzYWdlLS0tLS08YnI+DQomZ3Q7IEZyb206IGlldGYtYm91bmNlc0BpZXRmLm9y
ZyBbPGEgaHJlZj0ibWFpbHRvOmlldGYtYm91bmNlc0BpZXRmLm9yZyI+bWFpbHRvOmlldGYtYm91
bmNlc0BpZXRmLm9yZzwvYT5dIE9uIEJlaGFsZiBPZiBpZXRmLXJlcXVlc3RAaWV0Zi5vcmc8YnI+
DQomZ3Q7IFNlbnQ6IFR1ZXNkYXksIEp1bHkgMTYsIDIwMTMgODozMyBQTTxicj4NCiZndDsgVG86
IGlldGZAaWV0Zi5vcmc8YnI+DQomZ3Q7IFN1YmplY3Q6IElldGYgRGlnZXN0LCBWb2wgNjIsIElz
c3VlIDU3PGJyPg0KJmd0Ozxicj4NCiZndDsgSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyBkaWdl
c3Qgd2l0aG91dCBhbGwgdGhlIGluZGl2aWR1YWwgbWVzc2FnZSBhdHRhY2htZW50cyB5b3Ugd2ls
bCBuZWVkIHRvIHVwZGF0ZSB5b3VyIGRpZ2VzdCBvcHRpb25zIGluIHlvdXIgbGlzdCBzdWJzY3Jp
cHRpb24uJm5ic3A7IFRvIGRvIHNvLCBnbyB0bzxicj4NCiZndDs8YnI+DQomZ3Q7IDxhIGhyZWY9
Imh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vaWV0ZiI+aHR0cHM6Ly93d3cu
aWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pZXRmPC9hPjxicj4NCiZndDs8YnI+DQomZ3Q7IENs
aWNrIHRoZSAnVW5zdWJzY3JpYmUgb3IgZWRpdCBvcHRpb25zJyBidXR0b24sIGxvZyBpbiwgYW5k
IHNldCAiR2V0IE1JTUUgb3IgUGxhaW4gVGV4dCBEaWdlc3RzPyIgdG8gTUlNRS4mbmJzcDsgWW91
IGNhbiBzZXQgdGhpcyBvcHRpb24gZ2xvYmFsbHkgZm9yIGFsbCB0aGUgbGlzdCBkaWdlc3RzIHlv
dSByZWNlaXZlIGF0IHRoaXMgcG9pbnQuPGJyPg0KJmd0Ozxicj4NCiZndDs8YnI+DQomZ3Q7PGJy
Pg0KJmd0OyBTZW5kIElldGYgbWFpbGluZyBsaXN0IHN1Ym1pc3Npb25zIHRvPGJyPg0KJmd0OyAm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgaWV0ZkBpZXRmLm9yZzxicj4NCiZndDs8YnI+
DQomZ3Q7IFRvIHN1YnNjcmliZSBvciB1bnN1YnNjcmliZSB2aWEgdGhlIFdvcmxkIFdpZGUgV2Vi
LCB2aXNpdDxicj4NCiZndDsgJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IDxhIGhyZWY9
Imh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vaWV0ZiI+aHR0cHM6Ly93d3cu
aWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pZXRmPC9hPjxicj4NCiZndDsgb3IsIHZpYSBlbWFp
bCwgc2VuZCBhIG1lc3NhZ2Ugd2l0aCBzdWJqZWN0IG9yIGJvZHkgJ2hlbHAnIHRvPGJyPg0KJmd0
OyAmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgaWV0Zi1yZXF1ZXN0QGlldGYub3JnPGJy
Pg0KJmd0Ozxicj4NCiZndDsgWW91IGNhbiByZWFjaCB0aGUgcGVyc29uIG1hbmFnaW5nIHRoZSBs
aXN0IGF0PGJyPg0KJmd0OyAmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgaWV0Zi1vd25l
ckBpZXRmLm9yZzxicj4NCiZndDs8YnI+DQomZ3Q7IFdoZW4gcmVwbHlpbmcsIHBsZWFzZSBlZGl0
IHlvdXIgU3ViamVjdCBsaW5lIHNvIGl0IGlzIG1vcmUgc3BlY2lmaWMgdGhhbiAiUmU6IENvbnRl
bnRzIG9mIElldGYgZGlnZXN0Li4uIjxicj4NCiZndDs8YnI+PC9mb250PjwvcD4NCjwvYm9keT4N
CjwvaHRtbD4NCg==

--_000_900A1E2059ADB149B905E3C8FA0046A62C77E2500BFHDP1LUMXC7V2_--

From narten@us.ibm.com  Thu Jul 18 21:53:15 2013
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FECC21F9223 for <ietf@ietfa.amsl.com>; Thu, 18 Jul 2013 21:53:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.985
X-Spam-Level: 
X-Spam-Status: No, score=-109.985 tagged_above=-999 required=5 tests=[AWL=0.614, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XHDvk+D2su2U for <ietf@ietfa.amsl.com>; Thu, 18 Jul 2013 21:53:08 -0700 (PDT)
Received: from e39.co.us.ibm.com (e39.co.us.ibm.com [32.97.110.160]) by ietfa.amsl.com (Postfix) with ESMTP id 7648421F91CA for <ietf@ietf.org>; Thu, 18 Jul 2013 21:53:08 -0700 (PDT)
Received: from /spool/local by e39.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Thu, 18 Jul 2013 22:53:07 -0600
Received: from d01dlp01.pok.ibm.com (9.56.250.166) by e39.co.us.ibm.com (192.168.1.139) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 18 Jul 2013 22:53:06 -0600
Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236]) by d01dlp01.pok.ibm.com (Postfix) with ESMTP id 3B74538C8039 for <ietf@ietf.org>; Fri, 19 Jul 2013 00:53:04 -0400 (EDT)
Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by d01relay04.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r6J4r52c183346 for <ietf@ietf.org>; Fri, 19 Jul 2013 00:53:05 -0400
Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1]) by d03av02.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r6J4r4wc014508 for <ietf@ietf.org>; Thu, 18 Jul 2013 22:53:04 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d03av02.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r6J4r3hu014401 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 18 Jul 2013 22:53:04 -0600
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.7/8.12.5) with ESMTP id r6J4r3cL026313 for <ietf@ietf.org>; Fri, 19 Jul 2013 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.7/8.14.7/Submit) id r6J4r3aH026279 for ietf@ietf.org; Fri, 19 Jul 2013 00:53:03 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201307190453.r6J4r3aH026279@rotala.raleigh.ibm.com>
Date: Fri, 19 Jul 2013 00:53:02 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13071904-3620-0000-0000-00000396D8A8
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Jul 2013 04:53:15 -0000

Total of 140 messages in the last 7 days.
 
script run at: Fri Jul 19 00:53:02 EDT 2013
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  5.71% |    8 |  8.08% |    97324 | hallam@gmail.com
  6.43% |    9 |  6.96% |    83850 | denghui02@gmail.com
  4.29% |    6 |  4.53% |    54622 | stefan.winter@restena.lu
  3.57% |    5 |  4.57% |    55051 | abdussalambaryun@gmail.com
  3.57% |    5 |  4.25% |    51253 | bernard_aboba@hotmail.com
  2.86% |    4 |  4.62% |    55730 | mary.h.barnes@gmail.com
  3.57% |    5 |  3.02% |    36363 | john-ietf@jck.com
  3.57% |    5 |  2.92% |    35224 | ted.lemon@nominum.com
  2.14% |    3 |  4.28% |    51567 | adrian@olddog.co.uk
  2.86% |    4 |  2.49% |    29961 | paul@nohats.ca
  2.86% |    4 |  2.42% |    29197 | hsantos@isdg.net
  2.86% |    4 |  2.41% |    29071 | johnl@taugh.com
  2.86% |    4 |  2.39% |    28792 | hartmans-ietf@mit.edu
  2.86% |    4 |  2.30% |    27727 | bob.hinden@gmail.com
  2.86% |    4 |  1.98% |    23903 | dhc@dcrocker.net
  2.14% |    3 |  1.90% |    22957 | dougb@dougbarton.us
  2.14% |    3 |  1.54% |    18617 | ynir@checkpoint.com
  1.43% |    2 |  1.93% |    23242 | yaojk@cnnic.cn
  2.14% |    3 |  1.20% |    14449 | randy@psg.com
  1.43% |    2 |  1.76% |    21270 | sanjay.mishra@verizon.com
  1.43% |    2 |  1.63% |    19615 | david.black@emc.com
  1.43% |    2 |  1.54% |    18571 | moore@network-heretics.com
  1.43% |    2 |  1.32% |    15922 | jason_livingood@cable.comcast.com
  1.43% |    2 |  1.29% |    15570 | ben@nostrum.com
  1.43% |    2 |  1.29% |    15566 | sm+ietf@elandsys.com
  1.43% |    2 |  1.12% |    13496 | brian.e.carpenter@gmail.com
  1.43% |    2 |  1.04% |    12564 | cos@aaaaa.org
  1.43% |    2 |  0.90% |    10822 | jnc@mercury.lcs.mit.edu
  1.43% |    2 |  0.84% |    10168 | ietf-secretariat@ietf.org
  0.71% |    1 |  1.17% |    14159 | mary.ietf.barnes@gmail.com
  0.71% |    1 |  1.09% |    13117 | housley@vigilsec.com
  0.71% |    1 |  1.08% |    13018 | ted.ietf@gmail.com
  0.71% |    1 |  1.00% |    12082 | sm@resistor.net
  0.71% |    1 |  0.99% |    11935 | afabbie@hotmail.com
  0.71% |    1 |  0.86% |    10393 | narten@us.ibm.com
  0.71% |    1 |  0.84% |    10151 | joseph.yee@gmail.com
  0.71% |    1 |  0.77% |     9267 | bdickson@verisign.com
  0.71% |    1 |  0.76% |     9199 | marka@isc.org
  0.71% |    1 |  0.74% |     8911 | l.wood@surrey.ac.uk
  0.71% |    1 |  0.72% |     8624 | stephen.farrell@cs.tcd.ie
  0.71% |    1 |  0.67% |     8033 | paf@frobbit.se
  0.71% |    1 |  0.66% |     7910 | margaretw42@gmail.com
  0.71% |    1 |  0.65% |     7858 | medel@globetel.com.ph
  0.71% |    1 |  0.65% |     7792 | paitken@cisco.com
  0.71% |    1 |  0.63% |     7594 | eburger@standardstrack.com
  0.71% |    1 |  0.62% |     7504 | d3e3e3@gmail.com
  0.71% |    1 |  0.62% |     7428 | pthaler@broadcom.com
  0.71% |    1 |  0.61% |     7345 | tom@dropfuse.com
  0.71% |    1 |  0.59% |     7124 | sob@harvard.edu
  0.71% |    1 |  0.59% |     7109 | warren@kumari.net
  0.71% |    1 |  0.58% |     6934 | zehn.cao@gmail.com
  0.71% |    1 |  0.57% |     6874 | wesley.george@twcable.com
  0.71% |    1 |  0.55% |     6656 | fernando@gont.com.ar
  0.71% |    1 |  0.55% |     6603 | iab-chair@iab.org
  0.71% |    1 |  0.54% |     6560 | arturo.servin@gmail.com
  0.71% |    1 |  0.54% |     6450 | ocl@gih.com
  0.71% |    1 |  0.52% |     6322 | duerst@it.aoyama.ac.jp
  0.71% |    1 |  0.50% |     6028 | andy@yumaworks.com
  0.71% |    1 |  0.49% |     5936 | faber@isi.edu
  0.71% |    1 |  0.48% |     5815 | chair@ietf.org
  0.71% |    1 |  0.46% |     5598 | scott.brim@gmail.com
  0.71% |    1 |  0.46% |     5568 | yding@cs.helsinki.fi
  0.71% |    1 |  0.46% |     5491 | jari.arkko@piuha.net
  0.71% |    1 |  0.44% |     5301 | andy@hxr.us
--------+------+--------+----------+------------------------
100.00% |  140 |100.00% |  1205153 | Total


From d3e3e3@gmail.com  Fri Jul 19 04:55:56 2013
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D18011E810A; Fri, 19 Jul 2013 04:55:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.213
X-Spam-Level: 
X-Spam-Status: No, score=-102.213 tagged_above=-999 required=5 tests=[AWL=-0.212, BAYES_00=-2.599, J_CHICKENPOX_34=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qB2ElY8Hu89r; Fri, 19 Jul 2013 04:55:56 -0700 (PDT)
Received: from mail-ob0-x233.google.com (mail-ob0-x233.google.com [IPv6:2607:f8b0:4003:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id AB7B711E8105; Fri, 19 Jul 2013 04:55:55 -0700 (PDT)
Received: by mail-ob0-f179.google.com with SMTP id xk17so5205360obc.10 for <multiple recipients>; Fri, 19 Jul 2013 04:55:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=bQ0MKVmTCbs+qZBoTSi99ilGf9pNCdODN9AolNIvgCU=; b=Y9NipZB+WAFWl2zEk7WBUSv6OHY2c9p0SLKvTcKFOiQYSCB7m+FvzTLkXkylakfuAw jg00W1h7JKMCJsKsuCTGf24BXrxPZY9x21c8iAzQyqCiaZ1Ffj6P9TexveLwB+msGCVH tOv9Lol+mzdiA/1T7beOHDoTbTTpvNKrmiG4LSavPKiwF0gOz+uLQ48aJ9Mfs8Ptx/pF bHu7JS57ZIJuTMP+dXTERseUqogRHNvIh89JCW5qNROP8V4Y2PSsQO+ChTO1NKKbcbrt MFj52L0TgqjlsiRS37EanE2QtnQDFGmXaBWiIE5RLe5jg3vO4QDQw5MqhZpq+k5BTcWH p6Jg==
X-Received: by 10.60.42.101 with SMTP id n5mr17617516oel.4.1374234955231; Fri, 19 Jul 2013 04:55:55 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.73.106 with HTTP; Fri, 19 Jul 2013 04:55:35 -0700 (PDT)
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712984AC753@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE712984AC753@MX15A.corp.emc.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Fri, 19 Jul 2013 07:55:35 -0400
Message-ID: <CAF4+nEEdg27WfotYaV0OzTgzN=_pnCxwbvm=JatizsHGJDkw9w@mail.gmail.com>
Subject: Re: Gen-ART review of draft-ietf-trill-directory-framework-05
To: "Black, David" <david.black@emc.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "ldunbar@huawei.com" <ldunbar@huawei.com>, "ietf@ietf.org" <ietf@ietf.org>, General Area Review Team <gen-art@ietf.org>, "Radia@alum.mit.edu" <Radia@alum.mit.edu>, "trill@ietf.org" <trill@ietf.org>, "igor@yahoo-inc.com" <igor@yahoo-inc.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Jul 2013 11:55:56 -0000

Hi David,

Thanks for the review. See responses below.

On Wed, Jul 17, 2013 at 7:54 PM, Black, David <david.black@emc.com> wrote:
> Document: draft-ietf-trill-directory-framework-05
> Reviewer: David L. Black
> Review Date: July 17, 2013
> IETF LC End Date: July 18, 2013
>
> Summary:
> This draft is on the right track but has open issues, described in the review.
>
> This draft describes a framework for using directory servers to provide
> address mappings (address -> destination RBridge) to TRILL Rbridges as an
> alternative to data plane learning and use of the TRILL ESADI protocol.
>
> The draft's generally well written and clear.  I found a couple of minor
> issues.

Thanks.

> Major issues: None.
>
> Minor issues:
>
> [1] The last bullet in Section 3.1 says:
>
>        - In an environment where VMs migrate, there is a higher chance
>          of cached information becoming invalid, causing traffic to be
>          black-holed by the ingress RBridge, that is, persistently sent
>          to the wrong egress RBridge. If VMs do not flood gratuitous
>          ARP/ND or VDP [802.1Qbg] messages upon arriving at new
>          locations, the ingress nodes might not have MAC entries for the
>          MAC of the newly arrived VMs, causing unknown address flooding.
>
> This is incorrect in multiple ways and should just be removed:

OK.

> - Persistent black-holing is rare in practice because all common
>         VM migration implementations issue the gratuitous messages.
> - VMs don't send the gratuitous messages, hypervisors do.
> - VDP is not flooded.  The receiver's always a bridge.
> - At least one common VM migration implementation actually uses a gratuitous
>         RARP, not ARP.
> - Flooding is done by the bridges and Rbridges, not the VMs.
>
> [2] There are some unfortunate notation problems in Section 5.1 that carry
> into the following sections, based on the logical data structure:
>
>    [{IP, MAC/VLAN, {list of attached RBridge nicknames}, {list of
>    interested RBridges}]
>
> - The first open curly brace ('{') is unmatched.
> - Subsequent text uses [IP or MAC/VLAN], IP/MAC/VLAN and MAC&VLAN,
>         none of which appear in that structure.

We'll try to clean that up.

> Nits/editorial comments:
>
> Section 1 - item 1 in the numbered list does not explain why it makes
> a directory approach attractive.  This should be added, as it is
> present for the other three items .

I suggest combining point 1 with the material just before the table
and re-numbering points 2-4 to be 1-3.

> Section 2 - Say that IS-IS is a routing protocol.
> The definition of Station should say that the node or virtual node
> is on a network.  Also, please define or explain "virtual node".

OK on the first two points. On "virtual node", that is only used in
the definition of "station" which is different from the definition of
"end station". However, looking through the document, there was only
one instance of "station" without "end" before it and that instance
was talking about end stations. So I propose to remove the definition
of "station" and to insert "end" before the one occurrence of
"station" in the body of the document not already preceded by "end".

> Section 3.2 - Add the number of entries to be learned to scenario #1
> in order to parallel the scenario # 2 discussion.

OK.

> Section 4 - remove "(distributed model)" from first paragraph,
> as it's not explained.

OK.

> Section 5.3, top of p.13:
>
>    therefore, there needs to be some mechanism by which RBridges that
>    have pulled information that has not expired can be informed when
>    that information changes or the like.
>
> "or the like" is vague.  I suggest "or becomes invalid for other
>  reasons".

OK.

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

> idnits 2.12.17 didn't find any nits that need attention.
>
> Thanks,
> --David
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> EMC Corporation, 176 South St., Hopkinton, MA  01748
> +1 (508) 293-7953             FAX: +1 (508) 293-7786
> david.black@emc.com        Mobile: +1 (978) 394-7754
> ----------------------------------------------------

From tbray@textuality.com  Fri Jul 19 08:02:40 2013
Return-Path: <tbray@textuality.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5031C11E82AC for <ietf@ietfa.amsl.com>; Fri, 19 Jul 2013 08:02:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.56
X-Spam-Level: 
X-Spam-Status: No, score=-2.56 tagged_above=-999 required=5 tests=[AWL=0.416,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AGrf3xUxJTgE for <ietf@ietfa.amsl.com>; Fri, 19 Jul 2013 08:02:36 -0700 (PDT)
Received: from mail-ve0-f180.google.com (mail-ve0-f180.google.com [209.85.128.180]) by ietfa.amsl.com (Postfix) with ESMTP id E9A9D11E82D1 for <ietf@ietf.org>; Fri, 19 Jul 2013 08:02:35 -0700 (PDT)
Received: by mail-ve0-f180.google.com with SMTP id pa12so3493875veb.11 for <ietf@ietf.org>; Fri, 19 Jul 2013 08:02:35 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=QO0dnSFFoE9iQFA3LEo6iEPz5ooCqBCzGCwcxmkb/q4=; b=UZ/dOYcjK6NiMnmkamTibF1CMaDSr69JWkM+piNsTZI4VjgQ2lqYxQ0wBudxZxNAj3 jUPbzJXeO8Gu11cYj7T5wfD6ABT2+YwigwwadOGQqMEkD3sWYWrvY0hYMBkzN0vo5Erv r7b+4KnSy7566zG1PQ/PDNzENIJViIMxlF5yjwxEIah4A2ptNR5l755ms+j+c7YOaO8D bQXYnDsC69/DwAEeWLFtMo4ca9YVGD0KNcY0ho77XLSSMe3sworywsUzSK5LVBU7oYfK ax04SyLBIZEs5OhtPSKfr7ZcJMLwK3lWT5bsfr+IUPfBjaGwG8z7VPWYfYvTDYviZ183 mzbQ==
MIME-Version: 1.0
X-Received: by 10.52.66.49 with SMTP id c17mr4994080vdt.94.1374246155449; Fri, 19 Jul 2013 08:02:35 -0700 (PDT)
Received: by 10.220.219.200 with HTTP; Fri, 19 Jul 2013 08:02:35 -0700 (PDT)
X-Originating-IP: [24.84.235.32]
Date: Fri, 19 Jul 2013 08:02:35 -0700
Message-ID: <CAHBU6ivQs+vsAtrV+Wqxwe2VDDjegYjU8aLPcAvaDkWWrrLBsw@mail.gmail.com>
Subject: Last call: draft-montemurro-gsma-imei-urn-16.txt
From: Tim Bray <tbray@textuality.com>
To: IETF-Discussion Discussion <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=20cf3071d00aee08ac04e1de9d32
X-Gm-Message-State: ALoCoQkPGwvXqFq9M6+PjOR+NzqYdB2R/ty8gAtRaYePf5MUH5pQ/wJCqqMcuqDSF6OtbaDu3fSi
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Jul 2013 15:02:40 -0000

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

Just wanted to point out that both Apple (for iOS) and Google (for Android)
have strongly discouraged the use of IMEI to identify devices for the
purposes of application software.  There are privacy, quality, and
availability issues with their use.  Apple has removed the ability of
developers to work with the (often IMEI-derived) =E2=80=9CUniversal Device =
ID=E2=80=9D (see
http://blogs.avg.com/mobile-2/apple-ios-7-puts-unique-device-ids/) and
Google has officially deprecated their use:
http://android-developers.blogspot.ca/2011/03/identifying-app-installations=
.html

I=E2=80=99m not sure from reading the draft what the goal of having this UR=
N
namespace is, but if it involves encouraging its use by application
developers, I=E2=80=99m pretty sure it=E2=80=99s a bad idea.

 -Tim

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

<div dir=3D"ltr"><div><div>Just wanted to point out that both Apple (for iO=
S) and Google (for Android) have strongly discouraged the use of IMEI to id=
entify devices for the purposes of application software.=C2=A0 There are pr=
ivacy, quality, and availability issues with their use.=C2=A0 Apple has rem=
oved the ability of developers to work with the (often IMEI-derived) =E2=80=
=9CUniversal Device ID=E2=80=9D (see <a href=3D"http://blogs.avg.com/mobile=
-2/apple-ios-7-puts-unique-device-ids/">http://blogs.avg.com/mobile-2/apple=
-ios-7-puts-unique-device-ids/</a>) and Google has officially deprecated th=
eir use: <a href=3D"http://android-developers.blogspot.ca/2011/03/identifyi=
ng-app-installations.html">http://android-developers.blogspot.ca/2011/03/id=
entifying-app-installations.html</a><br>
<br></div>I=E2=80=99m not sure from reading the draft what the goal of havi=
ng this URN namespace is, but if it involves encouraging its use by applica=
tion developers, I=E2=80=99m pretty sure it=E2=80=99s a bad idea.<br><br></=
div>=C2=A0-Tim<br></div>

--20cf3071d00aee08ac04e1de9d32--

From david.black@emc.com  Fri Jul 19 06:16:49 2013
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D108D11E812A; Fri, 19 Jul 2013 06:16:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_34=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hriDw+FOmXDG; Fri, 19 Jul 2013 06:16:44 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id EC15F11E8117; Fri, 19 Jul 2013 06:16:43 -0700 (PDT)
Received: from hop04-l1d11-si04.isus.emc.com (HOP04-L1D11-SI04.isus.emc.com [10.254.111.24]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r6JDGN9i015225 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 19 Jul 2013 09:16:24 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd04.lss.emc.com [10.254.222.226]) by hop04-l1d11-si04.isus.emc.com (RSA Interceptor); Fri, 19 Jul 2013 09:16:03 -0400
Received: from mxhub31.corp.emc.com (mxhub31.corp.emc.com [128.222.70.171]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r6JDG2bh015134; Fri, 19 Jul 2013 09:16:02 -0400
Received: from mx15a.corp.emc.com ([169.254.1.184]) by mxhub31.corp.emc.com ([128.222.70.171]) with mapi; Fri, 19 Jul 2013 09:16:02 -0400
From: "Black, David" <david.black@emc.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Date: Fri, 19 Jul 2013 09:16:00 -0400
Subject: RE: Gen-ART review of draft-ietf-trill-directory-framework-05
Thread-Topic: Gen-ART review of draft-ietf-trill-directory-framework-05
Thread-Index: Ac6EdvpzYre5W29/SUuNLTq5/fBXxwACvX6w
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712984AC9E9@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE712984AC753@MX15A.corp.emc.com> <CAF4+nEEdg27WfotYaV0OzTgzN=_pnCxwbvm=JatizsHGJDkw9w@mail.gmail.com>
In-Reply-To: <CAF4+nEEdg27WfotYaV0OzTgzN=_pnCxwbvm=JatizsHGJDkw9w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Fri, 19 Jul 2013 08:02:44 -0700
Cc: "ldunbar@huawei.com" <ldunbar@huawei.com>, "ietf@ietf.org" <ietf@ietf.org>, General Area Review Team <gen-art@ietf.org>, "Radia@alum.mit.edu" <Radia@alum.mit.edu>, "trill@ietf.org" <trill@ietf.org>, "Black,  David" <david.black@emc.com>, "igor@yahoo-inc.com" <igor@yahoo-inc.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Jul 2013 13:16:50 -0000

Hi Donald,

All of your responses are fine with me.

Thanks,
--David

> -----Original Message-----
> From: Donald Eastlake [mailto:d3e3e3@gmail.com]
> Sent: Friday, July 19, 2013 7:56 AM
> To: Black, David
> Cc: ldunbar@huawei.com; Radia@alum.mit.edu; igor@yahoo-inc.com; General A=
rea
> Review Team; trill@ietf.org; ietf@ietf.org; Ted Lemon
> Subject: Re: Gen-ART review of draft-ietf-trill-directory-framework-05
>=20
> Hi David,
>=20
> Thanks for the review. See responses below.
>=20
> On Wed, Jul 17, 2013 at 7:54 PM, Black, David <david.black@emc.com> wrote=
:
> > Document: draft-ietf-trill-directory-framework-05
> > Reviewer: David L. Black
> > Review Date: July 17, 2013
> > IETF LC End Date: July 18, 2013
> >
> > Summary:
> > This draft is on the right track but has open issues, described in the
> review.
> >
> > This draft describes a framework for using directory servers to provide
> > address mappings (address -> destination RBridge) to TRILL Rbridges as =
an
> > alternative to data plane learning and use of the TRILL ESADI protocol.
> >
> > The draft's generally well written and clear.  I found a couple of mino=
r
> > issues.
>=20
> Thanks.
>=20
> > Major issues: None.
> >
> > Minor issues:
> >
> > [1] The last bullet in Section 3.1 says:
> >
> >        - In an environment where VMs migrate, there is a higher chance
> >          of cached information becoming invalid, causing traffic to be
> >          black-holed by the ingress RBridge, that is, persistently sent
> >          to the wrong egress RBridge. If VMs do not flood gratuitous
> >          ARP/ND or VDP [802.1Qbg] messages upon arriving at new
> >          locations, the ingress nodes might not have MAC entries for th=
e
> >          MAC of the newly arrived VMs, causing unknown address flooding=
.
> >
> > This is incorrect in multiple ways and should just be removed:
>=20
> OK.
>=20
> > - Persistent black-holing is rare in practice because all common
> >         VM migration implementations issue the gratuitous messages.
> > - VMs don't send the gratuitous messages, hypervisors do.
> > - VDP is not flooded.  The receiver's always a bridge.
> > - At least one common VM migration implementation actually uses a gratu=
itous
> >         RARP, not ARP.
> > - Flooding is done by the bridges and Rbridges, not the VMs.
> >
> > [2] There are some unfortunate notation problems in Section 5.1 that ca=
rry
> > into the following sections, based on the logical data structure:
> >
> >    [{IP, MAC/VLAN, {list of attached RBridge nicknames}, {list of
> >    interested RBridges}]
> >
> > - The first open curly brace ('{') is unmatched.
> > - Subsequent text uses [IP or MAC/VLAN], IP/MAC/VLAN and MAC&VLAN,
> >         none of which appear in that structure.
>=20
> We'll try to clean that up.
>=20
> > Nits/editorial comments:
> >
> > Section 1 - item 1 in the numbered list does not explain why it makes
> > a directory approach attractive.  This should be added, as it is
> > present for the other three items .
>=20
> I suggest combining point 1 with the material just before the table
> and re-numbering points 2-4 to be 1-3.
>=20
> > Section 2 - Say that IS-IS is a routing protocol.
> > The definition of Station should say that the node or virtual node
> > is on a network.  Also, please define or explain "virtual node".
>=20
> OK on the first two points. On "virtual node", that is only used in
> the definition of "station" which is different from the definition of
> "end station". However, looking through the document, there was only
> one instance of "station" without "end" before it and that instance
> was talking about end stations. So I propose to remove the definition
> of "station" and to insert "end" before the one occurrence of
> "station" in the body of the document not already preceded by "end".
>=20
> > Section 3.2 - Add the number of entries to be learned to scenario #1
> > in order to parallel the scenario # 2 discussion.
>=20
> OK.
>=20
> > Section 4 - remove "(distributed model)" from first paragraph,
> > as it's not explained.
>=20
> OK.
>=20
> > Section 5.3, top of p.13:
> >
> >    therefore, there needs to be some mechanism by which RBridges that
> >    have pulled information that has not expired can be informed when
> >    that information changes or the like.
> >
> > "or the like" is vague.  I suggest "or becomes invalid for other
> >  reasons".
>=20
> OK.
>=20
> Thanks,
> Donald
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>  155 Beaver Street, Milford, MA 01757 USA
>  d3e3e3@gmail.com
>=20
> > idnits 2.12.17 didn't find any nits that need attention.
> >
> > Thanks,
> > --David
> > ----------------------------------------------------
> > David L. Black, Distinguished Engineer
> > EMC Corporation, 176 South St., Hopkinton, MA  01748
> > +1 (508) 293-7953             FAX: +1 (508) 293-7786
> > david.black@emc.com        Mobile: +1 (978) 394-7754
> > ----------------------------------------------------


From prvs=19120f36ae=aallen@blackberry.com  Fri Jul 19 08:38:45 2013
Return-Path: <prvs=19120f36ae=aallen@blackberry.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B5AA11E82CD for <ietf@ietfa.amsl.com>; Fri, 19 Jul 2013 08:38:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.9
X-Spam-Level: 
X-Spam-Status: No, score=-5.9 tagged_above=-999 required=5 tests=[AWL=0.698, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5LyUq+3CxXju for <ietf@ietfa.amsl.com>; Fri, 19 Jul 2013 08:38:41 -0700 (PDT)
Received: from mhs061cnc.rim.net (mhs061cnc.rim.net [208.65.73.35]) by ietfa.amsl.com (Postfix) with ESMTP id 28B0221F9E62 for <ietf@ietf.org>; Fri, 19 Jul 2013 08:38:29 -0700 (PDT)
X-AuditID: 0a412830-b7fa06d000003f99-74-51e95d6c391a
Received: from XCT102ADS.rim.net (xct102ads.rim.net [10.67.111.43]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by mhs061cnc.rim.net (SBG) with SMTP id 20.D7.16281.D6D59E15; Fri, 19 Jul 2013 10:38:21 -0500 (CDT)
Received: from XMB104ADS.rim.net ([fe80::2494:a63d:e3:723b]) by XCT102ADS.rim.net ([fe80::4806:2e1d:2b7c:cfdf%22]) with mapi id 14.02.0328.009; Fri, 19 Jul 2013 10:38:20 -0500
From: Andrew Allen <aallen@blackberry.com>
To: "tbray@textuality.com" <tbray@textuality.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
Thread-Topic: Last call: draft-montemurro-gsma-imei-urn-16.txt
Thread-Index: AQHOhJEO4fYTwuVTOkCw8MDTXs0bMZlsItsK
Date: Fri, 19 Jul 2013 15:38:20 +0000
Message-ID: <BBF5DDFE515C3946BC18D733B20DAD2338DD1784@XMB104ADS.rim.net>
In-Reply-To: <CAHBU6ivQs+vsAtrV+Wqxwe2VDDjegYjU8aLPcAvaDkWWrrLBsw@mail.gmail.com>
Accept-Language: en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.67.110.252]
Content-Type: multipart/alternative; boundary="_000_BBF5DDFE515C3946BC18D733B20DAD2338DD1784XMB104ADSrimnet_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrLKsWRmVeSWpSXmKPExsXC5ZyvrZsb+zLQYMkVbotnG+ezWCz9M5/F gcljyZKfTB6Xlk5mDmCKamC0SUosKQvOTM/Tt7NJzMvLL0ksSVVISS1OtlXySU1PzFEIKMos S0yuVHDJLE7OSczMTS1SUshMsVUyUVIoyElMTs1NzSuxVUosKEjNS1Gy41LAADZAZZl5Cql5 yfkpmXnptkqewf66FhamlrqGSna6CZ08GccOXmEpWKBasfP8J8YGxgkqXYycHBICJhJN6zex QthiEhfurWfrYuTiEBJoY5Loe9XBDuFsZpSY0fuTGaSKTUBLYv/h6UwgtohAiMSapg4wW1jA VuLy6T+MEHE7ie8HL7FA2EYSc9d9AOtlEVCVOPrnKVA9BwevgIfEmW0KIGFOgUCJy4d3gpUz CshK7D57HWwks4C4xK0n85kgjhOQWLLnPDOELSrx8vE/qKMVJR63dLNA1OdLvLu7D6yeV0BQ 4uTMJywTGIVnIRk1C0nZLCRls4AuYhbQlFi/Sx+iRFFiSvdDdghbQ6J1zlx2ZPEFjOyrGAVz M4oNzAyT85L1ijJz9fJSSzYxgpKEo4bBDsb37y0OMQpwMCrx8C7xfBkoxJpYVlyZe4hRgoNZ SYT3V/KLQCHelMTKqtSi/Pii0pzU4kOMQcDwmcgsxZ2cD0xgeSXxxgYGRHKUxHmtz54NFBJI Byar7NTUgtQimKFMHJwgS7mkRIqBKSe1KLG0JCMelBjji4GpUaqBcbEQd+TjIImJ7H6OL00+ 7F7t4nmqfltruv3dd0sCco8vFJ6V3fstNdk9qZ3/+4LTCju2siUeVJ0pdWn5PoeOO7fm8Ru/ cJvlzcid+rP4EWcUd+e/1OleOeum5lvHP9c89ePqJ75XP7763bRwMJ+4eOXFXysaD2xQ97jH 6njmzbKbWv8eVLCsfKDEUpyRaKjFXFScCAAeRwdoYAMAAA==
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Jul 2013 15:38:45 -0000

--_000_BBF5DDFE515C3946BC18D733B20DAD2338DD1784XMB104ADSrimnet_
Content-Type: text/plain; charset="utf-8"
content-transfer-encoding: base64

DQpUaW0NCg0KSSBzdWdnZXN0IHlvdSBhbHNvIHJlYWQNCmh0dHA6Ly9kYXRhdHJhY2tlci5p
ZXRmLm9yZy9kb2MvZHJhZnQtYWxsZW4tZGlzcGF0Y2gtaW1laS11cm4tYXMtaW5zdGFuY2Vp
ZC8NCg0KVGhhdCB3aWxsIGV4cGxhaW4gdGhlIHByaW1hcnkgYXBwbGljYXRpb24gb2YgdGhp
cyBVUk4gd2hpY2ggaXMgaW50ZW5kZWQgZm9yIHVzZSBpbiB0aGUgM0dQUCBjZWxsdWxhciBz
dGFuZGFyZHMuDQoNCkFuZHJldw0KDQpGcm9tOiBUaW0gQnJheSBbbWFpbHRvOnRicmF5QHRl
eHR1YWxpdHkuY29tXQ0KU2VudDogRnJpZGF5LCBKdWx5IDE5LCAyMDEzIDEwOjAyIEFNIENl
bnRyYWwgU3RhbmRhcmQgVGltZQ0KVG86IElFVEYtRGlzY3Vzc2lvbiBEaXNjdXNzaW9uIDxp
ZXRmQGlldGYub3JnPg0KU3ViamVjdDogTGFzdCBjYWxsOiBkcmFmdC1tb250ZW11cnJvLWdz
bWEtaW1laS11cm4tMTYudHh0DQoNCkp1c3Qgd2FudGVkIHRvIHBvaW50IG91dCB0aGF0IGJv
dGggQXBwbGUgKGZvciBpT1MpIGFuZCBHb29nbGUgKGZvciBBbmRyb2lkKSBoYXZlIHN0cm9u
Z2x5IGRpc2NvdXJhZ2VkIHRoZSB1c2Ugb2YgSU1FSSB0byBpZGVudGlmeSBkZXZpY2VzIGZv
ciB0aGUgcHVycG9zZXMgb2YgYXBwbGljYXRpb24gc29mdHdhcmUuICBUaGVyZSBhcmUgcHJp
dmFjeSwgcXVhbGl0eSwgYW5kIGF2YWlsYWJpbGl0eSBpc3N1ZXMgd2l0aCB0aGVpciB1c2Uu
ICBBcHBsZSBoYXMgcmVtb3ZlZCB0aGUgYWJpbGl0eSBvZiBkZXZlbG9wZXJzIHRvIHdvcmsg
d2l0aCB0aGUgKG9mdGVuIElNRUktZGVyaXZlZCkg4oCcVW5pdmVyc2FsIERldmljZSBJROKA
nSAoc2VlIGh0dHA6Ly9ibG9ncy5hdmcuY29tL21vYmlsZS0yL2FwcGxlLWlvcy03LXB1dHMt
dW5pcXVlLWRldmljZS1pZHMvKSBhbmQgR29vZ2xlIGhhcyBvZmZpY2lhbGx5IGRlcHJlY2F0
ZWQgdGhlaXIgdXNlOiBodHRwOi8vYW5kcm9pZC1kZXZlbG9wZXJzLmJsb2dzcG90LmNhLzIw
MTEvMDMvaWRlbnRpZnlpbmctYXBwLWluc3RhbGxhdGlvbnMuaHRtbA0KDQpJ4oCZbSBub3Qg
c3VyZSBmcm9tIHJlYWRpbmcgdGhlIGRyYWZ0IHdoYXQgdGhlIGdvYWwgb2YgaGF2aW5nIHRo
aXMgVVJOIG5hbWVzcGFjZSBpcywgYnV0IGlmIGl0IGludm9sdmVzIGVuY291cmFnaW5nIGl0
cyB1c2UgYnkgYXBwbGljYXRpb24gZGV2ZWxvcGVycywgSeKAmW0gcHJldHR5IHN1cmUgaXTi
gJlzIGEgYmFkIGlkZWEuDQoNCiAtVGltDQoNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KVGhpcyB0cmFu
c21pc3Npb24gKGluY2x1ZGluZyBhbnkgYXR0YWNobWVudHMpIG1heSBjb250YWluIGNvbmZp
ZGVudGlhbCBpbmZvcm1hdGlvbiwgcHJpdmlsZWdlZCBtYXRlcmlhbCAoaW5jbHVkaW5nIG1h
dGVyaWFsIHByb3RlY3RlZCBieSB0aGUgc29saWNpdG9yLWNsaWVudCBvciBvdGhlciBhcHBs
aWNhYmxlIHByaXZpbGVnZXMpLCBvciBjb25zdGl0dXRlIG5vbi1wdWJsaWMgaW5mb3JtYXRp
b24uIEFueSB1c2Ugb2YgdGhpcyBpbmZvcm1hdGlvbiBieSBhbnlvbmUgb3RoZXIgdGhhbiB0
aGUgaW50ZW5kZWQgcmVjaXBpZW50IGlzIHByb2hpYml0ZWQuIElmIHlvdSBoYXZlIHJlY2Vp
dmVkIHRoaXMgdHJhbnNtaXNzaW9uIGluIGVycm9yLCBwbGVhc2UgaW1tZWRpYXRlbHkgcmVw
bHkgdG8gdGhlIHNlbmRlciBhbmQgZGVsZXRlIHRoaXMgaW5mb3JtYXRpb24gZnJvbSB5b3Vy
IHN5c3RlbS4gVXNlLCBkaXNzZW1pbmF0aW9uLCBkaXN0cmlidXRpb24sIG9yIHJlcHJvZHVj
dGlvbiBvZiB0aGlzIHRyYW5zbWlzc2lvbiBieSB1bmludGVuZGVkIHJlY2lwaWVudHMgaXMg
bm90IGF1dGhvcml6ZWQgYW5kIG1heSBiZSB1bmxhd2Z1bC4NCg==

--_000_BBF5DDFE515C3946BC18D733B20DAD2338DD1784XMB104ADSrimnet_
Content-Type: text/html; charset="utf-8"
content-transfer-encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5Pg0KPGZvbnQg
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxicj4NClRpbTxicj4N
Cjxicj4NCkkgc3VnZ2VzdCB5b3UgYWxzbyByZWFkPGJyPg0KaHR0cDovL2RhdGF0cmFja2Vy
LmlldGYub3JnL2RvYy9kcmFmdC1hbGxlbi1kaXNwYXRjaC1pbWVpLXVybi1hcy1pbnN0YW5j
ZWlkLzxicj4NCjxicj4NClRoYXQgd2lsbCBleHBsYWluIHRoZSBwcmltYXJ5IGFwcGxpY2F0
aW9uIG9mIHRoaXMgVVJOIHdoaWNoIGlzIGludGVuZGVkIGZvciB1c2UgaW4gdGhlIDNHUFAg
Y2VsbHVsYXIgc3RhbmRhcmRzLjxicj4NCjxicj4NCkFuZHJldzwvZm9udD48YnI+DQombmJz
cDs8YnI+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNCNUM0
REYgMS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbiI+DQo8Zm9udCBzdHlsZT0iZm9u
dC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fu
cy1zZXJpZiZxdW90OyI+PGI+RnJvbTwvYj46IFRpbSBCcmF5IFttYWlsdG86dGJyYXlAdGV4
dHVhbGl0eS5jb21dDQo8YnI+DQo8Yj5TZW50PC9iPjogRnJpZGF5LCBKdWx5IDE5LCAyMDEz
IDEwOjAyIEFNIENlbnRyYWwgU3RhbmRhcmQgVGltZTxicj4NCjxiPlRvPC9iPjogSUVURi1E
aXNjdXNzaW9uIERpc2N1c3Npb24gJmx0O2lldGZAaWV0Zi5vcmcmZ3Q7IDxicj4NCjxiPlN1
YmplY3Q8L2I+OiBMYXN0IGNhbGw6IGRyYWZ0LW1vbnRlbXVycm8tZ3NtYS1pbWVpLXVybi0x
Ni50eHQgPGJyPg0KPC9mb250PiZuYnNwOzxicj4NCjwvZGl2Pg0KPGRpdiBkaXI9Imx0ciI+
DQo8ZGl2Pg0KPGRpdj5KdXN0IHdhbnRlZCB0byBwb2ludCBvdXQgdGhhdCBib3RoIEFwcGxl
IChmb3IgaU9TKSBhbmQgR29vZ2xlIChmb3IgQW5kcm9pZCkgaGF2ZSBzdHJvbmdseSBkaXNj
b3VyYWdlZCB0aGUgdXNlIG9mIElNRUkgdG8gaWRlbnRpZnkgZGV2aWNlcyBmb3IgdGhlIHB1
cnBvc2VzIG9mIGFwcGxpY2F0aW9uIHNvZnR3YXJlLiZuYnNwOyBUaGVyZSBhcmUgcHJpdmFj
eSwgcXVhbGl0eSwgYW5kIGF2YWlsYWJpbGl0eSBpc3N1ZXMgd2l0aCB0aGVpciB1c2UuJm5i
c3A7IEFwcGxlDQogaGFzIHJlbW92ZWQgdGhlIGFiaWxpdHkgb2YgZGV2ZWxvcGVycyB0byB3
b3JrIHdpdGggdGhlIChvZnRlbiBJTUVJLWRlcml2ZWQpIOKAnFVuaXZlcnNhbCBEZXZpY2Ug
SUTigJ0gKHNlZQ0KPGEgaHJlZj0iaHR0cDovL2Jsb2dzLmF2Zy5jb20vbW9iaWxlLTIvYXBw
bGUtaW9zLTctcHV0cy11bmlxdWUtZGV2aWNlLWlkcy8iPmh0dHA6Ly9ibG9ncy5hdmcuY29t
L21vYmlsZS0yL2FwcGxlLWlvcy03LXB1dHMtdW5pcXVlLWRldmljZS1pZHMvPC9hPikgYW5k
IEdvb2dsZSBoYXMgb2ZmaWNpYWxseSBkZXByZWNhdGVkIHRoZWlyIHVzZToNCjxhIGhyZWY9
Imh0dHA6Ly9hbmRyb2lkLWRldmVsb3BlcnMuYmxvZ3Nwb3QuY2EvMjAxMS8wMy9pZGVudGlm
eWluZy1hcHAtaW5zdGFsbGF0aW9ucy5odG1sIj4NCmh0dHA6Ly9hbmRyb2lkLWRldmVsb3Bl
cnMuYmxvZ3Nwb3QuY2EvMjAxMS8wMy9pZGVudGlmeWluZy1hcHAtaW5zdGFsbGF0aW9ucy5o
dG1sPC9hPjxicj4NCjxicj4NCjwvZGl2Pg0KSeKAmW0gbm90IHN1cmUgZnJvbSByZWFkaW5n
IHRoZSBkcmFmdCB3aGF0IHRoZSBnb2FsIG9mIGhhdmluZyB0aGlzIFVSTiBuYW1lc3BhY2Ug
aXMsIGJ1dCBpZiBpdCBpbnZvbHZlcyBlbmNvdXJhZ2luZyBpdHMgdXNlIGJ5IGFwcGxpY2F0
aW9uIGRldmVsb3BlcnMsIEnigJltIHByZXR0eSBzdXJlIGl04oCZcyBhIGJhZCBpZGVhLjxi
cj4NCjxicj4NCjwvZGl2Pg0KJm5ic3A7LVRpbTxicj4NCjwvZGl2Pg0KLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tIDxicj4NClRoaXMgdHJhbnNtaXNzaW9uIChpbmNsdWRpbmcgYW55IGF0dGFjaG1lbnRz
KSBtYXkgY29udGFpbiBjb25maWRlbnRpYWwgaW5mb3JtYXRpb24sIHByaXZpbGVnZWQgbWF0
ZXJpYWwgKGluY2x1ZGluZyBtYXRlcmlhbCBwcm90ZWN0ZWQgYnkgdGhlIHNvbGljaXRvci1j
bGllbnQgb3Igb3RoZXIgYXBwbGljYWJsZSBwcml2aWxlZ2VzKSwgb3IgY29uc3RpdHV0ZSBu
b24tcHVibGljIGluZm9ybWF0aW9uLiBBbnkgdXNlIG9mIHRoaXMgaW5mb3JtYXRpb24gYnkg
YW55b25lIG90aGVyIHRoYW4gdGhlIGludGVuZGVkIHJlY2lwaWVudCBpcyBwcm9oaWJpdGVk
LiBJZiB5b3UgaGF2ZSByZWNlaXZlZCB0aGlzIHRyYW5zbWlzc2lvbiBpbiBlcnJvciwgcGxl
YXNlIGltbWVkaWF0ZWx5IHJlcGx5IHRvIHRoZSBzZW5kZXIgYW5kIGRlbGV0ZSB0aGlzIGlu
Zm9ybWF0aW9uIGZyb20geW91ciBzeXN0ZW0uIFVzZSwgZGlzc2VtaW5hdGlvbiwgZGlzdHJp
YnV0aW9uLCBvciByZXByb2R1Y3Rpb24gb2YgdGhpcyB0cmFuc21pc3Npb24gYnkgdW5pbnRl
bmRlZCByZWNpcGllbnRzIGlzIG5vdCBhdXRob3JpemVkIGFuZCBtYXkgYmUgdW5sYXdmdWwu
DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_BBF5DDFE515C3946BC18D733B20DAD2338DD1784XMB104ADSrimnet_--

From tbray@textuality.com  Fri Jul 19 08:58:45 2013
Return-Path: <tbray@textuality.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77D1321F9A16 for <ietf@ietfa.amsl.com>; Fri, 19 Jul 2013 08:58:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Level: 
X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[AWL=0.357,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bw2bPhG6zg7C for <ietf@ietfa.amsl.com>; Fri, 19 Jul 2013 08:58:39 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id EA96711E82AA for <ietf@ietf.org>; Fri, 19 Jul 2013 08:58:38 -0700 (PDT)
Received: by mail-vc0-f172.google.com with SMTP id m17so1632943vca.3 for <ietf@ietf.org>; Fri, 19 Jul 2013 08:58:37 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=95DgxS0VlWDcDJV4bqXkW4MlbVUe66wVDQ8u14QUnHM=; b=MVf6mUboXpgTaCwE0canyd5Nrr8Ka0Spw2jvQqu0JjZHsP1FOvZpXjMv8ikUL/kP0t DVkytzEh8/8/AyouDMnqjeu8Ms7XkmL4ENcPyZB6xx+z8LTs8qZ2b9NuoQepco6/4lPf 9Db5VhPeBl5Y0BESrv+p/X5FtMZ2t9ywWdcbTrG+peonrp3UdlZzvdhhp/5IpgS0l5Ku NETVsFKIENIKKhzg9fUBm+nUfsDXfDcByy8L8gC3RnsMwYyFKkhXksjYxIsFFJJOy9zu HVPxmFIi/pCxTw7/9Dyun4PKogRz5V+0u4A69PFnI4LXJlcvP78LzxGEXzC/Te+TkMpu vFfQ==
MIME-Version: 1.0
X-Received: by 10.58.2.137 with SMTP id 9mr6040166veu.50.1374249517214; Fri, 19 Jul 2013 08:58:37 -0700 (PDT)
Received: by 10.220.219.200 with HTTP; Fri, 19 Jul 2013 08:58:37 -0700 (PDT)
X-Originating-IP: [24.84.235.32]
In-Reply-To: <BBF5DDFE515C3946BC18D733B20DAD2338DD1784@XMB104ADS.rim.net>
References: <CAHBU6ivQs+vsAtrV+Wqxwe2VDDjegYjU8aLPcAvaDkWWrrLBsw@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD2338DD1784@XMB104ADS.rim.net>
Date: Fri, 19 Jul 2013 08:58:37 -0700
Message-ID: <CAHBU6ivC37fzO1oC=Ow3EGfBUt2GEsLRy3YWn6OZa9tTTTNZpQ@mail.gmail.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
From: Tim Bray <tbray@textuality.com>
To: Andrew Allen <aallen@blackberry.com>
Content-Type: multipart/alternative; boundary=047d7b2e75cc4e7a9c04e1df66cf
X-Gm-Message-State: ALoCoQnOhxwANX7inbYiDb+dwyeGEc/3MOcH6Ea3WDbxZSz5WAuip8tAHWe2Ccy3yzVWgB505tIL
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Jul 2013 15:58:45 -0000

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

On Fri, Jul 19, 2013 at 8:38 AM, Andrew Allen <aallen@blackberry.com> wrote=
:

>  I suggest you also read
>
> http://datatracker.ietf.org/doc/draft-allen-dispatch-imei-urn-as-instance=
id/
>

Quoting from that document: =E2=80=9CIf a URN scheme other than UUID is use=
d, the
UA MUST only use URNs for which an RFC (from the IETF stream) defines how
the specific URN needs to be constructed...=E2=80=9D

Now, I=E2=80=99m not an expert in the 3GPP world; but the suggestion in tha=
t
extract that UUIDs are a better choice than a (shaky, unreliable,
privacy-problematic) device identifier certainly rings true for those of us
who think at the apps level.  -T



>
> That will explain the primary application of this URN which is intended
> for use in the 3GPP cellular standards.
>
> Andrew
>
>  *From*: Tim Bray [mailto:tbray@textuality.com]
> *Sent*: Friday, July 19, 2013 10:02 AM Central Standard Time
> *To*: IETF-Discussion Discussion <ietf@ietf.org>
> *Subject*: Last call: draft-montemurro-gsma-imei-urn-16.txt
>
>   Just wanted to point out that both Apple (for iOS) and Google (for
> Android) have strongly discouraged the use of IMEI to identify devices fo=
r
> the purposes of application software.  There are privacy, quality, and
> availability issues with their use.  Apple has removed the ability of
> developers to work with the (often IMEI-derived) =E2=80=9CUniversal Devic=
e ID=E2=80=9D (see
> http://blogs.avg.com/mobile-2/apple-ios-7-puts-unique-device-ids/) and
> Google has officially deprecated their use:
> http://android-developers.blogspot.ca/2011/03/identifying-app-installatio=
ns.html
>
>  I=E2=80=99m not sure from reading the draft what the goal of having this=
 URN
> namespace is, but if it involves encouraging its use by application
> developers, I=E2=80=99m pretty sure it=E2=80=99s a bad idea.
>
>   -Tim
>  ---------------------------------------------------------------------
> This transmission (including any attachments) may contain confidential
> information, privileged material (including material protected by the
> solicitor-client or other applicable privileges), or constitute non-publi=
c
> information. Any use of this information by anyone other than the intende=
d
> recipient is prohibited. If you have received this transmission in error,
> please immediately reply to the sender and delete this information from
> your system. Use, dissemination, distribution, or reproduction of this
> transmission by unintended recipients is not authorized and may be
> unlawful.
>

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

<div dir=3D"ltr">On Fri, Jul 19, 2013 at 8:38 AM, Andrew Allen <span dir=3D=
"ltr">&lt;<a href=3D"mailto:aallen@blackberry.com" target=3D"_blank">aallen=
@blackberry.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div cl=
ass=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">



<div>
<font style=3D"font-size:11pt;font-family:&quot;Calibri&quot;,&quot;sans-se=
rif&quot;;color:rgb(31,73,125)">I suggest you also read<br>
<a href=3D"http://datatracker.ietf.org/doc/draft-allen-dispatch-imei-urn-as=
-instanceid/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-allen=
-dispatch-imei-urn-as-instanceid/</a><br></font></div></blockquote><div><br=
>
</div><div>Quoting from that document: =E2=80=9CIf a URN scheme other than =
UUID is used, the UA MUST only use URNs for which an RFC (from the IETF str=
eam) defines how the specific URN needs to be constructed...=E2=80=9D<br><b=
r></div><div>
Now, I=E2=80=99m not an expert in the 3GPP world; but the suggestion in tha=
t extract that UUIDs are a better choice than a (shaky, unreliable, privacy=
-problematic) device identifier certainly rings true for those of us who th=
ink at the apps level.=C2=A0 -T<br>
</div><div><br>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex=
"><div><font style=3D"font-size:11pt;font-family:&quot;Calibri&quot;,&quot;=
sans-serif&quot;;color:rgb(31,73,125)">
<br>
That will explain the primary application of this URN which is intended for=
 use in the 3GPP cellular standards.<br>
<br>
Andrew</font><br>
=C2=A0<br>
<div style=3D"border-width:1pt medium medium;border-style:solid none none;b=
order-color:rgb(181,196,223) -moz-use-text-color -moz-use-text-color;paddin=
g:3pt 0in 0in">
<font style=3D"font-size:10pt;font-family:&quot;Tahoma&quot;,&quot;sans-ser=
if&quot;"><b>From</b>: Tim Bray [mailto:<a href=3D"mailto:tbray@textuality.=
com" target=3D"_blank">tbray@textuality.com</a>]
<br>
<b>Sent</b>: Friday, July 19, 2013 10:02 AM Central Standard Time<br>
<b>To</b>: IETF-Discussion Discussion &lt;<a href=3D"mailto:ietf@ietf.org" =
target=3D"_blank">ietf@ietf.org</a>&gt; <br>
<b>Subject</b>: Last call: draft-montemurro-gsma-imei-urn-16.txt <br>
</font>=C2=A0<br>
</div><div class=3D"im">
<div dir=3D"ltr">
<div>
<div>Just wanted to point out that both Apple (for iOS) and Google (for And=
roid) have strongly discouraged the use of IMEI to identify devices for the=
 purposes of application software.=C2=A0 There are privacy, quality, and av=
ailability issues with their use.=C2=A0 Apple
 has removed the ability of developers to work with the (often IMEI-derived=
) =E2=80=9CUniversal Device ID=E2=80=9D (see
<a href=3D"http://blogs.avg.com/mobile-2/apple-ios-7-puts-unique-device-ids=
/" target=3D"_blank">http://blogs.avg.com/mobile-2/apple-ios-7-puts-unique-=
device-ids/</a>) and Google has officially deprecated their use:
<a href=3D"http://android-developers.blogspot.ca/2011/03/identifying-app-in=
stallations.html" target=3D"_blank">
http://android-developers.blogspot.ca/2011/03/identifying-app-installations=
.html</a><br>
<br>
</div>
I=E2=80=99m not sure from reading the draft what the goal of having this UR=
N namespace is, but if it involves encouraging its use by application devel=
opers, I=E2=80=99m pretty sure it=E2=80=99s a bad idea.<br>
<br>
</div>
=C2=A0-Tim<br>
</div></div>
--------------------------------------------------------------------- <br>
This transmission (including any attachments) may contain confidential info=
rmation, privileged material (including material protected by the solicitor=
-client or other applicable privileges), or constitute non-public informati=
on. Any use of this information by anyone other than the intended recipient=
 is prohibited. If you have received this transmission in error, please imm=
ediately reply to the sender and delete this information from your system. =
Use, dissemination, distribution, or reproduction of this transmission by u=
nintended recipients is not authorized and may be unlawful.
</div>

</blockquote></div><br></div></div>

--047d7b2e75cc4e7a9c04e1df66cf--

From martin.thomson@gmail.com  Fri Jul 19 09:25:26 2013
Return-Path: <martin.thomson@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C1CE11E8151 for <ietf@ietfa.amsl.com>; Fri, 19 Jul 2013 09:25:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.263
X-Spam-Level: 
X-Spam-Status: No, score=-2.263 tagged_above=-999 required=5 tests=[AWL=0.337,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RDTAAYIvj8G5 for <ietf@ietfa.amsl.com>; Fri, 19 Jul 2013 09:25:26 -0700 (PDT)
Received: from mail-wg0-x231.google.com (mail-wg0-x231.google.com [IPv6:2a00:1450:400c:c00::231]) by ietfa.amsl.com (Postfix) with ESMTP id C90AF11E8185 for <ietf@ietf.org>; Fri, 19 Jul 2013 09:25:10 -0700 (PDT)
Received: by mail-wg0-f49.google.com with SMTP id a12so4258619wgh.16 for <ietf@ietf.org>; Fri, 19 Jul 2013 09:25:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=9MwAsnl2UNc127IR+FFv3vb3e97osuRfPj0Hqernz8o=; b=py96qLD9O/QSnHH+1fEagW7Er512lpSLYZ1Jui7LyqdnyZ0EPPle8P3bSXw7JjMmFS KqHAx9AhOaXCy7WbYa1uabVJMgB2utuGripGuBwBbfnvF+B2/dT/Rqpeq3JJlAtvSM5j 2BVayUxAShAjZTBEnTitggvP3P+cQ3ogIZigSQkFDhFtA0JZDjhf8schirbr+Hpnjag1 XT0yVve3Xbz+z2lnA6DVym7Lgo08iaRLo5Q+wX5OTTaatRo2qWYjOPpbQaEB4DdpFsEy e+hSA2v9lgjR9LkQh9d8cvIaVZqt9q+yLblm3OdfVlemFBfVnrQ2ZdsXgk2yPkGKpNqr yaDw==
MIME-Version: 1.0
X-Received: by 10.180.39.236 with SMTP id s12mr23263531wik.14.1374251107012; Fri, 19 Jul 2013 09:25:07 -0700 (PDT)
Received: by 10.194.60.46 with HTTP; Fri, 19 Jul 2013 09:25:06 -0700 (PDT)
In-Reply-To: <BBF5DDFE515C3946BC18D733B20DAD2338DD1784@XMB104ADS.rim.net>
References: <CAHBU6ivQs+vsAtrV+Wqxwe2VDDjegYjU8aLPcAvaDkWWrrLBsw@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD2338DD1784@XMB104ADS.rim.net>
Date: Fri, 19 Jul 2013 09:25:06 -0700
Message-ID: <CABkgnnUk9kvtAoFYDsgDAsdeYmd7QUFv5P28H3sbc5HpsgBmjg@mail.gmail.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
From: Martin Thomson <martin.thomson@gmail.com>
To: Andrew Allen <aallen@blackberry.com>
Content-Type: text/plain; charset=UTF-8
Cc: "tbray@textuality.com" <tbray@textuality.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Jul 2013 16:25:26 -0000

On 19 July 2013 08:38, Andrew Allen <aallen@blackberry.com> wrote:
>
> I suggest you also read
> http://datatracker.ietf.org/doc/draft-allen-dispatch-imei-urn-as-instanceid/

I read that document.  The placement of IMEI in the instance id is a
little bit of a non-sequitur to my thinking.

There are three cases identified where it might be necessary to convey
an IMEI, but no real motivation is provided for why it has to be
included, specifically, in the instance ID.  Nor is it the case that
all of these cases necessarily require that IMEI is conveyed in the
clear.  I can imagine solutions to the real problems that do not
require that an IMEI transit the network.

However, I'll concede that the relationship between a network provider
and the devices that use the network does not necessarily grant those
devices any right protections of the form in which Tim seems to be
assuming to be necessary.  The real risk here is with scope of use.

I'd have thought that a P- header would have been more appropriate for
these use cases.

From sm@elandsys.com  Fri Jul 19 09:54:22 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D69AE21E80DD for <ietf@ietfa.amsl.com>; Fri, 19 Jul 2013 09:54:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.59
X-Spam-Level: 
X-Spam-Status: No, score=-102.59 tagged_above=-999 required=5 tests=[AWL=0.009, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id glS91p-1s3y0 for <ietf@ietfa.amsl.com>; Fri, 19 Jul 2013 09:54:21 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A57221F9A78 for <ietf@ietf.org>; Fri, 19 Jul 2013 09:54:18 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.157.46]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r6JGrpYX012795 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 19 Jul 2013 09:54:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1374252851; bh=N2dHv+k0U/xMQDL7OLBkKNpDoKwkUoKd1z9O/+WhfLg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=CjkJfeSHL2fjrp/vI1tJ5p6O/4VzGRbhcfPaLXCRi/hk9dtbev+PTgX1XTT6lEaPo CbtgFRXtL+9eIFfvy6JB/EpawOYmZ2eVBKBapXtsPTgIqLVX8+Q0vYVCMym3iV7fSe 4wiIposM0U9SAN354ibBW00Kx7yQmKobyPO/ikfo=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1374252851; i=@elandsys.com; bh=N2dHv+k0U/xMQDL7OLBkKNpDoKwkUoKd1z9O/+WhfLg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=nFDcb5pA7MCIv7OawJGrfMTN8Ho6PSIZHcMntFrklfta5sXscYasMQFIUrTmhEo8B wVfkoczLK4jNnm44ebAhm4S14rIBGC6H+1wg6FB9sagCvDmR8U92dEHkS1YfrC2Goe uOXgzaNuAiTk2Noft2Yv6eAXH8h+Vxtsre5KZNBQ=
Message-Id: <6.2.5.6.2.20130719084234.0d874c10@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 19 Jul 2013 09:52:40 -0700
To: ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
In-Reply-To: <CAHBU6ivQs+vsAtrV+Wqxwe2VDDjegYjU8aLPcAvaDkWWrrLBsw@mail.g mail.com>
References: <CAHBU6ivQs+vsAtrV+Wqxwe2VDDjegYjU8aLPcAvaDkWWrrLBsw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Tim Bray <tbray@textuality.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Jul 2013 16:54:23 -0000

At 08:02 19-07-2013, Tim Bray wrote:
>I'm not sure from reading the draft what the goal of having this URN 
>namespace is, but if it involves encouraging its use by application 
>developers, I'm pretty sure it's a bad idea.

I agree that it sounds like a bad idea to encourage application 
developers to use this URN namespace.  There was a documented 
vulnerability which demonstrated how the IMEI could be captured.

In 2006 Leslie Daigle mentioned that the sub-NID namespace does not 
belong in the version of the draft which was reviewed.

I'll quote some comments posted by Scott Brim in September 2010 to 
Apps Area Review.

   'First, this feels like a layering mixup.  When would -- or should -- a
    communicating peer outside a mobile network need to know the IMEI or
    IMEISV of a device inside a mobile network?  An IMEI is used for initial
    identification on a mobile network or for SIM-less emergency calls.
    Under what conditions would an Internet-based peer have an IMEI in hand
    and want to use it in a gsma: URN?  If as you say an "Internet device"
    is "interoperating" with a mobile device, it will do so using IP-based
    protocols and will (should) never learn the mobile device's IMEI.  I can
    see cases where an outsourced management entity might want to speak to a
    mobile network's administration regarding records for a particular IMEI,
    but it would do so in a very secure way, not using this particular URN.'

    If there is an assumption that we are going to start passing around
    IMEIs as general identifiers, then I'm concerned that you are
    engineering a world in which one must reveal permanent identifiers in
    order to communicate.

    Please enlighten me as to the intent.  Right now it feels to me like it
    enables us to do the wrong thing with IMEIs.'

The http://gsmworld.com/newsroom/document%2Dlibrary/ normative 
reference is a 404.

It would be easier to have the draft discuss the GSMA URN only.  The 
alternative is to have the draft discuss the privacy considerations 
of using IMEI and IMEISV.

Regards,
S. Moonesamy 


From tbray@textuality.com  Fri Jul 19 10:07:30 2013
Return-Path: <tbray@textuality.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C12C621E810F for <ietf@ietfa.amsl.com>; Fri, 19 Jul 2013 10:07:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.664
X-Spam-Level: 
X-Spam-Status: No, score=-2.664 tagged_above=-999 required=5 tests=[AWL=0.312,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AZ-aK2z7qElp for <ietf@ietfa.amsl.com>; Fri, 19 Jul 2013 10:07:23 -0700 (PDT)
Received: from mail-vb0-f43.google.com (mail-vb0-f43.google.com [209.85.212.43]) by ietfa.amsl.com (Postfix) with ESMTP id 6E09621E810C for <ietf@ietf.org>; Fri, 19 Jul 2013 10:07:20 -0700 (PDT)
Received: by mail-vb0-f43.google.com with SMTP id e12so3335988vbg.2 for <ietf@ietf.org>; Fri, 19 Jul 2013 10:07:18 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=XMhYDdZnhZABsUf1lJDsvtvLRvB2WeXqUjF/Rg5nfAI=; b=ZCICLMO5X8shoXd2293p5ilaOssERstW/XHjN35ocO9OTkasTmInZFpVqRj5Dfb/6A sFXbYZvfO6OwXesj9KnvLvKVho5Byb68xgOjbdjqFCdBzuH1VnCrSyltpN3ja3a3eqF7 hSsPuD8qjaK9HuAFpFFg8gPfyWzvlabDo01pklnhAqT+7ivtsgKsL0Eh72YPpGzz3GSU pWY/+76xwolmfz6/9TIPSTl/Nwjz4xKExtCaDS4YXo0VWOcev4B+4W9ugcVy3uDMAMzg w/UiB3ZHkyncATtGU8/fD85aWpVxABG0xQhmskC4y20WzemYSoKw6YhhBiu/s42UDNNQ ZiUQ==
MIME-Version: 1.0
X-Received: by 10.52.94.6 with SMTP id cy6mr4967473vdb.108.1374253638725; Fri, 19 Jul 2013 10:07:18 -0700 (PDT)
Received: by 10.220.219.200 with HTTP; Fri, 19 Jul 2013 10:07:18 -0700 (PDT)
X-Originating-IP: [24.84.235.32]
In-Reply-To: <6.2.5.6.2.20130719084234.0d874c10@resistor.net>
References: <CAHBU6ivQs+vsAtrV+Wqxwe2VDDjegYjU8aLPcAvaDkWWrrLBsw@mail.gmail.com> <6.2.5.6.2.20130719084234.0d874c10@resistor.net>
Date: Fri, 19 Jul 2013 10:07:18 -0700
Message-ID: <CAHBU6ivpc+6-ZnjnTr5g5vvpDyCNdhvdyNsXChscnbGDJQmMzg@mail.gmail.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
From: Tim Bray <tbray@textuality.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Content-Type: multipart/alternative; boundary=20cf307abe9ff7d6f504e1e05b89
X-Gm-Message-State: ALoCoQnF5ZVxQtCDJ2toUCE/AjvYEKVfQDDLgJENmfvQhZo1wa5FOAL4YxsyguCmX1FckCx5ppxi
Cc: IETF-Discussion Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Jul 2013 17:07:30 -0000

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

On Fri, Jul 19, 2013 at 9:52 AM, S Moonesamy <sm+ietf@elandsys.com> wrote:

>
> It would be easier to have the draft discuss the GSMA URN only.  The
> alternative is to have the draft discuss the privacy considerations of
> using IMEI and IMEISV.
>

Good catch.  Assuming this is a good idea (I=E2=80=99m dubious) it would be
completely unacceptable to register it without a discussion of privacy
implications. -T


>
> Regards,
> S. Moonesamy
>

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

<div dir=3D"ltr">On Fri, Jul 19, 2013 at 9:52 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 class=
=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><br>
It would be easier to have the draft discuss the GSMA URN only. =C2=A0The a=
lternative is to have the draft discuss the privacy considerations of using=
 IMEI and IMEISV.<br></blockquote><div><br></div><div>Good catch.=C2=A0 Ass=
uming this is a good idea (I=E2=80=99m dubious) it would be completely unac=
ceptable to register it without a discussion of privacy implications. -T<br=
>
</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Regards,<br>
S. Moonesamy <br>
</blockquote></div><br></div></div>

--20cf307abe9ff7d6f504e1e05b89--

From prvs=0912e67cf4=aallen@blackberry.com  Fri Jul 19 15:53:26 2013
Return-Path: <prvs=0912e67cf4=aallen@blackberry.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6596E11E81AF for <ietf@ietfa.amsl.com>; Fri, 19 Jul 2013 15:53:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.133
X-Spam-Level: 
X-Spam-Status: No, score=-6.133 tagged_above=-999 required=5 tests=[AWL=0.465,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ahicH3JE8Gry for <ietf@ietfa.amsl.com>; Fri, 19 Jul 2013 15:53:21 -0700 (PDT)
Received: from mhs060cnc.rim.net (mhs060cnc.rim.net [208.65.73.34]) by ietfa.amsl.com (Postfix) with ESMTP id 05D4011E8160 for <ietf@ietf.org>; Fri, 19 Jul 2013 15:53:20 -0700 (PDT)
X-AuditID: 0a41282f-b7f9b6d000002847-5f-51e9c35b7513
Received: from XCT102ADS.rim.net (xct102ads.rim.net [10.67.111.43]) by mhs060cnc.rim.net (SBG) with SMTP id FC.0B.10311.B53C9E15; Fri, 19 Jul 2013 17:53:15 -0500 (CDT)
Received: from XMB104ADS.rim.net ([fe80::2494:a63d:e3:723b]) by XCT102ADS.rim.net ([fe80::4806:2e1d:2b7c:cfdf%22]) with mapi id 14.02.0328.009; Fri, 19 Jul 2013 17:53:15 -0500
From: Andrew Allen <aallen@blackberry.com>
To: "tbray@textuality.com" <tbray@textuality.com>, "sm+ietf@elandsys.com" <sm+ietf@elandsys.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
Thread-Topic: Last call: draft-montemurro-gsma-imei-urn-16.txt
Thread-Index: AQHOhJEO4fYTwuVTOkCw8MDTXs0bMZlsOFEcgABXNwCAAAzWSw==
Date: Fri, 19 Jul 2013 22:53:14 +0000
Message-ID: <BBF5DDFE515C3946BC18D733B20DAD2338DD1D6D@XMB104ADS.rim.net>
In-Reply-To: <CAHBU6ivpc+6-ZnjnTr5g5vvpDyCNdhvdyNsXChscnbGDJQmMzg@mail.gmail.com>
Accept-Language: en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.67.110.252]
Content-Type: multipart/alternative; boundary="_000_BBF5DDFE515C3946BC18D733B20DAD2338DD1D6DXMB104ADSrimnet_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrAKsWRmVeSWpSXmKPExsXC5ZyvrRt9+GWgwewvFhbPNs5nsXjVf5PV Yumf+SwOzB733nxk8liy5CeTx6Wlk5kDmKMaGG2SEkvKgjPT8/TtbBLz8vJLEktSFVJSi5Nt lXxS0xNzFAKKMssSkysVXDKLk3MSM3NTi5QUMlNslUyUFApyEpNTc1PzSmyVEgsKUvNSlOy4 FDCADVBZZp5Cal5yfkpmXrqtkmewv66FhamlrqGSnW5CJ09GR79gwSy1iu3X+5gaGDtUuxg5 OSQETCSe7djPAmGLSVy4t56ti5GLQ0hgJaNE2+LjLBDOZkaJ298es4FUsQloSew/PJ0JxBYR SJJof/CPHcRmFlCWeLppDlhcWMBW4vLpP4wQNXYS3w9eYoGwnSR+v3sDNIeDg0VAVaJhjzVI mFfAQ+Lih39g4zkFAiXurVzNCmIzCshK7D57nQlivLjErSfzmSAOFZBYsuc8M4QtKvHy8T9W CFtR4nFLNwvIeGaBfIlP/8MhxgtKnJz5hGUCo8gsJJNmIVTNQlIFEdaUWL9LH6JaUWJK90N2 CFtDonXOXHZk8QWM7KsYBXMzig3MDJLzkvWKMnP18lJLNjGCUomjhv4OxrfvLQ4xCnAwKvHw su1/GSjEmlhWXJl7iFGCg1lJhLcgDSjEm5JYWZValB9fVJqTWnyIMQgYOhOZpbiT84FpLq8k 3tjAgEiOkjiv1dmzgUIC6cD0lZ2aWpBaBDOUiYMTZCmXlEgxMAmlFiWWlmTEg1JlfDEwWUo1 MJbWtHc/qTwS/yWQ6aP7mR7r1/9aP/sbLy48m3W27ny8afv+C/KRbxYdCfhx2285679XUpLl CbXMD3f8CYxgXPJXa3fBx62Sd79/exb84pnK66jyJboO3yY/XSJoYfA1g5ldqCq4qvNT8hue Dx8q6pUCF1pNSP34TuvQRGu7cnsz7wc7ry7hMFViKc5INNRiLipOBABRC6RYcwMAAA==
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Jul 2013 22:53:26 -0000

--_000_BBF5DDFE515C3946BC18D733B20DAD2338DD1D6DXMB104ADSrimnet_
Content-Type: text/plain; charset="utf-8"
content-transfer-encoding: base64

DQpUaW0NCg0KRG8geW91IG5vdCB0aGluayB0aGF0IHRoZSB0ZXh0IGluIHRoZSBzZWN1cml0
eSBjb25zaWRlcmF0aW9ucyBzZWN0aW9uOjoNCg0KImJlY2F1c2UgSU1FSXMgY2FuIGJlIGxv
b3NlbHkgY29ycmVsYXRlZCB0byBhIHVzZXIsIHRoZXkgbmVlZCB0byBiZSB0cmVhdGVkIGFz
IGFueSBvdGhlciBwZXJzb25hbGx5IGlkZW50aWZpYWJsZSBpbmZvcm1hdGlvbi4gSW4gcGFy
dGljdWxhciwgdGhlIElNRUkgVVJOIE1VU1QgTk9UIGJlIGluY2x1ZGVkIGluIG1lc3NhZ2Vz
IGludGVuZGVkIHRvIGNvbnZleSBhbnkgbGV2ZWwgb2YgYW5vbnltaXR5Ig0KDQpjb3ZlcnMg
dGhlIHByaXZhY3kgaXNzdWU/DQoNCklmIG5vdCB3aGF0IGlzIHRoZSBhZGRpdGlvbmFsIHBy
aXZhY3kgY29uY2Vybj8NCg0KQW5kcmV3DQoNCkZyb206IFRpbSBCcmF5IFttYWlsdG86dGJy
YXlAdGV4dHVhbGl0eS5jb21dDQpTZW50OiBGcmlkYXksIEp1bHkgMTksIDIwMTMgMTI6MDcg
UE0gQ2VudHJhbCBTdGFuZGFyZCBUaW1lDQpUbzogUyBNb29uZXNhbXkgPHNtK2lldGZAZWxh
bmRzeXMuY29tPg0KQ2M6IElFVEYtRGlzY3Vzc2lvbiBEaXNjdXNzaW9uIDxpZXRmQGlldGYu
b3JnPg0KU3ViamVjdDogUmU6IExhc3QgY2FsbDogZHJhZnQtbW9udGVtdXJyby1nc21hLWlt
ZWktdXJuLTE2LnR4dA0KDQpPbiBGcmksIEp1bCAxOSwgMjAxMyBhdCA5OjUyIEFNLCBTIE1v
b25lc2FteSA8c20raWV0ZkBlbGFuZHN5cy5jb208bWFpbHRvOnNtK2lldGZAZWxhbmRzeXMu
Y29tPj4gd3JvdGU6DQoNCkl0IHdvdWxkIGJlIGVhc2llciB0byBoYXZlIHRoZSBkcmFmdCBk
aXNjdXNzIHRoZSBHU01BIFVSTiBvbmx5LiAgVGhlIGFsdGVybmF0aXZlIGlzIHRvIGhhdmUg
dGhlIGRyYWZ0IGRpc2N1c3MgdGhlIHByaXZhY3kgY29uc2lkZXJhdGlvbnMgb2YgdXNpbmcg
SU1FSSBhbmQgSU1FSVNWLg0KDQpHb29kIGNhdGNoLiAgQXNzdW1pbmcgdGhpcyBpcyBhIGdv
b2QgaWRlYSAoSeKAmW0gZHViaW91cykgaXQgd291bGQgYmUgY29tcGxldGVseSB1bmFjY2Vw
dGFibGUgdG8gcmVnaXN0ZXIgaXQgd2l0aG91dCBhIGRpc2N1c3Npb24gb2YgcHJpdmFjeSBp
bXBsaWNhdGlvbnMuIC1UDQoNCg0KUmVnYXJkcywNClMuIE1vb25lc2FteQ0KDQoNCi0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLQ0KVGhpcyB0cmFuc21pc3Npb24gKGluY2x1ZGluZyBhbnkgYXR0YWNobWVu
dHMpIG1heSBjb250YWluIGNvbmZpZGVudGlhbCBpbmZvcm1hdGlvbiwgcHJpdmlsZWdlZCBt
YXRlcmlhbCAoaW5jbHVkaW5nIG1hdGVyaWFsIHByb3RlY3RlZCBieSB0aGUgc29saWNpdG9y
LWNsaWVudCBvciBvdGhlciBhcHBsaWNhYmxlIHByaXZpbGVnZXMpLCBvciBjb25zdGl0dXRl
IG5vbi1wdWJsaWMgaW5mb3JtYXRpb24uIEFueSB1c2Ugb2YgdGhpcyBpbmZvcm1hdGlvbiBi
eSBhbnlvbmUgb3RoZXIgdGhhbiB0aGUgaW50ZW5kZWQgcmVjaXBpZW50IGlzIHByb2hpYml0
ZWQuIElmIHlvdSBoYXZlIHJlY2VpdmVkIHRoaXMgdHJhbnNtaXNzaW9uIGluIGVycm9yLCBw
bGVhc2UgaW1tZWRpYXRlbHkgcmVwbHkgdG8gdGhlIHNlbmRlciBhbmQgZGVsZXRlIHRoaXMg
aW5mb3JtYXRpb24gZnJvbSB5b3VyIHN5c3RlbS4gVXNlLCBkaXNzZW1pbmF0aW9uLCBkaXN0
cmlidXRpb24sIG9yIHJlcHJvZHVjdGlvbiBvZiB0aGlzIHRyYW5zbWlzc2lvbiBieSB1bmlu
dGVuZGVkIHJlY2lwaWVudHMgaXMgbm90IGF1dGhvcml6ZWQgYW5kIG1heSBiZSB1bmxhd2Z1
bC4NCg==

--_000_BBF5DDFE515C3946BC18D733B20DAD2338DD1D6DXMB104ADSrimnet_
Content-Type: text/html; charset="utf-8"
content-transfer-encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5Pg0KPGZvbnQg
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxicj4NClRpbTxicj4N
Cjxicj4NCkRvIHlvdSBub3QgdGhpbmsgdGhhdCB0aGUgdGV4dCBpbiB0aGUgc2VjdXJpdHkg
Y29uc2lkZXJhdGlvbnMgc2VjdGlvbjo6PGJyPg0KPGJyPg0KJnF1b3Q7YmVjYXVzZSBJTUVJ
cyBjYW4gYmUgbG9vc2VseSBjb3JyZWxhdGVkIHRvIGEgdXNlciwgdGhleSBuZWVkIHRvIGJl
IHRyZWF0ZWQgYXMgYW55IG90aGVyIHBlcnNvbmFsbHkgaWRlbnRpZmlhYmxlIGluZm9ybWF0
aW9uLiBJbiBwYXJ0aWN1bGFyLCB0aGUgSU1FSSBVUk4gTVVTVCBOT1QgYmUgaW5jbHVkZWQg
aW4gbWVzc2FnZXMgaW50ZW5kZWQgdG8gY29udmV5IGFueSBsZXZlbCBvZiBhbm9ueW1pdHkm
cXVvdDs8YnI+DQo8YnI+DQpjb3ZlcnMgdGhlIHByaXZhY3kgaXNzdWU/PGJyPg0KPGJyPg0K
SWYgbm90IHdoYXQgaXMgdGhlIGFkZGl0aW9uYWwgcHJpdmFjeSBjb25jZXJuPzxicj4NCjxi
cj4NCkFuZHJldzwvZm9udD48YnI+DQombmJzcDs8YnI+DQo8ZGl2IHN0eWxlPSJib3JkZXI6
bm9uZTtib3JkZXItdG9wOnNvbGlkICNCNUM0REYgMS4wcHQ7cGFkZGluZzozLjBwdCAwaW4g
MGluIDBpbiI+DQo8Zm9udCBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTom
cXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PGI+RnJvbTwvYj46
IFRpbSBCcmF5IFttYWlsdG86dGJyYXlAdGV4dHVhbGl0eS5jb21dDQo8YnI+DQo8Yj5TZW50
PC9iPjogRnJpZGF5LCBKdWx5IDE5LCAyMDEzIDEyOjA3IFBNIENlbnRyYWwgU3RhbmRhcmQg
VGltZTxicj4NCjxiPlRvPC9iPjogUyBNb29uZXNhbXkgJmx0O3NtJiM0MztpZXRmQGVsYW5k
c3lzLmNvbSZndDsgPGJyPg0KPGI+Q2M8L2I+OiBJRVRGLURpc2N1c3Npb24gRGlzY3Vzc2lv
biAmbHQ7aWV0ZkBpZXRmLm9yZyZndDsgPGJyPg0KPGI+U3ViamVjdDwvYj46IFJlOiBMYXN0
IGNhbGw6IGRyYWZ0LW1vbnRlbXVycm8tZ3NtYS1pbWVpLXVybi0xNi50eHQgPGJyPg0KPC9m
b250PiZuYnNwOzxicj4NCjwvZGl2Pg0KPGRpdiBkaXI9Imx0ciI+T24gRnJpLCBKdWwgMTks
IDIwMTMgYXQgOTo1MiBBTSwgUyBNb29uZXNhbXkgPHNwYW4gZGlyPSJsdHIiPiZsdDs8YSBo
cmVmPSJtYWlsdG86c20mIzQzO2lldGZAZWxhbmRzeXMuY29tIiB0YXJnZXQ9Il9ibGFuayI+
c20mIzQzO2lldGZAZWxhbmRzeXMuY29tPC9hPiZndDs8L3NwYW4+IHdyb3RlOjxicj4NCjxk
aXYgY2xhc3M9ImdtYWlsX2V4dHJhIj4NCjxkaXYgY2xhc3M9ImdtYWlsX3F1b3RlIj4NCjxi
bG9ja3F1b3RlIGNsYXNzPSJnbWFpbF9xdW90ZSIgc3R5bGU9Im1hcmdpbjowIDAgMCAuOGV4
O2JvcmRlci1sZWZ0OjFweCAjY2NjIHNvbGlkO3BhZGRpbmctbGVmdDoxZXgiPg0KPGJyPg0K
SXQgd291bGQgYmUgZWFzaWVyIHRvIGhhdmUgdGhlIGRyYWZ0IGRpc2N1c3MgdGhlIEdTTUEg
VVJOIG9ubHkuICZuYnNwO1RoZSBhbHRlcm5hdGl2ZSBpcyB0byBoYXZlIHRoZSBkcmFmdCBk
aXNjdXNzIHRoZSBwcml2YWN5IGNvbnNpZGVyYXRpb25zIG9mIHVzaW5nIElNRUkgYW5kIElN
RUlTVi48YnI+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5Hb29k
IGNhdGNoLiZuYnNwOyBBc3N1bWluZyB0aGlzIGlzIGEgZ29vZCBpZGVhIChJ4oCZbSBkdWJp
b3VzKSBpdCB3b3VsZCBiZSBjb21wbGV0ZWx5IHVuYWNjZXB0YWJsZSB0byByZWdpc3RlciBp
dCB3aXRob3V0IGEgZGlzY3Vzc2lvbiBvZiBwcml2YWN5IGltcGxpY2F0aW9ucy4gLVQ8YnI+
DQo8L2Rpdj4NCjxkaXY+Jm5ic3A7PC9kaXY+DQo8YmxvY2txdW90ZSBjbGFzcz0iZ21haWxf
cXVvdGUiIHN0eWxlPSJtYXJnaW46MCAwIDAgLjhleDtib3JkZXItbGVmdDoxcHggI2NjYyBz
b2xpZDtwYWRkaW5nLWxlZnQ6MWV4Ij4NCjxicj4NClJlZ2FyZHMsPGJyPg0KUy4gTW9vbmVz
YW15IDxicj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPGJyPg0KPC9kaXY+DQo8L2Rpdj4N
Ci0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLSA8YnI+DQpUaGlzIHRyYW5zbWlzc2lvbiAoaW5jbHVkaW5nIGFu
eSBhdHRhY2htZW50cykgbWF5IGNvbnRhaW4gY29uZmlkZW50aWFsIGluZm9ybWF0aW9uLCBw
cml2aWxlZ2VkIG1hdGVyaWFsIChpbmNsdWRpbmcgbWF0ZXJpYWwgcHJvdGVjdGVkIGJ5IHRo
ZSBzb2xpY2l0b3ItY2xpZW50IG9yIG90aGVyIGFwcGxpY2FibGUgcHJpdmlsZWdlcyksIG9y
IGNvbnN0aXR1dGUgbm9uLXB1YmxpYyBpbmZvcm1hdGlvbi4gQW55IHVzZSBvZiB0aGlzIGlu
Zm9ybWF0aW9uIGJ5IGFueW9uZSBvdGhlciB0aGFuIHRoZSBpbnRlbmRlZCByZWNpcGllbnQg
aXMgcHJvaGliaXRlZC4gSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyB0cmFuc21pc3Npb24g
aW4gZXJyb3IsIHBsZWFzZSBpbW1lZGlhdGVseSByZXBseSB0byB0aGUgc2VuZGVyIGFuZCBk
ZWxldGUgdGhpcyBpbmZvcm1hdGlvbiBmcm9tIHlvdXIgc3lzdGVtLiBVc2UsIGRpc3NlbWlu
YXRpb24sIGRpc3RyaWJ1dGlvbiwgb3IgcmVwcm9kdWN0aW9uIG9mIHRoaXMgdHJhbnNtaXNz
aW9uIGJ5IHVuaW50ZW5kZWQgcmVjaXBpZW50cyBpcyBub3QgYXV0aG9yaXplZCBhbmQgbWF5
IGJlIHVubGF3ZnVsLg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_BBF5DDFE515C3946BC18D733B20DAD2338DD1D6DXMB104ADSrimnet_--

From tbray@textuality.com  Fri Jul 19 16:03:47 2013
Return-Path: <tbray@textuality.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF7D121F8468 for <ietf@ietfa.amsl.com>; Fri, 19 Jul 2013 16:03:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[AWL=0.278,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vucmAF1QJ01b for <ietf@ietfa.amsl.com>; Fri, 19 Jul 2013 16:03:29 -0700 (PDT)
Received: from mail-vc0-f179.google.com (mail-vc0-f179.google.com [209.85.220.179]) by ietfa.amsl.com (Postfix) with ESMTP id 18D9811E81B2 for <ietf@ietf.org>; Fri, 19 Jul 2013 16:03:29 -0700 (PDT)
Received: by mail-vc0-f179.google.com with SMTP id id13so86479vcb.38 for <ietf@ietf.org>; Fri, 19 Jul 2013 16:03:27 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=XCICQmaRhXSAMcF3RSHfeRv8s2y45lPnXvb4C8ml3zI=; b=UAtXuOyCm+VxKKSdbh4AU4ffJL19njLE+wZ+t8gge/E1+8b8fjtZoOEv8q9S0eOcck VA+pauuWE0R13AE0ZGE9U3Dhsh52zsRdtPs4qJORWe6D5AeuTWBpeRkjiwUPkSSTkTQU +ErVjt381IR58X/rEnDNH9mcuXqoSHOQa1rQIiNBGNq/OBNe2kdiKDwMwaX+nVfw4089 GwxZTTFvjDHCDorK4iNaVAhumiOhCg5jQLnZskjHgf1xeIbHWODyh5MWf7+2rkM4Zca0 HtKMyehj6QH/a/koagD9CUob+9c+Ukbj2Lj0sdraIqu7ZoTPyadeb9mgRUgq0uG/NdKO 8zRw==
MIME-Version: 1.0
X-Received: by 10.220.197.72 with SMTP id ej8mr6450080vcb.66.1374275007454; Fri, 19 Jul 2013 16:03:27 -0700 (PDT)
Received: by 10.220.219.200 with HTTP; Fri, 19 Jul 2013 16:03:27 -0700 (PDT)
X-Originating-IP: [24.84.235.32]
In-Reply-To: <BBF5DDFE515C3946BC18D733B20DAD2338DD1D6D@XMB104ADS.rim.net>
References: <CAHBU6ivpc+6-ZnjnTr5g5vvpDyCNdhvdyNsXChscnbGDJQmMzg@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD2338DD1D6D@XMB104ADS.rim.net>
Date: Fri, 19 Jul 2013 16:03:27 -0700
Message-ID: <CAHBU6iuH+CHTwq0TtQgzmoE4vjLBn-rDX9O_HEvouRypomXuPA@mail.gmail.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
From: Tim Bray <tbray@textuality.com>
To: Andrew Allen <aallen@blackberry.com>
Content-Type: multipart/alternative; boundary=001a11c1f08ea4af0104e1e55526
X-Gm-Message-State: ALoCoQlCqKYsrKos8BdDAwDlbaZkVKlUUvdqJnh12YjmlhTsN1hy6FuMgPzS6IfsEdRYRmtNOiHg
Cc: "sm+ietf@elandsys.com" <sm+ietf@elandsys.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Jul 2013 23:03:48 -0000

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

Hm, I confess that I searched the text of the draft for the word =E2=80=9Cp=
rivacy=E2=80=9D
and jumped to conclusions upon seeing no matches.  Probably a good idea to
work it in for impatient folk like me.

I would expand that section to point out that since the IMEI survives
device wipes and changes of possession, it shouldn=E2=80=99t be assumed to =
identify
a person.

And I really wouldn=E2=80=99t ever expose an IMEI at the application level,=
 but
maybe it=E2=80=99s appropriate at the level this draft is addressing.  We h=
ad
endless nightmares, not only because of the wipe-survival, but because app
code would try to run on a device that didn't have an IMEI and crash, and
so on.  -T


On Fri, Jul 19, 2013 at 3:53 PM, Andrew Allen <aallen@blackberry.com> wrote=
:

>
> Tim
>
> Do you not think that the text in the security considerations section::
>
> "because IMEIs can be loosely correlated to a user, they need to be
> treated as any other personally identifiable information. In particular,
> the IMEI URN MUST NOT be included in messages intended to convey any leve=
l
> of anonymity"
>
> covers the privacy issue?
>
> If not what is the additional privacy concern?
>
> Andrew
>
>  *From*: Tim Bray [mailto:tbray@textuality.com]
> *Sent*: Friday, July 19, 2013 12:07 PM Central Standard Time
> *To*: S Moonesamy <sm+ietf@elandsys.com>
> *Cc*: IETF-Discussion Discussion <ietf@ietf.org>
> *Subject*: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
>
>  On Fri, Jul 19, 2013 at 9:52 AM, S Moonesamy <sm+ietf@elandsys.com>wrote=
:
>
>>
>> It would be easier to have the draft discuss the GSMA URN only.  The
>> alternative is to have the draft discuss the privacy considerations of
>> using IMEI and IMEISV.
>>
>
>  Good catch.  Assuming this is a good idea (I=E2=80=99m dubious) it would=
 be
> completely unacceptable to register it without a discussion of privacy
> implications. -T
>
>
>>
>> Regards,
>> S. Moonesamy
>>
>
>  ---------------------------------------------------------------------
> This transmission (including any attachments) may contain confidential
> information, privileged material (including material protected by the
> solicitor-client or other applicable privileges), or constitute non-publi=
c
> information. Any use of this information by anyone other than the intende=
d
> recipient is prohibited. If you have received this transmission in error,
> please immediately reply to the sender and delete this information from
> your system. Use, dissemination, distribution, or reproduction of this
> transmission by unintended recipients is not authorized and may be
> unlawful.
>

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

<div dir=3D"ltr"><div>Hm, I confess that I searched the text of the draft f=
or the word =E2=80=9Cprivacy=E2=80=9D and jumped to conclusions upon seeing=
 no matches.=C2=A0 Probably a good idea to work it in for impatient folk li=
ke me.<br><br>I would expand that section to point out that since the IMEI =
survives device wipes and changes of possession, it shouldn=E2=80=99t be as=
sumed to identify a person. <br>
<br></div>And I really wouldn=E2=80=99t ever expose an IMEI at the applicat=
ion level, but maybe it=E2=80=99s appropriate at the level this draft is ad=
dressing.=C2=A0 We had endless nightmares, not only because of the wipe-sur=
vival, but because app code would try to run on a device that didn&#39;t ha=
ve an IMEI and crash, and so on.=C2=A0 -T<br>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Fri,=
 Jul 19, 2013 at 3:53 PM, Andrew Allen <span dir=3D"ltr">&lt;<a href=3D"mai=
lto:aallen@blackberry.com" target=3D"_blank">aallen@blackberry.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>
<font style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:#1f497d"><br>
Tim<br>
<br>
Do you not think that the text in the security considerations section::<br>
<br>
&quot;because IMEIs can be loosely correlated to a user, they need to be tr=
eated as any other personally identifiable information. In particular, the =
IMEI URN MUST NOT be included in messages intended to convey any level of a=
nonymity&quot;<br>

<br>
covers the privacy issue?<br>
<br>
If not what is the additional privacy concern?<br>
<br>
Andrew</font><br>
=C2=A0<br>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in =
0in 0in">
<font style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-s=
erif&quot;"><div class=3D"im"><b>From</b>: Tim Bray [mailto:<a href=3D"mail=
to:tbray@textuality.com" target=3D"_blank">tbray@textuality.com</a>]
<br>
</div><b>Sent</b>: Friday, July 19, 2013 12:07 PM Central Standard Time<br>
<b>To</b>: S Moonesamy &lt;<a href=3D"mailto:sm%2Bietf@elandsys.com" target=
=3D"_blank">sm+ietf@elandsys.com</a>&gt; <br>
<b>Cc</b>: IETF-Discussion Discussion &lt;<a href=3D"mailto:ietf@ietf.org" =
target=3D"_blank">ietf@ietf.org</a>&gt; <br>
<b>Subject</b>: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt <br>
</font>=C2=A0<br>
</div><div><div class=3D"h5">
<div dir=3D"ltr">On Fri, Jul 19, 2013 at 9:52 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 class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
It would be easier to have the draft discuss the GSMA URN only. =C2=A0The a=
lternative is to have the draft discuss the privacy considerations of using=
 IMEI and IMEISV.<br>
</blockquote>
<div><br>
</div>
<div>Good catch.=C2=A0 Assuming this is a good idea (I=E2=80=99m dubious) i=
t would be completely unacceptable to register it without a discussion of p=
rivacy implications. -T<br>
</div>
<div>=C2=A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
Regards,<br>
S. Moonesamy <br>
</blockquote>
</div>
<br>
</div>
</div></div></div><div class=3D"im">
--------------------------------------------------------------------- <br>
This transmission (including any attachments) may contain confidential info=
rmation, privileged material (including material protected by the solicitor=
-client or other applicable privileges), or constitute non-public informati=
on. Any use of this information by anyone other than the intended recipient=
 is prohibited. If you have received this transmission in error, please imm=
ediately reply to the sender and delete this information from your system. =
Use, dissemination, distribution, or reproduction of this transmission by u=
nintended recipients is not authorized and may be unlawful.
</div></div>

</blockquote></div><br></div>

--001a11c1f08ea4af0104e1e55526--

From stephen.farrell@cs.tcd.ie  Fri Jul 19 16:16:01 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2F4111E81CF for <ietf@ietfa.amsl.com>; Fri, 19 Jul 2013 16:16:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.442
X-Spam-Level: 
X-Spam-Status: No, score=-102.442 tagged_above=-999 required=5 tests=[AWL=-0.157, BAYES_00=-2.599, SARE_MILLIONSOF=0.315, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id divJCCJ7db+6 for <ietf@ietfa.amsl.com>; Fri, 19 Jul 2013 16:15:55 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id B1A0811E81BB for <ietf@ietf.org>; Fri, 19 Jul 2013 16:15:46 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 03287BE80; Sat, 20 Jul 2013 00:15:25 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7GQ3A4BNHPvF; Sat, 20 Jul 2013 00:15:24 +0100 (IST)
Received: from [10.87.48.9] (unknown [86.41.50.155]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 1D028BE77; Sat, 20 Jul 2013 00:15:24 +0100 (IST)
Message-ID: <51E9C87C.3020105@cs.tcd.ie>
Date: Sat, 20 Jul 2013 00:15:08 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: Andrew Allen <aallen@blackberry.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
References: <BBF5DDFE515C3946BC18D733B20DAD2338DD1D6D@XMB104ADS.rim.net>
In-Reply-To: <BBF5DDFE515C3946BC18D733B20DAD2338DD1D6D@XMB104ADS.rim.net>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "tbray@textuality.com" <tbray@textuality.com>, "sm+ietf@elandsys.com" <sm+ietf@elandsys.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Jul 2013 23:16:01 -0000

On 07/19/2013 11:53 PM, Andrew Allen wrote:
> the IMEI URN MUST NOT be included in messages intended to convey any level of anonymity

That seems both perfect RFC 6919 fodder and disingenuous at
the same time (how can a message convey a level of anonymity?).

I need to read the draft but this seems like it only has
downsides from a privacy perspective. So I'd hope there
are compelling functional reasons to want it that outweigh
the privacy downside.

IMEIs are very pervasive, carried around by 100's of millions
of people and generally not intended to be shared with the
Internet.

S.

From randy@psg.com  Fri Jul 19 16:48:12 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B416911E81B4 for <ietf@ietfa.amsl.com>; Fri, 19 Jul 2013 16:48:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.576
X-Spam-Level: 
X-Spam-Status: No, score=-2.576 tagged_above=-999 required=5 tests=[AWL=0.023,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YVbYMhY2QxOq for <ietf@ietfa.amsl.com>; Fri, 19 Jul 2013 16:48:12 -0700 (PDT)
Received: from ran.psg.com (unknown [IPv6:2001:418:8006::19]) by ietfa.amsl.com (Postfix) with ESMTP id E42C911E81BB for <ietf@ietf.org>; Fri, 19 Jul 2013 16:48:11 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1V0KPB-0004u2-NS; Fri, 19 Jul 2013 23:48:10 +0000
Date: Fri, 19 Jul 2013 16:48:09 -0700
Message-ID: <m2r4eu3ydi.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
In-Reply-To: <51E9C87C.3020105@cs.tcd.ie>
References: <BBF5DDFE515C3946BC18D733B20DAD2338DD1D6D@XMB104ADS.rim.net> <51E9C87C.3020105@cs.tcd.ie>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Jul 2013 23:48:12 -0000

> IMEIs are very pervasive, carried around by 100's of millions
> of people and generally not intended to be shared with the
> Internet.

my american social security card, which admittedly is a bit old, has
"Not to be used for identification" emblazoned on it in red.

for me, a seminal document was the 1973 "Records, Computers, and the
Rights Of Citizens," a report of the secretary's advisory committee on
automated personal data systems of the us department of health,
education, and welfare, chaired by willis ware.  it spawned the privacy
act of 1974, and i still have my copy.  see [0].  it warned of the use
the social seurity number as an identifier.  [interestingly, mitre (also
chaired by ware) did a report for the air force in '68 which reccomended
the ssn as an id]

today, in the states, the ssn is the ubiquitous identifier, and a major
target of identity thieves and may be second only to cross site cookies
as the identity target of marketeers.

in the mobile society, the ids of our devices are becoming identy gold,
and should be transmitted with extreme caution and only under compelling
circumstances.

randy

--

[0] http://itlaw.wikia.com/wiki/Records,_Computers_and_the_Rights_of_Citizens

From fluffy@cisco.com  Fri Jul 19 17:12:33 2013
Return-Path: <fluffy@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A2A121E80D8; Fri, 19 Jul 2013 17:12:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.233
X-Spam-Level: 
X-Spam-Status: No, score=-110.233 tagged_above=-999 required=5 tests=[AWL=-0.234, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lsZ+4KA8-CEO; Fri, 19 Jul 2013 17:12:28 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 3EA3F21E8099; Fri, 19 Jul 2013 17:12:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3964; q=dns/txt; s=iport; t=1374279143; x=1375488743; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=A2v46ecp32uktyJKzIu4CBNuGbXDDprIfwZCh80Ap1g=; b=T6X6a788lzidBRyphR8YybCdOxeCVakGEz4Rjk7ELCb+GqGVMES1Az9y Y+FutvbYp8fJ8dZM6+KC9AnD7LgmWWHqmqGF2zqY2LxyzjkD+0XRZz0+H P7PD7lUAZAerrvDp8kP8k1KUmhxBuFCNdbdi3V0yuh7W4DlXXUDhu0d0v U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah8FAG7V6VGtJXG+/2dsb2JhbABagwY1UMBLgREWdIIkAQEBAwEBAQFlBgsQAgEIIhkLJwsUEQIEDgUIiAIGDLdIj1wCMQeDEG4DmQaQJIFZgTmCKg
X-IronPort-AV: E=Sophos;i="4.89,705,1367971200"; d="scan'208";a="234170650"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-9.cisco.com with ESMTP; 20 Jul 2013 00:12:14 +0000
Received: from xhc-rcd-x07.cisco.com (xhc-rcd-x07.cisco.com [173.37.183.81]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id r6K0CDqQ028528 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 20 Jul 2013 00:12:13 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.116]) by xhc-rcd-x07.cisco.com ([173.37.183.81]) with mapi id 14.02.0318.004; Fri, 19 Jul 2013 19:12:12 -0500
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [payload] Last Call: <draft-ietf-payload-vp8-08.txt> (RTP Payload Format for	VP8 Video) to Proposed Standard
Thread-Topic: [payload] Last Call: <draft-ietf-payload-vp8-08.txt> (RTP Payload Format for	VP8 Video) to Proposed Standard
Thread-Index: AQHOhN3IWUW5SiulikKclv0UR7hd+A==
Date: Sat, 20 Jul 2013 00:12:12 +0000
Message-ID: <C5E08FE080ACFD4DAE31E4BDBF944EB1135E7A62@xmb-aln-x02.cisco.com>
References: <20130604222555.32402.16024.idtracker@ietfa.amsl.com>
In-Reply-To: <20130604222555.32402.16024.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.21.91.75]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <9E37F7028DA44C45A7B4D40F952DEBE8@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "payload@ietf.org" <payload@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Jul 2013 00:12:33 -0000

Resent on different list =85


I would like to raise an issue interoperability with this payload specifica=
tion that we are currently having with WebRTC implementations. In WebRTC, a=
nd many other places, you want SDP to be able to control the resolution of =
the image (or at least the outer limits of the resolution). Yes, I realize =
there are applications where you know the resolution vis a some out of band=
 mechanisms but O/A SDP is not one of the where this is guaranteed. We do n=
eed to specify how this works for use with O/A SDP.=20

Some implementations think that if you want the resolution to by 720 lines =
by 1280, you control the resolution of codec with a SDP line something like=
=20

 m=3Dvideo 62537 RTP/SAVPF 96  =20
 a=3Drtpmap:96 VP8/90000
 a=3Dssrc:5 imageattr:* [1280, 720]

Some other implementers think you control the resolution using RFC 6236 wit=
h something like=20

  m=3Dvideo 62537 RTP/SAVPF 96=20
  a=3Drtpmap:96 VP8/90000
  a=3Dimageattr:96 [x=3D1280,y=3D720]

There is one thing that as far as I can tell that all the implementors agre=
e on. None of the implications control the resolution using=20

  m=3Dvideo 62537 RTP/SAVPF 96=20
  a=3Drtpmap:96 VP8/90000
  a=3Dfmtp:96 max-fr=3D30;max-fs=3D3600

What resolution do you think "max-fs=3D3600" is? I have no idea. It is not =
possible to implement so it is not surprising no one is doing  it. However,=
 this draft-ietf-payload-vp8 draft says the resolution is specified using t=
he max-fs and max-fr.=20

I raised this in the WG and the WG came to consensus that current draft is =
fine. So I actually believe that current draft does represent IETF consensu=
s and that I was merely in the rough on that consensus. I had decided to ju=
st ignore it in LC because I was under the impressing that all the implemen=
tations would just ignore the RFC and do "a=3Dimageattr:96 [x=3D1280,y=3D72=
0]". However, when it came to my attention that many were doing  "a=3Dimage=
attr:96 [x=3D1280,y=3D720]" but some where doing the non interoperable "a=
=3Dssrc:5 imageattr:* [1280, 720]", I decided that this problem actually ne=
eded to be fixed.=20

I think this draft is broken and will create interoperability problems for =
years to come. I encourage the IESG to fix it. I don't care how it is resol=
ved, I care that there is a way to for O/A to sort out the resolution and s=
ince the approach used be SDP to do this is codec specific, it needs to be =
in this draft.=20

Cullen

On Jun 4, 2013, at 3:25 PM, The IESG <iesg-secretary@ietf.org> wrote:

>=20
> The IESG has received a request from the Audio/Video Transport Payloads
> WG (payload) to consider the following document:
> - 'RTP Payload Format for VP8 Video'
>  <draft-ietf-payload-vp8-08.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 2013-06-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 memo describes an RTP payload format for the VP8 video codec.
>   The payload format has wide applicability, as it supports
>   applications from low bit-rate peer-to-peer usage, to high bit-rate
>   video conferences.
>=20
>=20
>=20
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-payload-vp8/
>=20
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-payload-vp8/ballot/
>=20
>=20
> The following IPR Declarations may be related to this I-D:
>=20
>   http://datatracker.ietf.org/ipr/1622/
>=20
>=20
>=20
> _______________________________________________
> payload mailing list
> payload@ietf.org
> https://www.ietf.org/mailman/listinfo/payload


From scott.brim@gmail.com  Sat Jul 20 04:23:46 2013
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DABF21F9CA9 for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 04:23:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gok-Pk+NN+V1 for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 04:23:45 -0700 (PDT)
Received: from mail-oa0-x22e.google.com (mail-oa0-x22e.google.com [IPv6:2607:f8b0:4003:c02::22e]) by ietfa.amsl.com (Postfix) with ESMTP id AE91321F9477 for <ietf@ietf.org>; Sat, 20 Jul 2013 04:23:45 -0700 (PDT)
Received: by mail-oa0-f46.google.com with SMTP id h1so7267974oag.33 for <ietf@ietf.org>; Sat, 20 Jul 2013 04:23:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=0b/4/tPL7sqs0l0Q6J1zOQWCTiUnMC/cUEzfJILYu+4=; b=0J3Oiikj8HK0Ujaf0m+/d3RVT6cQVkMikECl4OEx/+3fkTaH1cY5cLgMNU9SNlH5vX Hh1ljA23pkuZe+fMVGn2VFJZ77J76rp9gi/PddvA9pC1gcdTYaHAe1KewKU6ZumEORIs gOhhGWvYM0taxYfi6BakO4tveG5nnV4uvzS9KmoXqg8htr82HVCtjmYYXUjxebUXgP2y QZ01BpxvQAV1Ny6M5wPVpvQi2SgIbb08p1Yx5Q4+I6PNUo41/nDIL0HDscnWMwrC7do1 GXgN/bMVrvfzdnUr4gq9qx+IIYxxPL+JusJo9BPcOtIG6EZxaSqtOO9OGcYGON6aX9N4 gH1A==
X-Received: by 10.60.135.167 with SMTP id pt7mr21137074oeb.59.1374319425255; Sat, 20 Jul 2013 04:23:45 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.251.226 with HTTP; Sat, 20 Jul 2013 04:23:25 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20130719084234.0d874c10@resistor.net>
References: <CAHBU6ivQs+vsAtrV+Wqxwe2VDDjegYjU8aLPcAvaDkWWrrLBsw@mail.gmail.com> <6.2.5.6.2.20130719084234.0d874c10@resistor.net>
From: Scott Brim <scott.brim@gmail.com>
Date: Sat, 20 Jul 2013 07:23:25 -0400
Message-ID: <CAPv4CP8KzNeYfavm6pW0gF_XZK3ZbJuj983WqS5f+MQpJwO9yg@mail.gmail.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
To: S Moonesamy <sm+ietf@elandsys.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Tim Bray <tbray@textuality.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Jul 2013 11:23:46 -0000

Thanks, SM, for finding what I said back in 2010.  I still think this
is architected wrong, conflating devices with communication endpoints
higher up the stack, and steers us toward a path toward eventually
"needing" to reduce privacy even more.  However, 3GPP has apparently
already already started marching down that path.  Could our liaison
explain the situation there?  Is anyone actually going to use it?  Is
this a done deal - do we have to support it because otherwise 3 years
of 3GPP work get undone?

Scott

From garbakora@gmail.com  Sat Jul 20 04:53:19 2013
Return-Path: <garbakora@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E96E021E808F for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 04:53:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FW0LsLd-Z7RQ for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 04:53:19 -0700 (PDT)
Received: from mail-ob0-x22d.google.com (mail-ob0-x22d.google.com [IPv6:2607:f8b0:4003:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 796AA21E804D for <ietf@ietf.org>; Sat, 20 Jul 2013 04:53:19 -0700 (PDT)
Received: by mail-ob0-f173.google.com with SMTP id wc20so6373805obb.4 for <ietf@ietf.org>; Sat, 20 Jul 2013 04:53:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=md9tvxH4NImP+yWHVLsZEa9OJIszJVlR4NpMCrQyr8A=; b=fesj+figgOPWev8pbGO96Sj8F36fikHys7p9Aff9njWEZ3EW43khIHY1aHjKizR6tW 4i9x79+mqXfWxtttKiUaLbHT+gXsTJNPXl45Ga61SD3WzQG1Z7dV2Gjn/eOrrW0PKnWm Hg4qjxyrtHhGRF2KFyHLr9r9Yo49r/LDXkXOHUWK+43WP1t3sdb8atqeLF/VPGXbPj2C /Q5gxLtLvtv2UvGyyuNWltZSDzOTpDsXXuGaHNml7Jf+hakl7enC9qldkitFe2SkrJL7 OcQ4gUW+IeTyKHHGQqBO7iPLAp4qrUZH02KA0RvU92/GOb12uSTIS+rkME3cV0QCAim8 mHVg==
MIME-Version: 1.0
X-Received: by 10.60.155.200 with SMTP id vy8mr21001488oeb.72.1374321199024; Sat, 20 Jul 2013 04:53:19 -0700 (PDT)
Received: by 10.76.88.18 with HTTP; Sat, 20 Jul 2013 04:53:18 -0700 (PDT)
In-Reply-To: <CAPv4CP8KzNeYfavm6pW0gF_XZK3ZbJuj983WqS5f+MQpJwO9yg@mail.gmail.com>
References: <CAHBU6ivQs+vsAtrV+Wqxwe2VDDjegYjU8aLPcAvaDkWWrrLBsw@mail.gmail.com> <6.2.5.6.2.20130719084234.0d874c10@resistor.net> <CAPv4CP8KzNeYfavm6pW0gF_XZK3ZbJuj983WqS5f+MQpJwO9yg@mail.gmail.com>
Date: Sat, 20 Jul 2013 13:53:18 +0200
Message-ID: <CA+bJALpv0NyJJCnLjY1d0ZK0z-Awqz2oBe023CPt47fD8YS52g@mail.gmail.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
From: GARBA KORA TAMSIRD BELLO <garbakora@gmail.com>
To: Scott Brim <scott.brim@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Tim Bray <tbray@textuality.com>, S Moonesamy <sm+ietf@elandsys.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Jul 2013 11:53:20 -0000

Hi

Yes it true , but more argumentations are welcome

Sinverely yours

2013/7/20, Scott Brim <scott.brim@gmail.com>:
> Thanks, SM, for finding what I said back in 2010.  I still think this
> is architected wrong, conflating devices with communication endpoints
> higher up the stack, and steers us toward a path toward eventually
> "needing" to reduce privacy even more.  However, 3GPP has apparently
> already already started marching down that path.  Could our liaison
> explain the situation there?  Is anyone actually going to use it?  Is
> this a done deal - do we have to support it because otherwise 3 years
> of 3GPP work get undone?
>
> Scott
>

From sm@elandsys.com  Sat Jul 20 06:19:05 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A8FC21F9991 for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 06:19:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.591
X-Spam-Level: 
X-Spam-Status: No, score=-103.591 tagged_above=-999 required=5 tests=[AWL=1.008, BAYES_00=-2.599, GB_I_LETTER=-2, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aqUL-DzHlgOs for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 06:19:04 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AFD621F9AFD for <ietf@ietf.org>; Sat, 20 Jul 2013 06:18:49 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.151.133]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r6KDIJaJ012498 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 20 Jul 2013 06:18:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1374326314; bh=hVJoqrbhxd733qKKs0JkPoP97n6oeDiFICTeXcbTDVE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=HSXaw9hCtRdlb/LmGpAS9kJOc/GHU6+4fq4zaPXPKO64Uva6aM+lxnlChi2KYI2Y4 DGk7dB+vAhgEGc+cYJXOWFIhGNW90qNHLs2DblcPX7EkVeUIl3mtBk0DC0CHUQCj7Z 0FH241726mzp5dclL1s/7pMfrwGWKGmYDnIwvgEk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1374326314; i=@elandsys.com; bh=hVJoqrbhxd733qKKs0JkPoP97n6oeDiFICTeXcbTDVE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=ZWD/3p3DAmF1+g+wFRYU6A6eTvak3GXCznDhS7ZNJT7zX3qoRae8w4sZkpaL+AB7h qFO4IdhFZz4iREmDTtNQpNBsJ6d/hkX4WUNl0TFBbrskeH3bH5rkv6mDb8x8MYpLI4 TYc/qJMxK0H1Xs34GhnpzO2abdMqnrCTee0zS/zc=
Message-Id: <6.2.5.6.2.20130719164640.0be3e570@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 20 Jul 2013 06:17:59 -0700
To: ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
In-Reply-To: <BBF5DDFE515C3946BC18D733B20DAD2338DD1D6D@XMB104ADS.rim.net >
References: <CAHBU6ivpc+6-ZnjnTr5g5vvpDyCNdhvdyNsXChscnbGDJQmMzg@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD2338DD1D6D@XMB104ADS.rim.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: tbray@textuality.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Jul 2013 13:19:05 -0000

At 15:53 19-07-2013, Andrew Allen wrote:
>Do you not think that the text in the security considerations section::
>
>"because IMEIs can be loosely correlated to a user, they need to be 
>treated as any other personally identifiable information. In 
>particular, the IMEI URN MUST NOT be included in messages intended 
>to convey any level of anonymity"
>
>covers the privacy issue?
>
>If not what is the additional privacy concern?

There is a difference between privacy concerns and privacy 
considerations.  It has been mentioned that "the view in 3GPP was 
that the IMEI should not be of any greater concern when used as an 
instance ID than using a UUID".  draft-montemurro-gsma-imei-urn-16 states that:

   "Specifically the IMEI is to be incorporated in a module which is
    contained within the terminal.  The IMEI SHALL NOT be changed
    after the terminal's production process.  It SHALL resist tampering,
    i.e. manipulation and change, by any means  (e.g. physical,
    electrical and software)."

The pervasive use of UUID in computing does not make it a good 
idea.  I doubt that there has been any privacy analysis of how UUID 
will be used or misused prior to the publication of the RFC.  The 
IMEI is built into the device.  The scope for misuse would be clear 
enough for a person designing identifiers.

 From draft-montemurro-gsma-imei-urn-16:

   "Therefore the IMEISV (that is, the IMEI URN with svn parameter)
    MUST NOT be delivered to devices that are not trusted.  Further,
    because IMEIs can be loosely correlated to a user, they need to
    be treated as any other personally identifiable information.  In
    particular, the IMEI URN MUST NOT be included in messages intended
    to convey any level of anonymity."

The IMEI is considered as personal data in some jurisdictions.  There 
is a strong correlation between the IMEI and a user.

I read draft-montemurro-gsma-imei-urn-16 and I see that the four 
authors have listed their phone numbers as "unlisted".  Is there a 
reason for that?  The question may sound unrelated to the draft and 
it can be argued that it is unrelated to the draft.  I asked it as it 
may help the casual reader understand what privacy is 
about.  draft-moonesamy-privacy-identifiers-00 (expired) argues that 
there is an implicit assumption that the underlying protocols are 
transmitting the right amount of information needed for the protocols 
to work.  Is for example, urn:gsma:imei:90420156-025763-0, required 
for SIP to work?  I do not think so.

The world was somewhat naive about privacy in 2006.  Privacy is a hot 
topic nowadays.  The metadata debacle is one of the contributing 
factors.  There seems to be an assumption that the IMEISV is usually 
sent over trusted channels to trusted parties.

The second sentence containing "must not" written in capital letters 
takes a position where anonymity of messages is opt-in.  The GSM 
Association has published a set of principles which mentions "privacy 
by design".  It is up to the reader to read the two sentences quoted 
above and determine whether "privacy by design" is just another 
buzzword or a principle which the GSM Association considers as important.

At 04:23 20-07-2013, Scott Brim wrote:
>Thanks, SM, for finding what I said back in 2010.  I still think this
>is architected wrong, conflating devices with communication endpoints
>higher up the stack, and steers us toward a path toward eventually
>"needing" to reduce privacy even more.  However, 3GPP has apparently
>already already started marching down that path.  Could our liaison
>explain the situation there?  Is anyone actually going to use it?  Is
>this a done deal - do we have to support it because otherwise 3 years
>of 3GPP work get undone?

As a responding to Scott's comment about the three years of work I 
would say that this has the signs of an inevitable decision.  I'll 
describe the IETF angle as follows:

   Is it okay to assign a Uniform Resource Name namespace for GSMA?

The namespace assignment is not a problem.  Have an assignment 
request sitting in the IETF queue for seven years is a problem.  It 
would be good if someone explained why this happened unless the IETF 
considers it as acceptable to be asked to take inevitable decisions.

I agree with Scott's comment.  Tim Bray already pointed out that this 
is a bad idea.

At 04:53 20-07-2013, GARBA KORA TAMSIRD BELLO wrote:
>Yes it true , but more argumentations are welcome

The duck won't fly. :-)

Regards,
S. Moonesamy 


From john-ietf@jck.com  Sat Jul 20 06:56:48 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5050F11E810A for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 06:56:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.631
X-Spam-Level: 
X-Spam-Status: No, score=-102.631 tagged_above=-999 required=5 tests=[AWL=-0.032, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1jBpd5x1iSHi for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 06:56:42 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 7506211E8101 for <ietf@ietf.org>; Sat, 20 Jul 2013 06:56:42 -0700 (PDT)
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 1V0XeL-000NWF-3e for ietf@ietf.org; Sat, 20 Jul 2013 09:56:41 -0400
Date: Sat, 20 Jul 2013 09:56:36 -0400
From: John C Klensin <john-ietf@jck.com>
To: ietf@ietf.org
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
Message-ID: <C950B8C7FFD6737406CB78C4@JcK-HP8200.jck.com>
In-Reply-To: <CAPv4CP8KzNeYfavm6pW0gF_XZK3ZbJuj983WqS5f+MQpJwO9yg@mail.gmail.com>
References: <CAHBU6ivQs+vsAtrV+Wqxwe2VDDjegYjU8aLPcAvaDkWWrrLBsw@mail.gmail.com> <6.2.5.6.2.20130719084234.0d874c10@resistor.net> <CAPv4CP8KzNeYfavm6pW0gF_XZK3ZbJuj983WqS5f+MQpJwO9yg@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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Jul 2013 13:56:48 -0000

Hi.

Borrowing from several other notes and comments, it seems to me
that we have three interlocking issues that keep recurring and
producing long discussions.  They are by no means independent of
this particular draft, but seem to be becoming generic.

(1) Are we willing to publish (or even standardize) specs whose
nature is to provide a vehicle for making privacy-sensitive
information public?  The arguments against doing so seem
obvious.  The arguments for doing so include "those who claim
they need this will do it anyway so we are better off publishing
a spec that will at least reduce interoperability side-effects
and permit spelling out the issues as "privacy considerations"
or security ones.

(2) Is turning hardware identifiers (physical-layer objects)
into applications or user level identifiers an acceptable idea?
Are DNS RRTYPEs that map application-level identifiers into
other identifiers that can loop back through the DNS without
guarantees that the process will terminate part of the same
problem or a different one?

(3) Do either of the above answers change if the proposal comes
from another SDO or a major industry group?

I don't know the answers, but I'm pretty sure that trying to
address each of these issues separately every time a new
protocol, RRTYPE, or URN (or URI) type comes along that
interacts with one of them is not the way.  It seems to me that
we ought to have something along the lines of RFC 1984 in our
future and that a plenary discussion might be a useful first
step.  I don't suppose the IAB or IESG would be willing to
postpone or push something out of the announced agendas to allow
for that discussion, which, given this Last Call and the recent
one over RRTYPs would seem to be critical path.   Any volunteers
to get in front of the mic lines?

    john


From stephen.farrell@cs.tcd.ie  Sat Jul 20 07:52:08 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABC2D21E808B for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 07:52:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.577
X-Spam-Level: 
X-Spam-Status: No, score=-102.577 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IsHFoPJ+6Qtf for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 07:52:02 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 1413711E810C for <ietf@ietf.org>; Sat, 20 Jul 2013 07:51:59 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 5635BBE61; Sat, 20 Jul 2013 15:51:36 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z8n-JJGH4BBL; Sat, 20 Jul 2013 15:51:29 +0100 (IST)
Received: from [10.87.48.9] (unknown [86.41.50.155]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 0A32BBE53; Sat, 20 Jul 2013 15:51:29 +0100 (IST)
Message-ID: <51EAA3E6.1060708@cs.tcd.ie>
Date: Sat, 20 Jul 2013 15:51:18 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
References: <CAHBU6ivQs+vsAtrV+Wqxwe2VDDjegYjU8aLPcAvaDkWWrrLBsw@mail.gmail.com> <6.2.5.6.2.20130719084234.0d874c10@resistor.net> <CAPv4CP8KzNeYfavm6pW0gF_XZK3ZbJuj983WqS5f+MQpJwO9yg@mail.gmail.com> <C950B8C7FFD6737406CB78C4@JcK-HP8200.jck.com>
In-Reply-To: <C950B8C7FFD6737406CB78C4@JcK-HP8200.jck.com>
X-Enigmail-Version: 1.5.1
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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Jul 2013 14:52:09 -0000

Wrt privacy in general...

On 07/20/2013 02:56 PM, John C Klensin wrote:
>  Any volunteers
> to get in front of the mic lines?

I'd welcome that discussion. I'd love to see us have a
BCP61-like [1] RFC on the topic of privacy and I also
reckon that that'd help short-cut a number of IETF LCs
and IESG DISCUSSes. (For example the Forwarded HTTP
header and WebFinger both caused extensive discussions.)

FWIW, my personal preference would be that such a BCP
would attempt to make our work be more privacy friendly
and by default though I'm not quite how how best to try
achieve that though.

But, even if the outcome wasn't a BCP along the lines
I'd prefer, I think such a beast would still be worth
having if it meant we could avoid a whole lot of these
kinds of similar discussions on individual drafts.

S.

[1] http://tools.ietf.org/html/bcp61

From scott.brim@gmail.com  Sat Jul 20 08:06:59 2013
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C3DE11E8116 for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 08:06:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XKEus9DJlail for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 08:06:58 -0700 (PDT)
Received: from mail-oa0-x22b.google.com (mail-oa0-x22b.google.com [IPv6:2607:f8b0:4003:c02::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 93E1B11E8115 for <ietf@ietf.org>; Sat, 20 Jul 2013 08:06:58 -0700 (PDT)
Received: by mail-oa0-f43.google.com with SMTP id i7so7273418oag.2 for <ietf@ietf.org>; Sat, 20 Jul 2013 08:06:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=gvp+k/oeunxpzB928w15AAgGNhk1eD2Fv5hho0VpQ+k=; b=xwMhZ8QoPdw7m6nZrzqqjHfUBIWcAuSswZ/12kLPMC2FyH2Z6XAnT0sROD/iX7TCAN zef1MHegT6noGiR4fAgnBPQqO2myjD2dPsO2/5+FI3wlwnrBWFjfpkXEU1unRicHAt8L AMf4hndk6rh/L8zTCVHzyq4iz68trY0QQaLKhRh5wqS1d47wCedEa1BjHNCxi2rDeI8f gBdghiuySrzslAzM3MBBim6PgrW7+6JHafOV6yQFa/QEe0fvaX9bHx11OJjG98b3bTIU PfJMsI8yMGIpyK56PXxH4qOvMLXHrR4/k5nhk9Hsz93IIMk/953rCfOWULMWkcr5lB+1 j0fA==
X-Received: by 10.182.214.39 with SMTP id nx7mr15646671obc.20.1374332818138; Sat, 20 Jul 2013 08:06:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.251.226 with HTTP; Sat, 20 Jul 2013 08:06:38 -0700 (PDT)
In-Reply-To: <51EAA3E6.1060708@cs.tcd.ie>
References: <CAHBU6ivQs+vsAtrV+Wqxwe2VDDjegYjU8aLPcAvaDkWWrrLBsw@mail.gmail.com> <6.2.5.6.2.20130719084234.0d874c10@resistor.net> <CAPv4CP8KzNeYfavm6pW0gF_XZK3ZbJuj983WqS5f+MQpJwO9yg@mail.gmail.com> <C950B8C7FFD6737406CB78C4@JcK-HP8200.jck.com> <51EAA3E6.1060708@cs.tcd.ie>
From: Scott Brim <scott.brim@gmail.com>
Date: Sat, 20 Jul 2013 11:06:38 -0400
Message-ID: <CAPv4CP-RJoQ4uEuG4Dm9M086DVT1EeYM6m2p0nwqg_7RaM=AaA@mail.gmail.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1
Cc: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Jul 2013 15:06:59 -0000

On Sat, Jul 20, 2013 at 10:51 AM, Stephen Farrell
<stephen.farrell@cs.tcd.ie> wrote:
>
> Wrt privacy in general...
>
> On 07/20/2013 02:56 PM, John C Klensin wrote:
>>  Any volunteers
>> to get in front of the mic lines?
>
> I'd welcome that discussion. I'd love to see us have a
> BCP61-like [1] RFC on the topic of privacy and I also
> reckon that that'd help short-cut a number of IETF LCs
> and IESG DISCUSSes. (For example the Forwarded HTTP
> header and WebFinger both caused extensive discussions.)
>
> FWIW, my personal preference would be that such a BCP
> would attempt to make our work be more privacy friendly
> and by default though I'm not quite how how best to try
> achieve that though.
>
> But, even if the outcome wasn't a BCP along the lines
> I'd prefer, I think such a beast would still be worth
> having if it meant we could avoid a whole lot of these
> kinds of similar discussions on individual drafts.
>
> S.
>
> [1] http://tools.ietf.org/html/bcp61

I agree completely.  Doesn't draft-iab-privacy-considerations do what
you want?  (And no matter what gets agreed to at a general level, we
will still have these discussions about specifics.)

From john-ietf@jck.com  Sat Jul 20 08:31:48 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E2C621E80B3 for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 08:31:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.629
X-Spam-Level: 
X-Spam-Status: No, score=-102.629 tagged_above=-999 required=5 tests=[AWL=-0.030, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pS-BLezJ6GCv for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 08:31:42 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 431D821E80A8 for <ietf@ietf.org>; Sat, 20 Jul 2013 08:31:42 -0700 (PDT)
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 1V0Z8H-000Nbd-Ie; Sat, 20 Jul 2013 11:31:41 -0400
Date: Sat, 20 Jul 2013 11:31:36 -0400
From: John C Klensin <john-ietf@jck.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
Message-ID: <59A1B79358577FFBF7A3181B@JcK-HP8200.jck.com>
In-Reply-To: <51EAA3E6.1060708@cs.tcd.ie>
References: <CAHBU6ivQs+vsAtrV+Wqxwe2VDDjegYjU8aLPcAvaDkWWrrLBsw@mail.gmail.com> <6.2.5.6.2.20130719084234.0d874c10@resistor.net> <CAPv4CP8KzNeYfavm6pW0gF_XZK3ZbJuj983WqS5f+MQpJwO9yg@mail.gmail.com> <C950B8C7FFD6737406CB78C4@JcK-HP8200.jck.com> <51EAA3E6.1060708@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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Jul 2013 15:31:48 -0000

--On Saturday, July 20, 2013 15:51 +0100 Stephen Farrell
<stephen.farrell@cs.tcd.ie> wrote:

>...
> But, even if the outcome wasn't a BCP along the lines
> I'd prefer, I think such a beast would still be worth
> having if it meant we could avoid a whole lot of these
> kinds of similar discussions on individual drafts.

That was exactly what I was thinking.

I think the security analogy is a combination of BCP 61 (RFC
3365) and RFC 1984.  That is a quibble but relates to the
question of whether draft-iab-privacy-considerations is
sufficient.  I think it is necessary, but not sufficient. The
other piece would be a fairly clear and ideally consensus,
statement about what we do and do not intend to do and why.
IMO, the only want to make progress on avoiding these similar
discussions on individual drafts would be to develop such a
consensus and focus the discussions on it.

   john




From hsantos@isdg.net  Sat Jul 20 08:50:35 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A0CE11E811A for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 08:50:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.464
X-Spam-Level: 
X-Spam-Status: No, score=-103.464 tagged_above=-999 required=5 tests=[AWL=1.136, BAYES_00=-2.599, GB_I_INVITATION=-2, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PnWOpmJxp9PE for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 08:50:29 -0700 (PDT)
Received: from winserver.com (pop3.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 472A121F96EF for <ietf@ietf.org>; Sat, 20 Jul 2013 08:50:28 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=3978; t=1374335423; h=Received:Received: Message-ID:Date:From:To:Subject:Organization:List-ID; bh=CAObFhE Ti4DSF4NcSLYYrVe6Nn0=; b=JVy8CB7utsbWftLjdOUTas/Yy1Zi+ZgiJpw73OG KrYsWUPrxyGeIgtPfbreaBy0bIs1wX2nKXeV2VNr/KnCMbxJ+CpfjlBBYPp8RWlF 5ghcPdTx5x9B6ql/nnAlZqBPmY+GlEXNZ7DyN82FOsplysoA+7ILFqpwT+5zxBdi 4xwQ=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sat, 20 Jul 2013 11:50:23 -0400
Received: from [208.247.131.8] ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 797970824.5343.2748; Sat, 20 Jul 2013 11:50:22 -0400
Message-ID: <51EAB100.7090508@isdg.net>
Date: Sat, 20 Jul 2013 11:47:12 -0400
From: Hector Santos <hsantos@isdg.net>
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Mentoring Electronic Participants [was  Invitation to request an IETF mentor]
References: <20130717225841.14002.89245.idtracker@ietfa.amsl.com>
In-Reply-To: <20130717225841.14002.89245.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF Chair <chair@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Jul 2013 15:50:35 -0000

Overall, I think the IETF has a marketing problem addressing its #1 
customer base - electronic participants.

I was somewhat hoping to see more done in the mentor area of assisting 
electronic participants. Of coarse, this sort of electronic mentoring it 
could include an end goal to get folks more involved with the IETF 
directly, i.e. go to meetings, become leaders, etc, but overall assist 
with protocol standards development.

I presume, the IETF gets a far more population of electronic 
participants, many who first get involved with writing I-Ds. I have 
found it to be a high hurdle to get a I-D completed, especially if you 
never attended IETF meetings or have not sent someone or group on your 
company behalf.

As I have been advised by some IETF vets, I'm sure it will help with the 
process of getting others more comfortable with you and your work, but 
is it really absolutely necessary to attend IETF meetings to get an I-D 
moved thru the process?

I guess I could of requested more IETF interest/review for particular 
I-Ds I have worked on but it would of required stepping on some toes. I 
decided to avoid contention although the help I received was an attempt 
to avoid a conflict.

Maybe I'm off-base, but it just seems the mentoring efforts is targeted 
at attracting full time IETF members, future leaders, etc and not just 
the specific technical person who might be just interested in various 
protocols of interest and no more.  Our products are internet based and 
hence has dozens of protocols implemented. I'm here really just to keep 
on top of them, assist with improvements, and if need be try to get an 
I-D written if only to prove a point or get an idea out there for 
consideration and creative synergism.  Not interested in become an IETF 
full time attendee nor "leader" per se.

The IETF needs to improved its market across the globe and that really 
can only feasibly be done electronically.  There are needs to take 
efforts of getting electronic participants more involved. I think it can 
start with first helping and mentoring I-D writers.

What generally happens when an individual I-D is submitted?   Is there 
an overseer of the submissions and decides there is something that 
interest the IETF?

Thanks

--
HLS


On 7/17/2013 6:58 PM, IETF Chair wrote:
> All,
>
> During IETF 87 in Berlin, we will be running a trial of the IETF Mentoring Program. The goal of the IETF Mentoring Program is to match people new to the IETF (people who have participated in three or fewer face-to-face meetings or anyone registering as a student) 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.
>
> The IETF Mentoring Program was created to help new IETF participants to get up to speed rapidly and help them begin to contribute to the IETF quickly and easily.  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 then introduce you to each other by email, and invite you to meet up in person at the IETF Meet & Greet event on Sunday afternoon in Berlin. 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 stephen.farrell@cs.tcd.ie  Sat Jul 20 11:10:39 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5488821F9EAF for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 11:10:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.579
X-Spam-Level: 
X-Spam-Status: No, score=-102.579 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zRT6PeFhx2Wa for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 11:10:33 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 00E3121F9D8F for <ietf@ietf.org>; Sat, 20 Jul 2013 11:10:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 42A23BE6E; Sat, 20 Jul 2013 19:10:10 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sN8IRMw6Qu+H; Sat, 20 Jul 2013 19:10:09 +0100 (IST)
Received: from [10.87.48.9] (unknown [86.41.50.155]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 2F9AFBE61; Sat, 20 Jul 2013 19:10:09 +0100 (IST)
Message-ID: <51EAD280.8020702@cs.tcd.ie>
Date: Sat, 20 Jul 2013 19:10:08 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
References: <CAHBU6ivQs+vsAtrV+Wqxwe2VDDjegYjU8aLPcAvaDkWWrrLBsw@mail.gmail.com> <6.2.5.6.2.20130719084234.0d874c10@resistor.net> <CAPv4CP8KzNeYfavm6pW0gF_XZK3ZbJuj983WqS5f+MQpJwO9yg@mail.gmail.com> <C950B8C7FFD6737406CB78C4@JcK-HP8200.jck.com> <51EAA3E6.1060708@cs.tcd.ie> <CAPv4CP-RJoQ4uEuG4Dm9M086DVT1EeYM6m2p0nwqg_7RaM=AaA@mail.gmail.com>
In-Reply-To: <CAPv4CP-RJoQ4uEuG4Dm9M086DVT1EeYM6m2p0nwqg_7RaM=AaA@mail.gmail.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Jul 2013 18:10:39 -0000

On 07/20/2013 04:06 PM, Scott Brim wrote:
> On Sat, Jul 20, 2013 at 10:51 AM, Stephen Farrell
> <stephen.farrell@cs.tcd.ie> wrote:
>>
>> Wrt privacy in general...
>>
>> On 07/20/2013 02:56 PM, John C Klensin wrote:
>>>  Any volunteers
>>> to get in front of the mic lines?
>>
>> I'd welcome that discussion. I'd love to see us have a
>> BCP61-like [1] RFC on the topic of privacy and I also
>> reckon that that'd help short-cut a number of IETF LCs
>> and IESG DISCUSSes. (For example the Forwarded HTTP
>> header and WebFinger both caused extensive discussions.)
>>
>> FWIW, my personal preference would be that such a BCP
>> would attempt to make our work be more privacy friendly
>> and by default though I'm not quite how how best to try
>> achieve that though.
>>
>> But, even if the outcome wasn't a BCP along the lines
>> I'd prefer, I think such a beast would still be worth
>> having if it meant we could avoid a whole lot of these
>> kinds of similar discussions on individual drafts.
>>
>> S.
>>
>> [1] http://tools.ietf.org/html/bcp61
> 
> I agree completely.  Doesn't draft-iab-privacy-considerations do what
> you want?  

As John said, that sets out considerations but what I'm
talking about here would be a BCP, so no that's a useful
input but doesn't represent an IETF consensus position
the way a BCP would.

S.

> (And no matter what gets agreed to at a general level, we
> will still have these discussions about specifics.)



> 

From stephen.farrell@cs.tcd.ie  Sat Jul 20 11:14:21 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1912F21F909A for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 11:14:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.582
X-Spam-Level: 
X-Spam-Status: No, score=-102.582 tagged_above=-999 required=5 tests=[AWL=0.018, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XP+ZXiku7kS3 for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 11:14:15 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id DCFF921F9BC3 for <ietf@ietf.org>; Sat, 20 Jul 2013 11:14:14 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 0EA79BE6E; Sat, 20 Jul 2013 19:13:53 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uzbsySqf9dgx; Sat, 20 Jul 2013 19:13:52 +0100 (IST)
Received: from [10.87.48.9] (unknown [86.41.50.155]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 4500DBE61; Sat, 20 Jul 2013 19:13:52 +0100 (IST)
Message-ID: <51EAD360.4040801@cs.tcd.ie>
Date: Sat, 20 Jul 2013 19:13:52 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
References: <CAHBU6ivQs+vsAtrV+Wqxwe2VDDjegYjU8aLPcAvaDkWWrrLBsw@mail.gmail.com> <6.2.5.6.2.20130719084234.0d874c10@resistor.net> <CAPv4CP8KzNeYfavm6pW0gF_XZK3ZbJuj983WqS5f+MQpJwO9yg@mail.gmail.com> <C950B8C7FFD6737406CB78C4@JcK-HP8200.jck.com> <51EAA3E6.1060708@cs.tcd.ie> <59A1B79358577FFBF7A3181B@JcK-HP8200.jck.com>
In-Reply-To: <59A1B79358577FFBF7A3181B@JcK-HP8200.jck.com>
X-Enigmail-Version: 1.5.1
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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Jul 2013 18:14:21 -0000

On 07/20/2013 04:31 PM, John C Klensin wrote:
> 
> 
> --On Saturday, July 20, 2013 15:51 +0100 Stephen Farrell
> <stephen.farrell@cs.tcd.ie> wrote:
> 
>> ...
>> But, even if the outcome wasn't a BCP along the lines
>> I'd prefer, I think such a beast would still be worth
>> having if it meant we could avoid a whole lot of these
>> kinds of similar discussions on individual drafts.
> 
> That was exactly what I was thinking.
> 
> I think the security analogy is a combination of BCP 61 (RFC
> 3365) and RFC 1984.  That is a quibble but relates to the
> question of whether draft-iab-privacy-considerations is
> sufficient.  I think it is necessary, but not sufficient. The
> other piece would be a fairly clear and ideally consensus,
> statement about what we do and do not intend to do and why.

Fully agree. I do hope we get this discussion at the mic in
Berlin. (Or if some folks are already interested in working
on this just send me a mail.)

If someone felt this whole thing was a bad plan, now'd also
be a good time to hear about that (and why). Though of course
there'd be loads more opportunities for that too.

S.

> IMO, the only want to make progress on avoiding these similar
> discussions on individual drafts would be to develop such a
> consensus and focus the discussions on it.
> 
>    john
> 
> 
> 
> 

From prvs=3913449491=aallen@blackberry.com  Sat Jul 20 11:28:27 2013
Return-Path: <prvs=3913449491=aallen@blackberry.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AD0921E80C1 for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 11:28:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.552
X-Spam-Level: 
X-Spam-Status: No, score=-5.552 tagged_above=-999 required=5 tests=[AWL=-0.349, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uiXC9fGIn9QM for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 11:28:21 -0700 (PDT)
Received: from mhs061cnc.rim.net (mhs061cnc.rim.net [208.65.73.35]) by ietfa.amsl.com (Postfix) with ESMTP id C5BFB11E811D for <ietf@ietf.org>; Sat, 20 Jul 2013 11:28:20 -0700 (PDT)
X-AuditID: 0a412830-b7fa06d000003f99-e5-51ead6bca158
Received: from XCT101ADS.rim.net (xct101ads.rim.net [10.67.111.42]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by mhs061cnc.rim.net (SBG) with SMTP id 13.5C.16281.CB6DAE15; Sat, 20 Jul 2013 13:28:12 -0500 (CDT)
Received: from XMB104ADS.rim.net ([fe80::2494:a63d:e3:723b]) by XCT101ADS.rim.net ([fe80::2c7e:1215:d554:35b5%20]) with mapi id 14.02.0328.009; Sat, 20 Jul 2013 13:28:11 -0500
From: Andrew Allen <aallen@blackberry.com>
To: "scott.brim@gmail.com" <scott.brim@gmail.com>, "sm+ietf@elandsys.com" <sm+ietf@elandsys.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
Thread-Topic: Last call: draft-montemurro-gsma-imei-urn-16.txt
Thread-Index: AQHOhJEO4fYTwuVTOkCw8MDTXs0bMZlsOFEcgAGJd4CAACLcBA==
Date: Sat, 20 Jul 2013 18:28:11 +0000
Message-ID: <BBF5DDFE515C3946BC18D733B20DAD2338DD2318@XMB104ADS.rim.net>
In-Reply-To: <CAPv4CP8KzNeYfavm6pW0gF_XZK3ZbJuj983WqS5f+MQpJwO9yg@mail.gmail.com>
Accept-Language: en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.67.110.252]
Content-Type: text/plain; charset="iso-8859-1"
content-transfer-encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrFKsWRmVeSWpSXmKPExsXC5Zyvpbvn2qtAg6mXjSyebZzPYvFux2E2 i1f9N1ktlv6Zz+LA4nHvzUcmj52z7rJ7LFnyk8nj0tLJzAEsUQ2MNkmJJWXBmel5+nY2iXl5 +SWJJakKKanFybZKPqnpiTkKAUWZZYnJlQoumcXJOYmZualFSgqZKbZKJkoKBTmJyam5qXkl tkqJBQWpeSlKdlwKGMAGqCwzTyE1Lzk/JTMv3VbJM9hf18LC1FLXUMlON6GTJ+PJlb9sBV95 K45MWcjYwLiFu4uRk0NCwERi44ojbBC2mMSFe+uBbC4OIYE2JonZlzYyQTibGSUWvr3ICFLF JqAlsf/wdCYQW0QgSWLhxA3MIDazQIjE4hcP2EFsYQFbicun/zBC1NhJfD94iQXCdpJ4/msZ 2DYWAVWJezM+g9m8Ah4SL341g9VzCgRK3FlwFizOKCArsfvsdSaI+eISt57MZ4K4VEBiyZ7z zBC2qMTLx/9YIWxFicct3SwQ9XoSN6ZOYYOwtSWWLXzNDLFLUOLkzCcsExhFZyEZOwtJyywk LbOQtCxgZFnFKJibUWxgZpicl6xXlJmrl5dasokRlDgcNQx2ML5/b3GIUYCDUYmHd8O2V4FC rIllxZW5hxglOJiVRHgP9gGFeFMSK6tSi/Lji0pzUosPMboCQ2IisxR3cj4wqeWVxBsbGODm KInzWp89GygkkA5MP9mpqQWpRTBzmDg4QfZwSYkUA5NIalFiaUlGPCjVxRcDk51UA2OKZnfC Hks7C3uXmF1qsdUvdMT1k0xCS1SkXTjLdJ2aOi4ImazI2fTgx5bMD5krnX8ummAQdVWr6my9 PqdSxdKp4W9/5zW3cM+a0SWQcix95oEFHKWLP/7WOu9tbDHxfu+9J2JbHK09wq68sSjsT3og X31NtcT1qDlv7lyrxz95+XKbzacvUWIpzkg01GIuKk4EAKp9X1NdAwAA
Cc: "tbray@textuality.com" <tbray@textuality.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Jul 2013 18:28:27 -0000

The URN containing the IMEI is used by all mobile phones that support voice=
 over LTE. It is a dependency for 3GPP release 8 (which was completed about=
 end of 2008). So yes it is going to be used and its more than 3 years of 3G=
PP work invested and is already incorporated into many devices. 

In the pre-existing circuit switched systems the IMEI is delivered to the ne=
twork as the device identifier and it is also necessary to deliver the same=
 device identifier to the network when using SIP so that when handover takes=
 place between packet switched and circuit switched the network can correlat=
e the communication as being with the same device. 

Regulations also require the IMEI to be delivered to the network. 
This associated draft describes how 3GPP uses the IMEI as a SIP instance ID=
 and the reasons why:
http://datatracker.ietf.org/doc/draft-allen-dispatch-imei-urn-as-instanceid/
 


----- Original Message -----
From: Scott Brim [mailto:scott.brim@gmail.com]
Sent: Saturday, July 20, 2013 06:23 AM Central Standard Time=0A=
To: S Moonesamy <sm+ietf@elandsys.com>
Cc: Tim Bray <tbray@textuality.com>; ietf@ietf.org <ietf@ietf.org>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt

Thanks, SM, for finding what I said back in 2010.  I still think this
is architected wrong, conflating devices with communication endpoints
higher up the stack, and steers us toward a path toward eventually
"needing" to reduce privacy even more.  However, 3GPP has apparently
already already started marching down that path.  Could our liaison
explain the situation there?  Is anyone actually going to use it?  Is
this a done deal - do we have to support it because otherwise 3 years
of 3GPP work get undone?

Scott

---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential infor=
mation, privileged material (including material protected by the solicitor-c=
lient or other applicable privileges), or constitute non-public information.=
 Any use of this information by anyone other than the intended recipient is=
 prohibited. If you have received this transmission in error, please immedia=
tely reply to the sender and delete this information from your system. Use,=
 dissemination, distribution, or reproduction of this transmission by uninte=
nded recipients is not authorized and may be unlawful.

From tbray@textuality.com  Sat Jul 20 11:36:37 2013
Return-Path: <tbray@textuality.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B7F621E80C1 for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 11:36:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.768
X-Spam-Level: 
X-Spam-Status: No, score=-2.768 tagged_above=-999 required=5 tests=[AWL=0.208,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2oda0QBYKclC for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 11:36:32 -0700 (PDT)
Received: from mail-ve0-f180.google.com (mail-ve0-f180.google.com [209.85.128.180]) by ietfa.amsl.com (Postfix) with ESMTP id 0681611E811D for <ietf@ietf.org>; Sat, 20 Jul 2013 11:36:31 -0700 (PDT)
Received: by mail-ve0-f180.google.com with SMTP id pa12so4173880veb.11 for <ietf@ietf.org>; Sat, 20 Jul 2013 11:36:30 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=RelOAaYGqlA0a+RyLcJ0Wz5UJi0sRTyd4HKoVvoHfV8=; b=gGKXc+RliQJ+VGHMPO9V0t+fZcXGNQ0gBYCMVBrz8Tl0QIEO5b2hD1exn7en1bE8Fz CPMIJxXsX5Y624WDNrUbFzNU2/qeihbxT2M+AKFSvXVc6NSUn49X4Wjw/Iss5MuO0jvj 8lg+G5mO8SydOm3yydBwu2HoINN0rbyCsPNY8CLUnfAAwwX2rkJnBsNWatKsq/S1yGdt djAQsoKDiC0tof7Kqih6l5a4UQTipkvgm/BFp2whfxYF9iH4+tGhxkvukaXtxxy0jtZi BSCpxrVqw77Fgijyqnj/gerfWImZ65caSQgUOlM0mOX06iijbc+N7IWseTaRZf68pEpF ACgQ==
MIME-Version: 1.0
X-Received: by 10.52.89.100 with SMTP id bn4mr403963vdb.94.1374345390211; Sat, 20 Jul 2013 11:36:30 -0700 (PDT)
Received: by 10.220.219.200 with HTTP; Sat, 20 Jul 2013 11:36:30 -0700 (PDT)
X-Originating-IP: [24.84.235.32]
In-Reply-To: <BBF5DDFE515C3946BC18D733B20DAD2338DD2318@XMB104ADS.rim.net>
References: <CAPv4CP8KzNeYfavm6pW0gF_XZK3ZbJuj983WqS5f+MQpJwO9yg@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD2338DD2318@XMB104ADS.rim.net>
Date: Sat, 20 Jul 2013 11:36:30 -0700
Message-ID: <CAHBU6ivmsWUzEa+vhhACdg_9e+=b2euZJoD9wj9Gvv3EbNiVdw@mail.gmail.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
From: Tim Bray <tbray@textuality.com>
To: Andrew Allen <aallen@blackberry.com>
Content-Type: multipart/alternative; boundary=20cf307d0650c85a4604e1f5b8ea
X-Gm-Message-State: ALoCoQmphf2EERojtVCMvtUN/sb8YdaiHk5S5+QYvHAMVllYRhoRF7TZv0O+MZjQyNIHIwHFTy+u
Cc: "sm+ietf@elandsys.com" <sm+ietf@elandsys.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Jul 2013 18:36:37 -0000

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

So if it=E2=80=99s going to be used, exactly as specified, whatever we do, =
then
what value is added by the IETF process?  -T


On Sat, Jul 20, 2013 at 11:28 AM, Andrew Allen <aallen@blackberry.com>wrote=
:

>
> The URN containing the IMEI is used by all mobile phones that support
> voice over LTE. It is a dependency for 3GPP release 8 (which was complete=
d
> about end of 2008). So yes it is going to be used and its more than 3 yea=
rs
> of 3GPP work invested and is already incorporated into many devices.
>
> In the pre-existing circuit switched systems the IMEI is delivered to the
> network as the device identifier and it is also necessary to deliver the
> same device identifier to the network when using SIP so that when handove=
r
> takes place between packet switched and circuit switched the network can
> correlate the communication as being with the same device.
>
> Regulations also require the IMEI to be delivered to the network.
> This associated draft describes how 3GPP uses the IMEI as a SIP instance
> ID and the reasons why:
>
> http://datatracker.ietf.org/doc/draft-allen-dispatch-imei-urn-as-instance=
id/
>
>
>
> ----- Original Message -----
> From: Scott Brim [mailto:scott.brim@gmail.com]
> Sent: Saturday, July 20, 2013 06:23 AM Central Standard Time
> To: S Moonesamy <sm+ietf@elandsys.com>
> Cc: Tim Bray <tbray@textuality.com>; ietf@ietf.org <ietf@ietf.org>
> Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
>
> Thanks, SM, for finding what I said back in 2010.  I still think this
> is architected wrong, conflating devices with communication endpoints
> higher up the stack, and steers us toward a path toward eventually
> "needing" to reduce privacy even more.  However, 3GPP has apparently
> already already started marching down that path.  Could our liaison
> explain the situation there?  Is anyone actually going to use it?  Is
> this a done deal - do we have to support it because otherwise 3 years
> of 3GPP work get undone?
>
> Scott
>
> ---------------------------------------------------------------------
> This transmission (including any attachments) may contain confidential
> information, privileged material (including material protected by the
> solicitor-client or other applicable privileges), or constitute non-publi=
c
> information. Any use of this information by anyone other than the intende=
d
> recipient is prohibited. If you have received this transmission in error,
> please immediately reply to the sender and delete this information from
> your system. Use, dissemination, distribution, or reproduction of this
> transmission by unintended recipients is not authorized and may be unlawf=
ul.
>

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

<div dir=3D"ltr">So if it=E2=80=99s going to be used, exactly as specified,=
 whatever we do, then what value is added by the IETF process?=C2=A0 -T<br>=
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Sat,=
 Jul 20, 2013 at 11:28 AM, Andrew Allen <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:aallen@blackberry.com" target=3D"_blank">aallen@blackberry.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>
The URN containing the IMEI is used by all mobile phones that support voice=
 over LTE. It is a dependency for 3GPP release 8 (which was completed about=
 end of 2008). So yes it is going to be used and its more than 3 years of 3=
GPP work invested and is already incorporated into many devices.<br>

<br>
In the pre-existing circuit switched systems the IMEI is delivered to the n=
etwork as the device identifier and it is also necessary to deliver the sam=
e device identifier to the network when using SIP so that when handover tak=
es place between packet switched and circuit switched the network can corre=
late the communication as being with the same device.<br>

<br>
Regulations also require the IMEI to be delivered to the network.<br>
This associated draft describes how 3GPP uses the IMEI as a SIP instance ID=
 and the reasons why:<br>
<a href=3D"http://datatracker.ietf.org/doc/draft-allen-dispatch-imei-urn-as=
-instanceid/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-allen=
-dispatch-imei-urn-as-instanceid/</a><br>
<div class=3D"im HOEnZb"><br>
<br>
<br>
----- Original Message -----<br>
From: Scott Brim [mailto:<a href=3D"mailto:scott.brim@gmail.com">scott.brim=
@gmail.com</a>]<br>
Sent: Saturday, July 20, 2013 06:23 AM Central Standard Time<br>
To: S Moonesamy &lt;<a href=3D"mailto:sm%2Bietf@elandsys.com">sm+ietf@eland=
sys.com</a>&gt;<br>
</div><div class=3D"im HOEnZb">Cc: Tim Bray &lt;<a href=3D"mailto:tbray@tex=
tuality.com">tbray@textuality.com</a>&gt;; <a href=3D"mailto:ietf@ietf.org"=
>ietf@ietf.org</a> &lt;<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&g=
t;<br>

Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt<br>
<br>
</div><div class=3D"HOEnZb"><div class=3D"h5">Thanks, SM, for finding what =
I said back in 2010. =C2=A0I still think this<br>
is architected wrong, conflating devices with communication endpoints<br>
higher up the stack, and steers us toward a path toward eventually<br>
&quot;needing&quot; to reduce privacy even more. =C2=A0However, 3GPP has ap=
parently<br>
already already started marching down that path. =C2=A0Could our liaison<br=
>
explain the situation there? =C2=A0Is anyone actually going to use it? =C2=
=A0Is<br>
this a done deal - do we have to support it because otherwise 3 years<br>
of 3GPP work get undone?<br>
<br>
Scott<br>
<br>
</div></div><div class=3D"HOEnZb"><div class=3D"h5">-----------------------=
----------------------------------------------<br>
This transmission (including any attachments) may contain confidential info=
rmation, privileged material (including material protected by the solicitor=
-client or other applicable privileges), or constitute non-public informati=
on. Any use of this information by anyone other than the intended recipient=
 is prohibited. If you have received this transmission in error, please imm=
ediately reply to the sender and delete this information from your system. =
Use, dissemination, distribution, or reproduction of this transmission by u=
nintended recipients is not authorized and may be unlawful.<br>

</div></div></blockquote></div><br></div>

--20cf307d0650c85a4604e1f5b8ea--

From prvs=6913658f8e=aallen@blackberry.com  Sat Jul 20 13:08:50 2013
Return-Path: <prvs=6913658f8e=aallen@blackberry.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B95A21F9A16 for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 13:08:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.179
X-Spam-Level: 
X-Spam-Status: No, score=-6.179 tagged_above=-999 required=5 tests=[AWL=0.419,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nCYtygp9vN3K for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 13:08:46 -0700 (PDT)
Received: from mhs060cnc.rim.net (mhs060cnc.rim.net [208.65.73.34]) by ietfa.amsl.com (Postfix) with ESMTP id DD4E521F9A05 for <ietf@ietf.org>; Sat, 20 Jul 2013 13:08:45 -0700 (PDT)
X-AuditID: 0a41282f-b7f9b6d000002847-75-51eaee3da235
Received: from XCT101ADS.rim.net (xct101ads.rim.net [10.67.111.42]) by mhs060cnc.rim.net (SBG) with SMTP id EE.DF.10311.D3EEAE15; Sat, 20 Jul 2013 15:08:30 -0500 (CDT)
Received: from XMB104ADS.rim.net ([fe80::2494:a63d:e3:723b]) by XCT101ADS.rim.net ([fe80::2c7e:1215:d554:35b5%20]) with mapi id 14.02.0328.009; Sat, 20 Jul 2013 15:08:29 -0500
From: Andrew Allen <aallen@blackberry.com>
To: "tbray@textuality.com" <tbray@textuality.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
Thread-Topic: Last call: draft-montemurro-gsma-imei-urn-16.txt
Thread-Index: AQHOhJEO4fYTwuVTOkCw8MDTXs0bMZlsItsKgABZfICAAYRS+g==
Date: Sat, 20 Jul 2013 20:08:28 +0000
Message-ID: <BBF5DDFE515C3946BC18D733B20DAD2338DD2341@XMB104ADS.rim.net>
In-Reply-To: <CAHBU6ivC37fzO1oC=Ow3EGfBUt2GEsLRy3YWn6OZa9tTTTNZpQ@mail.gmail.com>
Accept-Language: en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.67.110.252]
Content-Type: multipart/alternative; boundary="_000_BBF5DDFE515C3946BC18D733B20DAD2338DD2341XMB104ADSrimnet_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrBKsWRmVeSWpSXmKPExsXC5ZyvpWv37lWgwaPHLBbPNs5nsVj6Zz6L A5PHkiU/mTwuLZ3MHMAU1cBok5RYUhacmZ6nb2eTmJeXX5JYkqqQklqcbKvkk5qemKMQUJRZ lphcqeCSWZyck5iZm1qkpJCZYqtkoqRQkJOYnJqbmldiq5RYUJCal6Jkx6WAAWyAyjLzFFLz kvNTMvPSbZU8g/11LSxMLXUNlex0Ezp5MqbdfsFe8Cm6YsG1eYwNjBsiuxg5OSQETCRmbH/N BGGLSVy4t56ti5GLQ0hgJaPEy1XzoJzNjBIXXjSzg1SxCWhJ7D88HaiDg0NEwFBi0V4vkDCz gLLE001zwAYJC9hKXD79hxHEFhGwk/h+8BILhO0kMfnldbA4i4CqxPpZfYwgY3gFPCQ6TruC hDkFAiU+TrzPDGIzCshK7D57nQlivLjErSfzoe4UkFiy5zwzhC0q8fLxP1YIW1HicUs3C0R9 vkTjwQ9gF/MKCEqcnPmEZQKjyCwko2YhKZuFpGwW0EXMApoS63fpQ5QoSkzpfsgOYWtItM6Z y44svoCRfRWjYG5GsYGZQXJesl5RZq5eXmrJJkZQ6nDU0N/B+Pa9xSFGAQ5GJR5esYevAoVY E8uKK3MPMUpwMCuJ8Fo+AwrxpiRWVqUW5ccXleakFh9iDAKGz0RmKe7kfGBayyuJNzYwIJKj JM5rdfZsoJBAOjCFZaemFqQWwQxl4uAEWcolJVIMTESpRYmlJRnxoHQZXwxMmFINjA4SR359 Sqt/ZO1m/TTMnfmHy4w9+2OttroxSd3f9tf7ZFpO98n5S3lbr1qwcV5tin/QPXPbQbGC6kfe Yl9nsZVPen9zS//JWzN0H1ax+bzhtrTIS1e4wCOzRf2DikjzzuyA1Xk1BZnPOttC7362jl1u 7axzptd5mhGrwQwrhtu6QUKW047lKrEUZyQaajEXFScCAMdGSBhrAwAA
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Jul 2013 20:08:50 -0000

--_000_BBF5DDFE515C3946BC18D733B20DAD2338DD2341XMB104ADSrimnet_
Content-Type: text/plain; charset="utf-8"
content-transfer-encoding: base64

DQpUaW0NCg0KVGhlIHF1b3RlIGlzIGZyb20gUkZDIDU2MjYgd2hpY2ggYWxzbyBzdGF0ZXM6
DQoNCiIzLjEuIFN1bW1hcnkgb2YgTWVjaGFuaXNtDQoNCkVhY2ggVUEgaGFzIGEgdW5pcXVl
IGluc3RhbmNlLWlkIHRoYXQgc3RheXMgdGhlIHNhbWUgZm9yIHRoaXMgVUEgZXZlbiBpZiB0
aGUgVUEgcmVib290cyBvciBpcyBwb3dlciBjeWNsZWQuIg0KDQpTaW5jZSB0aGUgVVVJRCBp
biB0aGUgaW5zdGFuY2UgSUQgaXMgYWxzbyBzdGF0aWMgaG93IGlzIHRoaXMgc2lnbmlmaWNh
bnRseSBkaWZmZXJlbnQgaW4gdGVybXMgb2YgcHJpdmFjeSBjb25jZXJucyBmcm9tIHRoZSBJ
TUVJIGJlaW5nIHVzZWQgYXMgYW4gaW5zdGFuY2UgSUQ/DQoNCkFuZHJldw0KDQpGcm9tOiBU
aW0gQnJheSBbbWFpbHRvOnRicmF5QHRleHR1YWxpdHkuY29tXQ0KU2VudDogRnJpZGF5LCBK
dWx5IDE5LCAyMDEzIDEwOjU4IEFNIENlbnRyYWwgU3RhbmRhcmQgVGltZQ0KVG86IEFuZHJl
dyBBbGxlbg0KQ2M6IGlldGZAaWV0Zi5vcmcgPGlldGZAaWV0Zi5vcmc+DQpTdWJqZWN0OiBS
ZTogTGFzdCBjYWxsOiBkcmFmdC1tb250ZW11cnJvLWdzbWEtaW1laS11cm4tMTYudHh0DQoN
Ck9uIEZyaSwgSnVsIDE5LCAyMDEzIGF0IDg6MzggQU0sIEFuZHJldyBBbGxlbiA8YWFsbGVu
QGJsYWNrYmVycnkuY29tPG1haWx0bzphYWxsZW5AYmxhY2tiZXJyeS5jb20+PiB3cm90ZToN
Ckkgc3VnZ2VzdCB5b3UgYWxzbyByZWFkDQpodHRwOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcv
ZG9jL2RyYWZ0LWFsbGVuLWRpc3BhdGNoLWltZWktdXJuLWFzLWluc3RhbmNlaWQvDQoNClF1
b3RpbmcgZnJvbSB0aGF0IGRvY3VtZW50OiDigJxJZiBhIFVSTiBzY2hlbWUgb3RoZXIgdGhh
biBVVUlEIGlzIHVzZWQsIHRoZSBVQSBNVVNUIG9ubHkgdXNlIFVSTnMgZm9yIHdoaWNoIGFu
IFJGQyAoZnJvbSB0aGUgSUVURiBzdHJlYW0pIGRlZmluZXMgaG93IHRoZSBzcGVjaWZpYyBV
Uk4gbmVlZHMgdG8gYmUgY29uc3RydWN0ZWQuLi7igJ0NCg0KTm93LCBJ4oCZbSBub3QgYW4g
ZXhwZXJ0IGluIHRoZSAzR1BQIHdvcmxkOyBidXQgdGhlIHN1Z2dlc3Rpb24gaW4gdGhhdCBl
eHRyYWN0IHRoYXQgVVVJRHMgYXJlIGEgYmV0dGVyIGNob2ljZSB0aGFuIGEgKHNoYWt5LCB1
bnJlbGlhYmxlLCBwcml2YWN5LXByb2JsZW1hdGljKSBkZXZpY2UgaWRlbnRpZmllciBjZXJ0
YWlubHkgcmluZ3MgdHJ1ZSBmb3IgdGhvc2Ugb2YgdXMgd2hvIHRoaW5rIGF0IHRoZSBhcHBz
IGxldmVsLiAgLVQNCg0KDQoNClRoYXQgd2lsbCBleHBsYWluIHRoZSBwcmltYXJ5IGFwcGxp
Y2F0aW9uIG9mIHRoaXMgVVJOIHdoaWNoIGlzIGludGVuZGVkIGZvciB1c2UgaW4gdGhlIDNH
UFAgY2VsbHVsYXIgc3RhbmRhcmRzLg0KDQpBbmRyZXcNCg0KRnJvbTogVGltIEJyYXkgW21h
aWx0bzp0YnJheUB0ZXh0dWFsaXR5LmNvbTxtYWlsdG86dGJyYXlAdGV4dHVhbGl0eS5jb20+
XQ0KU2VudDogRnJpZGF5LCBKdWx5IDE5LCAyMDEzIDEwOjAyIEFNIENlbnRyYWwgU3RhbmRh
cmQgVGltZQ0KVG86IElFVEYtRGlzY3Vzc2lvbiBEaXNjdXNzaW9uIDxpZXRmQGlldGYub3Jn
PG1haWx0bzppZXRmQGlldGYub3JnPj4NClN1YmplY3Q6IExhc3QgY2FsbDogZHJhZnQtbW9u
dGVtdXJyby1nc21hLWltZWktdXJuLTE2LnR4dA0KDQpKdXN0IHdhbnRlZCB0byBwb2ludCBv
dXQgdGhhdCBib3RoIEFwcGxlIChmb3IgaU9TKSBhbmQgR29vZ2xlIChmb3IgQW5kcm9pZCkg
aGF2ZSBzdHJvbmdseSBkaXNjb3VyYWdlZCB0aGUgdXNlIG9mIElNRUkgdG8gaWRlbnRpZnkg
ZGV2aWNlcyBmb3IgdGhlIHB1cnBvc2VzIG9mIGFwcGxpY2F0aW9uIHNvZnR3YXJlLiAgVGhl
cmUgYXJlIHByaXZhY3ksIHF1YWxpdHksIGFuZCBhdmFpbGFiaWxpdHkgaXNzdWVzIHdpdGgg
dGhlaXIgdXNlLiAgQXBwbGUgaGFzIHJlbW92ZWQgdGhlIGFiaWxpdHkgb2YgZGV2ZWxvcGVy
cyB0byB3b3JrIHdpdGggdGhlIChvZnRlbiBJTUVJLWRlcml2ZWQpIOKAnFVuaXZlcnNhbCBE
ZXZpY2UgSUTigJ0gKHNlZSBodHRwOi8vYmxvZ3MuYXZnLmNvbS9tb2JpbGUtMi9hcHBsZS1p
b3MtNy1wdXRzLXVuaXF1ZS1kZXZpY2UtaWRzLykgYW5kIEdvb2dsZSBoYXMgb2ZmaWNpYWxs
eSBkZXByZWNhdGVkIHRoZWlyIHVzZTogaHR0cDovL2FuZHJvaWQtZGV2ZWxvcGVycy5ibG9n
c3BvdC5jYS8yMDExLzAzL2lkZW50aWZ5aW5nLWFwcC1pbnN0YWxsYXRpb25zLmh0bWwNCg0K
SeKAmW0gbm90IHN1cmUgZnJvbSByZWFkaW5nIHRoZSBkcmFmdCB3aGF0IHRoZSBnb2FsIG9m
IGhhdmluZyB0aGlzIFVSTiBuYW1lc3BhY2UgaXMsIGJ1dCBpZiBpdCBpbnZvbHZlcyBlbmNv
dXJhZ2luZyBpdHMgdXNlIGJ5IGFwcGxpY2F0aW9uIGRldmVsb3BlcnMsIEnigJltIHByZXR0
eSBzdXJlIGl04oCZcyBhIGJhZCBpZGVhLg0KDQogLVRpbQ0KLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQpU
aGlzIHRyYW5zbWlzc2lvbiAoaW5jbHVkaW5nIGFueSBhdHRhY2htZW50cykgbWF5IGNvbnRh
aW4gY29uZmlkZW50aWFsIGluZm9ybWF0aW9uLCBwcml2aWxlZ2VkIG1hdGVyaWFsIChpbmNs
dWRpbmcgbWF0ZXJpYWwgcHJvdGVjdGVkIGJ5IHRoZSBzb2xpY2l0b3ItY2xpZW50IG9yIG90
aGVyIGFwcGxpY2FibGUgcHJpdmlsZWdlcyksIG9yIGNvbnN0aXR1dGUgbm9uLXB1YmxpYyBp
bmZvcm1hdGlvbi4gQW55IHVzZSBvZiB0aGlzIGluZm9ybWF0aW9uIGJ5IGFueW9uZSBvdGhl
ciB0aGFuIHRoZSBpbnRlbmRlZCByZWNpcGllbnQgaXMgcHJvaGliaXRlZC4gSWYgeW91IGhh
dmUgcmVjZWl2ZWQgdGhpcyB0cmFuc21pc3Npb24gaW4gZXJyb3IsIHBsZWFzZSBpbW1lZGlh
dGVseSByZXBseSB0byB0aGUgc2VuZGVyIGFuZCBkZWxldGUgdGhpcyBpbmZvcm1hdGlvbiBm
cm9tIHlvdXIgc3lzdGVtLiBVc2UsIGRpc3NlbWluYXRpb24sIGRpc3RyaWJ1dGlvbiwgb3Ig
cmVwcm9kdWN0aW9uIG9mIHRoaXMgdHJhbnNtaXNzaW9uIGJ5IHVuaW50ZW5kZWQgcmVjaXBp
ZW50cyBpcyBub3QgYXV0aG9yaXplZCBhbmQgbWF5IGJlIHVubGF3ZnVsLg0KDQoNCi0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLQ0KVGhpcyB0cmFuc21pc3Npb24gKGluY2x1ZGluZyBhbnkgYXR0YWNobWVu
dHMpIG1heSBjb250YWluIGNvbmZpZGVudGlhbCBpbmZvcm1hdGlvbiwgcHJpdmlsZWdlZCBt
YXRlcmlhbCAoaW5jbHVkaW5nIG1hdGVyaWFsIHByb3RlY3RlZCBieSB0aGUgc29saWNpdG9y
LWNsaWVudCBvciBvdGhlciBhcHBsaWNhYmxlIHByaXZpbGVnZXMpLCBvciBjb25zdGl0dXRl
IG5vbi1wdWJsaWMgaW5mb3JtYXRpb24uIEFueSB1c2Ugb2YgdGhpcyBpbmZvcm1hdGlvbiBi
eSBhbnlvbmUgb3RoZXIgdGhhbiB0aGUgaW50ZW5kZWQgcmVjaXBpZW50IGlzIHByb2hpYml0
ZWQuIElmIHlvdSBoYXZlIHJlY2VpdmVkIHRoaXMgdHJhbnNtaXNzaW9uIGluIGVycm9yLCBw
bGVhc2UgaW1tZWRpYXRlbHkgcmVwbHkgdG8gdGhlIHNlbmRlciBhbmQgZGVsZXRlIHRoaXMg
aW5mb3JtYXRpb24gZnJvbSB5b3VyIHN5c3RlbS4gVXNlLCBkaXNzZW1pbmF0aW9uLCBkaXN0
cmlidXRpb24sIG9yIHJlcHJvZHVjdGlvbiBvZiB0aGlzIHRyYW5zbWlzc2lvbiBieSB1bmlu
dGVuZGVkIHJlY2lwaWVudHMgaXMgbm90IGF1dGhvcml6ZWQgYW5kIG1heSBiZSB1bmxhd2Z1
bC4NCg==

--_000_BBF5DDFE515C3946BC18D733B20DAD2338DD2341XMB104ADSrimnet_
Content-Type: text/html; charset="utf-8"
content-transfer-encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5Pg0KPGZvbnQg
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxicj4NClRpbTxicj4N
Cjxicj4NClRoZSBxdW90ZSBpcyBmcm9tIFJGQyA1NjI2IHdoaWNoIGFsc28gc3RhdGVzOjxi
cj4NCjxicj4NCiZxdW90OzMuMS4gU3VtbWFyeSBvZiBNZWNoYW5pc208YnI+DQo8YnI+DQpF
YWNoIFVBIGhhcyBhIHVuaXF1ZSBpbnN0YW5jZS1pZCB0aGF0IHN0YXlzIHRoZSBzYW1lIGZv
ciB0aGlzIFVBIGV2ZW4gaWYgdGhlIFVBIHJlYm9vdHMgb3IgaXMgcG93ZXIgY3ljbGVkLiZx
dW90Ow0KPGJyPg0KPGJyPg0KU2luY2UgdGhlIFVVSUQgaW4gdGhlIGluc3RhbmNlIElEIGlz
IGFsc28gc3RhdGljIGhvdyBpcyB0aGlzIHNpZ25pZmljYW50bHkgZGlmZmVyZW50IGluIHRl
cm1zIG9mIHByaXZhY3kgY29uY2VybnMgZnJvbSB0aGUgSU1FSSBiZWluZyB1c2VkIGFzIGFu
IGluc3RhbmNlIElEPzxicj4NCjxicj4NCkFuZHJldzwvZm9udD48YnI+DQombmJzcDs8YnI+
DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNCNUM0REYgMS4w
cHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbiI+DQo8Zm9udCBzdHlsZT0iZm9udC1zaXpl
OjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJp
ZiZxdW90OyI+PGI+RnJvbTwvYj46IFRpbSBCcmF5IFttYWlsdG86dGJyYXlAdGV4dHVhbGl0
eS5jb21dDQo8YnI+DQo8Yj5TZW50PC9iPjogRnJpZGF5LCBKdWx5IDE5LCAyMDEzIDEwOjU4
IEFNIENlbnRyYWwgU3RhbmRhcmQgVGltZTxicj4NCjxiPlRvPC9iPjogQW5kcmV3IEFsbGVu
IDxicj4NCjxiPkNjPC9iPjogaWV0ZkBpZXRmLm9yZyAmbHQ7aWV0ZkBpZXRmLm9yZyZndDsg
PGJyPg0KPGI+U3ViamVjdDwvYj46IFJlOiBMYXN0IGNhbGw6IGRyYWZ0LW1vbnRlbXVycm8t
Z3NtYS1pbWVpLXVybi0xNi50eHQgPGJyPg0KPC9mb250PiZuYnNwOzxicj4NCjwvZGl2Pg0K
PGRpdiBkaXI9Imx0ciI+T24gRnJpLCBKdWwgMTksIDIwMTMgYXQgODozOCBBTSwgQW5kcmV3
IEFsbGVuIDxzcGFuIGRpcj0ibHRyIj4mbHQ7PGEgaHJlZj0ibWFpbHRvOmFhbGxlbkBibGFj
a2JlcnJ5LmNvbSIgdGFyZ2V0PSJfYmxhbmsiPmFhbGxlbkBibGFja2JlcnJ5LmNvbTwvYT4m
Z3Q7PC9zcGFuPiB3cm90ZTo8YnI+DQo8ZGl2IGNsYXNzPSJnbWFpbF9leHRyYSI+DQo8ZGl2
IGNsYXNzPSJnbWFpbF9xdW90ZSI+DQo8YmxvY2txdW90ZSBjbGFzcz0iZ21haWxfcXVvdGUi
IHN0eWxlPSJtYXJnaW46MHB4IDBweCAwcHggMC44ZXg7Ym9yZGVyLWxlZnQ6MXB4IHNvbGlk
IHJnYigyMDQsMjA0LDIwNCk7cGFkZGluZy1sZWZ0OjFleCI+DQo8ZGl2Pjxmb250IHN0eWxl
PSJmb250LXNpemU6MTFwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90
O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6cmdiKDMxLDczLDEyNSkiPkkgc3VnZ2VzdCB5b3Ug
YWxzbyByZWFkPGJyPg0KPGEgaHJlZj0iaHR0cDovL2RhdGF0cmFja2VyLmlldGYub3JnL2Rv
Yy9kcmFmdC1hbGxlbi1kaXNwYXRjaC1pbWVpLXVybi1hcy1pbnN0YW5jZWlkLyIgdGFyZ2V0
PSJfYmxhbmsiPmh0dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtYWxsZW4t
ZGlzcGF0Y2gtaW1laS11cm4tYXMtaW5zdGFuY2VpZC88L2E+PGJyPg0KPC9mb250PjwvZGl2
Pg0KPC9ibG9ja3F1b3RlPg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+UXVvdGluZyBmcm9t
IHRoYXQgZG9jdW1lbnQ6IOKAnElmIGEgVVJOIHNjaGVtZSBvdGhlciB0aGFuIFVVSUQgaXMg
dXNlZCwgdGhlIFVBIE1VU1Qgb25seSB1c2UgVVJOcyBmb3Igd2hpY2ggYW4gUkZDIChmcm9t
IHRoZSBJRVRGIHN0cmVhbSkgZGVmaW5lcyBob3cgdGhlIHNwZWNpZmljIFVSTiBuZWVkcyB0
byBiZSBjb25zdHJ1Y3RlZC4uLuKAnTxicj4NCjxicj4NCjwvZGl2Pg0KPGRpdj5Ob3csIEni
gJltIG5vdCBhbiBleHBlcnQgaW4gdGhlIDNHUFAgd29ybGQ7IGJ1dCB0aGUgc3VnZ2VzdGlv
biBpbiB0aGF0IGV4dHJhY3QgdGhhdCBVVUlEcyBhcmUgYSBiZXR0ZXIgY2hvaWNlIHRoYW4g
YSAoc2hha3ksIHVucmVsaWFibGUsIHByaXZhY3ktcHJvYmxlbWF0aWMpIGRldmljZSBpZGVu
dGlmaWVyIGNlcnRhaW5seSByaW5ncyB0cnVlIGZvciB0aG9zZSBvZiB1cyB3aG8gdGhpbmsg
YXQgdGhlIGFwcHMgbGV2ZWwuJm5ic3A7IC1UPGJyPg0KPC9kaXY+DQo8ZGl2Pjxicj4NCiZu
YnNwOzwvZGl2Pg0KPGJsb2NrcXVvdGUgY2xhc3M9ImdtYWlsX3F1b3RlIiBzdHlsZT0ibWFy
Z2luOjBweCAwcHggMHB4IDAuOGV4O2JvcmRlci1sZWZ0OjFweCBzb2xpZCByZ2IoMjA0LDIw
NCwyMDQpO3BhZGRpbmctbGVmdDoxZXgiPg0KPGRpdj48Zm9udCBzdHlsZT0iZm9udC1zaXpl
OjExcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlm
JnF1b3Q7O2NvbG9yOnJnYigzMSw3MywxMjUpIj48YnI+DQpUaGF0IHdpbGwgZXhwbGFpbiB0
aGUgcHJpbWFyeSBhcHBsaWNhdGlvbiBvZiB0aGlzIFVSTiB3aGljaCBpcyBpbnRlbmRlZCBm
b3IgdXNlIGluIHRoZSAzR1BQIGNlbGx1bGFyIHN0YW5kYXJkcy48YnI+DQo8YnI+DQpBbmRy
ZXc8L2ZvbnQ+PGJyPg0KJm5ic3A7PGJyPg0KPGRpdiBzdHlsZT0iYm9yZGVyLXdpZHRoOjFw
dCBtZWRpdW0gbWVkaXVtO2JvcmRlci1zdHlsZTpzb2xpZCBub25lIG5vbmU7Ym9yZGVyLWNv
bG9yOnJnYigxODEsMTk2LDIyMykgLW1vei11c2UtdGV4dC1jb2xvciAtbW96LXVzZS10ZXh0
LWNvbG9yO3BhZGRpbmc6M3B0IDBpbiAwaW4iPg0KPGZvbnQgc3R5bGU9ImZvbnQtc2l6ZTox
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1
b3Q7Ij48Yj5Gcm9tPC9iPjogVGltIEJyYXkgW21haWx0bzo8YSBocmVmPSJtYWlsdG86dGJy
YXlAdGV4dHVhbGl0eS5jb20iIHRhcmdldD0iX2JsYW5rIj50YnJheUB0ZXh0dWFsaXR5LmNv
bTwvYT5dDQo8YnI+DQo8Yj5TZW50PC9iPjogRnJpZGF5LCBKdWx5IDE5LCAyMDEzIDEwOjAy
IEFNIENlbnRyYWwgU3RhbmRhcmQgVGltZTxicj4NCjxiPlRvPC9iPjogSUVURi1EaXNjdXNz
aW9uIERpc2N1c3Npb24gJmx0OzxhIGhyZWY9Im1haWx0bzppZXRmQGlldGYub3JnIiB0YXJn
ZXQ9Il9ibGFuayI+aWV0ZkBpZXRmLm9yZzwvYT4mZ3Q7DQo8YnI+DQo8Yj5TdWJqZWN0PC9i
PjogTGFzdCBjYWxsOiBkcmFmdC1tb250ZW11cnJvLWdzbWEtaW1laS11cm4tMTYudHh0IDxi
cj4NCjwvZm9udD4mbmJzcDs8YnI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9ImltIj4NCjxkaXYg
ZGlyPSJsdHIiPg0KPGRpdj4NCjxkaXY+SnVzdCB3YW50ZWQgdG8gcG9pbnQgb3V0IHRoYXQg
Ym90aCBBcHBsZSAoZm9yIGlPUykgYW5kIEdvb2dsZSAoZm9yIEFuZHJvaWQpIGhhdmUgc3Ry
b25nbHkgZGlzY291cmFnZWQgdGhlIHVzZSBvZiBJTUVJIHRvIGlkZW50aWZ5IGRldmljZXMg
Zm9yIHRoZSBwdXJwb3NlcyBvZiBhcHBsaWNhdGlvbiBzb2Z0d2FyZS4mbmJzcDsgVGhlcmUg
YXJlIHByaXZhY3ksIHF1YWxpdHksIGFuZCBhdmFpbGFiaWxpdHkgaXNzdWVzIHdpdGggdGhl
aXIgdXNlLiZuYnNwOyBBcHBsZQ0KIGhhcyByZW1vdmVkIHRoZSBhYmlsaXR5IG9mIGRldmVs
b3BlcnMgdG8gd29yayB3aXRoIHRoZSAob2Z0ZW4gSU1FSS1kZXJpdmVkKSDigJxVbml2ZXJz
YWwgRGV2aWNlIElE4oCdIChzZWUNCjxhIGhyZWY9Imh0dHA6Ly9ibG9ncy5hdmcuY29tL21v
YmlsZS0yL2FwcGxlLWlvcy03LXB1dHMtdW5pcXVlLWRldmljZS1pZHMvIiB0YXJnZXQ9Il9i
bGFuayI+DQpodHRwOi8vYmxvZ3MuYXZnLmNvbS9tb2JpbGUtMi9hcHBsZS1pb3MtNy1wdXRz
LXVuaXF1ZS1kZXZpY2UtaWRzLzwvYT4pIGFuZCBHb29nbGUgaGFzIG9mZmljaWFsbHkgZGVw
cmVjYXRlZCB0aGVpciB1c2U6DQo8YSBocmVmPSJodHRwOi8vYW5kcm9pZC1kZXZlbG9wZXJz
LmJsb2dzcG90LmNhLzIwMTEvMDMvaWRlbnRpZnlpbmctYXBwLWluc3RhbGxhdGlvbnMuaHRt
bCIgdGFyZ2V0PSJfYmxhbmsiPg0KaHR0cDovL2FuZHJvaWQtZGV2ZWxvcGVycy5ibG9nc3Bv
dC5jYS8yMDExLzAzL2lkZW50aWZ5aW5nLWFwcC1pbnN0YWxsYXRpb25zLmh0bWw8L2E+PGJy
Pg0KPGJyPg0KPC9kaXY+DQpJ4oCZbSBub3Qgc3VyZSBmcm9tIHJlYWRpbmcgdGhlIGRyYWZ0
IHdoYXQgdGhlIGdvYWwgb2YgaGF2aW5nIHRoaXMgVVJOIG5hbWVzcGFjZSBpcywgYnV0IGlm
IGl0IGludm9sdmVzIGVuY291cmFnaW5nIGl0cyB1c2UgYnkgYXBwbGljYXRpb24gZGV2ZWxv
cGVycywgSeKAmW0gcHJldHR5IHN1cmUgaXTigJlzIGEgYmFkIGlkZWEuPGJyPg0KPGJyPg0K
PC9kaXY+DQombmJzcDstVGltPGJyPg0KPC9kaXY+DQo8L2Rpdj4NCi0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LSA8YnI+DQpUaGlzIHRyYW5zbWlzc2lvbiAoaW5jbHVkaW5nIGFueSBhdHRhY2htZW50cykg
bWF5IGNvbnRhaW4gY29uZmlkZW50aWFsIGluZm9ybWF0aW9uLCBwcml2aWxlZ2VkIG1hdGVy
aWFsIChpbmNsdWRpbmcgbWF0ZXJpYWwgcHJvdGVjdGVkIGJ5IHRoZSBzb2xpY2l0b3ItY2xp
ZW50IG9yIG90aGVyIGFwcGxpY2FibGUgcHJpdmlsZWdlcyksIG9yIGNvbnN0aXR1dGUgbm9u
LXB1YmxpYyBpbmZvcm1hdGlvbi4gQW55IHVzZSBvZiB0aGlzIGluZm9ybWF0aW9uDQogYnkg
YW55b25lIG90aGVyIHRoYW4gdGhlIGludGVuZGVkIHJlY2lwaWVudCBpcyBwcm9oaWJpdGVk
LiBJZiB5b3UgaGF2ZSByZWNlaXZlZCB0aGlzIHRyYW5zbWlzc2lvbiBpbiBlcnJvciwgcGxl
YXNlIGltbWVkaWF0ZWx5IHJlcGx5IHRvIHRoZSBzZW5kZXIgYW5kIGRlbGV0ZSB0aGlzIGlu
Zm9ybWF0aW9uIGZyb20geW91ciBzeXN0ZW0uIFVzZSwgZGlzc2VtaW5hdGlvbiwgZGlzdHJp
YnV0aW9uLCBvciByZXByb2R1Y3Rpb24gb2YgdGhpcyB0cmFuc21pc3Npb24NCiBieSB1bmlu
dGVuZGVkIHJlY2lwaWVudHMgaXMgbm90IGF1dGhvcml6ZWQgYW5kIG1heSBiZSB1bmxhd2Z1
bC4gPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjxicj4NCjwvZGl2Pg0KPC9kaXY+
DQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0gPGJyPg0KVGhpcyB0cmFuc21pc3Npb24gKGluY2x1ZGluZyBh
bnkgYXR0YWNobWVudHMpIG1heSBjb250YWluIGNvbmZpZGVudGlhbCBpbmZvcm1hdGlvbiwg
cHJpdmlsZWdlZCBtYXRlcmlhbCAoaW5jbHVkaW5nIG1hdGVyaWFsIHByb3RlY3RlZCBieSB0
aGUgc29saWNpdG9yLWNsaWVudCBvciBvdGhlciBhcHBsaWNhYmxlIHByaXZpbGVnZXMpLCBv
ciBjb25zdGl0dXRlIG5vbi1wdWJsaWMgaW5mb3JtYXRpb24uIEFueSB1c2Ugb2YgdGhpcyBp
bmZvcm1hdGlvbiBieSBhbnlvbmUgb3RoZXIgdGhhbiB0aGUgaW50ZW5kZWQgcmVjaXBpZW50
IGlzIHByb2hpYml0ZWQuIElmIHlvdSBoYXZlIHJlY2VpdmVkIHRoaXMgdHJhbnNtaXNzaW9u
IGluIGVycm9yLCBwbGVhc2UgaW1tZWRpYXRlbHkgcmVwbHkgdG8gdGhlIHNlbmRlciBhbmQg
ZGVsZXRlIHRoaXMgaW5mb3JtYXRpb24gZnJvbSB5b3VyIHN5c3RlbS4gVXNlLCBkaXNzZW1p
bmF0aW9uLCBkaXN0cmlidXRpb24sIG9yIHJlcHJvZHVjdGlvbiBvZiB0aGlzIHRyYW5zbWlz
c2lvbiBieSB1bmludGVuZGVkIHJlY2lwaWVudHMgaXMgbm90IGF1dGhvcml6ZWQgYW5kIG1h
eSBiZSB1bmxhd2Z1bC4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_BBF5DDFE515C3946BC18D733B20DAD2338DD2341XMB104ADSrimnet_--

From tbray@textuality.com  Sat Jul 20 13:31:25 2013
Return-Path: <tbray@textuality.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 381F311E812A for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 13:31:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.784
X-Spam-Level: 
X-Spam-Status: No, score=-2.784 tagged_above=-999 required=5 tests=[AWL=0.192,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b5+N0LmxJVA1 for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 13:31:21 -0700 (PDT)
Received: from mail-vb0-f48.google.com (mail-vb0-f48.google.com [209.85.212.48]) by ietfa.amsl.com (Postfix) with ESMTP id BD33311E80D1 for <ietf@ietf.org>; Sat, 20 Jul 2013 13:31:20 -0700 (PDT)
Received: by mail-vb0-f48.google.com with SMTP id w15so3951360vbf.35 for <ietf@ietf.org>; Sat, 20 Jul 2013 13:31:19 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=K/wIqF1jybabLGr12gWeC12e0DiWejMXOSvPjbL+5eA=; b=KMnC7RkagP4NTq0bsVay35q/YToPjMxjJdvU8xitr0R8u7myLXc2ab00rHfl5gapfm jlDbwVao4pS+EfvV6EnHD25wIWe8WGapuoT7N6xtJU5prObYm3+VOK+gccvU8i4rf4rD 1Kfubr02PPtvQuO/u2uMGl3u733iojV73rJ8Nn4vZ4MtM+HUQQyCiO8U5QfuuFYJ2nCS xDErnEpSIK7kV/bZ5TJZYC8nkRT9Wj8GdSSqWceEZzVi7aRXKX3bmZfTHo1xVAJDXkRX CDcFrxscXcB2bvgvBFQ3Gn2GwV1fRsVElpX12zXtAv5FwlL/kOksuUNTlNFEvKIvCqlL +1dg==
MIME-Version: 1.0
X-Received: by 10.58.54.70 with SMTP id h6mr7488580vep.36.1374352279084; Sat, 20 Jul 2013 13:31:19 -0700 (PDT)
Received: by 10.220.219.200 with HTTP; Sat, 20 Jul 2013 13:31:18 -0700 (PDT)
X-Originating-IP: [24.84.235.32]
In-Reply-To: <BBF5DDFE515C3946BC18D733B20DAD2338DD2341@XMB104ADS.rim.net>
References: <CAHBU6ivC37fzO1oC=Ow3EGfBUt2GEsLRy3YWn6OZa9tTTTNZpQ@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD2338DD2341@XMB104ADS.rim.net>
Date: Sat, 20 Jul 2013 13:31:18 -0700
Message-ID: <CAHBU6isVHXo=LOjd8A5pv4=J6FsD9C0y5yYqFCezuUzmLHSm5g@mail.gmail.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
From: Tim Bray <tbray@textuality.com>
To: Andrew Allen <aallen@blackberry.com>
Content-Type: multipart/alternative; boundary=089e0122ad0664327304e1f75303
X-Gm-Message-State: ALoCoQkvmALgvDbdG2ToIA7lfe/qlRu1j0SurTULx7PnyWgmEXXI8/hKCbq3VgU/sXI5pcpFq93o
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Jul 2013 20:31:25 -0000

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

On Sat, Jul 20, 2013 at 1:08 PM, Andrew Allen <aallen@blackberry.com> wrote=
:

>
> The quote is from RFC 5626 which also states:
>
> "3.1. Summary of Mechanism
>
> Each UA has a unique instance-id that stays the same for this UA even if
> the UA reboots or is power cycled."
>
> Since the UUID in the instance ID is also static how is this significantl=
y
> different in terms of privacy concerns from the IMEI being used as an
> instance ID?
>

The difference is that the UUID (properly) vanishes when the device is
factory-reset (=E2=80=9Cwiped=E2=80=9D), as is common when a device is pass=
ed on to a new
owner.  The IMEI persists, however.  -T



>
> Andrew
>
>  *From*: Tim Bray [mailto:tbray@textuality.com]
> *Sent*: Friday, July 19, 2013 10:58 AM Central Standard Time
> *To*: Andrew Allen
> *Cc*: ietf@ietf.org <ietf@ietf.org>
> *Subject*: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
>
>  On Fri, Jul 19, 2013 at 8:38 AM, Andrew Allen <aallen@blackberry.com>wro=
te:
>
>> I suggest you also read
>>
>> http://datatracker.ietf.org/doc/draft-allen-dispatch-imei-urn-as-instanc=
eid/
>>
>
>  Quoting from that document: =E2=80=9CIf a URN scheme other than UUID is =
used,
> the UA MUST only use URNs for which an RFC (from the IETF stream) defines
> how the specific URN needs to be constructed...=E2=80=9D
>
>  Now, I=E2=80=99m not an expert in the 3GPP world; but the suggestion in =
that
> extract that UUIDs are a better choice than a (shaky, unreliable,
> privacy-problematic) device identifier certainly rings true for those of =
us
> who think at the apps level.  -T
>
>
>
>>
>> That will explain the primary application of this URN which is intended
>> for use in the 3GPP cellular standards.
>>
>> Andrew
>>
>>  *From*: Tim Bray [mailto:tbray@textuality.com]
>> *Sent*: Friday, July 19, 2013 10:02 AM Central Standard Time
>> *To*: IETF-Discussion Discussion <ietf@ietf.org>
>> *Subject*: Last call: draft-montemurro-gsma-imei-urn-16.txt
>>
>>   Just wanted to point out that both Apple (for iOS) and Google (for
>> Android) have strongly discouraged the use of IMEI to identify devices f=
or
>> the purposes of application software.  There are privacy, quality, and
>> availability issues with their use.  Apple has removed the ability of
>> developers to work with the (often IMEI-derived) =E2=80=9CUniversal Devi=
ce ID=E2=80=9D (see
>> http://blogs.avg.com/mobile-2/apple-ios-7-puts-unique-device-ids/) and
>> Google has officially deprecated their use:
>> http://android-developers.blogspot.ca/2011/03/identifying-app-installati=
ons.html
>>
>>  I=E2=80=99m not sure from reading the draft what the goal of having thi=
s URN
>> namespace is, but if it involves encouraging its use by application
>> developers, I=E2=80=99m pretty sure it=E2=80=99s a bad idea.
>>
>>   -Tim
>>  ---------------------------------------------------------------------
>> This transmission (including any attachments) may contain confidential
>> information, privileged material (including material protected by the
>> solicitor-client or other applicable privileges), or constitute non-publ=
ic
>> information. Any use of this information by anyone other than the intend=
ed
>> recipient is prohibited. If you have received this transmission in error=
,
>> please immediately reply to the sender and delete this information from
>> your system. Use, dissemination, distribution, or reproduction of this
>> transmission by unintended recipients is not authorized and may be
>> unlawful.
>>
>
>  ---------------------------------------------------------------------
> This transmission (including any attachments) may contain confidential
> information, privileged material (including material protected by the
> solicitor-client or other applicable privileges), or constitute non-publi=
c
> information. Any use of this information by anyone other than the intende=
d
> recipient is prohibited. If you have received this transmission in error,
> please immediately reply to the sender and delete this information from
> your system. Use, dissemination, distribution, or reproduction of this
> transmission by unintended recipients is not authorized and may be
> unlawful.
>

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

<div dir=3D"ltr">On Sat, Jul 20, 2013 at 1:08 PM, Andrew Allen <span dir=3D=
"ltr">&lt;<a href=3D"mailto:aallen@blackberry.com" target=3D"_blank">aallen=
@blackberry.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div cl=
ass=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">



<div>
<font style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:#1f497d"><br>
The quote is from RFC 5626 which also states:<br>
<br>
&quot;3.1. Summary of Mechanism<br>
<br>
Each UA has a unique instance-id that stays the same for this UA even if th=
e UA reboots or is power cycled.&quot;
<br>
<br>
Since the UUID in the instance ID is also static how is this significantly =
different in terms of privacy concerns from the IMEI being used as an insta=
nce ID?<br></font></div></blockquote><div><br></div><div>The difference is =
that the UUID (properly) vanishes when the device is factory-reset (=E2=80=
=9Cwiped=E2=80=9D), as is common when a device is passed on to a new owner.=
=C2=A0 The IMEI persists, however.=C2=A0 -T<br>
</div><div><br>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><font style=
=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;=
;color:#1f497d">
<br>
Andrew</font><br>
=C2=A0<br>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in =
0in 0in">
<font style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-s=
erif&quot;"><div class=3D"im"><b>From</b>: Tim Bray [mailto:<a href=3D"mail=
to:tbray@textuality.com" target=3D"_blank">tbray@textuality.com</a>]
<br>
</div><b>Sent</b>: Friday, July 19, 2013 10:58 AM Central Standard Time<br>
<b>To</b>: Andrew Allen <br>
<b>Cc</b>: <a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ietf.org=
</a> &lt;<a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ietf.org</=
a>&gt; <br><div class=3D"im">
<b>Subject</b>: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt <br>
</div></font>=C2=A0<br>
</div><div><div class=3D"h5">
<div dir=3D"ltr">On Fri, Jul 19, 2013 at 8:38 AM, Andrew Allen <span dir=3D=
"ltr">&lt;<a href=3D"mailto:aallen@blackberry.com" target=3D"_blank">aallen=
@blackberry.com</a>&gt;</span> wrote:<br>
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
<div><font style=3D"font-size:11pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:rgb(31,73,125)">I suggest you also read<br>
<a href=3D"http://datatracker.ietf.org/doc/draft-allen-dispatch-imei-urn-as=
-instanceid/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-allen=
-dispatch-imei-urn-as-instanceid/</a><br>
</font></div>
</blockquote>
<div><br>
</div>
<div>Quoting from that document: =E2=80=9CIf a URN scheme other than UUID i=
s used, the UA MUST only use URNs for which an RFC (from the IETF stream) d=
efines how the specific URN needs to be constructed...=E2=80=9D<br>
<br>
</div>
<div>Now, I=E2=80=99m not an expert in the 3GPP world; but the suggestion i=
n that extract that UUIDs are a better choice than a (shaky, unreliable, pr=
ivacy-problematic) device identifier certainly rings true for those of us w=
ho think at the apps level.=C2=A0 -T<br>

</div>
<div><br>
=C2=A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
<div><font style=3D"font-size:11pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:rgb(31,73,125)"><br>
That will explain the primary application of this URN which is intended for=
 use in the 3GPP cellular standards.<br>
<br>
Andrew</font><br>
=C2=A0<br>
<div style=3D"border-width:1pt medium medium;border-style:solid none none;b=
order-color:rgb(181,196,223) -moz-use-text-color -moz-use-text-color;paddin=
g:3pt 0in 0in">
<font style=3D"font-size:10pt;font-family:&quot;Tahoma&quot;,&quot;sans-ser=
if&quot;"><b>From</b>: Tim Bray [mailto:<a href=3D"mailto:tbray@textuality.=
com" target=3D"_blank">tbray@textuality.com</a>]
<br>
<b>Sent</b>: Friday, July 19, 2013 10:02 AM Central Standard Time<br>
<b>To</b>: IETF-Discussion Discussion &lt;<a href=3D"mailto:ietf@ietf.org" =
target=3D"_blank">ietf@ietf.org</a>&gt;
<br>
<b>Subject</b>: Last call: draft-montemurro-gsma-imei-urn-16.txt <br>
</font>=C2=A0<br>
</div>
<div>
<div dir=3D"ltr">
<div>
<div>Just wanted to point out that both Apple (for iOS) and Google (for And=
roid) have strongly discouraged the use of IMEI to identify devices for the=
 purposes of application software.=C2=A0 There are privacy, quality, and av=
ailability issues with their use.=C2=A0 Apple
 has removed the ability of developers to work with the (often IMEI-derived=
) =E2=80=9CUniversal Device ID=E2=80=9D (see
<a href=3D"http://blogs.avg.com/mobile-2/apple-ios-7-puts-unique-device-ids=
/" target=3D"_blank">
http://blogs.avg.com/mobile-2/apple-ios-7-puts-unique-device-ids/</a>) and =
Google has officially deprecated their use:
<a href=3D"http://android-developers.blogspot.ca/2011/03/identifying-app-in=
stallations.html" target=3D"_blank">
http://android-developers.blogspot.ca/2011/03/identifying-app-installations=
.html</a><br>
<br>
</div>
I=E2=80=99m not sure from reading the draft what the goal of having this UR=
N namespace is, but if it involves encouraging its use by application devel=
opers, I=E2=80=99m pretty sure it=E2=80=99s a bad idea.<br>
<br>
</div>
=C2=A0-Tim<br>
</div>
</div>
--------------------------------------------------------------------- <br>
This transmission (including any attachments) may contain confidential info=
rmation, privileged material (including material protected by the solicitor=
-client or other applicable privileges), or constitute non-public informati=
on. Any use of this information
 by anyone other than the intended recipient is prohibited. If you have rec=
eived this transmission in error, please immediately reply to the sender an=
d delete this information from your system. Use, dissemination, distributio=
n, or reproduction of this transmission
 by unintended recipients is not authorized and may be unlawful. </div>
</blockquote>
</div>
<br>
</div>
</div>
--------------------------------------------------------------------- <br>
This transmission (including any attachments) may contain confidential info=
rmation, privileged material (including material protected by the solicitor=
-client or other applicable privileges), or constitute non-public informati=
on. Any use of this information by anyone other than the intended recipient=
 is prohibited. If you have received this transmission in error, please imm=
ediately reply to the sender and delete this information from your system. =
Use, dissemination, distribution, or reproduction of this transmission by u=
nintended recipients is not authorized and may be unlawful.
</div></div></div>

</blockquote></div><br></div></div>

--089e0122ad0664327304e1f75303--

From prvs=2913bc3790=aallen@blackberry.com  Sat Jul 20 13:47:49 2013
Return-Path: <prvs=2913bc3790=aallen@blackberry.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E657A21E809E for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 13:47:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level: 
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[AWL=0.349,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uQFVqNZJkUd3 for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 13:47:46 -0700 (PDT)
Received: from mhs061cnc.rim.net (mhs061cnc.rim.net [208.65.73.35]) by ietfa.amsl.com (Postfix) with ESMTP id 3700B11E80E0 for <ietf@ietf.org>; Sat, 20 Jul 2013 13:47:44 -0700 (PDT)
X-AuditID: 0a412830-b7fa06d000003f99-14-51eaf766919a
Received: from XCT102ADS.rim.net (xct102ads.rim.net [10.67.111.43]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by mhs061cnc.rim.net (SBG) with SMTP id E9.CC.16281.667FAE15; Sat, 20 Jul 2013 15:47:34 -0500 (CDT)
Received: from XMB104ADS.rim.net ([fe80::2494:a63d:e3:723b]) by XCT102ADS.rim.net ([fe80::4806:2e1d:2b7c:cfdf%22]) with mapi id 14.02.0328.009; Sat, 20 Jul 2013 15:47:33 -0500
From: Andrew Allen <aallen@blackberry.com>
To: "tbray@textuality.com" <tbray@textuality.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
Thread-Topic: Last call: draft-montemurro-gsma-imei-urn-16.txt
Thread-Index: AQHOhJEO4fYTwuVTOkCw8MDTXs0bMZlsItsKgABZfICAAYRS+oAAWjMA//+wuFc=
Date: Sat, 20 Jul 2013 20:47:33 +0000
Message-ID: <BBF5DDFE515C3946BC18D733B20DAD2338DD235E@XMB104ADS.rim.net>
In-Reply-To: <CAHBU6isVHXo=LOjd8A5pv4=J6FsD9C0y5yYqFCezuUzmLHSm5g@mail.gmail.com>
Accept-Language: en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.67.110.252]
Content-Type: multipart/alternative; boundary="_000_BBF5DDFE515C3946BC18D733B20DAD2338DD235EXMB104ADSrimnet_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrOKsWRmVeSWpSXmKPExsXC5ZyvrZv2/VWgweJeU4tnG+ezWCz9M5/F gcljyZKfTB6Xlk5mDmCKamC0SUosKQvOTM/Tt7NJzMvLL0ksSVVISS1OtlXySU1PzFEIKMos S0yuVHDJLE7OSczMTS1SUshMsVUyUVIoyElMTs1NzSuxVUosKEjNS1Gy41LAADZAZZl5Cql5 yfkpmXnptkqewf66FhamlrqGSna6CZ08GWtuWhcs62eseNb7mLmBcU83YxcjJ4eEgInEvRXP mSBsMYkL99azdTFycQgJtDFJ7PvczwzhbGaUmNbbwgpSxSagJbH/8HSgDg4OEQFDiUV7vUDC zALKEk83zQEbJCxgK3H59B+wBSICdhLfD15igbD9JH7dOg5mswioSqy8/ZoZZAyvgIfEz9vi IGFOgUCJi+9ngbUyCshK7D57nQlivLjErSfzoe4UkFiy5zwzhC0q8fLxP1YIW1HicUs3C8hI ZoF8iW9r+UDCvAKCEidnPmGZwCgyC8mkWQhVs5BUQYQ1Jdbv0oeoVpSY0v2QHcLWkGidM5cd WXwBI/sqRsHcjGIDM8PkvGS9osxcvbzUkk2MoMThqGGwg/H9e4tDjAIcjEo8vDZfXwUKsSaW FVfmHmKU4GBWEuG1fAYU4k1JrKxKLcqPLyrNSS0+xBgEDJ2JzFLcyfnApJZXEm9sYEAkR0mc 1/rs2UAhgXRgAstOTS1ILYIZysTBCbKUS0qkGJiGUosSS0sy4kHJMr4YmC6lGhgTlEW8suo0 SytqS/Ob38/8+Ozun/Ui5yZdZ3eJEf9xlzP9WYvEDAGlmCoHsy1Pv/c8ffvwtGzE9Fqe6Lv7 lv6trHnGcEBvarDSyhuSbp9vs+v+PBOS7qsudCswlnevlZjL8cLQuTtn1C+7vHKKw4vbO+2r LQNVVTnv3WLuN5Az/t/fZeBSKqbEUpyRaKjFXFScCAAaU5/vagMAAA==
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Jul 2013 20:47:50 -0000

--_000_BBF5DDFE515C3946BC18D733B20DAD2338DD235EXMB104ADSrimnet_
Content-Type: text/plain; charset="utf-8"
content-transfer-encoding: base64

VGltDQoNCk1vYmlsZSBwaG9uZXMgYXJlIG5vdCB1c3VhbGx5IGNvbXBsZXRlbHkgImZhY3Rv
cnkgcmVzZXQiIGlmIHJlc29sZCBhbmQgZXZlbiBpZiB0aGV5IHdlcmUgYSBVVUlEIG1heSBz
dGlsbCBoYXZlIGJlZW4gc3RvcmVkIGluIG5vbiB2b2xhdGlsZSBhcyBpdCBtYXkgaGF2ZSBi
ZWVuIGdlbmVyYXRlZCBkdXJpbmcgZmluYWwgdGVzdC4NCg0KSW4gYW55IGNhc2UgaWYgdGhl
IElNRUkgd2FzIHRvIHBlcnNpc3QgYWZ0ZXIgYSByZXNhbGUgaG93IHdvdWxkIHRoYXQgYmUg
YSBwcml2YWN5IHByb2JsZW0gZ2l2ZW4gdGhlIHJlc3RyaWN0aW9ucyBwbGFjZWQgb24gdGhl
IHVzYWdlIGluDQpodHRwOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWFsbGVu
LWRpc3BhdGNoLWltZWktdXJuLWFzLWluc3RhbmNlaWQvPw0KDQpUaGUgaW50ZW50aW9uIGlz
IHRoYXQgdGhlIElNRUkgaXMgbm90IHBhc3NlZCB0byB0aGUgcmVtb3RlIHBhcnR5IGV4Y2Vw
dCB3aGVuIHJlcXVpcmVkIGJ5IHJlZ3VsYXRpb25zIGZvciBhbiBFbWVyZ2VuY3kgY2FsbC4N
Cg0KQW5kcmV3DQoNCkZyb206IFRpbSBCcmF5IFttYWlsdG86dGJyYXlAdGV4dHVhbGl0eS5j
b21dDQpTZW50OiBTYXR1cmRheSwgSnVseSAyMCwgMjAxMyAwMzozMSBQTSBDZW50cmFsIFN0
YW5kYXJkIFRpbWUNClRvOiBBbmRyZXcgQWxsZW4NCkNjOiBpZXRmQGlldGYub3JnIDxpZXRm
QGlldGYub3JnPg0KU3ViamVjdDogUmU6IExhc3QgY2FsbDogZHJhZnQtbW9udGVtdXJyby1n
c21hLWltZWktdXJuLTE2LnR4dA0KDQpPbiBTYXQsIEp1bCAyMCwgMjAxMyBhdCAxOjA4IFBN
LCBBbmRyZXcgQWxsZW4gPGFhbGxlbkBibGFja2JlcnJ5LmNvbTxtYWlsdG86YWFsbGVuQGJs
YWNrYmVycnkuY29tPj4gd3JvdGU6DQoNClRoZSBxdW90ZSBpcyBmcm9tIFJGQyA1NjI2IHdo
aWNoIGFsc28gc3RhdGVzOg0KDQoiMy4xLiBTdW1tYXJ5IG9mIE1lY2hhbmlzbQ0KDQpFYWNo
IFVBIGhhcyBhIHVuaXF1ZSBpbnN0YW5jZS1pZCB0aGF0IHN0YXlzIHRoZSBzYW1lIGZvciB0
aGlzIFVBIGV2ZW4gaWYgdGhlIFVBIHJlYm9vdHMgb3IgaXMgcG93ZXIgY3ljbGVkLiINCg0K
U2luY2UgdGhlIFVVSUQgaW4gdGhlIGluc3RhbmNlIElEIGlzIGFsc28gc3RhdGljIGhvdyBp
cyB0aGlzIHNpZ25pZmljYW50bHkgZGlmZmVyZW50IGluIHRlcm1zIG9mIHByaXZhY3kgY29u
Y2VybnMgZnJvbSB0aGUgSU1FSSBiZWluZyB1c2VkIGFzIGFuIGluc3RhbmNlIElEPw0KDQpU
aGUgZGlmZmVyZW5jZSBpcyB0aGF0IHRoZSBVVUlEIChwcm9wZXJseSkgdmFuaXNoZXMgd2hl
biB0aGUgZGV2aWNlIGlzIGZhY3RvcnktcmVzZXQgKOKAnHdpcGVk4oCdKSwgYXMgaXMgY29t
bW9uIHdoZW4gYSBkZXZpY2UgaXMgcGFzc2VkIG9uIHRvIGEgbmV3IG93bmVyLiAgVGhlIElN
RUkgcGVyc2lzdHMsIGhvd2V2ZXIuICAtVA0KDQoNCg0KQW5kcmV3DQoNCkZyb206IFRpbSBC
cmF5IFttYWlsdG86dGJyYXlAdGV4dHVhbGl0eS5jb208bWFpbHRvOnRicmF5QHRleHR1YWxp
dHkuY29tPl0NClNlbnQ6IEZyaWRheSwgSnVseSAxOSwgMjAxMyAxMDo1OCBBTSBDZW50cmFs
IFN0YW5kYXJkIFRpbWUNClRvOiBBbmRyZXcgQWxsZW4NCkNjOiBpZXRmQGlldGYub3JnPG1h
aWx0bzppZXRmQGlldGYub3JnPiA8aWV0ZkBpZXRmLm9yZzxtYWlsdG86aWV0ZkBpZXRmLm9y
Zz4+DQpTdWJqZWN0OiBSZTogTGFzdCBjYWxsOiBkcmFmdC1tb250ZW11cnJvLWdzbWEtaW1l
aS11cm4tMTYudHh0DQoNCk9uIEZyaSwgSnVsIDE5LCAyMDEzIGF0IDg6MzggQU0sIEFuZHJl
dyBBbGxlbiA8YWFsbGVuQGJsYWNrYmVycnkuY29tPG1haWx0bzphYWxsZW5AYmxhY2tiZXJy
eS5jb20+PiB3cm90ZToNCkkgc3VnZ2VzdCB5b3UgYWxzbyByZWFkDQpodHRwOi8vZGF0YXRy
YWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWFsbGVuLWRpc3BhdGNoLWltZWktdXJuLWFzLWlu
c3RhbmNlaWQvDQoNClF1b3RpbmcgZnJvbSB0aGF0IGRvY3VtZW50OiDigJxJZiBhIFVSTiBz
Y2hlbWUgb3RoZXIgdGhhbiBVVUlEIGlzIHVzZWQsIHRoZSBVQSBNVVNUIG9ubHkgdXNlIFVS
TnMgZm9yIHdoaWNoIGFuIFJGQyAoZnJvbSB0aGUgSUVURiBzdHJlYW0pIGRlZmluZXMgaG93
IHRoZSBzcGVjaWZpYyBVUk4gbmVlZHMgdG8gYmUgY29uc3RydWN0ZWQuLi7igJ0NCg0KTm93
LCBJ4oCZbSBub3QgYW4gZXhwZXJ0IGluIHRoZSAzR1BQIHdvcmxkOyBidXQgdGhlIHN1Z2dl
c3Rpb24gaW4gdGhhdCBleHRyYWN0IHRoYXQgVVVJRHMgYXJlIGEgYmV0dGVyIGNob2ljZSB0
aGFuIGEgKHNoYWt5LCB1bnJlbGlhYmxlLCBwcml2YWN5LXByb2JsZW1hdGljKSBkZXZpY2Ug
aWRlbnRpZmllciBjZXJ0YWlubHkgcmluZ3MgdHJ1ZSBmb3IgdGhvc2Ugb2YgdXMgd2hvIHRo
aW5rIGF0IHRoZSBhcHBzIGxldmVsLiAgLVQNCg0KDQoNClRoYXQgd2lsbCBleHBsYWluIHRo
ZSBwcmltYXJ5IGFwcGxpY2F0aW9uIG9mIHRoaXMgVVJOIHdoaWNoIGlzIGludGVuZGVkIGZv
ciB1c2UgaW4gdGhlIDNHUFAgY2VsbHVsYXIgc3RhbmRhcmRzLg0KDQpBbmRyZXcNCg0KRnJv
bTogVGltIEJyYXkgW21haWx0bzp0YnJheUB0ZXh0dWFsaXR5LmNvbTxtYWlsdG86dGJyYXlA
dGV4dHVhbGl0eS5jb20+XQ0KU2VudDogRnJpZGF5LCBKdWx5IDE5LCAyMDEzIDEwOjAyIEFN
IENlbnRyYWwgU3RhbmRhcmQgVGltZQ0KVG86IElFVEYtRGlzY3Vzc2lvbiBEaXNjdXNzaW9u
IDxpZXRmQGlldGYub3JnPG1haWx0bzppZXRmQGlldGYub3JnPj4NClN1YmplY3Q6IExhc3Qg
Y2FsbDogZHJhZnQtbW9udGVtdXJyby1nc21hLWltZWktdXJuLTE2LnR4dA0KDQpKdXN0IHdh
bnRlZCB0byBwb2ludCBvdXQgdGhhdCBib3RoIEFwcGxlIChmb3IgaU9TKSBhbmQgR29vZ2xl
IChmb3IgQW5kcm9pZCkgaGF2ZSBzdHJvbmdseSBkaXNjb3VyYWdlZCB0aGUgdXNlIG9mIElN
RUkgdG8gaWRlbnRpZnkgZGV2aWNlcyBmb3IgdGhlIHB1cnBvc2VzIG9mIGFwcGxpY2F0aW9u
IHNvZnR3YXJlLiAgVGhlcmUgYXJlIHByaXZhY3ksIHF1YWxpdHksIGFuZCBhdmFpbGFiaWxp
dHkgaXNzdWVzIHdpdGggdGhlaXIgdXNlLiAgQXBwbGUgaGFzIHJlbW92ZWQgdGhlIGFiaWxp
dHkgb2YgZGV2ZWxvcGVycyB0byB3b3JrIHdpdGggdGhlIChvZnRlbiBJTUVJLWRlcml2ZWQp
IOKAnFVuaXZlcnNhbCBEZXZpY2UgSUTigJ0gKHNlZSBodHRwOi8vYmxvZ3MuYXZnLmNvbS9t
b2JpbGUtMi9hcHBsZS1pb3MtNy1wdXRzLXVuaXF1ZS1kZXZpY2UtaWRzLykgYW5kIEdvb2ds
ZSBoYXMgb2ZmaWNpYWxseSBkZXByZWNhdGVkIHRoZWlyIHVzZTogaHR0cDovL2FuZHJvaWQt
ZGV2ZWxvcGVycy5ibG9nc3BvdC5jYS8yMDExLzAzL2lkZW50aWZ5aW5nLWFwcC1pbnN0YWxs
YXRpb25zLmh0bWwNCg0KSeKAmW0gbm90IHN1cmUgZnJvbSByZWFkaW5nIHRoZSBkcmFmdCB3
aGF0IHRoZSBnb2FsIG9mIGhhdmluZyB0aGlzIFVSTiBuYW1lc3BhY2UgaXMsIGJ1dCBpZiBp
dCBpbnZvbHZlcyBlbmNvdXJhZ2luZyBpdHMgdXNlIGJ5IGFwcGxpY2F0aW9uIGRldmVsb3Bl
cnMsIEnigJltIHByZXR0eSBzdXJlIGl04oCZcyBhIGJhZCBpZGVhLg0KDQogLVRpbQ0KLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tDQpUaGlzIHRyYW5zbWlzc2lvbiAoaW5jbHVkaW5nIGFueSBhdHRhY2ht
ZW50cykgbWF5IGNvbnRhaW4gY29uZmlkZW50aWFsIGluZm9ybWF0aW9uLCBwcml2aWxlZ2Vk
IG1hdGVyaWFsIChpbmNsdWRpbmcgbWF0ZXJpYWwgcHJvdGVjdGVkIGJ5IHRoZSBzb2xpY2l0
b3ItY2xpZW50IG9yIG90aGVyIGFwcGxpY2FibGUgcHJpdmlsZWdlcyksIG9yIGNvbnN0aXR1
dGUgbm9uLXB1YmxpYyBpbmZvcm1hdGlvbi4gQW55IHVzZSBvZiB0aGlzIGluZm9ybWF0aW9u
IGJ5IGFueW9uZSBvdGhlciB0aGFuIHRoZSBpbnRlbmRlZCByZWNpcGllbnQgaXMgcHJvaGli
aXRlZC4gSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyB0cmFuc21pc3Npb24gaW4gZXJyb3Is
IHBsZWFzZSBpbW1lZGlhdGVseSByZXBseSB0byB0aGUgc2VuZGVyIGFuZCBkZWxldGUgdGhp
cyBpbmZvcm1hdGlvbiBmcm9tIHlvdXIgc3lzdGVtLiBVc2UsIGRpc3NlbWluYXRpb24sIGRp
c3RyaWJ1dGlvbiwgb3IgcmVwcm9kdWN0aW9uIG9mIHRoaXMgdHJhbnNtaXNzaW9uIGJ5IHVu
aW50ZW5kZWQgcmVjaXBpZW50cyBpcyBub3QgYXV0aG9yaXplZCBhbmQgbWF5IGJlIHVubGF3
ZnVsLg0KDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NClRoaXMgdHJhbnNtaXNzaW9uIChpbmNsdWRpbmcg
YW55IGF0dGFjaG1lbnRzKSBtYXkgY29udGFpbiBjb25maWRlbnRpYWwgaW5mb3JtYXRpb24s
IHByaXZpbGVnZWQgbWF0ZXJpYWwgKGluY2x1ZGluZyBtYXRlcmlhbCBwcm90ZWN0ZWQgYnkg
dGhlIHNvbGljaXRvci1jbGllbnQgb3Igb3RoZXIgYXBwbGljYWJsZSBwcml2aWxlZ2VzKSwg
b3IgY29uc3RpdHV0ZSBub24tcHVibGljIGluZm9ybWF0aW9uLiBBbnkgdXNlIG9mIHRoaXMg
aW5mb3JtYXRpb24gYnkgYW55b25lIG90aGVyIHRoYW4gdGhlIGludGVuZGVkIHJlY2lwaWVu
dCBpcyBwcm9oaWJpdGVkLiBJZiB5b3UgaGF2ZSByZWNlaXZlZCB0aGlzIHRyYW5zbWlzc2lv
biBpbiBlcnJvciwgcGxlYXNlIGltbWVkaWF0ZWx5IHJlcGx5IHRvIHRoZSBzZW5kZXIgYW5k
IGRlbGV0ZSB0aGlzIGluZm9ybWF0aW9uIGZyb20geW91ciBzeXN0ZW0uIFVzZSwgZGlzc2Vt
aW5hdGlvbiwgZGlzdHJpYnV0aW9uLCBvciByZXByb2R1Y3Rpb24gb2YgdGhpcyB0cmFuc21p
c3Npb24gYnkgdW5pbnRlbmRlZCByZWNpcGllbnRzIGlzIG5vdCBhdXRob3JpemVkIGFuZCBt
YXkgYmUgdW5sYXdmdWwuDQoNCg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQpUaGlzIHRyYW5zbWlzc2lv
biAoaW5jbHVkaW5nIGFueSBhdHRhY2htZW50cykgbWF5IGNvbnRhaW4gY29uZmlkZW50aWFs
IGluZm9ybWF0aW9uLCBwcml2aWxlZ2VkIG1hdGVyaWFsIChpbmNsdWRpbmcgbWF0ZXJpYWwg
cHJvdGVjdGVkIGJ5IHRoZSBzb2xpY2l0b3ItY2xpZW50IG9yIG90aGVyIGFwcGxpY2FibGUg
cHJpdmlsZWdlcyksIG9yIGNvbnN0aXR1dGUgbm9uLXB1YmxpYyBpbmZvcm1hdGlvbi4gQW55
IHVzZSBvZiB0aGlzIGluZm9ybWF0aW9uIGJ5IGFueW9uZSBvdGhlciB0aGFuIHRoZSBpbnRl
bmRlZCByZWNpcGllbnQgaXMgcHJvaGliaXRlZC4gSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhp
cyB0cmFuc21pc3Npb24gaW4gZXJyb3IsIHBsZWFzZSBpbW1lZGlhdGVseSByZXBseSB0byB0
aGUgc2VuZGVyIGFuZCBkZWxldGUgdGhpcyBpbmZvcm1hdGlvbiBmcm9tIHlvdXIgc3lzdGVt
LiBVc2UsIGRpc3NlbWluYXRpb24sIGRpc3RyaWJ1dGlvbiwgb3IgcmVwcm9kdWN0aW9uIG9m
IHRoaXMgdHJhbnNtaXNzaW9uIGJ5IHVuaW50ZW5kZWQgcmVjaXBpZW50cyBpcyBub3QgYXV0
aG9yaXplZCBhbmQgbWF5IGJlIHVubGF3ZnVsLg0K

--_000_BBF5DDFE515C3946BC18D733B20DAD2338DD235EXMB104ADSrimnet_
Content-Type: text/html; charset="utf-8"
content-transfer-encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5Pg0KPGZvbnQg
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPlRpbTxicj4NCjxicj4N
Ck1vYmlsZSBwaG9uZXMgYXJlIG5vdCB1c3VhbGx5IGNvbXBsZXRlbHkgJnF1b3Q7ZmFjdG9y
eSByZXNldCZxdW90OyBpZiByZXNvbGQgYW5kIGV2ZW4gaWYgdGhleSB3ZXJlIGEgVVVJRCBt
YXkgc3RpbGwgaGF2ZSBiZWVuIHN0b3JlZCBpbiBub24gdm9sYXRpbGUgYXMgaXQgbWF5IGhh
dmUgYmVlbiBnZW5lcmF0ZWQgZHVyaW5nIGZpbmFsIHRlc3QuPGJyPg0KPGJyPg0KSW4gYW55
IGNhc2UgaWYgdGhlIElNRUkgd2FzIHRvIHBlcnNpc3QgYWZ0ZXIgYSByZXNhbGUgaG93IHdv
dWxkIHRoYXQgYmUgYSBwcml2YWN5IHByb2JsZW0gZ2l2ZW4gdGhlIHJlc3RyaWN0aW9ucyBw
bGFjZWQgb24gdGhlIHVzYWdlIGluDQo8YnI+DQpodHRwOi8vZGF0YXRyYWNrZXIuaWV0Zi5v
cmcvZG9jL2RyYWZ0LWFsbGVuLWRpc3BhdGNoLWltZWktdXJuLWFzLWluc3RhbmNlaWQvPzxi
cj4NCjxicj4NClRoZSBpbnRlbnRpb24gaXMgdGhhdCB0aGUgSU1FSSBpcyBub3QgcGFzc2Vk
IHRvIHRoZSByZW1vdGUgcGFydHkgZXhjZXB0IHdoZW4gcmVxdWlyZWQgYnkgcmVndWxhdGlv
bnMgZm9yIGFuIEVtZXJnZW5jeSBjYWxsLjxicj4NCjxicj4NCkFuZHJldzwvZm9udD48YnI+
DQombmJzcDs8YnI+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlk
ICNCNUM0REYgMS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbiI+DQo8Zm9udCBzdHls
ZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1
b3Q7c2Fucy1zZXJpZiZxdW90OyI+PGI+RnJvbTwvYj46IFRpbSBCcmF5IFttYWlsdG86dGJy
YXlAdGV4dHVhbGl0eS5jb21dDQo8YnI+DQo8Yj5TZW50PC9iPjogU2F0dXJkYXksIEp1bHkg
MjAsIDIwMTMgMDM6MzEgUE0gQ2VudHJhbCBTdGFuZGFyZCBUaW1lPGJyPg0KPGI+VG88L2I+
OiBBbmRyZXcgQWxsZW4gPGJyPg0KPGI+Q2M8L2I+OiBpZXRmQGlldGYub3JnICZsdDtpZXRm
QGlldGYub3JnJmd0OyA8YnI+DQo8Yj5TdWJqZWN0PC9iPjogUmU6IExhc3QgY2FsbDogZHJh
ZnQtbW9udGVtdXJyby1nc21hLWltZWktdXJuLTE2LnR4dCA8YnI+DQo8L2ZvbnQ+Jm5ic3A7
PGJyPg0KPC9kaXY+DQo8ZGl2IGRpcj0ibHRyIj5PbiBTYXQsIEp1bCAyMCwgMjAxMyBhdCAx
OjA4IFBNLCBBbmRyZXcgQWxsZW4gPHNwYW4gZGlyPSJsdHIiPiZsdDs8YSBocmVmPSJtYWls
dG86YWFsbGVuQGJsYWNrYmVycnkuY29tIiB0YXJnZXQ9Il9ibGFuayI+YWFsbGVuQGJsYWNr
YmVycnkuY29tPC9hPiZndDs8L3NwYW4+IHdyb3RlOjxicj4NCjxkaXYgY2xhc3M9ImdtYWls
X2V4dHJhIj4NCjxkaXYgY2xhc3M9ImdtYWlsX3F1b3RlIj4NCjxibG9ja3F1b3RlIGNsYXNz
PSJnbWFpbF9xdW90ZSIgc3R5bGU9Im1hcmdpbjowIDAgMCAuOGV4O2JvcmRlci1sZWZ0OjFw
eCAjY2NjIHNvbGlkO3BhZGRpbmctbGVmdDoxZXgiPg0KPGRpdj48Zm9udCBzdHlsZT0iZm9u
dC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3Nh
bnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFmNDk3ZCI+PGJyPg0KVGhlIHF1b3RlIGlzIGZyb20g
UkZDIDU2MjYgd2hpY2ggYWxzbyBzdGF0ZXM6PGJyPg0KPGJyPg0KJnF1b3Q7My4xLiBTdW1t
YXJ5IG9mIE1lY2hhbmlzbTxicj4NCjxicj4NCkVhY2ggVUEgaGFzIGEgdW5pcXVlIGluc3Rh
bmNlLWlkIHRoYXQgc3RheXMgdGhlIHNhbWUgZm9yIHRoaXMgVUEgZXZlbiBpZiB0aGUgVUEg
cmVib290cyBvciBpcyBwb3dlciBjeWNsZWQuJnF1b3Q7DQo8YnI+DQo8YnI+DQpTaW5jZSB0
aGUgVVVJRCBpbiB0aGUgaW5zdGFuY2UgSUQgaXMgYWxzbyBzdGF0aWMgaG93IGlzIHRoaXMg
c2lnbmlmaWNhbnRseSBkaWZmZXJlbnQgaW4gdGVybXMgb2YgcHJpdmFjeSBjb25jZXJucyBm
cm9tIHRoZSBJTUVJIGJlaW5nIHVzZWQgYXMgYW4gaW5zdGFuY2UgSUQ/PGJyPg0KPC9mb250
PjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+VGhlIGRp
ZmZlcmVuY2UgaXMgdGhhdCB0aGUgVVVJRCAocHJvcGVybHkpIHZhbmlzaGVzIHdoZW4gdGhl
IGRldmljZSBpcyBmYWN0b3J5LXJlc2V0ICjigJx3aXBlZOKAnSksIGFzIGlzIGNvbW1vbiB3
aGVuIGEgZGV2aWNlIGlzIHBhc3NlZCBvbiB0byBhIG5ldyBvd25lci4mbmJzcDsgVGhlIElN
RUkgcGVyc2lzdHMsIGhvd2V2ZXIuJm5ic3A7IC1UPGJyPg0KPC9kaXY+DQo8ZGl2Pjxicj4N
CiZuYnNwOzwvZGl2Pg0KPGJsb2NrcXVvdGUgY2xhc3M9ImdtYWlsX3F1b3RlIiBzdHlsZT0i
bWFyZ2luOjAgMCAwIC44ZXg7Ym9yZGVyLWxlZnQ6MXB4ICNjY2Mgc29saWQ7cGFkZGluZy1s
ZWZ0OjFleCI+DQo8ZGl2Pjxmb250IHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjoj
MWY0OTdkIj48YnI+DQpBbmRyZXc8L2ZvbnQ+PGJyPg0KJm5ic3A7PGJyPg0KPGRpdiBzdHls
ZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjYjVjNGRmIDEuMHB0O3BhZGRpbmc6
My4wcHQgMGluIDBpbiAwaW4iPg0KPGZvbnQgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPg0K
PGRpdiBjbGFzcz0iaW0iPjxiPkZyb208L2I+OiBUaW0gQnJheSBbbWFpbHRvOjxhIGhyZWY9
Im1haWx0bzp0YnJheUB0ZXh0dWFsaXR5LmNvbSIgdGFyZ2V0PSJfYmxhbmsiPnRicmF5QHRl
eHR1YWxpdHkuY29tPC9hPl0NCjxicj4NCjwvZGl2Pg0KPGI+U2VudDwvYj46IEZyaWRheSwg
SnVseSAxOSwgMjAxMyAxMDo1OCBBTSBDZW50cmFsIFN0YW5kYXJkIFRpbWU8YnI+DQo8Yj5U
bzwvYj46IEFuZHJldyBBbGxlbiA8YnI+DQo8Yj5DYzwvYj46IDxhIGhyZWY9Im1haWx0bzpp
ZXRmQGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+aWV0ZkBpZXRmLm9yZzwvYT4gJmx0Ozxh
IGhyZWY9Im1haWx0bzppZXRmQGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+aWV0ZkBpZXRm
Lm9yZzwvYT4mZ3Q7DQo8YnI+DQo8ZGl2IGNsYXNzPSJpbSI+PGI+U3ViamVjdDwvYj46IFJl
OiBMYXN0IGNhbGw6IGRyYWZ0LW1vbnRlbXVycm8tZ3NtYS1pbWVpLXVybi0xNi50eHQNCjxi
cj4NCjwvZGl2Pg0KPC9mb250PiZuYnNwOzxicj4NCjwvZGl2Pg0KPGRpdj4NCjxkaXYgY2xh
c3M9Img1Ij4NCjxkaXYgZGlyPSJsdHIiPk9uIEZyaSwgSnVsIDE5LCAyMDEzIGF0IDg6Mzgg
QU0sIEFuZHJldyBBbGxlbiA8c3BhbiBkaXI9Imx0ciI+Jmx0OzxhIGhyZWY9Im1haWx0bzph
YWxsZW5AYmxhY2tiZXJyeS5jb20iIHRhcmdldD0iX2JsYW5rIj5hYWxsZW5AYmxhY2tiZXJy
eS5jb208L2E+Jmd0Ozwvc3Bhbj4gd3JvdGU6PGJyPg0KPGRpdiBjbGFzcz0iZ21haWxfZXh0
cmEiPg0KPGRpdiBjbGFzcz0iZ21haWxfcXVvdGUiPg0KPGJsb2NrcXVvdGUgY2xhc3M9Imdt
YWlsX3F1b3RlIiBzdHlsZT0ibWFyZ2luOjBweCAwcHggMHB4IDAuOGV4O2JvcmRlci1sZWZ0
OjFweCBzb2xpZCByZ2IoMjA0LDIwNCwyMDQpO3BhZGRpbmctbGVmdDoxZXgiPg0KPGRpdj48
Zm9udCBzdHlsZT0iZm9udC1zaXplOjExcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZx
dW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOnJnYigzMSw3MywxMjUpIj5JIHN1
Z2dlc3QgeW91IGFsc28gcmVhZDxicj4NCjxhIGhyZWY9Imh0dHA6Ly9kYXRhdHJhY2tlci5p
ZXRmLm9yZy9kb2MvZHJhZnQtYWxsZW4tZGlzcGF0Y2gtaW1laS11cm4tYXMtaW5zdGFuY2Vp
ZC8iIHRhcmdldD0iX2JsYW5rIj5odHRwOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2Ry
YWZ0LWFsbGVuLWRpc3BhdGNoLWltZWktdXJuLWFzLWluc3RhbmNlaWQvPC9hPjxicj4NCjwv
Zm9udD48L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2PlF1
b3RpbmcgZnJvbSB0aGF0IGRvY3VtZW50OiDigJxJZiBhIFVSTiBzY2hlbWUgb3RoZXIgdGhh
biBVVUlEIGlzIHVzZWQsIHRoZSBVQSBNVVNUIG9ubHkgdXNlIFVSTnMgZm9yIHdoaWNoIGFu
IFJGQyAoZnJvbSB0aGUgSUVURiBzdHJlYW0pIGRlZmluZXMgaG93IHRoZSBzcGVjaWZpYyBV
Uk4gbmVlZHMgdG8gYmUgY29uc3RydWN0ZWQuLi7igJ08YnI+DQo8YnI+DQo8L2Rpdj4NCjxk
aXY+Tm93LCBJ4oCZbSBub3QgYW4gZXhwZXJ0IGluIHRoZSAzR1BQIHdvcmxkOyBidXQgdGhl
IHN1Z2dlc3Rpb24gaW4gdGhhdCBleHRyYWN0IHRoYXQgVVVJRHMgYXJlIGEgYmV0dGVyIGNo
b2ljZSB0aGFuIGEgKHNoYWt5LCB1bnJlbGlhYmxlLCBwcml2YWN5LXByb2JsZW1hdGljKSBk
ZXZpY2UgaWRlbnRpZmllciBjZXJ0YWlubHkgcmluZ3MgdHJ1ZSBmb3IgdGhvc2Ugb2YgdXMg
d2hvIHRoaW5rIGF0IHRoZSBhcHBzIGxldmVsLiZuYnNwOyAtVDxicj4NCjwvZGl2Pg0KPGRp
dj48YnI+DQombmJzcDs8L2Rpdj4NCjxibG9ja3F1b3RlIGNsYXNzPSJnbWFpbF9xdW90ZSIg
c3R5bGU9Im1hcmdpbjowcHggMHB4IDBweCAwLjhleDtib3JkZXItbGVmdDoxcHggc29saWQg
cmdiKDIwNCwyMDQsMjA0KTtwYWRkaW5nLWxlZnQ6MWV4Ij4NCjxkaXY+PGZvbnQgc3R5bGU9
ImZvbnQtc2l6ZToxMXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7
c2Fucy1zZXJpZiZxdW90Oztjb2xvcjpyZ2IoMzEsNzMsMTI1KSI+PGJyPg0KVGhhdCB3aWxs
IGV4cGxhaW4gdGhlIHByaW1hcnkgYXBwbGljYXRpb24gb2YgdGhpcyBVUk4gd2hpY2ggaXMg
aW50ZW5kZWQgZm9yIHVzZSBpbiB0aGUgM0dQUCBjZWxsdWxhciBzdGFuZGFyZHMuPGJyPg0K
PGJyPg0KQW5kcmV3PC9mb250Pjxicj4NCiZuYnNwOzxicj4NCjxkaXYgc3R5bGU9ImJvcmRl
ci13aWR0aDoxcHQgbWVkaXVtIG1lZGl1bTtib3JkZXItc3R5bGU6c29saWQgbm9uZSBub25l
O2JvcmRlci1jb2xvcjpyZ2IoMTgxLDE5NiwyMjMpIC1tb3otdXNlLXRleHQtY29sb3IgLW1v
ei11c2UtdGV4dC1jb2xvcjtwYWRkaW5nOjNwdCAwaW4gMGluIj4NCjxmb250IHN0eWxlPSJm
b250LXNpemU6MTBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fu
cy1zZXJpZiZxdW90OyI+PGI+RnJvbTwvYj46IFRpbSBCcmF5IFttYWlsdG86PGEgaHJlZj0i
bWFpbHRvOnRicmF5QHRleHR1YWxpdHkuY29tIiB0YXJnZXQ9Il9ibGFuayI+dGJyYXlAdGV4
dHVhbGl0eS5jb208L2E+XQ0KPGJyPg0KPGI+U2VudDwvYj46IEZyaWRheSwgSnVseSAxOSwg
MjAxMyAxMDowMiBBTSBDZW50cmFsIFN0YW5kYXJkIFRpbWU8YnI+DQo8Yj5UbzwvYj46IElF
VEYtRGlzY3Vzc2lvbiBEaXNjdXNzaW9uICZsdDs8YSBocmVmPSJtYWlsdG86aWV0ZkBpZXRm
Lm9yZyIgdGFyZ2V0PSJfYmxhbmsiPmlldGZAaWV0Zi5vcmc8L2E+Jmd0Ow0KPGJyPg0KPGI+
U3ViamVjdDwvYj46IExhc3QgY2FsbDogZHJhZnQtbW9udGVtdXJyby1nc21hLWltZWktdXJu
LTE2LnR4dCA8YnI+DQo8L2ZvbnQ+Jm5ic3A7PGJyPg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdiBk
aXI9Imx0ciI+DQo8ZGl2Pg0KPGRpdj5KdXN0IHdhbnRlZCB0byBwb2ludCBvdXQgdGhhdCBi
b3RoIEFwcGxlIChmb3IgaU9TKSBhbmQgR29vZ2xlIChmb3IgQW5kcm9pZCkgaGF2ZSBzdHJv
bmdseSBkaXNjb3VyYWdlZCB0aGUgdXNlIG9mIElNRUkgdG8gaWRlbnRpZnkgZGV2aWNlcyBm
b3IgdGhlIHB1cnBvc2VzIG9mIGFwcGxpY2F0aW9uIHNvZnR3YXJlLiZuYnNwOyBUaGVyZSBh
cmUgcHJpdmFjeSwgcXVhbGl0eSwgYW5kIGF2YWlsYWJpbGl0eSBpc3N1ZXMgd2l0aCB0aGVp
ciB1c2UuJm5ic3A7IEFwcGxlDQogaGFzIHJlbW92ZWQgdGhlIGFiaWxpdHkgb2YgZGV2ZWxv
cGVycyB0byB3b3JrIHdpdGggdGhlIChvZnRlbiBJTUVJLWRlcml2ZWQpIOKAnFVuaXZlcnNh
bCBEZXZpY2UgSUTigJ0gKHNlZQ0KPGEgaHJlZj0iaHR0cDovL2Jsb2dzLmF2Zy5jb20vbW9i
aWxlLTIvYXBwbGUtaW9zLTctcHV0cy11bmlxdWUtZGV2aWNlLWlkcy8iIHRhcmdldD0iX2Js
YW5rIj4NCmh0dHA6Ly9ibG9ncy5hdmcuY29tL21vYmlsZS0yL2FwcGxlLWlvcy03LXB1dHMt
dW5pcXVlLWRldmljZS1pZHMvPC9hPikgYW5kIEdvb2dsZSBoYXMgb2ZmaWNpYWxseSBkZXBy
ZWNhdGVkIHRoZWlyIHVzZToNCjxhIGhyZWY9Imh0dHA6Ly9hbmRyb2lkLWRldmVsb3BlcnMu
YmxvZ3Nwb3QuY2EvMjAxMS8wMy9pZGVudGlmeWluZy1hcHAtaW5zdGFsbGF0aW9ucy5odG1s
IiB0YXJnZXQ9Il9ibGFuayI+DQpodHRwOi8vYW5kcm9pZC1kZXZlbG9wZXJzLmJsb2dzcG90
LmNhLzIwMTEvMDMvaWRlbnRpZnlpbmctYXBwLWluc3RhbGxhdGlvbnMuaHRtbDwvYT48YnI+
DQo8YnI+DQo8L2Rpdj4NCknigJltIG5vdCBzdXJlIGZyb20gcmVhZGluZyB0aGUgZHJhZnQg
d2hhdCB0aGUgZ29hbCBvZiBoYXZpbmcgdGhpcyBVUk4gbmFtZXNwYWNlIGlzLCBidXQgaWYg
aXQgaW52b2x2ZXMgZW5jb3VyYWdpbmcgaXRzIHVzZSBieSBhcHBsaWNhdGlvbiBkZXZlbG9w
ZXJzLCBJ4oCZbSBwcmV0dHkgc3VyZSBpdOKAmXMgYSBiYWQgaWRlYS48YnI+DQo8YnI+DQo8
L2Rpdj4NCiZuYnNwOy1UaW08YnI+DQo8L2Rpdj4NCjwvZGl2Pg0KLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
IDxicj4NClRoaXMgdHJhbnNtaXNzaW9uIChpbmNsdWRpbmcgYW55IGF0dGFjaG1lbnRzKSBt
YXkgY29udGFpbiBjb25maWRlbnRpYWwgaW5mb3JtYXRpb24sIHByaXZpbGVnZWQgbWF0ZXJp
YWwgKGluY2x1ZGluZyBtYXRlcmlhbCBwcm90ZWN0ZWQgYnkgdGhlIHNvbGljaXRvci1jbGll
bnQgb3Igb3RoZXIgYXBwbGljYWJsZSBwcml2aWxlZ2VzKSwgb3IgY29uc3RpdHV0ZSBub24t
cHVibGljIGluZm9ybWF0aW9uLiBBbnkgdXNlIG9mIHRoaXMgaW5mb3JtYXRpb24NCiBieSBh
bnlvbmUgb3RoZXIgdGhhbiB0aGUgaW50ZW5kZWQgcmVjaXBpZW50IGlzIHByb2hpYml0ZWQu
IElmIHlvdSBoYXZlIHJlY2VpdmVkIHRoaXMgdHJhbnNtaXNzaW9uIGluIGVycm9yLCBwbGVh
c2UgaW1tZWRpYXRlbHkgcmVwbHkgdG8gdGhlIHNlbmRlciBhbmQgZGVsZXRlIHRoaXMgaW5m
b3JtYXRpb24gZnJvbSB5b3VyIHN5c3RlbS4gVXNlLCBkaXNzZW1pbmF0aW9uLCBkaXN0cmli
dXRpb24sIG9yIHJlcHJvZHVjdGlvbiBvZiB0aGlzIHRyYW5zbWlzc2lvbg0KIGJ5IHVuaW50
ZW5kZWQgcmVjaXBpZW50cyBpcyBub3QgYXV0aG9yaXplZCBhbmQgbWF5IGJlIHVubGF3ZnVs
LiA8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPGJyPg0KPC9kaXY+DQo8L2Rpdj4N
Ci0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLSA8YnI+DQpUaGlzIHRyYW5zbWlzc2lvbiAoaW5jbHVkaW5nIGFu
eSBhdHRhY2htZW50cykgbWF5IGNvbnRhaW4gY29uZmlkZW50aWFsIGluZm9ybWF0aW9uLCBw
cml2aWxlZ2VkIG1hdGVyaWFsIChpbmNsdWRpbmcgbWF0ZXJpYWwgcHJvdGVjdGVkIGJ5IHRo
ZSBzb2xpY2l0b3ItY2xpZW50IG9yIG90aGVyIGFwcGxpY2FibGUgcHJpdmlsZWdlcyksIG9y
IGNvbnN0aXR1dGUgbm9uLXB1YmxpYyBpbmZvcm1hdGlvbi4gQW55IHVzZSBvZiB0aGlzIGlu
Zm9ybWF0aW9uDQogYnkgYW55b25lIG90aGVyIHRoYW4gdGhlIGludGVuZGVkIHJlY2lwaWVu
dCBpcyBwcm9oaWJpdGVkLiBJZiB5b3UgaGF2ZSByZWNlaXZlZCB0aGlzIHRyYW5zbWlzc2lv
biBpbiBlcnJvciwgcGxlYXNlIGltbWVkaWF0ZWx5IHJlcGx5IHRvIHRoZSBzZW5kZXIgYW5k
IGRlbGV0ZSB0aGlzIGluZm9ybWF0aW9uIGZyb20geW91ciBzeXN0ZW0uIFVzZSwgZGlzc2Vt
aW5hdGlvbiwgZGlzdHJpYnV0aW9uLCBvciByZXByb2R1Y3Rpb24gb2YgdGhpcyB0cmFuc21p
c3Npb24NCiBieSB1bmludGVuZGVkIHJlY2lwaWVudHMgaXMgbm90IGF1dGhvcml6ZWQgYW5k
IG1heSBiZSB1bmxhd2Z1bC4gPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3Rl
Pg0KPC9kaXY+DQo8YnI+DQo8L2Rpdj4NCjwvZGl2Pg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tIDxicj4N
ClRoaXMgdHJhbnNtaXNzaW9uIChpbmNsdWRpbmcgYW55IGF0dGFjaG1lbnRzKSBtYXkgY29u
dGFpbiBjb25maWRlbnRpYWwgaW5mb3JtYXRpb24sIHByaXZpbGVnZWQgbWF0ZXJpYWwgKGlu
Y2x1ZGluZyBtYXRlcmlhbCBwcm90ZWN0ZWQgYnkgdGhlIHNvbGljaXRvci1jbGllbnQgb3Ig
b3RoZXIgYXBwbGljYWJsZSBwcml2aWxlZ2VzKSwgb3IgY29uc3RpdHV0ZSBub24tcHVibGlj
IGluZm9ybWF0aW9uLiBBbnkgdXNlIG9mIHRoaXMgaW5mb3JtYXRpb24gYnkgYW55b25lIG90
aGVyIHRoYW4gdGhlIGludGVuZGVkIHJlY2lwaWVudCBpcyBwcm9oaWJpdGVkLiBJZiB5b3Ug
aGF2ZSByZWNlaXZlZCB0aGlzIHRyYW5zbWlzc2lvbiBpbiBlcnJvciwgcGxlYXNlIGltbWVk
aWF0ZWx5IHJlcGx5IHRvIHRoZSBzZW5kZXIgYW5kIGRlbGV0ZSB0aGlzIGluZm9ybWF0aW9u
IGZyb20geW91ciBzeXN0ZW0uIFVzZSwgZGlzc2VtaW5hdGlvbiwgZGlzdHJpYnV0aW9uLCBv
ciByZXByb2R1Y3Rpb24gb2YgdGhpcyB0cmFuc21pc3Npb24gYnkgdW5pbnRlbmRlZCByZWNp
cGllbnRzIGlzIG5vdCBhdXRob3JpemVkIGFuZCBtYXkgYmUgdW5sYXdmdWwuDQo8L2JvZHk+
DQo8L2h0bWw+DQo=

--_000_BBF5DDFE515C3946BC18D733B20DAD2338DD235EXMB104ADSrimnet_--

From prvs=2913bc3790=aallen@blackberry.com  Sat Jul 20 13:48:27 2013
Return-Path: <prvs=2913bc3790=aallen@blackberry.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 789B011E80D1 for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 13:48:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=0.299,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i8ZQgWFuOX04 for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 13:48:23 -0700 (PDT)
Received: from mhs060cnc.rim.net (mhs060cnc.rim.net [208.65.73.34]) by ietfa.amsl.com (Postfix) with ESMTP id 95B5B21E80BE for <ietf@ietf.org>; Sat, 20 Jul 2013 13:48:19 -0700 (PDT)
X-AuditID: 0a41282f-b7f9b6d000002847-6d-51eaf792c042
Received: from XCT101ADS.rim.net (xct101ads.rim.net [10.67.111.42]) by mhs060cnc.rim.net (SBG) with SMTP id 43.00.10311.297FAE15; Sat, 20 Jul 2013 15:48:18 -0500 (CDT)
Received: from XMB104ADS.rim.net ([fe80::2494:a63d:e3:723b]) by XCT101ADS.rim.net ([fe80::2c7e:1215:d554:35b5%20]) with mapi id 14.02.0328.009; Sat, 20 Jul 2013 15:48:18 -0500
From: Andrew Allen <aallen@blackberry.com>
To: "tbray@textuality.com" <tbray@textuality.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
Thread-Topic: Last call: draft-montemurro-gsma-imei-urn-16.txt
Thread-Index: AQHOhJEO4fYTwuVTOkCw8MDTXs0bMZlsOFEcgAGJd4CAACLcBIAAViUA///RAKQ=
Date: Sat, 20 Jul 2013 20:48:17 +0000
Message-ID: <BBF5DDFE515C3946BC18D733B20DAD2338DD2369@XMB104ADS.rim.net>
In-Reply-To: <CAHBU6ivmsWUzEa+vhhACdg_9e+=b2euZJoD9wj9Gvv3EbNiVdw@mail.gmail.com>
Accept-Language: en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.67.110.252]
Content-Type: multipart/alternative; boundary="_000_BBF5DDFE515C3946BC18D733B20DAD2338DD2369XMB104ADSrimnet_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrHKsWRmVeSWpSXmKPExsXC5ZyvpTvp+6tAg91dVhbPNs5nsXi34zCb xav+m6wWS//MZ3Fg8bj35iOTx85Zd9k9liz5yeRxaelk5gCWqAZGm6TEkrLgzPQ8fTubxLy8 /JLEklSFlNTiZFsln9T0xByFgKLMssTkSgWXzOLknMTM3NQiJYXMFFslEyWFgpzE5NTc1LwS W6XEgoLUvBQlOy4FDGADVJaZp5Cal5yfkpmXbqvkGeyva2FhaqlrqGSnm9DJk/F7/QOmghsh FZs/3mdpYFwT1MXIySEhYCLxYPpMZghbTOLCvfVsXYxcHEICKxklTi69ygzhbGaUOHHrHytI FZuAlsT+w9OZuhg5OEQEDCUW7fUCqWEWaGaU2HzpG9gkYQFbicun/zCC2CICdhLfD15igbD9 JG4+X8EGYrMIqEo8b7wJFucV8JDY0n0GrJdTIFDi/985YL2MArISu89eZwKxmQXEJW49mc8E camAxJI956GuFpV4+RjiNgkBRYnHLd0sEPX5Emfu7meHmC8ocXLmE5YJjCKzkIyahaRsFpKy WUCvMQtoSqzfpQ9RoigxpfshO4StIdE6Zy47svgCRvZVjIK5GcUGZgbJecl6RZm5enmpJZsY QWnGUUN/B+Pb9xaHGAU4GJV4eIu/vQoUYk0sK67MPcQowcGsJMJr+QwoxJuSWFmVWpQfX1Sa k1p8iDEIGEATmaW4k/OBKTCvJN7YwIBIjpI4r9XZs4FCAunANJadmlqQWgQzlImDE2Qpl5RI MTAZpRYllpZkxINSZnwxMGlKNTCK3t8iLsH4ZY5Kb2jblNCP7I8EPpV8sc+WvZE07zGH7eWU i3PKwrgPKToodqoU2m3Yf0j0xTJr/4fbqhrLu8WD4zx4AkOutuxdbPR27fSrZzbbvTNoDtq2 nNV8btrS1efyX2/enrhwft66P//4HXl9S/7d37q5tdRv41aBRQ/kjnH5MS+dH2evxFKckWio xVxUnAgAihhrwYEDAAA=
Cc: "sm+ietf@elandsys.com" <sm+ietf@elandsys.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Jul 2013 20:48:27 -0000

--_000_BBF5DDFE515C3946BC18D733B20DAD2338DD2369XMB104ADSrimnet_
Content-Type: text/plain; charset="utf-8"
content-transfer-encoding: base64

DQpJIHRoaW5rIElBTkEgcmVnaXN0cmF0aW9uIG9mIG5hbWVzcGFjZXMgaGFzIGEgbG90IG9m
IHZhbHVlLg0KDQoNCkZyb206IFRpbSBCcmF5IFttYWlsdG86dGJyYXlAdGV4dHVhbGl0eS5j
b21dDQpTZW50OiBTYXR1cmRheSwgSnVseSAyMCwgMjAxMyAwMTozNiBQTSBDZW50cmFsIFN0
YW5kYXJkIFRpbWUNClRvOiBBbmRyZXcgQWxsZW4NCkNjOiBzY290dC5icmltQGdtYWlsLmNv
bSA8c2NvdHQuYnJpbUBnbWFpbC5jb20+OyBzbStpZXRmQGVsYW5kc3lzLmNvbSA8c20raWV0
ZkBlbGFuZHN5cy5jb20+OyBpZXRmQGlldGYub3JnIDxpZXRmQGlldGYub3JnPg0KU3ViamVj
dDogUmU6IExhc3QgY2FsbDogZHJhZnQtbW9udGVtdXJyby1nc21hLWltZWktdXJuLTE2LnR4
dA0KDQpTbyBpZiBpdOKAmXMgZ29pbmcgdG8gYmUgdXNlZCwgZXhhY3RseSBhcyBzcGVjaWZp
ZWQsIHdoYXRldmVyIHdlIGRvLCB0aGVuIHdoYXQgdmFsdWUgaXMgYWRkZWQgYnkgdGhlIElF
VEYgcHJvY2Vzcz8gIC1UDQoNCg0KT24gU2F0LCBKdWwgMjAsIDIwMTMgYXQgMTE6MjggQU0s
IEFuZHJldyBBbGxlbiA8YWFsbGVuQGJsYWNrYmVycnkuY29tPG1haWx0bzphYWxsZW5AYmxh
Y2tiZXJyeS5jb20+PiB3cm90ZToNCg0KVGhlIFVSTiBjb250YWluaW5nIHRoZSBJTUVJIGlz
IHVzZWQgYnkgYWxsIG1vYmlsZSBwaG9uZXMgdGhhdCBzdXBwb3J0IHZvaWNlIG92ZXIgTFRF
LiBJdCBpcyBhIGRlcGVuZGVuY3kgZm9yIDNHUFAgcmVsZWFzZSA4ICh3aGljaCB3YXMgY29t
cGxldGVkIGFib3V0IGVuZCBvZiAyMDA4KS4gU28geWVzIGl0IGlzIGdvaW5nIHRvIGJlIHVz
ZWQgYW5kIGl0cyBtb3JlIHRoYW4gMyB5ZWFycyBvZiAzR1BQIHdvcmsgaW52ZXN0ZWQgYW5k
IGlzIGFscmVhZHkgaW5jb3Jwb3JhdGVkIGludG8gbWFueSBkZXZpY2VzLg0KDQpJbiB0aGUg
cHJlLWV4aXN0aW5nIGNpcmN1aXQgc3dpdGNoZWQgc3lzdGVtcyB0aGUgSU1FSSBpcyBkZWxp
dmVyZWQgdG8gdGhlIG5ldHdvcmsgYXMgdGhlIGRldmljZSBpZGVudGlmaWVyIGFuZCBpdCBp
cyBhbHNvIG5lY2Vzc2FyeSB0byBkZWxpdmVyIHRoZSBzYW1lIGRldmljZSBpZGVudGlmaWVy
IHRvIHRoZSBuZXR3b3JrIHdoZW4gdXNpbmcgU0lQIHNvIHRoYXQgd2hlbiBoYW5kb3ZlciB0
YWtlcyBwbGFjZSBiZXR3ZWVuIHBhY2tldCBzd2l0Y2hlZCBhbmQgY2lyY3VpdCBzd2l0Y2hl
ZCB0aGUgbmV0d29yayBjYW4gY29ycmVsYXRlIHRoZSBjb21tdW5pY2F0aW9uIGFzIGJlaW5n
IHdpdGggdGhlIHNhbWUgZGV2aWNlLg0KDQpSZWd1bGF0aW9ucyBhbHNvIHJlcXVpcmUgdGhl
IElNRUkgdG8gYmUgZGVsaXZlcmVkIHRvIHRoZSBuZXR3b3JrLg0KVGhpcyBhc3NvY2lhdGVk
IGRyYWZ0IGRlc2NyaWJlcyBob3cgM0dQUCB1c2VzIHRoZSBJTUVJIGFzIGEgU0lQIGluc3Rh
bmNlIElEIGFuZCB0aGUgcmVhc29ucyB3aHk6DQpodHRwOi8vZGF0YXRyYWNrZXIuaWV0Zi5v
cmcvZG9jL2RyYWZ0LWFsbGVuLWRpc3BhdGNoLWltZWktdXJuLWFzLWluc3RhbmNlaWQvDQoN
Cg0KDQotLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tDQpGcm9tOiBTY290dCBCcmltIFtt
YWlsdG86c2NvdHQuYnJpbUBnbWFpbC5jb208bWFpbHRvOnNjb3R0LmJyaW1AZ21haWwuY29t
Pl0NClNlbnQ6IFNhdHVyZGF5LCBKdWx5IDIwLCAyMDEzIDA2OjIzIEFNIENlbnRyYWwgU3Rh
bmRhcmQgVGltZQ0KVG86IFMgTW9vbmVzYW15IDxzbStpZXRmQGVsYW5kc3lzLmNvbTxtYWls
dG86c20lMkJpZXRmQGVsYW5kc3lzLmNvbT4+DQpDYzogVGltIEJyYXkgPHRicmF5QHRleHR1
YWxpdHkuY29tPG1haWx0bzp0YnJheUB0ZXh0dWFsaXR5LmNvbT4+OyBpZXRmQGlldGYub3Jn
PG1haWx0bzppZXRmQGlldGYub3JnPiA8aWV0ZkBpZXRmLm9yZzxtYWlsdG86aWV0ZkBpZXRm
Lm9yZz4+DQpTdWJqZWN0OiBSZTogTGFzdCBjYWxsOiBkcmFmdC1tb250ZW11cnJvLWdzbWEt
aW1laS11cm4tMTYudHh0DQoNClRoYW5rcywgU00sIGZvciBmaW5kaW5nIHdoYXQgSSBzYWlk
IGJhY2sgaW4gMjAxMC4gIEkgc3RpbGwgdGhpbmsgdGhpcw0KaXMgYXJjaGl0ZWN0ZWQgd3Jv
bmcsIGNvbmZsYXRpbmcgZGV2aWNlcyB3aXRoIGNvbW11bmljYXRpb24gZW5kcG9pbnRzDQpo
aWdoZXIgdXAgdGhlIHN0YWNrLCBhbmQgc3RlZXJzIHVzIHRvd2FyZCBhIHBhdGggdG93YXJk
IGV2ZW50dWFsbHkNCiJuZWVkaW5nIiB0byByZWR1Y2UgcHJpdmFjeSBldmVuIG1vcmUuICBI
b3dldmVyLCAzR1BQIGhhcyBhcHBhcmVudGx5DQphbHJlYWR5IGFscmVhZHkgc3RhcnRlZCBt
YXJjaGluZyBkb3duIHRoYXQgcGF0aC4gIENvdWxkIG91ciBsaWFpc29uDQpleHBsYWluIHRo
ZSBzaXR1YXRpb24gdGhlcmU/ICBJcyBhbnlvbmUgYWN0dWFsbHkgZ29pbmcgdG8gdXNlIGl0
PyAgSXMNCnRoaXMgYSBkb25lIGRlYWwgLSBkbyB3ZSBoYXZlIHRvIHN1cHBvcnQgaXQgYmVj
YXVzZSBvdGhlcndpc2UgMyB5ZWFycw0Kb2YgM0dQUCB3b3JrIGdldCB1bmRvbmU/DQoNClNj
b3R0DQoNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KVGhpcyB0cmFuc21pc3Npb24gKGluY2x1ZGluZyBh
bnkgYXR0YWNobWVudHMpIG1heSBjb250YWluIGNvbmZpZGVudGlhbCBpbmZvcm1hdGlvbiwg
cHJpdmlsZWdlZCBtYXRlcmlhbCAoaW5jbHVkaW5nIG1hdGVyaWFsIHByb3RlY3RlZCBieSB0
aGUgc29saWNpdG9yLWNsaWVudCBvciBvdGhlciBhcHBsaWNhYmxlIHByaXZpbGVnZXMpLCBv
ciBjb25zdGl0dXRlIG5vbi1wdWJsaWMgaW5mb3JtYXRpb24uIEFueSB1c2Ugb2YgdGhpcyBp
bmZvcm1hdGlvbiBieSBhbnlvbmUgb3RoZXIgdGhhbiB0aGUgaW50ZW5kZWQgcmVjaXBpZW50
IGlzIHByb2hpYml0ZWQuIElmIHlvdSBoYXZlIHJlY2VpdmVkIHRoaXMgdHJhbnNtaXNzaW9u
IGluIGVycm9yLCBwbGVhc2UgaW1tZWRpYXRlbHkgcmVwbHkgdG8gdGhlIHNlbmRlciBhbmQg
ZGVsZXRlIHRoaXMgaW5mb3JtYXRpb24gZnJvbSB5b3VyIHN5c3RlbS4gVXNlLCBkaXNzZW1p
bmF0aW9uLCBkaXN0cmlidXRpb24sIG9yIHJlcHJvZHVjdGlvbiBvZiB0aGlzIHRyYW5zbWlz
c2lvbiBieSB1bmludGVuZGVkIHJlY2lwaWVudHMgaXMgbm90IGF1dGhvcml6ZWQgYW5kIG1h
eSBiZSB1bmxhd2Z1bC4NCg0KDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NClRoaXMgdHJhbnNtaXNzaW9u
IChpbmNsdWRpbmcgYW55IGF0dGFjaG1lbnRzKSBtYXkgY29udGFpbiBjb25maWRlbnRpYWwg
aW5mb3JtYXRpb24sIHByaXZpbGVnZWQgbWF0ZXJpYWwgKGluY2x1ZGluZyBtYXRlcmlhbCBw
cm90ZWN0ZWQgYnkgdGhlIHNvbGljaXRvci1jbGllbnQgb3Igb3RoZXIgYXBwbGljYWJsZSBw
cml2aWxlZ2VzKSwgb3IgY29uc3RpdHV0ZSBub24tcHVibGljIGluZm9ybWF0aW9uLiBBbnkg
dXNlIG9mIHRoaXMgaW5mb3JtYXRpb24gYnkgYW55b25lIG90aGVyIHRoYW4gdGhlIGludGVu
ZGVkIHJlY2lwaWVudCBpcyBwcm9oaWJpdGVkLiBJZiB5b3UgaGF2ZSByZWNlaXZlZCB0aGlz
IHRyYW5zbWlzc2lvbiBpbiBlcnJvciwgcGxlYXNlIGltbWVkaWF0ZWx5IHJlcGx5IHRvIHRo
ZSBzZW5kZXIgYW5kIGRlbGV0ZSB0aGlzIGluZm9ybWF0aW9uIGZyb20geW91ciBzeXN0ZW0u
IFVzZSwgZGlzc2VtaW5hdGlvbiwgZGlzdHJpYnV0aW9uLCBvciByZXByb2R1Y3Rpb24gb2Yg
dGhpcyB0cmFuc21pc3Npb24gYnkgdW5pbnRlbmRlZCByZWNpcGllbnRzIGlzIG5vdCBhdXRo
b3JpemVkIGFuZCBtYXkgYmUgdW5sYXdmdWwuDQo=

--_000_BBF5DDFE515C3946BC18D733B20DAD2338DD2369XMB104ADSrimnet_
Content-Type: text/html; charset="utf-8"
content-transfer-encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5Pg0KPGZvbnQg
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxicj4NCkkgdGhpbmsg
SUFOQSByZWdpc3RyYXRpb24gb2YgbmFtZXNwYWNlcyBoYXMgYSBsb3Qgb2YgdmFsdWUuPGJy
Pg0KPC9mb250Pjxicj4NCiZuYnNwOzxicj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2Jv
cmRlci10b3A6c29saWQgI0I1QzRERiAxLjBwdDtwYWRkaW5nOjMuMHB0IDBpbiAwaW4gMGlu
Ij4NCjxmb250IHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1Rh
aG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij48Yj5Gcm9tPC9iPjogVGltIEJy
YXkgW21haWx0bzp0YnJheUB0ZXh0dWFsaXR5LmNvbV0NCjxicj4NCjxiPlNlbnQ8L2I+OiBT
YXR1cmRheSwgSnVseSAyMCwgMjAxMyAwMTozNiBQTSBDZW50cmFsIFN0YW5kYXJkIFRpbWU8
YnI+DQo8Yj5UbzwvYj46IEFuZHJldyBBbGxlbiA8YnI+DQo8Yj5DYzwvYj46IHNjb3R0LmJy
aW1AZ21haWwuY29tICZsdDtzY290dC5icmltQGdtYWlsLmNvbSZndDs7IHNtJiM0MztpZXRm
QGVsYW5kc3lzLmNvbSAmbHQ7c20mIzQzO2lldGZAZWxhbmRzeXMuY29tJmd0OzsgaWV0ZkBp
ZXRmLm9yZyAmbHQ7aWV0ZkBpZXRmLm9yZyZndDsNCjxicj4NCjxiPlN1YmplY3Q8L2I+OiBS
ZTogTGFzdCBjYWxsOiBkcmFmdC1tb250ZW11cnJvLWdzbWEtaW1laS11cm4tMTYudHh0IDxi
cj4NCjwvZm9udD4mbmJzcDs8YnI+DQo8L2Rpdj4NCjxkaXYgZGlyPSJsdHIiPlNvIGlmIGl0
4oCZcyBnb2luZyB0byBiZSB1c2VkLCBleGFjdGx5IGFzIHNwZWNpZmllZCwgd2hhdGV2ZXIg
d2UgZG8sIHRoZW4gd2hhdCB2YWx1ZSBpcyBhZGRlZCBieSB0aGUgSUVURiBwcm9jZXNzPyZu
YnNwOyAtVDxicj4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0iZ21haWxfZXh0cmEiPjxicj4NCjxi
cj4NCjxkaXYgY2xhc3M9ImdtYWlsX3F1b3RlIj5PbiBTYXQsIEp1bCAyMCwgMjAxMyBhdCAx
MToyOCBBTSwgQW5kcmV3IEFsbGVuIDxzcGFuIGRpcj0ibHRyIj4NCiZsdDs8YSBocmVmPSJt
YWlsdG86YWFsbGVuQGJsYWNrYmVycnkuY29tIiB0YXJnZXQ9Il9ibGFuayI+YWFsbGVuQGJs
YWNrYmVycnkuY29tPC9hPiZndDs8L3NwYW4+IHdyb3RlOjxicj4NCjxibG9ja3F1b3RlIGNs
YXNzPSJnbWFpbF9xdW90ZSIgc3R5bGU9Im1hcmdpbjowIDAgMCAuOGV4O2JvcmRlci1sZWZ0
OjFweCAjY2NjIHNvbGlkO3BhZGRpbmctbGVmdDoxZXgiPg0KPGJyPg0KVGhlIFVSTiBjb250
YWluaW5nIHRoZSBJTUVJIGlzIHVzZWQgYnkgYWxsIG1vYmlsZSBwaG9uZXMgdGhhdCBzdXBw
b3J0IHZvaWNlIG92ZXIgTFRFLiBJdCBpcyBhIGRlcGVuZGVuY3kgZm9yIDNHUFAgcmVsZWFz
ZSA4ICh3aGljaCB3YXMgY29tcGxldGVkIGFib3V0IGVuZCBvZiAyMDA4KS4gU28geWVzIGl0
IGlzIGdvaW5nIHRvIGJlIHVzZWQgYW5kIGl0cyBtb3JlIHRoYW4gMyB5ZWFycyBvZiAzR1BQ
IHdvcmsgaW52ZXN0ZWQgYW5kIGlzIGFscmVhZHkNCiBpbmNvcnBvcmF0ZWQgaW50byBtYW55
IGRldmljZXMuPGJyPg0KPGJyPg0KSW4gdGhlIHByZS1leGlzdGluZyBjaXJjdWl0IHN3aXRj
aGVkIHN5c3RlbXMgdGhlIElNRUkgaXMgZGVsaXZlcmVkIHRvIHRoZSBuZXR3b3JrIGFzIHRo
ZSBkZXZpY2UgaWRlbnRpZmllciBhbmQgaXQgaXMgYWxzbyBuZWNlc3NhcnkgdG8gZGVsaXZl
ciB0aGUgc2FtZSBkZXZpY2UgaWRlbnRpZmllciB0byB0aGUgbmV0d29yayB3aGVuIHVzaW5n
IFNJUCBzbyB0aGF0IHdoZW4gaGFuZG92ZXIgdGFrZXMgcGxhY2UgYmV0d2VlbiBwYWNrZXQg
c3dpdGNoZWQNCiBhbmQgY2lyY3VpdCBzd2l0Y2hlZCB0aGUgbmV0d29yayBjYW4gY29ycmVs
YXRlIHRoZSBjb21tdW5pY2F0aW9uIGFzIGJlaW5nIHdpdGggdGhlIHNhbWUgZGV2aWNlLjxi
cj4NCjxicj4NClJlZ3VsYXRpb25zIGFsc28gcmVxdWlyZSB0aGUgSU1FSSB0byBiZSBkZWxp
dmVyZWQgdG8gdGhlIG5ldHdvcmsuPGJyPg0KVGhpcyBhc3NvY2lhdGVkIGRyYWZ0IGRlc2Ny
aWJlcyBob3cgM0dQUCB1c2VzIHRoZSBJTUVJIGFzIGEgU0lQIGluc3RhbmNlIElEIGFuZCB0
aGUgcmVhc29ucyB3aHk6PGJyPg0KPGEgaHJlZj0iaHR0cDovL2RhdGF0cmFja2VyLmlldGYu
b3JnL2RvYy9kcmFmdC1hbGxlbi1kaXNwYXRjaC1pbWVpLXVybi1hcy1pbnN0YW5jZWlkLyIg
dGFyZ2V0PSJfYmxhbmsiPmh0dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQt
YWxsZW4tZGlzcGF0Y2gtaW1laS11cm4tYXMtaW5zdGFuY2VpZC88L2E+PGJyPg0KPGRpdiBj
bGFzcz0iaW0gSE9FblpiIj48YnI+DQo8YnI+DQo8YnI+DQotLS0tLSBPcmlnaW5hbCBNZXNz
YWdlIC0tLS0tPGJyPg0KRnJvbTogU2NvdHQgQnJpbSBbbWFpbHRvOjxhIGhyZWY9Im1haWx0
bzpzY290dC5icmltQGdtYWlsLmNvbSI+c2NvdHQuYnJpbUBnbWFpbC5jb208L2E+XTxicj4N
ClNlbnQ6IFNhdHVyZGF5LCBKdWx5IDIwLCAyMDEzIDA2OjIzIEFNIENlbnRyYWwgU3RhbmRh
cmQgVGltZTxicj4NClRvOiBTIE1vb25lc2FteSAmbHQ7PGEgaHJlZj0ibWFpbHRvOnNtJTJC
aWV0ZkBlbGFuZHN5cy5jb20iPnNtJiM0MztpZXRmQGVsYW5kc3lzLmNvbTwvYT4mZ3Q7PGJy
Pg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSJpbSBIT0VuWmIiPkNjOiBUaW0gQnJheSAmbHQ7PGEg
aHJlZj0ibWFpbHRvOnRicmF5QHRleHR1YWxpdHkuY29tIj50YnJheUB0ZXh0dWFsaXR5LmNv
bTwvYT4mZ3Q7Ow0KPGEgaHJlZj0ibWFpbHRvOmlldGZAaWV0Zi5vcmciPmlldGZAaWV0Zi5v
cmc8L2E+ICZsdDs8YSBocmVmPSJtYWlsdG86aWV0ZkBpZXRmLm9yZyI+aWV0ZkBpZXRmLm9y
ZzwvYT4mZ3Q7PGJyPg0KU3ViamVjdDogUmU6IExhc3QgY2FsbDogZHJhZnQtbW9udGVtdXJy
by1nc21hLWltZWktdXJuLTE2LnR4dDxicj4NCjxicj4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0i
SE9FblpiIj4NCjxkaXYgY2xhc3M9Img1Ij5UaGFua3MsIFNNLCBmb3IgZmluZGluZyB3aGF0
IEkgc2FpZCBiYWNrIGluIDIwMTAuICZuYnNwO0kgc3RpbGwgdGhpbmsgdGhpczxicj4NCmlz
IGFyY2hpdGVjdGVkIHdyb25nLCBjb25mbGF0aW5nIGRldmljZXMgd2l0aCBjb21tdW5pY2F0
aW9uIGVuZHBvaW50czxicj4NCmhpZ2hlciB1cCB0aGUgc3RhY2ssIGFuZCBzdGVlcnMgdXMg
dG93YXJkIGEgcGF0aCB0b3dhcmQgZXZlbnR1YWxseTxicj4NCiZxdW90O25lZWRpbmcmcXVv
dDsgdG8gcmVkdWNlIHByaXZhY3kgZXZlbiBtb3JlLiAmbmJzcDtIb3dldmVyLCAzR1BQIGhh
cyBhcHBhcmVudGx5PGJyPg0KYWxyZWFkeSBhbHJlYWR5IHN0YXJ0ZWQgbWFyY2hpbmcgZG93
biB0aGF0IHBhdGguICZuYnNwO0NvdWxkIG91ciBsaWFpc29uPGJyPg0KZXhwbGFpbiB0aGUg
c2l0dWF0aW9uIHRoZXJlPyAmbmJzcDtJcyBhbnlvbmUgYWN0dWFsbHkgZ29pbmcgdG8gdXNl
IGl0PyAmbmJzcDtJczxicj4NCnRoaXMgYSBkb25lIGRlYWwgLSBkbyB3ZSBoYXZlIHRvIHN1
cHBvcnQgaXQgYmVjYXVzZSBvdGhlcndpc2UgMyB5ZWFyczxicj4NCm9mIDNHUFAgd29yayBn
ZXQgdW5kb25lPzxicj4NCjxicj4NClNjb3R0PGJyPg0KPGJyPg0KPC9kaXY+DQo8L2Rpdj4N
CjxkaXYgY2xhc3M9IkhPRW5aYiI+DQo8ZGl2IGNsYXNzPSJoNSI+LS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
PGJyPg0KVGhpcyB0cmFuc21pc3Npb24gKGluY2x1ZGluZyBhbnkgYXR0YWNobWVudHMpIG1h
eSBjb250YWluIGNvbmZpZGVudGlhbCBpbmZvcm1hdGlvbiwgcHJpdmlsZWdlZCBtYXRlcmlh
bCAoaW5jbHVkaW5nIG1hdGVyaWFsIHByb3RlY3RlZCBieSB0aGUgc29saWNpdG9yLWNsaWVu
dCBvciBvdGhlciBhcHBsaWNhYmxlIHByaXZpbGVnZXMpLCBvciBjb25zdGl0dXRlIG5vbi1w
dWJsaWMgaW5mb3JtYXRpb24uIEFueSB1c2Ugb2YgdGhpcyBpbmZvcm1hdGlvbg0KIGJ5IGFu
eW9uZSBvdGhlciB0aGFuIHRoZSBpbnRlbmRlZCByZWNpcGllbnQgaXMgcHJvaGliaXRlZC4g
SWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyB0cmFuc21pc3Npb24gaW4gZXJyb3IsIHBsZWFz
ZSBpbW1lZGlhdGVseSByZXBseSB0byB0aGUgc2VuZGVyIGFuZCBkZWxldGUgdGhpcyBpbmZv
cm1hdGlvbiBmcm9tIHlvdXIgc3lzdGVtLiBVc2UsIGRpc3NlbWluYXRpb24sIGRpc3RyaWJ1
dGlvbiwgb3IgcmVwcm9kdWN0aW9uIG9mIHRoaXMgdHJhbnNtaXNzaW9uDQogYnkgdW5pbnRl
bmRlZCByZWNpcGllbnRzIGlzIG5vdCBhdXRob3JpemVkIGFuZCBtYXkgYmUgdW5sYXdmdWwu
PGJyPg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPGJyPg0KPC9k
aXY+DQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0gPGJyPg0KVGhpcyB0cmFuc21pc3Npb24gKGluY2x1ZGlu
ZyBhbnkgYXR0YWNobWVudHMpIG1heSBjb250YWluIGNvbmZpZGVudGlhbCBpbmZvcm1hdGlv
biwgcHJpdmlsZWdlZCBtYXRlcmlhbCAoaW5jbHVkaW5nIG1hdGVyaWFsIHByb3RlY3RlZCBi
eSB0aGUgc29saWNpdG9yLWNsaWVudCBvciBvdGhlciBhcHBsaWNhYmxlIHByaXZpbGVnZXMp
LCBvciBjb25zdGl0dXRlIG5vbi1wdWJsaWMgaW5mb3JtYXRpb24uIEFueSB1c2Ugb2YgdGhp
cyBpbmZvcm1hdGlvbiBieSBhbnlvbmUgb3RoZXIgdGhhbiB0aGUgaW50ZW5kZWQgcmVjaXBp
ZW50IGlzIHByb2hpYml0ZWQuIElmIHlvdSBoYXZlIHJlY2VpdmVkIHRoaXMgdHJhbnNtaXNz
aW9uIGluIGVycm9yLCBwbGVhc2UgaW1tZWRpYXRlbHkgcmVwbHkgdG8gdGhlIHNlbmRlciBh
bmQgZGVsZXRlIHRoaXMgaW5mb3JtYXRpb24gZnJvbSB5b3VyIHN5c3RlbS4gVXNlLCBkaXNz
ZW1pbmF0aW9uLCBkaXN0cmlidXRpb24sIG9yIHJlcHJvZHVjdGlvbiBvZiB0aGlzIHRyYW5z
bWlzc2lvbiBieSB1bmludGVuZGVkIHJlY2lwaWVudHMgaXMgbm90IGF1dGhvcml6ZWQgYW5k
IG1heSBiZSB1bmxhd2Z1bC4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_BBF5DDFE515C3946BC18D733B20DAD2338DD2369XMB104ADSrimnet_--

From scott.brim@gmail.com  Sat Jul 20 13:55:48 2013
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8263321E80A9 for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 13:55:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VatF8bi3XZH8 for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 13:55:48 -0700 (PDT)
Received: from mail-ob0-x22e.google.com (mail-ob0-x22e.google.com [IPv6:2607:f8b0:4003:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 19D6B21E80A6 for <ietf@ietf.org>; Sat, 20 Jul 2013 13:55:48 -0700 (PDT)
Received: by mail-ob0-f174.google.com with SMTP id wd20so6695141obb.19 for <ietf@ietf.org>; Sat, 20 Jul 2013 13:55:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=oasQW2wsfpsM6FBAunwC5VoATy9cIcQyX0ey0cr08Lk=; b=FpcDaY0QCFfHlRdX0AetJjsakfQUIepsbNDwhGHi8ZadxV5F/XZKXp1TGaGC6OKyPP SklELnnYfCX60U7N4Qm4fDz8NE4opgCgpmLACu/qWaeHpi5eTdW1x5sLbHCOZGY24UFw KN7TFnx+6GCSSqEg/gVOsxEFG+6w9+N3NBUvg1djrDWM2s67ID4vCOrRuw/61q9TWlLo 3408+EsySutYoiZK5S0LXKudoAJJ88Acp9iLnQZoOzSH0YrBwj64ja8IduT0KT5uY0Xl PRjrb9XZqt09lt7Oe/nTTCokfRu0sSrHM8wowH333qc5KwsPm4gEiQt1IZ0V6iJl5q2u XOPQ==
X-Received: by 10.60.95.198 with SMTP id dm6mr22177472oeb.44.1374353747581; Sat, 20 Jul 2013 13:55:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.251.226 with HTTP; Sat, 20 Jul 2013 13:55:27 -0700 (PDT)
In-Reply-To: <BBF5DDFE515C3946BC18D733B20DAD2338DD2341@XMB104ADS.rim.net>
References: <CAHBU6ivC37fzO1oC=Ow3EGfBUt2GEsLRy3YWn6OZa9tTTTNZpQ@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD2338DD2341@XMB104ADS.rim.net>
From: Scott Brim <scott.brim@gmail.com>
Date: Sat, 20 Jul 2013 16:55:27 -0400
Message-ID: <CAPv4CP_g-FtAowBvP6CS2t4OB3j6usHSV2sTAc=tmTpESc2dHw@mail.gmail.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
To: Andrew Allen <aallen@blackberry.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "tbray@textuality.com" <tbray@textuality.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Jul 2013 20:55:48 -0000

On Sat, Jul 20, 2013 at 4:08 PM, Andrew Allen <aallen@blackberry.com> wrote:
> Tim
>
> The quote is from RFC 5626 which also states:
>
> "3.1. Summary of Mechanism
>
> Each UA has a unique instance-id that stays the same for this UA even if the
> UA reboots or is power cycled."
>
> Since the UUID in the instance ID is also static how is this significantly
> different in terms of privacy concerns from the IMEI being used as an
> instance ID?

You're not demonstrating that an IMEI is just as good, you're
demonstrating that a UUID is just as bad.

From tbray@textuality.com  Sat Jul 20 14:07:31 2013
Return-Path: <tbray@textuality.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1A1E21F9F50 for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 14:07:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.798
X-Spam-Level: 
X-Spam-Status: No, score=-2.798 tagged_above=-999 required=5 tests=[AWL=0.179,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id urRjszLWYNdP for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 14:07:22 -0700 (PDT)
Received: from mail-ve0-f181.google.com (mail-ve0-f181.google.com [209.85.128.181]) by ietfa.amsl.com (Postfix) with ESMTP id 03ABE21F9E52 for <ietf@ietf.org>; Sat, 20 Jul 2013 14:07:21 -0700 (PDT)
Received: by mail-ve0-f181.google.com with SMTP id db10so4207712veb.12 for <ietf@ietf.org>; Sat, 20 Jul 2013 14:07:21 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=BXrjZP1rZTvGEtpF5ekF/wr9UqQz+cEoPGaWyGRiV7A=; b=J8bnN8nmRGjtNIz9DmmU8cnSPmdhfnY6kLT4s9SXUCfSIpEtTLhnkztU8mXlze6d/S 1tPpoli0PsKBI01uEQlVxsn0HC55vZx9NDFzdT/ZxB2Rt5x54dEzECokGMc7QH2oO6Ct SAppgZljMfNfXQHPAgd6iT1RmzLNAzl1ycEuuzjNx9kAJ4BaKZUx0IfBJ6rHXX0orTDY KIa3UqRcRw5fHucI00Z9Jimv1p2HuKG8DYE76oEJoS5wkp0ExWnL7QqgXp78iunyOqTD HHdpI+J0znRGce2QypFiw5PHuH0b2MgR/7g9iWVxSSPF0bIjxZPjp6wf3A/6zpauNFW2 S0zg==
MIME-Version: 1.0
X-Received: by 10.58.85.161 with SMTP id i1mr7336743vez.97.1374354441461; Sat, 20 Jul 2013 14:07:21 -0700 (PDT)
Received: by 10.220.219.200 with HTTP; Sat, 20 Jul 2013 14:07:21 -0700 (PDT)
X-Originating-IP: [24.84.235.32]
In-Reply-To: <CAPv4CP_g-FtAowBvP6CS2t4OB3j6usHSV2sTAc=tmTpESc2dHw@mail.gmail.com>
References: <CAHBU6ivC37fzO1oC=Ow3EGfBUt2GEsLRy3YWn6OZa9tTTTNZpQ@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD2338DD2341@XMB104ADS.rim.net> <CAPv4CP_g-FtAowBvP6CS2t4OB3j6usHSV2sTAc=tmTpESc2dHw@mail.gmail.com>
Date: Sat, 20 Jul 2013 14:07:21 -0700
Message-ID: <CAHBU6isF=37q3wbr7teq1Yx-s1hs+mwgzqSvVU7v=AW+nOW2zA@mail.gmail.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
From: Tim Bray <tbray@textuality.com>
To: Scott Brim <scott.brim@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b6da6ac4773fd04e1f7d488
X-Gm-Message-State: ALoCoQnIoQ1WsvowRsgZd1FwZ/Cwn+ST+7p8SohoFrd6sXztFO+Nt8HKwZbVj3/j8gAb8hSpNjKo
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Jul 2013 21:07:31 -0000

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

Except that for normal usages at the application level, the UUID is
generated by the app and placed in its private per-app storage, which is
always erased on a factory-reset.  To Andrew Allen: I strongly recommend
factory-resetting your phone before you sell it, and also factory-resetting
any phones you buy second-hand, just to be sure.  Most people do this, for
good reason. -T


On Sat, Jul 20, 2013 at 1:55 PM, Scott Brim <scott.brim@gmail.com> wrote:

> On Sat, Jul 20, 2013 at 4:08 PM, Andrew Allen <aallen@blackberry.com>
> wrote:
> > Tim
> >
> > The quote is from RFC 5626 which also states:
> >
> > "3.1. Summary of Mechanism
> >
> > Each UA has a unique instance-id that stays the same for this UA even if
> the
> > UA reboots or is power cycled."
> >
> > Since the UUID in the instance ID is also static how is this
> significantly
> > different in terms of privacy concerns from the IMEI being used as an
> > instance ID?
>
> You're not demonstrating that an IMEI is just as good, you're
> demonstrating that a UUID is just as bad.
>

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

<div dir=3D"ltr">Except that for normal usages at the application level, th=
e UUID is generated by the app and placed in its private per-app storage, w=
hich is always erased on a factory-reset.=C2=A0 To Andrew Allen: I strongly=
 recommend factory-resetting your phone before you sell it, and also factor=
y-resetting any phones you buy second-hand, just to be sure.=C2=A0 Most peo=
ple do this, for good reason. -T<br>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Sat,=
 Jul 20, 2013 at 1:55 PM, Scott Brim <span dir=3D"ltr">&lt;<a href=3D"mailt=
o:scott.brim@gmail.com" target=3D"_blank">scott.brim@gmail.com</a>&gt;</spa=
n> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On Sat, Jul 20, 2013 at 4:=
08 PM, Andrew Allen &lt;<a href=3D"mailto:aallen@blackberry.com">aallen@bla=
ckberry.com</a>&gt; wrote:<br>

</div><div class=3D"im">&gt; Tim<br>
&gt;<br>
&gt; The quote is from RFC 5626 which also states:<br>
&gt;<br>
&gt; &quot;3.1. Summary of Mechanism<br>
&gt;<br>
&gt; Each UA has a unique instance-id that stays the same for this UA even =
if the<br>
&gt; UA reboots or is power cycled.&quot;<br>
&gt;<br>
&gt; Since the UUID in the instance ID is also static how is this significa=
ntly<br>
&gt; different in terms of privacy concerns from the IMEI being used as an<=
br>
&gt; instance ID?<br>
<br>
</div>You&#39;re not demonstrating that an IMEI is just as good, you&#39;re=
<br>
demonstrating that a UUID is just as bad.<br>
</blockquote></div><br></div>

--047d7b6da6ac4773fd04e1f7d488--

From dougb@dougbarton.us  Sat Jul 20 15:20:00 2013
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E17AD21F880F for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 15:20:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b76k13Ksv9Yu for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 15:20:00 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [IPv6:2607:f2f8:ab14::2]) by ietfa.amsl.com (Postfix) with ESMTP id 708D321F868C for <ietf@ietf.org>; Sat, 20 Jul 2013 15:20:00 -0700 (PDT)
Received: from [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b] (unknown [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b]) by dougbarton.us (Postfix) with ESMTPSA id 1601E22B26 for <ietf@ietf.org>; Sat, 20 Jul 2013 22:19:58 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1374358798; bh=3k7wtaEsImuyltCnMSHz+ZCbq3Nm/wsYahsg2jJLbVQ=; h=Date:From:To:Subject:References:In-Reply-To; b=JurrqS21OOQTjyArSlLYExzhsBKQt6mdA9q+aTDntvHlfeMEvYC9HqyDDiju7zh6G drS7tRcTQi+k5tbyUsTq/+PJ8Gq/TkAi6tCy/4fds1idV8H56qObQAtGqyw64xC7PY hWtxZsFrTjxGCL0hRvo83ZL115f5i0DkrNdpJCO8=
Message-ID: <51EB0D0D.8040008@dougbarton.us>
Date: Sat, 20 Jul 2013 15:19:57 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
References: <BBF5DDFE515C3946BC18D733B20DAD2338DD2369@XMB104ADS.rim.net>
In-Reply-To: <BBF5DDFE515C3946BC18D733B20DAD2338DD2369@XMB104ADS.rim.net>
X-Enigmail-Version: 1.5.2
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Jul 2013 22:20:01 -0000

On 07/20/2013 01:48 PM, Andrew Allen wrote:
> I think IANA registration of namespaces has a lot of value.

I think backfilling registrations for poached identifiers sets a 
bad/dangerous example.

Doug (not necessarily speaking with any hats, current or former)


From prvs=9913f7849d=aallen@blackberry.com  Sat Jul 20 15:20:35 2013
Return-Path: <prvs=9913f7849d=aallen@blackberry.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C37721F9E12 for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 15:20:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.639
X-Spam-Level: 
X-Spam-Status: No, score=-5.639 tagged_above=-999 required=5 tests=[AWL=-0.436, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JwqOVLjDwOQU for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 15:20:30 -0700 (PDT)
Received: from mhs060cnc.rim.net (mhs060cnc.rim.net [208.65.73.34]) by ietfa.amsl.com (Postfix) with ESMTP id 20CB421E805D for <ietf@ietf.org>; Sat, 20 Jul 2013 15:20:30 -0700 (PDT)
X-AuditID: 0a41282f-b7f9b6d000002847-9a-51eb0d270870
Received: from XCT105ADS.rim.net (xct105ads.rim.net [10.67.111.46]) by mhs060cnc.rim.net (SBG) with SMTP id 54.50.10311.72D0BE15; Sat, 20 Jul 2013 17:20:23 -0500 (CDT)
Received: from XMB104ADS.rim.net ([fe80::2494:a63d:e3:723b]) by XCT105ADS.rim.net ([fe80::2d01:2041:eea3:819b%22]) with mapi id 14.02.0328.009; Sat, 20 Jul 2013 17:20:22 -0500
From: Andrew Allen <aallen@blackberry.com>
To: "scott.brim@gmail.com" <scott.brim@gmail.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
Thread-Topic: Last call: draft-montemurro-gsma-imei-urn-16.txt
Thread-Index: AQHOhJEO4fYTwuVTOkCw8MDTXs0bMZlsItsKgABZfICAAYRS+oAAYPKA///D5wY=
Date: Sat, 20 Jul 2013 22:20:21 +0000
Message-ID: <BBF5DDFE515C3946BC18D733B20DAD2338DD23A8@XMB104ADS.rim.net>
In-Reply-To: <CAPv4CP_g-FtAowBvP6CS2t4OB3j6usHSV2sTAc=tmTpESc2dHw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.67.110.252]
Content-Type: text/plain; charset="iso-8859-1"
content-transfer-encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrAKsWRmVeSWpSXmKPExsXC5Zyvp6vO+zrQYN0iKYtnG+ezWLzbcZjN Yumf+SwOzB47Z91l91iy5CeTx6Wlk5kDmKMaGG2SEkvKgjPT8/TtbBLz8vJLEktSFVJSi5Nt lXxS0xNzFAKKMssSkysVXDKLk3MSM3NTi5QUMlNslUyUFApyEpNTc1PzSmyVEgsKUvNSlOy4 FDCADVBZZp5Cal5yfkpmXrqtkmewv66FhamlrqGSnW5CJ0/G7m2/GQvmcFUcf32YvYFxDkcX IyeHhICJxO/fd9khbDGJC/fWs3UxcnEICaxklNi4+TMLhLOZUeLqt2msIFVsAloS+w9PZwKx RQQMJdYvbWIDsZkFQiQWv3gANklYwFbi8uk/jBA1dhLfD15igbD9JF51LASrZxFQlThyag6Y zSvgITHj6UqwXk6BQImfs1aA2YxAF30/tYYJYr64xK0n85kgLhWQWLLnPDOELSrx8vE/Vghb UeJxSzcLRL2exI2pU6Bu05ZYtvA1M8QuQYmTM5+wTGAUnYVk7CwkLbOQtMxC0rKAkWUVo2Bu RrGBmUFyXrJeUWauXl5qySZGUJJw1NDfwfj2vcUhRgEORiUeXnP214FCrIllxZW5hxglOJiV RHgtn70KFOJNSaysSi3Kjy8qzUktPsToCgyJicxS3Mn5wASWVxJvbGCAm6Mkzmt19mygkEA6 MP1kp6YWpBbBzGHi4ATZwyUlUgxMIqlFiaUlGfGgVBdfDEx2Ug2MHGaed66Uf/+y2+FlWlPb qY57fzxnrfdO6de+eG7tjsP2BtknyhPrix9YGF8pC9DolFzcM+X4g6xXylv7m3zufCsJ31pj sfppY1aNQsxuzpSZ7lnapi/c09Q8Mq7u4D3wwJhdKdjgasRN10dCHCab2AOidS2CJgp03GU0 Zjh/v/h/aaxfaLASS3FGoqEWc1FxIgDJdQb+UwMAAA==
Cc: "tbray@textuality.com" <tbray@textuality.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Jul 2013 22:20:36 -0000

Equivalence is equivalence the rest seems subjective to me - is the glass ha=
lf full or half empty.

The point is they are no more or less harmful.

Can it please be explained how the IMEI URN when used as stated in http://da=
tatracker.ietf.org/doc/draft-allen-dispatch-imei-urn-as-instanceid/
Is any more harmful than as the IMEI is used today by over 90% of mobile pho=
nes in use today worldwide?

Andrew

----- Original Message -----
From: Scott Brim [mailto:scott.brim@gmail.com]
Sent: Saturday, July 20, 2013 03:55 PM Central Standard Time=0A=
To: Andrew Allen
Cc: tbray@textuality.com <tbray@textuality.com>; ietf@ietf.org <ietf@ietf.or=
g>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt

On Sat, Jul 20, 2013 at 4:08 PM, Andrew Allen <aallen@blackberry.com> wrote:
> Tim
>
> The quote is from RFC 5626 which also states:
>
> "3.1. Summary of Mechanism
>
> Each UA has a unique instance-id that stays the same for this UA even if t=
he
> UA reboots or is power cycled."
>
> Since the UUID in the instance ID is also static how is this significantly
> different in terms of privacy concerns from the IMEI being used as an
> instance ID?

You're not demonstrating that an IMEI is just as good, you're
demonstrating that a UUID is just as bad.

---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential infor=
mation, privileged material (including material protected by the solicitor-c=
lient or other applicable privileges), or constitute non-public information.=
 Any use of this information by anyone other than the intended recipient is=
 prohibited. If you have received this transmission in error, please immedia=
tely reply to the sender and delete this information from your system. Use,=
 dissemination, distribution, or reproduction of this transmission by uninte=
nded recipients is not authorized and may be unlawful.

From prvs=3913449491=aallen@blackberry.com  Sat Jul 20 15:34:49 2013
Return-Path: <prvs=3913449491=aallen@blackberry.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB9BB21F9984 for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 15:34:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.59
X-Spam-Level: 
X-Spam-Status: No, score=-5.59 tagged_above=-999 required=5 tests=[AWL=-0.387,  BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ovrj2T69LE0o for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 15:34:45 -0700 (PDT)
Received: from mhs060cnc.rim.net (mhs060cnc.rim.net [208.65.73.34]) by ietfa.amsl.com (Postfix) with ESMTP id 7DF9721F97E6 for <ietf@ietf.org>; Sat, 20 Jul 2013 15:34:45 -0700 (PDT)
X-AuditID: 0a41282f-b7f9b6d000002847-e8-51eb10849d56
Received: from XCT102ADS.rim.net (xct102ads.rim.net [10.67.111.43]) by mhs060cnc.rim.net (SBG) with SMTP id 2F.50.10311.4801BE15; Sat, 20 Jul 2013 17:34:44 -0500 (CDT)
Received: from XMB104ADS.rim.net ([fe80::2494:a63d:e3:723b]) by XCT102ADS.rim.net ([fe80::4806:2e1d:2b7c:cfdf%22]) with mapi id 14.02.0328.009; Sat, 20 Jul 2013 17:34:43 -0500
From: Andrew Allen <aallen@blackberry.com>
To: "martin.thomson@gmail.com" <martin.thomson@gmail.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
Thread-Topic: Last call: draft-montemurro-gsma-imei-urn-16.txt
Thread-Index: AQHOhJEO4fYTwuVTOkCw8MDTXs0bMZlsItsKgABg4wCAAaXI/g==
Date: Sat, 20 Jul 2013 22:34:43 +0000
Message-ID: <BBF5DDFE515C3946BC18D733B20DAD2338DD23C3@XMB104ADS.rim.net>
In-Reply-To: <CABkgnnUk9kvtAoFYDsgDAsdeYmd7QUFv5P28H3sbc5HpsgBmjg@mail.gmail.com>
Accept-Language: en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.67.110.252]
Content-Type: text/plain; charset="iso-8859-1"
content-transfer-encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrPKsWRmVeSWpSXmKPExsXC5Zyvrdsi8DrQYMVVRYtnG+ezWFw784/R Yumf+SwOzB47Z91l91iy5CeTx6Wlk5kDmKMaGG2SEkvKgjPT8/TtbBLz8vJLEktSFVJSi5Nt lXxS0xNzFAKKMssSkysVXDKLk3MSM3NTi5QUMlNslUyUFApyEpNTc1PzSmyVEgsKUvNSlOy4 FDCADVBZZp5Cal5yfkpmXrqtkmewv66FhamlrqGSnW5CJ0/G5q1OBYt5Kk6cW8vewNjI1cXI ySEhYCKx4ts6RghbTOLCvfVsXYxcHEICKxkldvzbDuVsZpS4eG8BC0gVm4CWxP7D05lAbBEB S4mDOyaBdTMLhEgsfvGAHcQWFrCVuHz6DyNEjZ3E94OXWCBsJ4nNZ/6C1bAIqEpcO7SSFcTm FfCQuDl7GdhMToFAicunfjOD2IwCshK7z15ngpgvLnHryXwmiEsFJJbsOc8MYYtKvHz8jxXC VpR43NLNAlGvJ3Fj6hQ2CFtbYtnC18wQuwQlTs58wjKBUXQWkrGzkLTMQtIyC0nLAkaWVYyC uRnFBmYGyXnJekWZuXp5qSWbGEEpwlFDfwfj2/cWhxgFOBiVeHjN2V8HCrEmlhVX5h5ilOBg VhLhtXz2KlCINyWxsiq1KD++qDQntfgQoyswJCYyS3En5wPTV15JvLGBAW6Okjiv1dmzgUIC 6cDkk52aWpBaBDOHiYMTZA+XlEgxMIWkFiWWlmTEgxJdfDEw1Uk1MB6ImLLkcFR3qZdjrJj5 cpYd85aHTznYKcvybV/F8Ytrz5w9eJjhSn2hTnT5g7XOF1kyi/qvLQ/bkK+5+Peu9QXmC25l vg6IYtmrevrkl9k7Yg8cvJK0ybhM8+I5L+1bQbP3OWeaH/St/TRTVMWI9fEaxbOTnc+ensrA 83P69dmXo/ecVim70/RSiaU4I9FQi7moOBEASqkKUFIDAAA=
Cc: "tbray@textuality.com" <tbray@textuality.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Jul 2013 22:34:49 -0000

Martin

There are obviously always alternative design choices but why would you want=
 to include both a pre assigned device ID and a generated device ID in the s=
ame message?

Andrew

----- Original Message -----
From: Martin Thomson [mailto:martin.thomson@gmail.com]
Sent: Friday, July 19, 2013 11:25 AM Central Standard Time=0A=
To: Andrew Allen
Cc: tbray@textuality.com <tbray@textuality.com>; ietf@ietf.org <ietf@ietf.or=
g>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt

On 19 July 2013 08:38, Andrew Allen <aallen@blackberry.com> wrote:
>
> I suggest you also read
> http://datatracker.ietf.org/doc/draft-allen-dispatch-imei-urn-as-instancei=
d/

I read that document.  The placement of IMEI in the instance id is a
little bit of a non-sequitur to my thinking.

There are three cases identified where it might be necessary to convey
an IMEI, but no real motivation is provided for why it has to be
included, specifically, in the instance ID.  Nor is it the case that
all of these cases necessarily require that IMEI is conveyed in the
clear.  I can imagine solutions to the real problems that do not
require that an IMEI transit the network.

However, I'll concede that the relationship between a network provider
and the devices that use the network does not necessarily grant those
devices any right protections of the form in which Tim seems to be
assuming to be necessary.  The real risk here is with scope of use.

I'd have thought that a P- header would have been more appropriate for
these use cases.

---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential infor=
mation, privileged material (including material protected by the solicitor-c=
lient or other applicable privileges), or constitute non-public information.=
 Any use of this information by anyone other than the intended recipient is=
 prohibited. If you have received this transmission in error, please immedia=
tely reply to the sender and delete this information from your system. Use,=
 dissemination, distribution, or reproduction of this transmission by uninte=
nded recipients is not authorized and may be unlawful.

From prvs=0913097806=aallen@blackberry.com  Sat Jul 20 15:46:09 2013
Return-Path: <prvs=0913097806=aallen@blackberry.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F02F11E8131 for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 15:46:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level: 
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[AWL=0.349,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3kGauc4rQVPK for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 15:46:05 -0700 (PDT)
Received: from mhs060cnc.rim.net (mhs060cnc.rim.net [208.65.73.34]) by ietfa.amsl.com (Postfix) with ESMTP id B14F211E810D for <ietf@ietf.org>; Sat, 20 Jul 2013 15:45:53 -0700 (PDT)
X-AuditID: 0a41282f-b7f9b6d000002847-2b-51eb131a74b4
Received: from XCT104ADS.rim.net (xct104ads.rim.net [10.67.111.45]) by mhs060cnc.rim.net (SBG) with SMTP id D8.60.10311.A131BE15; Sat, 20 Jul 2013 17:45:46 -0500 (CDT)
Received: from XMB104ADS.rim.net ([fe80::2494:a63d:e3:723b]) by XCT104ADS.rim.net ([fe80::90f9:3b89:1d94:aa9b%22]) with mapi id 14.02.0328.009; Sat, 20 Jul 2013 17:45:45 -0500
From: Andrew Allen <aallen@blackberry.com>
To: "tbray@textuality.com" <tbray@textuality.com>, "scott.brim@gmail.com" <scott.brim@gmail.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
Thread-Topic: Last call: draft-montemurro-gsma-imei-urn-16.txt
Thread-Index: AQHOhJEO4fYTwuVTOkCw8MDTXs0bMZlsItsKgABZfICAAYRS+oAAYPKAgAADVID//8erAA==
Date: Sat, 20 Jul 2013 22:45:44 +0000
Message-ID: <BBF5DDFE515C3946BC18D733B20DAD2338DD23D4@XMB104ADS.rim.net>
In-Reply-To: <CAHBU6isF=37q3wbr7teq1Yx-s1hs+mwgzqSvVU7v=AW+nOW2zA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.67.110.252]
Content-Type: multipart/alternative; boundary="_000_BBF5DDFE515C3946BC18D733B20DAD2338DD23D4XMB104ADSrimnet_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrEKsWRmVeSWpSXmKPExsXC5Zyvqysl/DrQYN0KVYtnG+ezWLzbcZjN Yumf+SwOzB47Z91l91iy5CeTx6Wlk5kDmKMaGG2SEkvKgjPT8/TtbBLz8vJLEktSFVJSi5Nt lXxS0xNzFAKKMssSkysVXDKLk3MSM3NTi5QUMlNslUyUFApyEpNTc1PzSmyVEgsKUvNSlOy4 FDCADVBZZp5Cal5yfkpmXrqtkmewv66FhamlrqGSnW5CJ0/GhjXfGAtOuFXcet3D2MB4xqWL kZNDQsBEoqXjCzOELSZx4d56ti5GLg4hgZWMEufOvWeGcDYzSkz7+IEVpIpNQEti/+HpTCC2 iECSxPLXf8G6mQWUJZ5umgMWFxawlbh8+g8jRI2dxPeDl1i6GDmA7DCJZw9LQcIsAqoShx4s AQvzCnhI3PloCRLmFAiUODlrDdgmRqB7vp9awwQxXVzi1pP5TBB3Ckgs2XMe6mZRiZeP/7FC 2IoSj1u6WSDq8yU+r+sHq+cVEJQ4OfMJywRGkVlIRs1CUjYLSdksoIuYBTQl1u/ShyhRlJjS /ZAdwtaQaJ0zlx1ZfAEj+ypGwdyMYgMzg+S8ZL2izFy9vNSSTYygdOKoob+D8e17i0OMAhyM Sjy85uyvA4VYE8uKK3MPMUpwMCuJ8Fo+exUoxJuSWFmVWpQfX1Sak1p8iDEIGD4TmaW4k/OB qS6vJN7YwIBIjpI4r9XZs4FCAunAFJadmlqQWgQzlImDE2Qpl5RIMTARpRYllpZkxIPSZXwx MGFKNTAKB1lEyi4wFc8+v+hNbcgWGRGmsIKcgA0T7v5f//7uC1nx7/HTLn3UyeLvmbxk2SGb TIZnx2dNkeUWFFc+9PMCJ0s6F2/RzxUyvS9fejc3hV1kEpi05MpJK7O9U7asY74iLMuasEzn 2N13jYfVHUKnPpjk1anCtrPHYYZqvMBRk9XFFz6arvJWYinOSDTUYi4qTgQABtizZnUDAAA=
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Jul 2013 22:46:09 -0000

--_000_BBF5DDFE515C3946BC18D733B20DAD2338DD23D4XMB104ADSrimnet_
Content-Type: text/plain; charset="utf-8"
content-transfer-encoding: base64

VGltDQoNClRoaXMgaXMgbm90IHRoZSAibm9ybWFsIiAzR1BQIElNUyBzY2VuYXJpby4gSW4g
SU1TIHRoZSBkZXZpY2UgYXMgYSB3aG9sZSBpcyBjb25zaWRlcmVkIGFzIGEgc2luZ2xlIFVB
LCBtdWx0aXBsZSBJTVMgYXBwbGljYXRpb25zIHdpbGwgbmVlZCB0byBzaGFyZSBhIGNvbW1v
biByZWdpc3RyYXRpb24gcHJvY2VkdXJlIHRoYXQgaXMgcHJvdmlkZWQgYnkgdGhlIHVuZGVy
bHlpbmcgT1MuDQoNCk90aGVyd2lzZSBtdWx0aXBsZSBJTVMgcmVnaXN0cmF0aW9ucyBmcm9t
IGRpZmZlcmVudCBhcHBsaWNhdGlvbnMgb24gYSAzR1BQIHRlcm1pbmFsIHdpbGwgbGlrZWx5
IGNvbmZsaWN0IHdpdGggZWFjaCBvdGhlciBpZiB0aGV5IGRvIG5vdCBzaGFyZSBhIGNvbW1v
biByZWdpc3RyYXRpb24gbWVjaGFuaXNtIHRoYXQgcmVnaXN0ZXJzIGFsbCBJTVMgYXBwcyB1
c2luZyBhIGNvbW1vbiByZWdpc3RyYXRpb24gcHJvY2VkdXJlLiBJbiBJTVMsIGNvbnRhY3Rz
IGZyb20gdGhlIHNhbWUgZW50aXR5IGFyZSBvdmVyd3JpdHRlbiBieSBzdWJzZXF1ZW50IHJl
Z2lzdHJhdGlvbnMuIFdoaWNoIG1lYW5zIHRoYXQgaWYgZWFjaCBhcHAgd2VyZSB0byByZWdp
c3RlciBpbmRpdmlkdWFsbHkgdGhlbiBhbnkgY29udGFjdCBwYXJhbWV0ZXJzIHN1Y2ggYXMg
ZmVhdHVyZSB0YWdzIGZyb20gYSBwcmV2aW91cyByZWdpc3RlcmVkIGFwcCB3b3VsZCBiZSBv
dmVyd3JpdHRlbiBieSB0aGUgbGF0ZXN0IHJlZ2lzdGVyaW5nIGFwcC4NCg0KVGhlcmVmb3Jl
IHRoZSByZWdpc3RyYXRpb24gZnVuY3Rpb24gYW5kIHRoZSBpbnN0YW5jZSBJRCB3aWxsIGxp
a2VseSBiZSBwYXJ0IG9mIHRoZSBPUyBhbmQgbm90IHRoZSBhcHBsaWNhdGlvbi4NCg0KSW4g
YW55IGNhc2UgUkZDIDU2MjYgc2F5cyBub3RoaW5nIGFib3V0IHJlcXVpcmluZyBpbnN0YW5j
ZSBJRHMgdG8gYmUgd2lwZWQgb3IgcmVnZW5lcmF0ZWQgd2hlbiB0aGUgVUEgaXMgdHJhbnNm
ZXJyZWQgdG8gYW5vdGhlciB1c2VyIG9yIHRoYXQgdGhlIFVBIGNhbm5vdCBiZSBlbWJlZGRl
ZCBpbiBub24gdm9sYXRpdmUuIEl0IGRvZXNuJ3QgZXZlbiBiYXJyIHRoZSBpbnN0YW5jZSBJ
RCBiZWluZyBkZWxpdmVyZWQgdG8gb3RoZXIgdXNlcnMuDQpodHRwOi8vZGF0YXRyYWNrZXIu
aWV0Zi5vcmcvZG9jL2RyYWZ0LWFsbGVuLWRpc3BhdGNoLWltZWktdXJuLWFzLWluc3RhbmNl
aWQvIGdvZXMgYSBsb3QgZnVydGhlciB0aGFuIFJGQyA1NjI2IGluIGFkZHJlc3NpbmcgcHJp
dmFjeSBvZiB0aGUgaW5zdGFuY2UgSUQgaW4gdGhhdCByZWdhcmQuDQoNCkFuZHJldw0KDQpG
cm9tOiBUaW0gQnJheSBbbWFpbHRvOnRicmF5QHRleHR1YWxpdHkuY29tXQ0KU2VudDogU2F0
dXJkYXksIEp1bHkgMjAsIDIwMTMgMDQ6MDcgUE0gQ2VudHJhbCBTdGFuZGFyZCBUaW1lDQpU
bzogU2NvdHQgQnJpbSA8c2NvdHQuYnJpbUBnbWFpbC5jb20+DQpDYzogQW5kcmV3IEFsbGVu
OyBpZXRmQGlldGYub3JnIDxpZXRmQGlldGYub3JnPg0KU3ViamVjdDogUmU6IExhc3QgY2Fs
bDogZHJhZnQtbW9udGVtdXJyby1nc21hLWltZWktdXJuLTE2LnR4dA0KDQpFeGNlcHQgdGhh
dCBmb3Igbm9ybWFsIHVzYWdlcyBhdCB0aGUgYXBwbGljYXRpb24gbGV2ZWwsIHRoZSBVVUlE
IGlzIGdlbmVyYXRlZCBieSB0aGUgYXBwIGFuZCBwbGFjZWQgaW4gaXRzIHByaXZhdGUgcGVy
LWFwcCBzdG9yYWdlLCB3aGljaCBpcyBhbHdheXMgZXJhc2VkIG9uIGEgZmFjdG9yeS1yZXNl
dC4gIFRvIEFuZHJldyBBbGxlbjogSSBzdHJvbmdseSByZWNvbW1lbmQgZmFjdG9yeS1yZXNl
dHRpbmcgeW91ciBwaG9uZSBiZWZvcmUgeW91IHNlbGwgaXQsIGFuZCBhbHNvIGZhY3Rvcnkt
cmVzZXR0aW5nIGFueSBwaG9uZXMgeW91IGJ1eSBzZWNvbmQtaGFuZCwganVzdCB0byBiZSBz
dXJlLiAgTW9zdCBwZW9wbGUgZG8gdGhpcywgZm9yIGdvb2QgcmVhc29uLiAtVA0KDQoNCk9u
IFNhdCwgSnVsIDIwLCAyMDEzIGF0IDE6NTUgUE0sIFNjb3R0IEJyaW0gPHNjb3R0LmJyaW1A
Z21haWwuY29tPG1haWx0bzpzY290dC5icmltQGdtYWlsLmNvbT4+IHdyb3RlOg0KT24gU2F0
LCBKdWwgMjAsIDIwMTMgYXQgNDowOCBQTSwgQW5kcmV3IEFsbGVuIDxhYWxsZW5AYmxhY2ti
ZXJyeS5jb208bWFpbHRvOmFhbGxlbkBibGFja2JlcnJ5LmNvbT4+IHdyb3RlOg0KPiBUaW0N
Cj4NCj4gVGhlIHF1b3RlIGlzIGZyb20gUkZDIDU2MjYgd2hpY2ggYWxzbyBzdGF0ZXM6DQo+
DQo+ICIzLjEuIFN1bW1hcnkgb2YgTWVjaGFuaXNtDQo+DQo+IEVhY2ggVUEgaGFzIGEgdW5p
cXVlIGluc3RhbmNlLWlkIHRoYXQgc3RheXMgdGhlIHNhbWUgZm9yIHRoaXMgVUEgZXZlbiBp
ZiB0aGUNCj4gVUEgcmVib290cyBvciBpcyBwb3dlciBjeWNsZWQuIg0KPg0KPiBTaW5jZSB0
aGUgVVVJRCBpbiB0aGUgaW5zdGFuY2UgSUQgaXMgYWxzbyBzdGF0aWMgaG93IGlzIHRoaXMg
c2lnbmlmaWNhbnRseQ0KPiBkaWZmZXJlbnQgaW4gdGVybXMgb2YgcHJpdmFjeSBjb25jZXJu
cyBmcm9tIHRoZSBJTUVJIGJlaW5nIHVzZWQgYXMgYW4NCj4gaW5zdGFuY2UgSUQ/DQoNCllv
dSdyZSBub3QgZGVtb25zdHJhdGluZyB0aGF0IGFuIElNRUkgaXMganVzdCBhcyBnb29kLCB5
b3UncmUNCmRlbW9uc3RyYXRpbmcgdGhhdCBhIFVVSUQgaXMganVzdCBhcyBiYWQuDQoNCg0K
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tDQpUaGlzIHRyYW5zbWlzc2lvbiAoaW5jbHVkaW5nIGFueSBhdHRh
Y2htZW50cykgbWF5IGNvbnRhaW4gY29uZmlkZW50aWFsIGluZm9ybWF0aW9uLCBwcml2aWxl
Z2VkIG1hdGVyaWFsIChpbmNsdWRpbmcgbWF0ZXJpYWwgcHJvdGVjdGVkIGJ5IHRoZSBzb2xp
Y2l0b3ItY2xpZW50IG9yIG90aGVyIGFwcGxpY2FibGUgcHJpdmlsZWdlcyksIG9yIGNvbnN0
aXR1dGUgbm9uLXB1YmxpYyBpbmZvcm1hdGlvbi4gQW55IHVzZSBvZiB0aGlzIGluZm9ybWF0
aW9uIGJ5IGFueW9uZSBvdGhlciB0aGFuIHRoZSBpbnRlbmRlZCByZWNpcGllbnQgaXMgcHJv
aGliaXRlZC4gSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyB0cmFuc21pc3Npb24gaW4gZXJy
b3IsIHBsZWFzZSBpbW1lZGlhdGVseSByZXBseSB0byB0aGUgc2VuZGVyIGFuZCBkZWxldGUg
dGhpcyBpbmZvcm1hdGlvbiBmcm9tIHlvdXIgc3lzdGVtLiBVc2UsIGRpc3NlbWluYXRpb24s
IGRpc3RyaWJ1dGlvbiwgb3IgcmVwcm9kdWN0aW9uIG9mIHRoaXMgdHJhbnNtaXNzaW9uIGJ5
IHVuaW50ZW5kZWQgcmVjaXBpZW50cyBpcyBub3QgYXV0aG9yaXplZCBhbmQgbWF5IGJlIHVu
bGF3ZnVsLg0K

--_000_BBF5DDFE515C3946BC18D733B20DAD2338DD23D4XMB104ADSrimnet_
Content-Type: text/html; charset="utf-8"
content-transfer-encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5Pg0KPGZvbnQg
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPlRpbTxicj4NCjxicj4N
ClRoaXMgaXMgbm90IHRoZSAmcXVvdDtub3JtYWwmcXVvdDsgM0dQUCBJTVMgc2NlbmFyaW8u
IEluIElNUyB0aGUgZGV2aWNlIGFzIGEgd2hvbGUgaXMgY29uc2lkZXJlZCBhcyBhIHNpbmds
ZSBVQSwgbXVsdGlwbGUgSU1TIGFwcGxpY2F0aW9ucyB3aWxsIG5lZWQgdG8gc2hhcmUgYSBj
b21tb24gcmVnaXN0cmF0aW9uIHByb2NlZHVyZSB0aGF0IGlzIHByb3ZpZGVkIGJ5IHRoZSB1
bmRlcmx5aW5nIE9TLg0KPGJyPg0KPGJyPg0KT3RoZXJ3aXNlIG11bHRpcGxlIElNUyByZWdp
c3RyYXRpb25zIGZyb20gZGlmZmVyZW50IGFwcGxpY2F0aW9ucyBvbiBhIDNHUFAgdGVybWlu
YWwgd2lsbCBsaWtlbHkgY29uZmxpY3Qgd2l0aCBlYWNoIG90aGVyIGlmIHRoZXkgZG8gbm90
IHNoYXJlIGEgY29tbW9uIHJlZ2lzdHJhdGlvbiBtZWNoYW5pc20gdGhhdCByZWdpc3RlcnMg
YWxsIElNUyBhcHBzIHVzaW5nIGEgY29tbW9uIHJlZ2lzdHJhdGlvbiBwcm9jZWR1cmUuIElu
IElNUywgY29udGFjdHMNCiBmcm9tIHRoZSBzYW1lIGVudGl0eSBhcmUgb3ZlcndyaXR0ZW4g
Ynkgc3Vic2VxdWVudCByZWdpc3RyYXRpb25zLiBXaGljaCBtZWFucyB0aGF0IGlmIGVhY2gg
YXBwIHdlcmUgdG8gcmVnaXN0ZXIgaW5kaXZpZHVhbGx5IHRoZW4gYW55IGNvbnRhY3QgcGFy
YW1ldGVycyBzdWNoIGFzIGZlYXR1cmUgdGFncyBmcm9tIGEgcHJldmlvdXMgcmVnaXN0ZXJl
ZCBhcHAgd291bGQgYmUgb3ZlcndyaXR0ZW4gYnkgdGhlIGxhdGVzdCByZWdpc3RlcmluZyBh
cHAuPGJyPg0KPGJyPg0KVGhlcmVmb3JlIHRoZSByZWdpc3RyYXRpb24gZnVuY3Rpb24gYW5k
IHRoZSBpbnN0YW5jZSBJRCB3aWxsIGxpa2VseSBiZSBwYXJ0IG9mIHRoZSBPUyBhbmQgbm90
IHRoZSBhcHBsaWNhdGlvbi48YnI+DQo8YnI+DQpJbiBhbnkgY2FzZSBSRkMgNTYyNiBzYXlz
IG5vdGhpbmcgYWJvdXQgcmVxdWlyaW5nIGluc3RhbmNlIElEcyB0byBiZSB3aXBlZCBvciBy
ZWdlbmVyYXRlZCB3aGVuIHRoZSBVQSBpcyB0cmFuc2ZlcnJlZCB0byBhbm90aGVyIHVzZXIg
b3IgdGhhdCB0aGUgVUEgY2Fubm90IGJlIGVtYmVkZGVkIGluIG5vbiB2b2xhdGl2ZS4gSXQg
ZG9lc24ndCBldmVuIGJhcnIgdGhlIGluc3RhbmNlIElEIGJlaW5nIGRlbGl2ZXJlZCB0byBv
dGhlciB1c2Vycy4NCjxicj4NCmh0dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJh
ZnQtYWxsZW4tZGlzcGF0Y2gtaW1laS11cm4tYXMtaW5zdGFuY2VpZC8gZ29lcyBhIGxvdCBm
dXJ0aGVyIHRoYW4gUkZDIDU2MjYgaW4gYWRkcmVzc2luZyBwcml2YWN5IG9mIHRoZSBpbnN0
YW5jZSBJRCBpbiB0aGF0IHJlZ2FyZC4NCjxicj4NCjxicj4NCkFuZHJldzwvZm9udD48YnI+
DQombmJzcDs8YnI+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlk
ICNCNUM0REYgMS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbiI+DQo8Zm9udCBzdHls
ZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1
b3Q7c2Fucy1zZXJpZiZxdW90OyI+PGI+RnJvbTwvYj46IFRpbSBCcmF5IFttYWlsdG86dGJy
YXlAdGV4dHVhbGl0eS5jb21dDQo8YnI+DQo8Yj5TZW50PC9iPjogU2F0dXJkYXksIEp1bHkg
MjAsIDIwMTMgMDQ6MDcgUE0gQ2VudHJhbCBTdGFuZGFyZCBUaW1lPGJyPg0KPGI+VG88L2I+
OiBTY290dCBCcmltICZsdDtzY290dC5icmltQGdtYWlsLmNvbSZndDsgPGJyPg0KPGI+Q2M8
L2I+OiBBbmRyZXcgQWxsZW47IGlldGZAaWV0Zi5vcmcgJmx0O2lldGZAaWV0Zi5vcmcmZ3Q7
IDxicj4NCjxiPlN1YmplY3Q8L2I+OiBSZTogTGFzdCBjYWxsOiBkcmFmdC1tb250ZW11cnJv
LWdzbWEtaW1laS11cm4tMTYudHh0IDxicj4NCjwvZm9udD4mbmJzcDs8YnI+DQo8L2Rpdj4N
CjxkaXYgZGlyPSJsdHIiPkV4Y2VwdCB0aGF0IGZvciBub3JtYWwgdXNhZ2VzIGF0IHRoZSBh
cHBsaWNhdGlvbiBsZXZlbCwgdGhlIFVVSUQgaXMgZ2VuZXJhdGVkIGJ5IHRoZSBhcHAgYW5k
IHBsYWNlZCBpbiBpdHMgcHJpdmF0ZSBwZXItYXBwIHN0b3JhZ2UsIHdoaWNoIGlzIGFsd2F5
cyBlcmFzZWQgb24gYSBmYWN0b3J5LXJlc2V0LiZuYnNwOyBUbyBBbmRyZXcgQWxsZW46IEkg
c3Ryb25nbHkgcmVjb21tZW5kIGZhY3RvcnktcmVzZXR0aW5nIHlvdXIgcGhvbmUNCiBiZWZv
cmUgeW91IHNlbGwgaXQsIGFuZCBhbHNvIGZhY3RvcnktcmVzZXR0aW5nIGFueSBwaG9uZXMg
eW91IGJ1eSBzZWNvbmQtaGFuZCwganVzdCB0byBiZSBzdXJlLiZuYnNwOyBNb3N0IHBlb3Bs
ZSBkbyB0aGlzLCBmb3IgZ29vZCByZWFzb24uIC1UPGJyPg0KPC9kaXY+DQo8ZGl2IGNsYXNz
PSJnbWFpbF9leHRyYSI+PGJyPg0KPGJyPg0KPGRpdiBjbGFzcz0iZ21haWxfcXVvdGUiPk9u
IFNhdCwgSnVsIDIwLCAyMDEzIGF0IDE6NTUgUE0sIFNjb3R0IEJyaW0gPHNwYW4gZGlyPSJs
dHIiPg0KJmx0OzxhIGhyZWY9Im1haWx0bzpzY290dC5icmltQGdtYWlsLmNvbSIgdGFyZ2V0
PSJfYmxhbmsiPnNjb3R0LmJyaW1AZ21haWwuY29tPC9hPiZndDs8L3NwYW4+IHdyb3RlOjxi
cj4NCjxibG9ja3F1b3RlIGNsYXNzPSJnbWFpbF9xdW90ZSIgc3R5bGU9Im1hcmdpbjowIDAg
MCAuOGV4O2JvcmRlci1sZWZ0OjFweCAjY2NjIHNvbGlkO3BhZGRpbmctbGVmdDoxZXgiPg0K
PGRpdiBjbGFzcz0iaW0iPk9uIFNhdCwgSnVsIDIwLCAyMDEzIGF0IDQ6MDggUE0sIEFuZHJl
dyBBbGxlbiAmbHQ7PGEgaHJlZj0ibWFpbHRvOmFhbGxlbkBibGFja2JlcnJ5LmNvbSI+YWFs
bGVuQGJsYWNrYmVycnkuY29tPC9hPiZndDsgd3JvdGU6PGJyPg0KPC9kaXY+DQo8ZGl2IGNs
YXNzPSJpbSI+Jmd0OyBUaW08YnI+DQomZ3Q7PGJyPg0KJmd0OyBUaGUgcXVvdGUgaXMgZnJv
bSBSRkMgNTYyNiB3aGljaCBhbHNvIHN0YXRlczo8YnI+DQomZ3Q7PGJyPg0KJmd0OyAmcXVv
dDszLjEuIFN1bW1hcnkgb2YgTWVjaGFuaXNtPGJyPg0KJmd0Ozxicj4NCiZndDsgRWFjaCBV
QSBoYXMgYSB1bmlxdWUgaW5zdGFuY2UtaWQgdGhhdCBzdGF5cyB0aGUgc2FtZSBmb3IgdGhp
cyBVQSBldmVuIGlmIHRoZTxicj4NCiZndDsgVUEgcmVib290cyBvciBpcyBwb3dlciBjeWNs
ZWQuJnF1b3Q7PGJyPg0KJmd0Ozxicj4NCiZndDsgU2luY2UgdGhlIFVVSUQgaW4gdGhlIGlu
c3RhbmNlIElEIGlzIGFsc28gc3RhdGljIGhvdyBpcyB0aGlzIHNpZ25pZmljYW50bHk8YnI+
DQomZ3Q7IGRpZmZlcmVudCBpbiB0ZXJtcyBvZiBwcml2YWN5IGNvbmNlcm5zIGZyb20gdGhl
IElNRUkgYmVpbmcgdXNlZCBhcyBhbjxicj4NCiZndDsgaW5zdGFuY2UgSUQ/PGJyPg0KPGJy
Pg0KPC9kaXY+DQpZb3UncmUgbm90IGRlbW9uc3RyYXRpbmcgdGhhdCBhbiBJTUVJIGlzIGp1
c3QgYXMgZ29vZCwgeW91J3JlPGJyPg0KZGVtb25zdHJhdGluZyB0aGF0IGEgVVVJRCBpcyBq
dXN0IGFzIGJhZC48YnI+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjxicj4NCjwvZGl2Pg0K
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tIDxicj4NClRoaXMgdHJhbnNtaXNzaW9uIChpbmNsdWRpbmcgYW55
IGF0dGFjaG1lbnRzKSBtYXkgY29udGFpbiBjb25maWRlbnRpYWwgaW5mb3JtYXRpb24sIHBy
aXZpbGVnZWQgbWF0ZXJpYWwgKGluY2x1ZGluZyBtYXRlcmlhbCBwcm90ZWN0ZWQgYnkgdGhl
IHNvbGljaXRvci1jbGllbnQgb3Igb3RoZXIgYXBwbGljYWJsZSBwcml2aWxlZ2VzKSwgb3Ig
Y29uc3RpdHV0ZSBub24tcHVibGljIGluZm9ybWF0aW9uLiBBbnkgdXNlIG9mIHRoaXMgaW5m
b3JtYXRpb24gYnkgYW55b25lIG90aGVyIHRoYW4gdGhlIGludGVuZGVkIHJlY2lwaWVudCBp
cyBwcm9oaWJpdGVkLiBJZiB5b3UgaGF2ZSByZWNlaXZlZCB0aGlzIHRyYW5zbWlzc2lvbiBp
biBlcnJvciwgcGxlYXNlIGltbWVkaWF0ZWx5IHJlcGx5IHRvIHRoZSBzZW5kZXIgYW5kIGRl
bGV0ZSB0aGlzIGluZm9ybWF0aW9uIGZyb20geW91ciBzeXN0ZW0uIFVzZSwgZGlzc2VtaW5h
dGlvbiwgZGlzdHJpYnV0aW9uLCBvciByZXByb2R1Y3Rpb24gb2YgdGhpcyB0cmFuc21pc3Np
b24gYnkgdW5pbnRlbmRlZCByZWNpcGllbnRzIGlzIG5vdCBhdXRob3JpemVkIGFuZCBtYXkg
YmUgdW5sYXdmdWwuDQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_BBF5DDFE515C3946BC18D733B20DAD2338DD23D4XMB104ADSrimnet_--

From randy@psg.com  Sat Jul 20 15:48:39 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5BB011E812A for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 15:48:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.579
X-Spam-Level: 
X-Spam-Status: No, score=-2.579 tagged_above=-999 required=5 tests=[AWL=0.020,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ONtuvEb1lAU9 for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 15:48:39 -0700 (PDT)
Received: from ran.psg.com (unknown [IPv6:2001:418:8006::19]) by ietfa.amsl.com (Postfix) with ESMTP id 3D81311E810D for <ietf@ietf.org>; Sat, 20 Jul 2013 15:48:35 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1V0fx4-0001Ql-3G; Sat, 20 Jul 2013 22:48:34 +0000
Date: Sat, 20 Jul 2013 15:48:33 -0700
Message-ID: <m2d2qc3l1a.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Andrew Allen <aallen@blackberry.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
In-Reply-To: <BBF5DDFE515C3946BC18D733B20DAD2338DD2369@XMB104ADS.rim.net>
References: <CAHBU6ivmsWUzEa+vhhACdg_9e+=b2euZJoD9wj9Gvv3EbNiVdw@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD2338DD2369@XMB104ADS.rim.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: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Jul 2013 22:48:40 -0000

> I think IANA registration of namespaces has a lot of value.

let me ask the other side of the coin, in this case, what harm will be
done by not making this an rfc and registering the imei uri?

and i am not a fan of the mrs goldberg argument.

randy

From dougb@dougbarton.us  Sat Jul 20 15:54:01 2013
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F3D821F8411 for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 15:54:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.522
X-Spam-Level: 
X-Spam-Status: No, score=-2.522 tagged_above=-999 required=5 tests=[AWL=0.077,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F8O9rU1zjf0Z for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 15:53:56 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [208.79.90.218]) by ietfa.amsl.com (Postfix) with ESMTP id 20B9221F8749 for <ietf@ietf.org>; Sat, 20 Jul 2013 15:53:52 -0700 (PDT)
Received: from [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b] (unknown [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b]) by dougbarton.us (Postfix) with ESMTPSA id F194422B0C for <ietf@ietf.org>; Sat, 20 Jul 2013 22:53:44 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1374360825; bh=RRA8g1UqGTS8oU0ptWBBTSIj0qEbYOjCisI34V/yyLE=; h=Date:From:To:Subject:References:In-Reply-To; b=U319JlT3ND08FanGJ4ztI3u+7MwgFAl6p4jnh09NLcqun++ITwWHQ7HsCDPrhFaID 6xy8Y37VWxrV7ZkZj7OEkJBIZZMlIioTuMm8hGp/jKCuawzuf7EhncnPw25MKTEXFL EV02HL9PgqzGn4e41QbzpUyXBzaKFC4T4LpQLhLw=
Message-ID: <51EB14F8.3080100@dougbarton.us>
Date: Sat, 20 Jul 2013 15:53:44 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
References: <CAHBU6ivmsWUzEa+vhhACdg_9e+=b2euZJoD9wj9Gvv3EbNiVdw@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD2338DD2369@XMB104ADS.rim.net> <m2d2qc3l1a.wl%randy@psg.com>
In-Reply-To: <m2d2qc3l1a.wl%randy@psg.com>
X-Enigmail-Version: 1.5.2
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Jul 2013 22:54:01 -0000

On 07/20/2013 03:48 PM, Randy Bush wrote:
>> I think IANA registration of namespaces has a lot of value.
>
> let me ask the other side of the coin, in this case, what harm will be
> done by not making this an rfc and registering the imei uri?

None, because we lost the battle over protocol parameter poaching years 
ago. Doesn't mean I have to like it. :)

Doug


From prvs=3913449491=aallen@blackberry.com  Sat Jul 20 16:00:32 2013
Return-Path: <prvs=3913449491=aallen@blackberry.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3CF121E805D for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 16:00:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.583
X-Spam-Level: 
X-Spam-Status: No, score=-5.583 tagged_above=-999 required=5 tests=[AWL=-0.380, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PaZup-8jykWd for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 16:00:26 -0700 (PDT)
Received: from mhs060cnc.rim.net (mhs060cnc.rim.net [208.65.73.34]) by ietfa.amsl.com (Postfix) with ESMTP id B28C411E80F4 for <ietf@ietf.org>; Sat, 20 Jul 2013 16:00:26 -0700 (PDT)
X-AuditID: 0a41282f-b7f9b6d000002847-80-51eb168105a9
Received: from XCT105ADS.rim.net (xct105ads.rim.net [10.67.111.46]) by mhs060cnc.rim.net (SBG) with SMTP id B4.70.10311.1861BE15; Sat, 20 Jul 2013 18:00:17 -0500 (CDT)
Received: from XMB104ADS.rim.net ([fe80::2494:a63d:e3:723b]) by XCT105ADS.rim.net ([fe80::2d01:2041:eea3:819b%22]) with mapi id 14.02.0328.009; Sat, 20 Jul 2013 18:00:17 -0500
From: Andrew Allen <aallen@blackberry.com>
To: "randy@psg.com" <randy@psg.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
Thread-Topic: Last call: draft-montemurro-gsma-imei-urn-16.txt
Thread-Index: AQHOhJEO4fYTwuVTOkCw8MDTXs0bMZlsOFEcgAGJd4CAACLcBIAAViUA///RAKSAAHVsgP//r3Ne
Date: Sat, 20 Jul 2013 23:00:15 +0000
Message-ID: <BBF5DDFE515C3946BC18D733B20DAD2338DD2452@XMB104ADS.rim.net>
In-Reply-To: <m2d2qc3l1a.wl%randy@psg.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.67.110.252]
Content-Type: text/plain; charset="iso-8859-1"
content-transfer-encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrKKsWRmVeSWpSXmKPExsXC5Zyvp9so9jrQYO8MPYtnG+ezWDxrfcnk wOSxZMlPJo+pM2czBjBFNTDaJCWWlAVnpufp29kk5uXllySWpCqkpBYn2yr5pKYn5igEFGWW JSZXKrhkFifnJGbmphYpKWSm2CqZKCkU5CQmp+am5pXYKiUWFKTmpSjZcSlgABugssw8hdS8 5PyUzLx0WyXPYH9dCwtTS11DJTvdhE6ejNbtzUwFuzkq/k1awNbAeJuti5GDQ0LARGLjPa4u Rk4gU0ziwr31QGEuDiGBlYwS3zduYoJwNjNKXH94hhmkik1AS2L/4elMILaIgLLE0wm3wWxm EHvTHDBbWMBW4vLpP4wQNXYS3w9eYoGwoyT23VwLVsMioCqx5cEjsJm8Ah4SB25uZQexOYHm X7/RD1bDCHTR91NroOaLS9x6Mp8J4lIBiSV7zjND2KISLx//Y4WwFSUet3SzQNTrSdyYOoUN wtaWWLbwNdQuQYmTM5+wTGAUnYVk7CwkLbOQtMxC0rKAkWUVo2BuRrGBmUFyXrJeUWauXl5q ySZGUDpw1NDfwfj2vcUhRgEORiUeXnP214FCrIllxZW5hxglOJiVRHgtn70KFOJNSaysSi3K jy8qzUktPsToCgyJicxS3Mn5wFSVVxJvbGCAm6Mkzmt19mygkEA6MPlkp6YWpBbBzGHi4ATZ wyUlUgxMIalFiaUlGfGgRBdfDEx1Ug2Msl+EXr6K1jy/4M0uAaF0sUqVCiGVHwrxvFcNjwv6 3T8lvj4qgWNhUX4O351jUrYNs/iCuH8+v+4sXr2KUeRC+pbFir2s39/PivyWMGP3LaGgL6oV e55KZb0JvHd+asbs+9MuTT2dtPbTnymf955Q1LSONbNlf/vlVt0RA9FYlj/WvmzaZj/6lViK MxINtZiLihMBpnq+AkgDAAA=
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Jul 2013 23:00:32 -0000

Randy

Are you suggesting its not a problem if everyone were to just go off and def=
ine namespaces and not have them registered with IANA?

I don't think that's a good precedence.

The GSMA is the authoritative organisation for some identifers that have bee=
n used in billions of mobile devices for 20 years. Why should IETF deny them=
 a namespace and a listing in the  IANA registry for such identifers?

If there are concerns with the usage of these identifiers those concerns sho=
uld be addressed in  the drafts that define the usage.

Andrew


----- Original Message -----
From: Randy Bush [mailto:randy@psg.com]
Sent: Saturday, July 20, 2013 05:48 PM Central Standard Time=0A=
To: Andrew Allen
Cc: IETF Disgust <ietf@ietf.org>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt

> I think IANA registration of namespaces has a lot of value.

let me ask the other side of the coin, in this case, what harm will be
done by not making this an rfc and registering the imei uri?

and i am not a fan of the mrs goldberg argument.

randy

---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential infor=
mation, privileged material (including material protected by the solicitor-c=
lient or other applicable privileges), or constitute non-public information.=
 Any use of this information by anyone other than the intended recipient is=
 prohibited. If you have received this transmission in error, please immedia=
tely reply to the sender and delete this information from your system. Use,=
 dissemination, distribution, or reproduction of this transmission by uninte=
nded recipients is not authorized and may be unlawful.

From john-ietf@jck.com  Sat Jul 20 16:27:42 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4534711E810D for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 16:27:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.628
X-Spam-Level: 
X-Spam-Status: No, score=-102.628 tagged_above=-999 required=5 tests=[AWL=-0.029, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NDxWEOIOtxjb for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 16:27:36 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 5401E21F9C25 for <ietf@ietf.org>; Sat, 20 Jul 2013 16:27:36 -0700 (PDT)
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 1V0gYo-000O3T-Ll; Sat, 20 Jul 2013 19:27:34 -0400
Date: Sat, 20 Jul 2013 19:27:29 -0400
From: John C Klensin <john-ietf@jck.com>
To: Doug Barton <dougb@dougbarton.us>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
Message-ID: <317374B2C2143EF222ADBC47@JcK-HP8200.jck.com>
In-Reply-To: <51EB0D0D.8040008@dougbarton.us>
References: <BBF5DDFE515C3946BC18D733B20DAD2338DD2369@XMB104ADS.rim.net> <51EB0D0D.8040008@dougbarton.us>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Jul 2013 23:27:42 -0000

--On Saturday, July 20, 2013 15:19 -0700 Doug Barton
<dougb@dougbarton.us> wrote:

> On 07/20/2013 01:48 PM, Andrew Allen wrote:
>> I think IANA registration of namespaces has a lot of value.
> 
> I think backfilling registrations for poached identifiers sets
> a bad/dangerous example.

Doug,

This is another of those arguments that I wish we could avoid
repeating for each individual document.

One of our oldest precedents and principles is that it is better
to have things registered than not, even when they are ugly.
Having such registrations gives us a fighting chance of avoiding
the interoperability problems associated with two different
parties accidentally using the same name for different purposes.
It also provides a centralized mechanism for mapping identifiers
onto documentation.  That is both a good thing in itself and, in
some cases, provides a place to include warnings about improper
uses, nasty side-effects, and security and/or privacy problems.

The Internet is not an operating system (or even the PSTN) in
which the arbiters of taste can keep something from being
incorporated in a release or used. If someone is determined to
use a particular capability under a particular name, we can try
to talk them out of it but, if they are still determined, the
only question is whether we are better off with registration and
documentation than without them.   And, generally, we are better
off with the first.

Discussions about poaching, squatting, and even stupidity or bad
taste are interesting but not generally helpful.

    john



From sm@elandsys.com  Sat Jul 20 16:57:19 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DAB4A21E805A for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 16:57:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.616
X-Spam-Level: 
X-Spam-Status: No, score=-102.616 tagged_above=-999 required=5 tests=[AWL=-0.017, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 59930+qvdq-P for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 16:57:09 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id A749821E8088 for <ietf@ietf.org>; Sat, 20 Jul 2013 16:57:09 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.151.133]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r6KNujaJ007241 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 20 Jul 2013 16:56:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1374364620; bh=+N9a5EP4q6rGbGMYeWAiI+0Lf/vH9Fkr0/n7FXzOShQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=AK/qjhJaSNb8L2COlgBj1w5OWDfaWSjOr/rVvGJkQ7bVQZsd2AOxfqRQawBVkKNPb 7zTcCQTtePLymKrwJPE/X+il1GMD4HHK5LDLauU+yB2pCZNb5JqY5c29idk0qA9EHB 1YUg3RJeqPGBaSGbeKt/D4iep//15AgWzcVFiAKc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1374364620; i=@elandsys.com; bh=+N9a5EP4q6rGbGMYeWAiI+0Lf/vH9Fkr0/n7FXzOShQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=ZjJm2penOphoGa5U0DdV2Ktf0zIx5LrGrtQ0P77eRO/any9I9F6v1ip/46tHdy4un uN7niY/GyaQrMnHkaxZ8ArkXvEVV67XbYnwy3DvvcuYNBIG31uxsxwIv3hdxel4yNj CwkSl2IALe/jeNQ74apU8Oq6owV3C85ljojGRQ6M=
Message-Id: <6.2.5.6.2.20130720155920.06cc9ce0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 20 Jul 2013 16:50:20 -0700
To: Andrew Allen <aallen@blackberry.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
In-Reply-To: <BBF5DDFE515C3946BC18D733B20DAD2338DD2369@XMB104ADS.rim.net >
References: <CAHBU6ivmsWUzEa+vhhACdg_9e+=b2euZJoD9wj9Gvv3EbNiVdw@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD2338DD2369@XMB104ADS.rim.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: tbray@textuality.com, draft-montemurro-gsma-imei-urn.all@tools.ietf.org, sm+ietf@elandsys.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Jul 2013 23:57:20 -0000

Hi Andrew,
At 13:48 20-07-2013, Andrew Allen wrote:
>I think IANA registration of namespaces has a lot of value.

draft-montemurro-gsma-imei-urn-16 discusses about two namespaces:

  (i)  gsma

  (ii) imei

It is not possible to get a IANA registration for (ii) as according 
to draft-montemurro-gsma-imei-urn-16 (ii) is managed by (i).  In 
simple terms (ii) does not require IETF approval.

Regards,
S. Moonesamy 


From tbray@textuality.com  Sat Jul 20 17:02:05 2013
Return-Path: <tbray@textuality.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 535EE21E8088 for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 17:02:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.809
X-Spam-Level: 
X-Spam-Status: No, score=-2.809 tagged_above=-999 required=5 tests=[AWL=0.167,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O+2F+yQhWeQZ for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 17:02:00 -0700 (PDT)
Received: from mail-ve0-f172.google.com (mail-ve0-f172.google.com [209.85.128.172]) by ietfa.amsl.com (Postfix) with ESMTP id 64F1B21E805A for <ietf@ietf.org>; Sat, 20 Jul 2013 17:02:00 -0700 (PDT)
Received: by mail-ve0-f172.google.com with SMTP id jz10so4283950veb.17 for <ietf@ietf.org>; Sat, 20 Jul 2013 17:01:58 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=6UUrKgqKwy64FNfFIPLU9F1txC7mSdeQabF08CeL29M=; b=AS7E/ucCNM7nn71IDXE7dpLENd6dJ+X3nIsPrcW6vvtY/LpWn31IrzbYcuuIEDPNyg HQixjL9KZv74zPA+0BtycsoN3Uhzfu7wN7OvQpd1HvC7yurhyorw5QsURwgXu5v13A0W BrFbAhQtz4IUXJLnwjuKogtkZl1f7sKk5VTNsDMTgEeslrGhcx3jlZLE6H7mCrGwTmJj OzaQt8ttWlvxhDufUlJDrljOYBk8oOnSBDK9Gs1lnpv5FauM1ipE83Rtn6C8BlfBwlx7 b4a7ycn7OTLmwrxh18gy6Ddut7JqQxrotKJ3taPxCsM4BAuf9b58MAxPuvnzy2U5kCS9 1Wuw==
MIME-Version: 1.0
X-Received: by 10.52.94.6 with SMTP id cy6mr6282228vdb.108.1374364918738; Sat, 20 Jul 2013 17:01:58 -0700 (PDT)
Received: by 10.220.219.200 with HTTP; Sat, 20 Jul 2013 17:01:58 -0700 (PDT)
X-Originating-IP: [24.84.235.32]
In-Reply-To: <BBF5DDFE515C3946BC18D733B20DAD2338DD23A8@XMB104ADS.rim.net>
References: <CAPv4CP_g-FtAowBvP6CS2t4OB3j6usHSV2sTAc=tmTpESc2dHw@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD2338DD23A8@XMB104ADS.rim.net>
Date: Sat, 20 Jul 2013 17:01:58 -0700
Message-ID: <CAHBU6iuSK9nFKakvbPR0-BEUghuhgDg4G1T9qzDr=EAyh-N-Uw@mail.gmail.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
From: Tim Bray <tbray@textuality.com>
To: Andrew Allen <aallen@blackberry.com>
Content-Type: multipart/alternative; boundary=20cf307abe9fc6051204e1fa4413
X-Gm-Message-State: ALoCoQmKgCHjUr6RMhsD3OscnUbQX7XntQwZ0CBkmCukOT4uUhrJXmT2tkgu9/YkQtxzpxT35srl
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Jul 2013 00:02:05 -0000

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

On Sat, Jul 20, 2013 at 3:20 PM, Andrew Allen <aallen@blackberry.com> wrote=
:

> Can it please be explained how the IMEI URN when used as stated in
> http://datatracker.ietf.org/doc/draft-allen-dispatch-imei-urn-as-instance=
id/
> Is any more harmful than as the IMEI is used today by over 90% of mobile
> phones in use today worldwide?
>

It survives device wipes, which usually happen upon change of device
ownership.

I=E2=80=99m not an expert in your application domain, so pardon me if this =
question
is hopelessly naive: It seems that this identifier is related in some way
to SIP sessions.  It seems that it would be a common operation to launch a
SIP session on a device such as a WiFi-only tablet, or an iPod touch, that
doesn=E2=80=99t have an IMEI.  Is this a problem?

 -T


>
> Andrew
>
> ----- Original Message -----
> From: Scott Brim [mailto:scott.brim@gmail.com]
> Sent: Saturday, July 20, 2013 03:55 PM Central Standard Time
> To: Andrew Allen
> Cc: tbray@textuality.com <tbray@textuality.com>; ietf@ietf.org <
> ietf@ietf.org>
> Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
>
> On Sat, Jul 20, 2013 at 4:08 PM, Andrew Allen <aallen@blackberry.com>
> wrote:
> > Tim
> >
> > The quote is from RFC 5626 which also states:
> >
> > "3.1. Summary of Mechanism
> >
> > Each UA has a unique instance-id that stays the same for this UA even i=
f
> the
> > UA reboots or is power cycled."
> >
> > Since the UUID in the instance ID is also static how is this
> significantly
> > different in terms of privacy concerns from the IMEI being used as an
> > instance ID?
>
> You're not demonstrating that an IMEI is just as good, you're
> demonstrating that a UUID is just as bad.
>
> ---------------------------------------------------------------------
> This transmission (including any attachments) may contain confidential
> information, privileged material (including material protected by the
> solicitor-client or other applicable privileges), or constitute non-publi=
c
> information. Any use of this information by anyone other than the intende=
d
> recipient is prohibited. If you have received this transmission in error,
> please immediately reply to the sender and delete this information from
> your system. Use, dissemination, distribution, or reproduction of this
> transmission by unintended recipients is not authorized and may be unlawf=
ul.
>

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

<div dir=3D"ltr">On Sat, Jul 20, 2013 at 3:20 PM, Andrew Allen <span dir=3D=
"ltr">&lt;<a href=3D"mailto:aallen@blackberry.com" target=3D"_blank">aallen=
@blackberry.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div cl=
ass=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Can it please be explained how the IMEI URN =
when used as stated in <a href=3D"http://datatracker.ietf.org/doc/draft-all=
en-dispatch-imei-urn-as-instanceid/" target=3D"_blank">http://datatracker.i=
etf.org/doc/draft-allen-dispatch-imei-urn-as-instanceid/</a><br>

Is any more harmful than as the IMEI is used today by over 90% of mobile ph=
ones in use today worldwide?<br></blockquote><div><br></div><div>It survive=
s device wipes, which usually happen upon change of device ownership.=C2=A0=
 <br>
<br>I=E2=80=99m not an expert in your application domain, so pardon me if t=
his question is hopelessly naive: It seems that this identifier is related =
in some way to SIP sessions.=C2=A0 It seems that it would be a common opera=
tion to launch a SIP session on a device such as a WiFi-only tablet, or an =
iPod touch, that doesn=E2=80=99t have an IMEI.=C2=A0 Is this a problem?<br>
<br></div><div>=C2=A0-T<br></div><div>=C2=A0</div><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex">
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Andrew<br>
</font></span><div class=3D"im HOEnZb"><br>
----- Original Message -----<br>
From: Scott Brim [mailto:<a href=3D"mailto:scott.brim@gmail.com">scott.brim=
@gmail.com</a>]<br>
</div><div class=3D"im HOEnZb">Sent: Saturday, July 20, 2013 03:55 PM Centr=
al Standard Time<br>
To: Andrew Allen<br>
</div><div class=3D"im HOEnZb">Cc: <a href=3D"mailto:tbray@textuality.com">=
tbray@textuality.com</a> &lt;<a href=3D"mailto:tbray@textuality.com">tbray@=
textuality.com</a>&gt;; <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a> =
&lt;<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&gt;<br>

Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt<br>
<br>
</div><div class=3D"HOEnZb"><div class=3D"h5">On Sat, Jul 20, 2013 at 4:08 =
PM, Andrew Allen &lt;<a href=3D"mailto:aallen@blackberry.com">aallen@blackb=
erry.com</a>&gt; wrote:<br>
&gt; Tim<br>
&gt;<br>
&gt; The quote is from RFC 5626 which also states:<br>
&gt;<br>
&gt; &quot;3.1. Summary of Mechanism<br>
&gt;<br>
&gt; Each UA has a unique instance-id that stays the same for this UA even =
if the<br>
&gt; UA reboots or is power cycled.&quot;<br>
&gt;<br>
&gt; Since the UUID in the instance ID is also static how is this significa=
ntly<br>
&gt; different in terms of privacy concerns from the IMEI being used as an<=
br>
&gt; instance ID?<br>
<br>
You&#39;re not demonstrating that an IMEI is just as good, you&#39;re<br>
demonstrating that a UUID is just as bad.<br>
<br>
</div></div><div class=3D"HOEnZb"><div class=3D"h5">-----------------------=
----------------------------------------------<br>
This transmission (including any attachments) may contain confidential info=
rmation, privileged material (including material protected by the solicitor=
-client or other applicable privileges), or constitute non-public informati=
on. Any use of this information by anyone other than the intended recipient=
 is prohibited. If you have received this transmission in error, please imm=
ediately reply to the sender and delete this information from your system. =
Use, dissemination, distribution, or reproduction of this transmission by u=
nintended recipients is not authorized and may be unlawful.<br>

</div></div></blockquote></div><br></div></div>

--20cf307abe9fc6051204e1fa4413--

From john@jck.com  Sat Jul 20 18:24:09 2013
Return-Path: <john@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B108521F84AF for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 18:24:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P+kstP8a2KT6 for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 18:24:03 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id D520721F84A1 for <ietf@ietf.org>; Sat, 20 Jul 2013 18:24:03 -0700 (PDT)
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 1V0iNV-000OAQ-PA; Sat, 20 Jul 2013 21:24:01 -0400
Date: Sat, 20 Jul 2013 21:23:56 -0400
From: John C Klensin <john@jck.com>
To: Tim Bray <tbray@textuality.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
Message-ID: <E3FFA1821F56A7BE7F895293@JcK-HP8200.jck.com>
In-Reply-To: <CAHBU6ivmsWUzEa+vhhACdg_9e+=b2euZJoD9wj9Gvv3EbNiVdw@mail.gmail.com>
References: <CAPv4CP8KzNeYfavm6pW0gF_XZK3ZbJuj983WqS5f+MQpJwO9yg@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD2338DD2318@XMB104ADS.rim.net> <CAHBU6ivmsWUzEa+vhhACdg_9e+=b2euZJoD9wj9Gvv3EbNiVdw@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@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Jul 2013 01:24:10 -0000

--On Saturday, July 20, 2013 11:36 -0700 Tim Bray
<tbray@textuality.com> wrote:

> So if it's going to be used, exactly as specified, whatever
> we do, then what value is added by the IETF process?  -T

See my earlier note, but mostly to aid in getting the
documentation right.  For example, to the extent that the recent
discussion results in a more complete treatment of privacy
and/or security considerations in the documentation, that is a
net improvement and added value.

  john




From tbray@textuality.com  Sat Jul 20 19:17:51 2013
Return-Path: <tbray@textuality.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE65021F9E6A for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 19:17:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.662
X-Spam-Level: 
X-Spam-Status: No, score=-2.662 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yKF+B7eP2O7n for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 19:17:42 -0700 (PDT)
Received: from mail-lb0-f179.google.com (mail-lb0-f179.google.com [209.85.217.179]) by ietfa.amsl.com (Postfix) with ESMTP id 881FD21F9A16 for <ietf@ietf.org>; Sat, 20 Jul 2013 19:17:41 -0700 (PDT)
Received: by mail-lb0-f179.google.com with SMTP id w20so4347001lbh.38 for <ietf@ietf.org>; Sat, 20 Jul 2013 19:17:40 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=z4z++AlPL/SSNCNGPcPvc/fA7bWwS/sOj613l7cGsg4=; b=NyJ+Tnr1HEZGuP1BUKycd2k4s0uSPo7FYTZ+R8cjlLGU+VJrLATzv8kOE06BVOpKZl 9L29E6f1HQzZT3dzB5PI5nykBaBeG3vucJBvDbkWNK2U8vjkr1r/WRln5HMV7qlqkTAs CLCzKMDf1P7MetuSZCnWJ3hkxq8buF18obh2sSLpjNMZrjPacRhU/+wLmRgUbAKPW+s+ pFN5xbPQUnHGXedPUyJbAAlH0fQzvJpyJ95+ggGiUu6kEKpRWqx2UFeXaQVqgiBNkuFv xXtkAWqJvwXePUy3qFf9sGwM/u9HxvtwPlzVr1MLQClKPKOG5R45sVAgXmBQcdeuS016 H2nA==
MIME-Version: 1.0
X-Received: by 10.152.8.103 with SMTP id q7mr10086272laa.64.1374373060386; Sat, 20 Jul 2013 19:17:40 -0700 (PDT)
Received: by 10.114.21.132 with HTTP; Sat, 20 Jul 2013 19:17:40 -0700 (PDT)
X-Originating-IP: [24.84.235.32]
In-Reply-To: <E3FFA1821F56A7BE7F895293@JcK-HP8200.jck.com>
References: <CAPv4CP8KzNeYfavm6pW0gF_XZK3ZbJuj983WqS5f+MQpJwO9yg@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD2338DD2318@XMB104ADS.rim.net> <CAHBU6ivmsWUzEa+vhhACdg_9e+=b2euZJoD9wj9Gvv3EbNiVdw@mail.gmail.com> <E3FFA1821F56A7BE7F895293@JcK-HP8200.jck.com>
Date: Sat, 20 Jul 2013 19:17:40 -0700
Message-ID: <CAHBU6is0H5TG9Te1-9To_ea5PLUYvConPQhmURBMET4Mu0PksQ@mail.gmail.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
From: Tim Bray <tbray@textuality.com>
To: John C Klensin <john@jck.com>
Content-Type: multipart/alternative; boundary=001a11c366820dafbc04e1fc2af5
X-Gm-Message-State: ALoCoQkomN+nXr1Gwfxz+79ucnJpX/3NABzgRzA4H4vZxkXTxAflqF+pGt1u8fo9vHJyMV8cUkFj
Cc: IETF-Discussion Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Jul 2013 02:17:52 -0000

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

Fair enough.  I think it would be reasonable to ask that:

- the draft include the word =E2=80=9Cprivacy=E2=80=9D
- the draft discuss the issues around relying on an identifier that
persists across changes in device ownership

There may be an issue concerning a SIP-related identifier which is
unavailable on millions of mobile devices which do not have IMEIs, but it=
=E2=80=99s
quite possible that it=E2=80=99s non-applicable in the context of the draft=
.  -T


On Sat, Jul 20, 2013 at 6:23 PM, John C Klensin <john@jck.com> wrote:

>
>
> --On Saturday, July 20, 2013 11:36 -0700 Tim Bray
> <tbray@textuality.com> wrote:
>
> > So if it's going to be used, exactly as specified, whatever
> > we do, then what value is added by the IETF process?  -T
>
> See my earlier note, but mostly to aid in getting the
> documentation right.  For example, to the extent that the recent
> discussion results in a more complete treatment of privacy
> and/or security considerations in the documentation, that is a
> net improvement and added value.
>
>   john
>
>
>
>

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

<div dir=3D"ltr"><div><div><div>Fair enough.=C2=A0 I think it would be reas=
onable to ask that:<br><br></div>- the draft include the word =E2=80=9Cpriv=
acy=E2=80=9D<br></div>- the draft discuss the issues around relying on an i=
dentifier that persists across changes in device ownership<br>
<br></div>There may be an issue concerning a SIP-related identifier which i=
s unavailable on millions of mobile devices which do not have IMEIs, but it=
=E2=80=99s quite possible that it=E2=80=99s non-applicable in the context o=
f the draft.=C2=A0 -T<br>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Sat,=
 Jul 20, 2013 at 6:23 PM, John C Klensin <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:john@jck.com" target=3D"_blank">john@jck.com</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">
<br>
<br>
--On Saturday, July 20, 2013 11:36 -0700 Tim Bray<br>
<div class=3D"im">&lt;<a href=3D"mailto:tbray@textuality.com">tbray@textual=
ity.com</a>&gt; wrote:<br>
<br>
&gt; So if it&#39;s going to be used, exactly as specified, whatever<br>
&gt; we do, then what value is added by the IETF process? =C2=A0-T<br>
<br>
</div>See my earlier note, but mostly to aid in getting the<br>
documentation right. =C2=A0For example, to the extent that the recent<br>
discussion results in a more complete treatment of privacy<br>
and/or security considerations in the documentation, that is a<br>
net improvement and added value.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
=C2=A0 john<br>
<br>
<br>
<br>
</font></span></blockquote></div><br></div>

--001a11c366820dafbc04e1fc2af5--

From john-ietf@jck.com  Sat Jul 20 19:44:33 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3826021F999B for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 19:44:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.47
X-Spam-Level: 
X-Spam-Status: No, score=-102.47 tagged_above=-999 required=5 tests=[AWL=-0.185, BAYES_00=-2.599, SARE_MILLIONSOF=0.315, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mv2alKsqce-3 for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 19:44:27 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 6B76221F9F13 for <ietf@ietf.org>; Sat, 20 Jul 2013 19:44:27 -0700 (PDT)
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 1V0jdH-000OEw-O3; Sat, 20 Jul 2013 22:44:23 -0400
Date: Sat, 20 Jul 2013 22:44:18 -0400
From: John C Klensin <john-ietf@jck.com>
To: Tim Bray <tbray@textuality.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
Message-ID: <0230573D31DB808B0685E3CE@JcK-HP8200.jck.com>
In-Reply-To: <CAHBU6is0H5TG9Te1-9To_ea5PLUYvConPQhmURBMET4Mu0PksQ@mail.gmail.com>
References: <CAPv4CP8KzNeYfavm6pW0gF_XZK3ZbJuj983WqS5f+MQpJwO9yg@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD2338DD2318@XMB104ADS.rim.net> <CAHBU6ivmsWUzEa+vhhACdg_9e+=b2euZJoD9wj9Gvv3EbNiVdw@mail.gmail.com> <E3FFA1821F56A7BE7F895293@JcK-HP8200.jck.com> <CAHBU6is0H5TG9Te1-9To_ea5PLUYvConPQhmURBMET4Mu0PksQ@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 Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Jul 2013 02:44:33 -0000

--On Saturday, July 20, 2013 19:17 -0700 Tim Bray
<tbray@textuality.com> wrote:

> Fair enough.  I think it would be reasonable to ask that:
> 
> - the draft include the word "privacy"
> - the draft discuss the issues around relying on an identifier
> that persists across changes in device ownership
> 
> There may be an issue concerning a SIP-related identifier
> which is unavailable on millions of mobile devices which do
> not have IMEIs, but it's quite possible that it's
> non-applicable in the context of the draft.  -T

Personally, I'd consider getting all three of those issues
addressed in the document (including a discussion of the
applicability of the latter and a serious discussion of the
privacy issues) as adding value... and as requirements for RFC
publication in the IETF Stream.

   john


From sm@elandsys.com  Sat Jul 20 20:49:28 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 827DB11E8139 for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 20:49:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.616
X-Spam-Level: 
X-Spam-Status: No, score=-102.616 tagged_above=-999 required=5 tests=[AWL=-0.017, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LFclYxZ3g0tC for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 20:49:27 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 832B011E80F7 for <ietf@ietf.org>; Sat, 20 Jul 2013 20:49:22 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.151.133]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r6L3n6VC022084 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 20 Jul 2013 20:49:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1374378558; bh=VNdyRSJdHHmbCDXHiupTmriA/k5XhbfKWraj6mMxhYA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=HuQ1ZOoLTmdTaUGVIKq4WhdpJHJxYzynuTQ12Gtfs5dcCuvzt24w1o9yt+r5sG9SA KY2gO2rGa+i++9qpr5iZGkPNlFmuGXZ/d3uXsQlL1OOJEinXE+5cw9nYlXUWYhzPHQ Rpc1R2BHUIM4CJ2ofTZIcOEgZIpCp+3+M9RWH9/E=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1374378558; i=@elandsys.com; bh=VNdyRSJdHHmbCDXHiupTmriA/k5XhbfKWraj6mMxhYA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=ReBw6V/eTi2uSWdt/z7hqEHzsX4V2et+wOGTc9S7oMUGoFPWrKeCWY7Hk+aJGN0jn 3+DbIaOdLhIv/VWybb9d5KUkVyD2KksV0AEO/sNmaDmhPEUexk24vmCN4qBpEOvvWT redCBmxrex/crvUkqTzcWwjibPhoDV5zfIufOzqk=
Message-Id: <6.2.5.6.2.20130720193906.06cdd008@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 20 Jul 2013 20:48:02 -0700
To: John C Klensin <john@jck.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
In-Reply-To: <E3FFA1821F56A7BE7F895293@JcK-HP8200.jck.com>
References: <CAPv4CP8KzNeYfavm6pW0gF_XZK3ZbJuj983WqS5f+MQpJwO9yg@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD2338DD2318@XMB104ADS.rim.net> <CAHBU6ivmsWUzEa+vhhACdg_9e+=b2euZJoD9wj9Gvv3EbNiVdw@mail.gmail.com> <E3FFA1821F56A7BE7F895293@JcK-HP8200.jck.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Tim Bray <tbray@textuality.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Jul 2013 03:49:28 -0000

Hi John,
At 18:23 20-07-2013, John C Klensin wrote:
>See my earlier note, but mostly to aid in getting the
>documentation right.  For example, to the extent that the recent
>discussion results in a more complete treatment of privacy
>and/or security considerations in the documentation, that is a
>net improvement and added value.

There was a Last Call for draft-montemurro-gsma-imei-urn-01 in 
2007.  The draft was sponsored by an Apps 
AD.  draft-montemurro-gsma-imei-urn-04 was evaluated (I did not 
verify the details) in 2009.  An IPR disclosure, about a patent filed 
several years ago, was filed after that evaluation.  The DISCUSS got 
cleared automatically.  draft-montemurro-gsma-imei-urn-08  was 
dispatched to RAI in 2011.

3GPP was assigned a URN in 2008.  The shepherd write-up 
for  draft-montemurro-gsma-imei-urn-16 mentions that "this document 
is required for the 3GPP/IMS specification, thus any
vendor that implements the 3GPP specifications follows this 
specification".  The significant difference between the 3GPP URN and 
the requested GSMA URN is that there is an IPR disclosure on that latter.

One of the questions asked by Tim Bray was about the WiFi-only 
scenario.  That was raised previously through a DISCUSS as the softphone issue.

The privacy discussion might cause some discontent.  As for whether 
the draft will gain consensus, well, what can I say; if it is the 
consensus of the IETF to support state-sponsored surveillance there 
is nothing I can do about it. :-)

Regards,
S. Moonesamy 


From prvs=99147d9d4e=aallen@blackberry.com  Sat Jul 20 21:48:49 2013
Return-Path: <prvs=99147d9d4e=aallen@blackberry.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DBB221F8C40 for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 21:48:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level: 
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[AWL=0.349,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id drrNiPIdm6wB for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 21:48:43 -0700 (PDT)
Received: from mhs060cnc.rim.net (mhs060cnc.rim.net [208.65.73.34]) by ietfa.amsl.com (Postfix) with ESMTP id 09C1521F9B94 for <ietf@ietf.org>; Sat, 20 Jul 2013 21:48:42 -0700 (PDT)
X-AuditID: 0a41282f-b7f9b6d000002847-39-51eb6826f8d8
Received: from XCT105ADS.rim.net (xct105ads.rim.net [10.67.111.46]) by mhs060cnc.rim.net (SBG) with SMTP id E2.51.10311.6286BE15; Sat, 20 Jul 2013 23:48:39 -0500 (CDT)
Received: from XMB104ADS.rim.net ([fe80::2494:a63d:e3:723b]) by XCT105ADS.rim.net ([fe80::2d01:2041:eea3:819b%22]) with mapi id 14.02.0328.009; Sat, 20 Jul 2013 23:48:38 -0500
From: Andrew Allen <aallen@blackberry.com>
To: "tbray@textuality.com" <tbray@textuality.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
Thread-Topic: Last call: draft-montemurro-gsma-imei-urn-16.txt
Thread-Index: AQHOhJEO4fYTwuVTOkCw8MDTXs0bMZlsItsKgABZfICAAYRS+oAAYPKA///D5waAAHA2AP///EWK
Date: Sun, 21 Jul 2013 04:48:37 +0000
Message-ID: <BBF5DDFE515C3946BC18D733B20DAD2338DD24D0@XMB104ADS.rim.net>
In-Reply-To: <CAHBU6iuSK9nFKakvbPR0-BEUghuhgDg4G1T9qzDr=EAyh-N-Uw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.67.110.252]
Content-Type: multipart/alternative; boundary="_000_BBF5DDFE515C3946BC18D733B20DAD2338DD24D0XMB104ADSrimnet_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrIKsWRmVeSWpSXmKPExsXC5Zyvp6ue8TrQ4OktFotnG+ezWLzbcZjN Yumf+SwOzB47Z91l91iy5CeTx6Wlk5kDmKMaGG2SEkvKgjPT8/TtbBLz8vJLEktSFVJSi5Nt lXxS0xNzFAKKMssSkysVXDKLk3MSM3NTi5QUMlNslUyUFApyEpNTc1PzSmyVEgsKUvNSlOy4 FDCADVBZZp5Cal5yfkpmXrqtkmewv66FhamlrqGSnW5CJ09G46tdLAUTUiua+v+xNjBuSOpi 5OCQEDCR+PApuYuRE8gUk7hwbz1bFyMXh5DASkaJHxMvMEM4mxkltty5yQRSxSagJbH/8HQm kGYRAUOJRXu9QMLMAiESL5unsIPYwgK2EpdP/2EEsUUE7CS+H7zEAmFHSWw80McKYrMIqEp0 PNkDNpJXwENi2u2nzCAjOQUCJT6/KwAJMwLd8/3UGiaI8eISt57MZ4K4U0BiyZ7zzBC2qMTL x/9YIWxFicct3SwQ9fkSj6dvZoMYLyhxcuYTlgmMIrOQjJqFpGwWkrJZQFcwC2hKrN+lD1Gi KDGl+yE7hK0h0TpnLjuy+AJG9lWMgrkZxQZmBsl5yXpFmbl6eaklmxhBycRRQ38H49v3FocY BTgYlXh4BSNfBwqxJpYVV+YeYpTgYFYS4b0dCxTiTUmsrEotyo8vKs1JLT7EGAQMn4nMUtzJ +cBEl1cSb2xgQCRHSZzX6uzZQCGBdGACy05NLUgtghnKxMEJspRLSqQYmIZSixJLSzLiQcky vhiYLqUaGD0vCnq96FBr2Nln/vrt3JnLEz7/ON8VMScr06tFI2ZShd+y/b2R1/jki46fCqmN mFV2eGrmEp+Li3iXzA/Tvme+IaAnxUrs0jS5TNHFh1dJTAmzEfjrxOs6s7//Z7navEAHhzvL 2JdPmlHMWD4xxPp1pim3Zbd20+HTE5W3Td4ucv33ar3Ix0osxRmJhlrMRcWJANVWME50AwAA
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Jul 2013 04:48:49 -0000

--_000_BBF5DDFE515C3946BC18D733B20DAD2338DD24D0XMB104ADSrimnet_
Content-Type: text/plain; charset="utf-8"
content-transfer-encoding: base64

DQpUaW0NCg0KRmlyc3RseSBhcyBzdGF0ZWQgaW4NCmh0dHA6Ly9kYXRhdHJhY2tlci5pZXRm
Lm9yZy9kb2MvZHJhZnQtYWxsZW4tZGlzcGF0Y2gtaW1laS11cm4tYXMtaW5zdGFuY2VpZC8N
CnRoZSB1c2Ugb2YgdGhlIElNRUkgYXMgYSBTSVAgSW5zdGFuY2UgSUQgb25seSBwZXJ0YWlu
cyB0byB1c2FnZSBvZiBTSVAgd2l0aCB0aGUgM0dQUCBJTVMgYW5kIGlmIGEgZGV2aWNlIGlz
IG5vdCB1c2luZyBJTVMgc2luZyBJTVMgd2l0aG91dCBhbiBJTUVJIHVzZXMgSU1TIHRoZW4g
aXQgd2lsbCBzdGlsbCB1c2UgYSBVVUlEIGFzIHRoZSBTSVAgaW5zdGFuY2UgSUQgYXMgcGVy
IFJGQyA1NjI2LiBJZiBhIGRldmljZSB3aXRob3V0IGFuIElNRUkgdXNlcyBJTVMgdGhlbiBp
dCB3aWxsIGFsc28gc3RpbGwgdXNlIGEgVVVJRCBhcyB0aGUgU0lQIGluc3RhbmNlIElEIGFz
IHBlciBSRkMgNTYyNi4gVGhpcyBpcyBzcGVjaWZpZWQgYWxzbyBpbiB0aGUgM0dQUCBJTVMg
c3BlY2lmaWNhdGlvbiBUUyAyNC4yMjkgYXMgd2VsbCBhcyB0aGUgYWJvdmUgZHJhZnQuDQoN
ClNvIGFwcGxpY2F0aW9ucyBydW5uaW5nIG9uIGRldmljZXMgdGhhdCBkb24ndCBoYXZlIGFu
IElNRUkgY2FuIHN0aWxsIHVzZSBTSVAgZm9yIHNlc3Npb25zLg0KDQpUaGUgSU1FSSB3aGlj
aCBoYXMgYmVlbiB1c2VkIGluIG1vYmlsZSBkZXZpY2VzIGZvciAyMCB5ZWFycyBhbHNvIHN1
cnZpdmVzIGRldmljZSB3aXBlcyBmb3IgdGhlIGNpcmN1aXQgc3dpdGNoZWQgY2FsbGluZyBj
YXBhYmlsaXR5IGFzIHVzZWQgYnkgYmlsbGlvbnMgb2YgbW9iaWxlcyB0b2RheSB3aXRoIDJH
IGFuZCAzRyBuZXR3b3Jrcy4gU28gYWdhaW4gaG93IGlzIHRoaXMgbW9yZSBoYXJtZnVsIGZv
ciA0RyB0aGFuIHRoZSBjdXJyZW50IHNpdHVhdGlvbiB3aXRoIDJHIGFuZCAzRyBpZiBhIG1v
YmlsZSBkZXZpY2UgaXMgdHJhbnNmZXJyZWQgdG8gYSBuZXcgb3duZXI/DQoNCkFuZHJldw0K
DQpGcm9tOiBUaW0gQnJheSBbbWFpbHRvOnRicmF5QHRleHR1YWxpdHkuY29tXQ0KU2VudDog
U2F0dXJkYXksIEp1bHkgMjAsIDIwMTMgMDc6MDEgUE0gQ2VudHJhbCBTdGFuZGFyZCBUaW1l
DQpUbzogQW5kcmV3IEFsbGVuDQpDYzogc2NvdHQuYnJpbUBnbWFpbC5jb20gPHNjb3R0LmJy
aW1AZ21haWwuY29tPjsgaWV0ZkBpZXRmLm9yZyA8aWV0ZkBpZXRmLm9yZz4NClN1YmplY3Q6
IFJlOiBMYXN0IGNhbGw6IGRyYWZ0LW1vbnRlbXVycm8tZ3NtYS1pbWVpLXVybi0xNi50eHQN
Cg0KT24gU2F0LCBKdWwgMjAsIDIwMTMgYXQgMzoyMCBQTSwgQW5kcmV3IEFsbGVuIDxhYWxs
ZW5AYmxhY2tiZXJyeS5jb208bWFpbHRvOmFhbGxlbkBibGFja2JlcnJ5LmNvbT4+IHdyb3Rl
Og0KQ2FuIGl0IHBsZWFzZSBiZSBleHBsYWluZWQgaG93IHRoZSBJTUVJIFVSTiB3aGVuIHVz
ZWQgYXMgc3RhdGVkIGluIGh0dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQt
YWxsZW4tZGlzcGF0Y2gtaW1laS11cm4tYXMtaW5zdGFuY2VpZC8NCklzIGFueSBtb3JlIGhh
cm1mdWwgdGhhbiBhcyB0aGUgSU1FSSBpcyB1c2VkIHRvZGF5IGJ5IG92ZXIgOTAlIG9mIG1v
YmlsZSBwaG9uZXMgaW4gdXNlIHRvZGF5IHdvcmxkd2lkZT8NCg0KSXQgc3Vydml2ZXMgZGV2
aWNlIHdpcGVzLCB3aGljaCB1c3VhbGx5IGhhcHBlbiB1cG9uIGNoYW5nZSBvZiBkZXZpY2Ug
b3duZXJzaGlwLg0KDQpJ4oCZbSBub3QgYW4gZXhwZXJ0IGluIHlvdXIgYXBwbGljYXRpb24g
ZG9tYWluLCBzbyBwYXJkb24gbWUgaWYgdGhpcyBxdWVzdGlvbiBpcyBob3BlbGVzc2x5IG5h
aXZlOiBJdCBzZWVtcyB0aGF0IHRoaXMgaWRlbnRpZmllciBpcyByZWxhdGVkIGluIHNvbWUg
d2F5IHRvIFNJUCBzZXNzaW9ucy4gIEl0IHNlZW1zIHRoYXQgaXQgd291bGQgYmUgYSBjb21t
b24gb3BlcmF0aW9uIHRvIGxhdW5jaCBhIFNJUCBzZXNzaW9uIG9uIGEgZGV2aWNlIHN1Y2gg
YXMgYSBXaUZpLW9ubHkgdGFibGV0LCBvciBhbiBpUG9kIHRvdWNoLCB0aGF0IGRvZXNu4oCZ
dCBoYXZlIGFuIElNRUkuICBJcyB0aGlzIGEgcHJvYmxlbT8NCg0KIC1UDQoNCg0KQW5kcmV3
DQoNCi0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0NCkZyb206IFNjb3R0IEJyaW0gW21h
aWx0bzpzY290dC5icmltQGdtYWlsLmNvbTxtYWlsdG86c2NvdHQuYnJpbUBnbWFpbC5jb20+
XQ0KU2VudDogU2F0dXJkYXksIEp1bHkgMjAsIDIwMTMgMDM6NTUgUE0gQ2VudHJhbCBTdGFu
ZGFyZCBUaW1lDQpUbzogQW5kcmV3IEFsbGVuDQpDYzogdGJyYXlAdGV4dHVhbGl0eS5jb208
bWFpbHRvOnRicmF5QHRleHR1YWxpdHkuY29tPiA8dGJyYXlAdGV4dHVhbGl0eS5jb208bWFp
bHRvOnRicmF5QHRleHR1YWxpdHkuY29tPj47IGlldGZAaWV0Zi5vcmc8bWFpbHRvOmlldGZA
aWV0Zi5vcmc+IDxpZXRmQGlldGYub3JnPG1haWx0bzppZXRmQGlldGYub3JnPj4NClN1Ympl
Y3Q6IFJlOiBMYXN0IGNhbGw6IGRyYWZ0LW1vbnRlbXVycm8tZ3NtYS1pbWVpLXVybi0xNi50
eHQNCg0KT24gU2F0LCBKdWwgMjAsIDIwMTMgYXQgNDowOCBQTSwgQW5kcmV3IEFsbGVuIDxh
YWxsZW5AYmxhY2tiZXJyeS5jb208bWFpbHRvOmFhbGxlbkBibGFja2JlcnJ5LmNvbT4+IHdy
b3RlOg0KPiBUaW0NCj4NCj4gVGhlIHF1b3RlIGlzIGZyb20gUkZDIDU2MjYgd2hpY2ggYWxz
byBzdGF0ZXM6DQo+DQo+ICIzLjEuIFN1bW1hcnkgb2YgTWVjaGFuaXNtDQo+DQo+IEVhY2gg
VUEgaGFzIGEgdW5pcXVlIGluc3RhbmNlLWlkIHRoYXQgc3RheXMgdGhlIHNhbWUgZm9yIHRo
aXMgVUEgZXZlbiBpZiB0aGUNCj4gVUEgcmVib290cyBvciBpcyBwb3dlciBjeWNsZWQuIg0K
Pg0KPiBTaW5jZSB0aGUgVVVJRCBpbiB0aGUgaW5zdGFuY2UgSUQgaXMgYWxzbyBzdGF0aWMg
aG93IGlzIHRoaXMgc2lnbmlmaWNhbnRseQ0KPiBkaWZmZXJlbnQgaW4gdGVybXMgb2YgcHJp
dmFjeSBjb25jZXJucyBmcm9tIHRoZSBJTUVJIGJlaW5nIHVzZWQgYXMgYW4NCj4gaW5zdGFu
Y2UgSUQ/DQoNCllvdSdyZSBub3QgZGVtb25zdHJhdGluZyB0aGF0IGFuIElNRUkgaXMganVz
dCBhcyBnb29kLCB5b3UncmUNCmRlbW9uc3RyYXRpbmcgdGhhdCBhIFVVSUQgaXMganVzdCBh
cyBiYWQuDQoNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KVGhpcyB0cmFuc21pc3Npb24gKGluY2x1ZGlu
ZyBhbnkgYXR0YWNobWVudHMpIG1heSBjb250YWluIGNvbmZpZGVudGlhbCBpbmZvcm1hdGlv
biwgcHJpdmlsZWdlZCBtYXRlcmlhbCAoaW5jbHVkaW5nIG1hdGVyaWFsIHByb3RlY3RlZCBi
eSB0aGUgc29saWNpdG9yLWNsaWVudCBvciBvdGhlciBhcHBsaWNhYmxlIHByaXZpbGVnZXMp
LCBvciBjb25zdGl0dXRlIG5vbi1wdWJsaWMgaW5mb3JtYXRpb24uIEFueSB1c2Ugb2YgdGhp
cyBpbmZvcm1hdGlvbiBieSBhbnlvbmUgb3RoZXIgdGhhbiB0aGUgaW50ZW5kZWQgcmVjaXBp
ZW50IGlzIHByb2hpYml0ZWQuIElmIHlvdSBoYXZlIHJlY2VpdmVkIHRoaXMgdHJhbnNtaXNz
aW9uIGluIGVycm9yLCBwbGVhc2UgaW1tZWRpYXRlbHkgcmVwbHkgdG8gdGhlIHNlbmRlciBh
bmQgZGVsZXRlIHRoaXMgaW5mb3JtYXRpb24gZnJvbSB5b3VyIHN5c3RlbS4gVXNlLCBkaXNz
ZW1pbmF0aW9uLCBkaXN0cmlidXRpb24sIG9yIHJlcHJvZHVjdGlvbiBvZiB0aGlzIHRyYW5z
bWlzc2lvbiBieSB1bmludGVuZGVkIHJlY2lwaWVudHMgaXMgbm90IGF1dGhvcml6ZWQgYW5k
IG1heSBiZSB1bmxhd2Z1bC4NCg0KDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NClRoaXMgdHJhbnNtaXNz
aW9uIChpbmNsdWRpbmcgYW55IGF0dGFjaG1lbnRzKSBtYXkgY29udGFpbiBjb25maWRlbnRp
YWwgaW5mb3JtYXRpb24sIHByaXZpbGVnZWQgbWF0ZXJpYWwgKGluY2x1ZGluZyBtYXRlcmlh
bCBwcm90ZWN0ZWQgYnkgdGhlIHNvbGljaXRvci1jbGllbnQgb3Igb3RoZXIgYXBwbGljYWJs
ZSBwcml2aWxlZ2VzKSwgb3IgY29uc3RpdHV0ZSBub24tcHVibGljIGluZm9ybWF0aW9uLiBB
bnkgdXNlIG9mIHRoaXMgaW5mb3JtYXRpb24gYnkgYW55b25lIG90aGVyIHRoYW4gdGhlIGlu
dGVuZGVkIHJlY2lwaWVudCBpcyBwcm9oaWJpdGVkLiBJZiB5b3UgaGF2ZSByZWNlaXZlZCB0
aGlzIHRyYW5zbWlzc2lvbiBpbiBlcnJvciwgcGxlYXNlIGltbWVkaWF0ZWx5IHJlcGx5IHRv
IHRoZSBzZW5kZXIgYW5kIGRlbGV0ZSB0aGlzIGluZm9ybWF0aW9uIGZyb20geW91ciBzeXN0
ZW0uIFVzZSwgZGlzc2VtaW5hdGlvbiwgZGlzdHJpYnV0aW9uLCBvciByZXByb2R1Y3Rpb24g
b2YgdGhpcyB0cmFuc21pc3Npb24gYnkgdW5pbnRlbmRlZCByZWNpcGllbnRzIGlzIG5vdCBh
dXRob3JpemVkIGFuZCBtYXkgYmUgdW5sYXdmdWwuDQo=

--_000_BBF5DDFE515C3946BC18D733B20DAD2338DD24D0XMB104ADSrimnet_
Content-Type: text/html; charset="utf-8"
content-transfer-encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5Pg0KPGZvbnQg
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxicj4NClRpbTxicj4N
Cjxicj4NCkZpcnN0bHkgYXMgc3RhdGVkIGluPGJyPg0KaHR0cDovL2RhdGF0cmFja2VyLmll
dGYub3JnL2RvYy9kcmFmdC1hbGxlbi1kaXNwYXRjaC1pbWVpLXVybi1hcy1pbnN0YW5jZWlk
Lzxicj4NCnRoZSB1c2Ugb2YgdGhlIElNRUkgYXMgYSBTSVAgSW5zdGFuY2UgSUQgb25seSBw
ZXJ0YWlucyB0byB1c2FnZSBvZiBTSVAgd2l0aCB0aGUgM0dQUCBJTVMgYW5kIGlmIGEgZGV2
aWNlIGlzIG5vdCB1c2luZyBJTVMgc2luZyBJTVMgd2l0aG91dCBhbiBJTUVJIHVzZXMgSU1T
IHRoZW4gaXQgd2lsbCBzdGlsbCB1c2UgYSBVVUlEIGFzIHRoZSBTSVAgaW5zdGFuY2UgSUQg
YXMgcGVyIFJGQyA1NjI2LiBJZiBhIGRldmljZSB3aXRob3V0IGFuIElNRUkgdXNlcw0KIElN
UyB0aGVuIGl0IHdpbGwgYWxzbyBzdGlsbCB1c2UgYSBVVUlEIGFzIHRoZSBTSVAgaW5zdGFu
Y2UgSUQgYXMgcGVyIFJGQyA1NjI2LiBUaGlzIGlzIHNwZWNpZmllZCBhbHNvIGluIHRoZSAz
R1BQIElNUyBzcGVjaWZpY2F0aW9uIFRTIDI0LjIyOSBhcyB3ZWxsIGFzIHRoZSBhYm92ZSBk
cmFmdC48YnI+DQo8YnI+DQpTbyBhcHBsaWNhdGlvbnMgcnVubmluZyBvbiBkZXZpY2VzIHRo
YXQgZG9uJ3QgaGF2ZSBhbiBJTUVJIGNhbiBzdGlsbCB1c2UgU0lQIGZvciBzZXNzaW9ucy4N
Cjxicj4NCjxicj4NClRoZSBJTUVJIHdoaWNoIGhhcyBiZWVuIHVzZWQgaW4gbW9iaWxlIGRl
dmljZXMgZm9yIDIwIHllYXJzIGFsc28gc3Vydml2ZXMgZGV2aWNlIHdpcGVzIGZvciB0aGUg
Y2lyY3VpdCBzd2l0Y2hlZCBjYWxsaW5nIGNhcGFiaWxpdHkgYXMgdXNlZCBieSBiaWxsaW9u
cyBvZiBtb2JpbGVzIHRvZGF5IHdpdGggMkcgYW5kIDNHIG5ldHdvcmtzLiBTbyBhZ2FpbiBo
b3cgaXMgdGhpcyBtb3JlIGhhcm1mdWwgZm9yIDRHIHRoYW4gdGhlIGN1cnJlbnQgc2l0dWF0
aW9uDQogd2l0aCAyRyBhbmQgM0cgaWYgYSBtb2JpbGUgZGV2aWNlIGlzIHRyYW5zZmVycmVk
IHRvIGEgbmV3IG93bmVyPzxicj4NCjxicj4NCkFuZHJldzwvZm9udD48YnI+DQombmJzcDs8
YnI+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNCNUM0REYg
MS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbiI+DQo8Zm9udCBzdHlsZT0iZm9udC1z
aXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1z
ZXJpZiZxdW90OyI+PGI+RnJvbTwvYj46IFRpbSBCcmF5IFttYWlsdG86dGJyYXlAdGV4dHVh
bGl0eS5jb21dDQo8YnI+DQo8Yj5TZW50PC9iPjogU2F0dXJkYXksIEp1bHkgMjAsIDIwMTMg
MDc6MDEgUE0gQ2VudHJhbCBTdGFuZGFyZCBUaW1lPGJyPg0KPGI+VG88L2I+OiBBbmRyZXcg
QWxsZW4gPGJyPg0KPGI+Q2M8L2I+OiBzY290dC5icmltQGdtYWlsLmNvbSAmbHQ7c2NvdHQu
YnJpbUBnbWFpbC5jb20mZ3Q7OyBpZXRmQGlldGYub3JnICZsdDtpZXRmQGlldGYub3JnJmd0
Ow0KPGJyPg0KPGI+U3ViamVjdDwvYj46IFJlOiBMYXN0IGNhbGw6IGRyYWZ0LW1vbnRlbXVy
cm8tZ3NtYS1pbWVpLXVybi0xNi50eHQgPGJyPg0KPC9mb250PiZuYnNwOzxicj4NCjwvZGl2
Pg0KPGRpdiBkaXI9Imx0ciI+T24gU2F0LCBKdWwgMjAsIDIwMTMgYXQgMzoyMCBQTSwgQW5k
cmV3IEFsbGVuIDxzcGFuIGRpcj0ibHRyIj4mbHQ7PGEgaHJlZj0ibWFpbHRvOmFhbGxlbkBi
bGFja2JlcnJ5LmNvbSIgdGFyZ2V0PSJfYmxhbmsiPmFhbGxlbkBibGFja2JlcnJ5LmNvbTwv
YT4mZ3Q7PC9zcGFuPiB3cm90ZTo8YnI+DQo8ZGl2IGNsYXNzPSJnbWFpbF9leHRyYSI+DQo8
ZGl2IGNsYXNzPSJnbWFpbF9xdW90ZSI+DQo8YmxvY2txdW90ZSBjbGFzcz0iZ21haWxfcXVv
dGUiIHN0eWxlPSJtYXJnaW46MCAwIDAgLjhleDtib3JkZXItbGVmdDoxcHggI2NjYyBzb2xp
ZDtwYWRkaW5nLWxlZnQ6MWV4Ij4NCkNhbiBpdCBwbGVhc2UgYmUgZXhwbGFpbmVkIGhvdyB0
aGUgSU1FSSBVUk4gd2hlbiB1c2VkIGFzIHN0YXRlZCBpbiA8YSBocmVmPSJodHRwOi8vZGF0
YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWFsbGVuLWRpc3BhdGNoLWltZWktdXJuLWFz
LWluc3RhbmNlaWQvIiB0YXJnZXQ9Il9ibGFuayI+DQpodHRwOi8vZGF0YXRyYWNrZXIuaWV0
Zi5vcmcvZG9jL2RyYWZ0LWFsbGVuLWRpc3BhdGNoLWltZWktdXJuLWFzLWluc3RhbmNlaWQv
PC9hPjxicj4NCklzIGFueSBtb3JlIGhhcm1mdWwgdGhhbiBhcyB0aGUgSU1FSSBpcyB1c2Vk
IHRvZGF5IGJ5IG92ZXIgOTAlIG9mIG1vYmlsZSBwaG9uZXMgaW4gdXNlIHRvZGF5IHdvcmxk
d2lkZT88YnI+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5JdCBz
dXJ2aXZlcyBkZXZpY2Ugd2lwZXMsIHdoaWNoIHVzdWFsbHkgaGFwcGVuIHVwb24gY2hhbmdl
IG9mIGRldmljZSBvd25lcnNoaXAuJm5ic3A7DQo8YnI+DQo8YnI+DQpJ4oCZbSBub3QgYW4g
ZXhwZXJ0IGluIHlvdXIgYXBwbGljYXRpb24gZG9tYWluLCBzbyBwYXJkb24gbWUgaWYgdGhp
cyBxdWVzdGlvbiBpcyBob3BlbGVzc2x5IG5haXZlOiBJdCBzZWVtcyB0aGF0IHRoaXMgaWRl
bnRpZmllciBpcyByZWxhdGVkIGluIHNvbWUgd2F5IHRvIFNJUCBzZXNzaW9ucy4mbmJzcDsg
SXQgc2VlbXMgdGhhdCBpdCB3b3VsZCBiZSBhIGNvbW1vbiBvcGVyYXRpb24gdG8gbGF1bmNo
IGEgU0lQIHNlc3Npb24gb24gYSBkZXZpY2Ugc3VjaCBhcw0KIGEgV2lGaS1vbmx5IHRhYmxl
dCwgb3IgYW4gaVBvZCB0b3VjaCwgdGhhdCBkb2VzbuKAmXQgaGF2ZSBhbiBJTUVJLiZuYnNw
OyBJcyB0aGlzIGEgcHJvYmxlbT88YnI+DQo8YnI+DQo8L2Rpdj4NCjxkaXY+Jm5ic3A7LVQ8
YnI+DQo8L2Rpdj4NCjxkaXY+Jm5ic3A7PC9kaXY+DQo8YmxvY2txdW90ZSBjbGFzcz0iZ21h
aWxfcXVvdGUiIHN0eWxlPSJtYXJnaW46MCAwIDAgLjhleDtib3JkZXItbGVmdDoxcHggI2Nj
YyBzb2xpZDtwYWRkaW5nLWxlZnQ6MWV4Ij4NCjxzcGFuIGNsYXNzPSJIT0VuWmIiPjxmb250
IGNvbG9yPSIjODg4ODg4Ij48YnI+DQpBbmRyZXc8YnI+DQo8L2ZvbnQ+PC9zcGFuPg0KPGRp
diBjbGFzcz0iaW0gSE9FblpiIj48YnI+DQotLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0t
PGJyPg0KRnJvbTogU2NvdHQgQnJpbSBbbWFpbHRvOjxhIGhyZWY9Im1haWx0bzpzY290dC5i
cmltQGdtYWlsLmNvbSI+c2NvdHQuYnJpbUBnbWFpbC5jb208L2E+XTxicj4NCjwvZGl2Pg0K
PGRpdiBjbGFzcz0iaW0gSE9FblpiIj5TZW50OiBTYXR1cmRheSwgSnVseSAyMCwgMjAxMyAw
Mzo1NSBQTSBDZW50cmFsIFN0YW5kYXJkIFRpbWU8YnI+DQpUbzogQW5kcmV3IEFsbGVuPGJy
Pg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSJpbSBIT0VuWmIiPkNjOiA8YSBocmVmPSJtYWlsdG86
dGJyYXlAdGV4dHVhbGl0eS5jb20iPnRicmF5QHRleHR1YWxpdHkuY29tPC9hPiAmbHQ7PGEg
aHJlZj0ibWFpbHRvOnRicmF5QHRleHR1YWxpdHkuY29tIj50YnJheUB0ZXh0dWFsaXR5LmNv
bTwvYT4mZ3Q7Ow0KPGEgaHJlZj0ibWFpbHRvOmlldGZAaWV0Zi5vcmciPmlldGZAaWV0Zi5v
cmc8L2E+ICZsdDs8YSBocmVmPSJtYWlsdG86aWV0ZkBpZXRmLm9yZyI+aWV0ZkBpZXRmLm9y
ZzwvYT4mZ3Q7PGJyPg0KU3ViamVjdDogUmU6IExhc3QgY2FsbDogZHJhZnQtbW9udGVtdXJy
by1nc21hLWltZWktdXJuLTE2LnR4dDxicj4NCjxicj4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0i
SE9FblpiIj4NCjxkaXYgY2xhc3M9Img1Ij5PbiBTYXQsIEp1bCAyMCwgMjAxMyBhdCA0OjA4
IFBNLCBBbmRyZXcgQWxsZW4gJmx0OzxhIGhyZWY9Im1haWx0bzphYWxsZW5AYmxhY2tiZXJy
eS5jb20iPmFhbGxlbkBibGFja2JlcnJ5LmNvbTwvYT4mZ3Q7IHdyb3RlOjxicj4NCiZndDsg
VGltPGJyPg0KJmd0Ozxicj4NCiZndDsgVGhlIHF1b3RlIGlzIGZyb20gUkZDIDU2MjYgd2hp
Y2ggYWxzbyBzdGF0ZXM6PGJyPg0KJmd0Ozxicj4NCiZndDsgJnF1b3Q7My4xLiBTdW1tYXJ5
IG9mIE1lY2hhbmlzbTxicj4NCiZndDs8YnI+DQomZ3Q7IEVhY2ggVUEgaGFzIGEgdW5pcXVl
IGluc3RhbmNlLWlkIHRoYXQgc3RheXMgdGhlIHNhbWUgZm9yIHRoaXMgVUEgZXZlbiBpZiB0
aGU8YnI+DQomZ3Q7IFVBIHJlYm9vdHMgb3IgaXMgcG93ZXIgY3ljbGVkLiZxdW90Ozxicj4N
CiZndDs8YnI+DQomZ3Q7IFNpbmNlIHRoZSBVVUlEIGluIHRoZSBpbnN0YW5jZSBJRCBpcyBh
bHNvIHN0YXRpYyBob3cgaXMgdGhpcyBzaWduaWZpY2FudGx5PGJyPg0KJmd0OyBkaWZmZXJl
bnQgaW4gdGVybXMgb2YgcHJpdmFjeSBjb25jZXJucyBmcm9tIHRoZSBJTUVJIGJlaW5nIHVz
ZWQgYXMgYW48YnI+DQomZ3Q7IGluc3RhbmNlIElEPzxicj4NCjxicj4NCllvdSdyZSBub3Qg
ZGVtb25zdHJhdGluZyB0aGF0IGFuIElNRUkgaXMganVzdCBhcyBnb29kLCB5b3UncmU8YnI+
DQpkZW1vbnN0cmF0aW5nIHRoYXQgYSBVVUlEIGlzIGp1c3QgYXMgYmFkLjxicj4NCjxicj4N
CjwvZGl2Pg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSJIT0VuWmIiPg0KPGRpdiBjbGFzcz0iaDUi
Pi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLTxicj4NClRoaXMgdHJhbnNtaXNzaW9uIChpbmNsdWRpbmcgYW55
IGF0dGFjaG1lbnRzKSBtYXkgY29udGFpbiBjb25maWRlbnRpYWwgaW5mb3JtYXRpb24sIHBy
aXZpbGVnZWQgbWF0ZXJpYWwgKGluY2x1ZGluZyBtYXRlcmlhbCBwcm90ZWN0ZWQgYnkgdGhl
IHNvbGljaXRvci1jbGllbnQgb3Igb3RoZXIgYXBwbGljYWJsZSBwcml2aWxlZ2VzKSwgb3Ig
Y29uc3RpdHV0ZSBub24tcHVibGljIGluZm9ybWF0aW9uLiBBbnkgdXNlIG9mIHRoaXMgaW5m
b3JtYXRpb24NCiBieSBhbnlvbmUgb3RoZXIgdGhhbiB0aGUgaW50ZW5kZWQgcmVjaXBpZW50
IGlzIHByb2hpYml0ZWQuIElmIHlvdSBoYXZlIHJlY2VpdmVkIHRoaXMgdHJhbnNtaXNzaW9u
IGluIGVycm9yLCBwbGVhc2UgaW1tZWRpYXRlbHkgcmVwbHkgdG8gdGhlIHNlbmRlciBhbmQg
ZGVsZXRlIHRoaXMgaW5mb3JtYXRpb24gZnJvbSB5b3VyIHN5c3RlbS4gVXNlLCBkaXNzZW1p
bmF0aW9uLCBkaXN0cmlidXRpb24sIG9yIHJlcHJvZHVjdGlvbiBvZiB0aGlzIHRyYW5zbWlz
c2lvbg0KIGJ5IHVuaW50ZW5kZWQgcmVjaXBpZW50cyBpcyBub3QgYXV0aG9yaXplZCBhbmQg
bWF5IGJlIHVubGF3ZnVsLjxicj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8
L2Rpdj4NCjxicj4NCjwvZGl2Pg0KPC9kaXY+DQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0gPGJyPg0KVGhp
cyB0cmFuc21pc3Npb24gKGluY2x1ZGluZyBhbnkgYXR0YWNobWVudHMpIG1heSBjb250YWlu
IGNvbmZpZGVudGlhbCBpbmZvcm1hdGlvbiwgcHJpdmlsZWdlZCBtYXRlcmlhbCAoaW5jbHVk
aW5nIG1hdGVyaWFsIHByb3RlY3RlZCBieSB0aGUgc29saWNpdG9yLWNsaWVudCBvciBvdGhl
ciBhcHBsaWNhYmxlIHByaXZpbGVnZXMpLCBvciBjb25zdGl0dXRlIG5vbi1wdWJsaWMgaW5m
b3JtYXRpb24uIEFueSB1c2Ugb2YgdGhpcyBpbmZvcm1hdGlvbiBieSBhbnlvbmUgb3RoZXIg
dGhhbiB0aGUgaW50ZW5kZWQgcmVjaXBpZW50IGlzIHByb2hpYml0ZWQuIElmIHlvdSBoYXZl
IHJlY2VpdmVkIHRoaXMgdHJhbnNtaXNzaW9uIGluIGVycm9yLCBwbGVhc2UgaW1tZWRpYXRl
bHkgcmVwbHkgdG8gdGhlIHNlbmRlciBhbmQgZGVsZXRlIHRoaXMgaW5mb3JtYXRpb24gZnJv
bSB5b3VyIHN5c3RlbS4gVXNlLCBkaXNzZW1pbmF0aW9uLCBkaXN0cmlidXRpb24sIG9yIHJl
cHJvZHVjdGlvbiBvZiB0aGlzIHRyYW5zbWlzc2lvbiBieSB1bmludGVuZGVkIHJlY2lwaWVu
dHMgaXMgbm90IGF1dGhvcml6ZWQgYW5kIG1heSBiZSB1bmxhd2Z1bC4NCjwvYm9keT4NCjwv
aHRtbD4NCg==

--_000_BBF5DDFE515C3946BC18D733B20DAD2338DD24D0XMB104ADSrimnet_--

From prvs=7914a55762=aallen@blackberry.com  Sat Jul 20 22:05:44 2013
Return-Path: <prvs=7914a55762=aallen@blackberry.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 652E821F9E3C for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 22:05:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.421
X-Spam-Level: 
X-Spam-Status: No, score=-5.421 tagged_above=-999 required=5 tests=[AWL=-0.533, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xTwrr1cxEcV0 for <ietf@ietfa.amsl.com>; Sat, 20 Jul 2013 22:05:40 -0700 (PDT)
Received: from mhs060cnc.rim.net (mhs060cnc.rim.net [208.65.73.34]) by ietfa.amsl.com (Postfix) with ESMTP id 06D4121F9D6B for <ietf@ietf.org>; Sat, 20 Jul 2013 22:05:39 -0700 (PDT)
X-AuditID: 0a41282f-b7f9b6d000002847-70-51eb6c1ca06e
Received: from XCT102ADS.rim.net (xct102ads.rim.net [10.67.111.43]) by mhs060cnc.rim.net (SBG) with SMTP id EA.51.10311.C1C6BE15; Sun, 21 Jul 2013 00:05:32 -0500 (CDT)
Received: from XMB104ADS.rim.net ([fe80::2494:a63d:e3:723b]) by XCT102ADS.rim.net ([fe80::4806:2e1d:2b7c:cfdf%22]) with mapi id 14.02.0328.009; Sun, 21 Jul 2013 00:05:31 -0500
From: Andrew Allen <aallen@blackberry.com>
To: "john-ietf@jck.com" <john-ietf@jck.com>, "tbray@textuality.com" <tbray@textuality.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
Thread-Topic: Last call: draft-montemurro-gsma-imei-urn-16.txt
Thread-Index: AQHOhJEO4fYTwuVTOkCw8MDTXs0bMZlsOFEcgAGJd4CAACLcBIAAViUAgABx1gCAAA8DAIAAB3EA///To6k=
Date: Sun, 21 Jul 2013 05:05:31 +0000
Message-ID: <BBF5DDFE515C3946BC18D733B20DAD2338DD24F1@XMB104ADS.rim.net>
In-Reply-To: <0230573D31DB808B0685E3CE@JcK-HP8200.jck.com>
Accept-Language: en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.67.110.252]
Content-Type: text/plain; charset="iso-8859-1"
content-transfer-encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrHKsWRmVeSWpSXmKPExsXC5ZyvrSuT8zrQYPc6S4tnG+ezWLRe+sNm sfTPfBYHZo8lS34yeVxe+ZrZ49LSycwBzFENjDZJiSVlwZnpefp2Nol5efkliSWpCimpxcm2 Sj6p6Yk5CgFFmWWJyZUKLpnFyTmJmbmpRUoKmSm2SiZKCgU5icmpual5JbZKiQUFqXkpSnZc ChjABqgsM08hNS85PyUzL91WyTPYX9fCwtRS11DJTjehkydjY8tU5oLDPBWTjq5iaWCcytXF yMkhIWAi8Wj6ejYIW0ziwj0Qm4tDSGAlo8Sbe8ehnM2MEk/u/WQBqWIT0JLYf3g6E4gtIhAj 8eX4VVYQm1lAWeLppjlgcWEBW4nLp/8wQtTYSXw/eIkFwk6SWDvjLZDNwcEioAq0ORzE5BXw kLi30BukglPASmLPo5fsIDajgKzE7rPXmSCmi0vcejKfCeJOAYkle84zQ9iiEi8f/2OFsBUl Hrd0s0DU60ncmDqFDcLWlli28DVYPa+AoMTJmU9YJjCKzkIydhaSlllIWmYhaVnAyLKKUTA3 o9jAzCA5L1mvKDNXLy+1ZBMjKEE4aujvYHz73uIQowAHoxIPr2Dk60Ah1sSy4srcQ4wSHMxK Iry3Y4FCvCmJlVWpRfnxRaU5qcWHGF2B4TCRWYo7OR+YvPJK4o0NDHBzlMR5rc6eDRQSSAem nuzU1ILUIpg5TBycIHu4pESKgQkktSixtCQjHpTm4ouBiU6qgfGwdGDBOlVm5YQH76Mn9+1V Mk59pPJaZOPtix0LGpezsjfW2So+vZd+TdPo98tXrcsOzXg05+aW60tkdB8vjOOYyPdPze7V Z/ktYUv5wu97vd6/+TXHrpX79of8W6HvwlfOtDn7zNa7k+cf0tvedMDWTYflacy3Fg1fQePy RX8Nvv9uFfu3s6BfiaU4I9FQi7moOBEAV+RLJlEDAAA=
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Jul 2013 05:05:44 -0000

Certainly text can be added to the draft to address concerns. 

Could Tim please elaborate on what issues he sees when a device is transferr=
ed between owners and what potential uses of the URN he has a concern with?=
 

Certainly I can see that if it was used as address that had some permanence=
 then that would be an issue however this is not the case as per http://data=
tracker.ietf.org/doc/draft-allen-dispatch-imei-urn-as-instanceid/

Andrew

----- Original Message -----
From: John C Klensin [mailto:john-ietf@jck.com]
Sent: Saturday, July 20, 2013 09:44 PM Central Standard Time=0A=
To: Tim Bray <tbray@textuality.com>
Cc: IETF-Discussion Discussion <ietf@ietf.org>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt



--On Saturday, July 20, 2013 19:17 -0700 Tim Bray
<tbray@textuality.com> wrote:

> Fair enough.  I think it would be reasonable to ask that:
> 
> - the draft include the word "privacy"
> - the draft discuss the issues around relying on an identifier
> that persists across changes in device ownership
> 
> There may be an issue concerning a SIP-related identifier
> which is unavailable on millions of mobile devices which do
> not have IMEIs, but it's quite possible that it's
> non-applicable in the context of the draft.  -T

Personally, I'd consider getting all three of those issues
addressed in the document (including a discussion of the
applicability of the latter and a serious discussion of the
privacy issues) as adding value... and as requirements for RFC
publication in the IETF Stream.

   john


---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential infor=
mation, privileged material (including material protected by the solicitor-c=
lient or other applicable privileges), or constitute non-public information.=
 Any use of this information by anyone other than the intended recipient is=
 prohibited. If you have received this transmission in error, please immedia=
tely reply to the sender and delete this information from your system. Use,=
 dissemination, distribution, or reproduction of this transmission by uninte=
nded recipients is not authorized and may be unlawful.

From prvs=5914595058=aallen@blackberry.com  Sun Jul 21 00:04:15 2013
Return-Path: <prvs=5914595058=aallen@blackberry.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E435B21E8056 for <ietf@ietfa.amsl.com>; Sun, 21 Jul 2013 00:04:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.54
X-Spam-Level: 
X-Spam-Status: No, score=-5.54 tagged_above=-999 required=5 tests=[AWL=-0.337,  BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BAorewoEkMsF for <ietf@ietfa.amsl.com>; Sun, 21 Jul 2013 00:04:10 -0700 (PDT)
Received: from mhs060cnc.rim.net (mhs060cnc.rim.net [208.65.73.34]) by ietfa.amsl.com (Postfix) with ESMTP id A419C21F99E3 for <ietf@ietf.org>; Sun, 21 Jul 2013 00:04:10 -0700 (PDT)
X-AuditID: 0a41282f-b7f9b6d000002847-27-51eb87df2c8a
Received: from XCT101ADS.rim.net (xct101ads.rim.net [10.67.111.42]) by mhs060cnc.rim.net (SBG) with SMTP id 9A.91.10311.FD78BE15; Sun, 21 Jul 2013 02:03:59 -0500 (CDT)
Received: from XMB104ADS.rim.net ([fe80::2494:a63d:e3:723b]) by XCT101ADS.rim.net ([fe80::2c7e:1215:d554:35b5%20]) with mapi id 14.02.0328.009; Sun, 21 Jul 2013 02:03:58 -0500
From: Andrew Allen <aallen@blackberry.com>
To: "sm+ietf@elandsys.com" <sm+ietf@elandsys.com>, "john@jck.com" <john@jck.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
Thread-Topic: Last call: draft-montemurro-gsma-imei-urn-16.txt
Thread-Index: AQHOhJEO4fYTwuVTOkCw8MDTXs0bMZlsOFEcgAGJd4CAACLcBIAAViUAgABx1gCAAChDAP//4utk
Date: Sun, 21 Jul 2013 07:03:57 +0000
Message-ID: <BBF5DDFE515C3946BC18D733B20DAD2338DD2606@XMB104ADS.rim.net>
In-Reply-To: <6.2.5.6.2.20130720193906.06cdd008@resistor.net>
Accept-Language: en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.67.110.252]
Content-Type: text/plain; charset="iso-8859-1"
content-transfer-encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrOKsWRmVeSWpSXmKPExsXC5ZyvpXu//XWgweVuCYtnG+ezWFw+uYbd 4lX/TVaLpX/msziweNx785HJY8mSn0wel1e+Zva4tHQycwBLVAOjTVJiSVlwZnqevp1NYl5e fkliSapCSmpxsq2ST2p6Yo5CQFFmWWJypYJLZnFyTmJmbmqRkkJmiq2SiZJCQU5icmpual6J rVJiQUFqXoqSHZcCBrABKsvMU0jNS85PycxLt1XyDPbXtbAwtdQ1VLLTTejkydj9nb3gv1BF z+ptzA2Mp/m7GDk4JARMJB7+y+pi5AQyxSQu3FvP1sXIxSEksJJRomfVYihnM6PEs7WzWUCq 2AS0JPYfns4EYosIBEl8e3cTzGYWCJFY/OIBO4gtLGArcfn0H0aIGjuJ7wcvsUDYURI/vt8D q2ERUJV4/uIsC8gRvAIeEucOgJVzArUuWjURbCSjgKzE7rPXocaLS9x6Mp8J4lABiSV7zjND 2KISLx//Y4WwFSUet3SzQNTrSdyYOoUNwtaWWLbwNVg9r4CgxMmZT1gmMIrOQjJ2FpKWWUha ZiFpWcDIsopRMDej2MDMIDkvWa8oM1cvL7VkEyMoZThq6O9gfPve4hCjAAejEg/vrsbXgUKs iWXFlbmHGCU4mJVEeG/HAoV4UxIrq1KL8uOLSnNSiw8xugIDYiKzFHdyPjCd5ZXEGxsY4OYo ifNanT0bKCSQDkw82ampBalFMHOYODhB9nBJiRQD00dqUWJpSUY8KMnFFwPTnFQD49UVRq5P IowCppUe1Xn+WGjOvwKTOezBs81++6evqlxy0tHuwKdE9ukWRQcv7PQ7Mvn1znVhAicTv5cb HnBJV1n6Jjx7ie/BA+Yfkxicnz15oXNm+mGGWbb7Pu8zSPw712jT1Noj7+5Gy7/lZH932S8o ZiHHNnbN/+x1V21TWDPeyK/NsVLgWqbEUpyRaKjFXFScCAD7CzXTWgMAAA==
Cc: "tbray@textuality.com" <tbray@textuality.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Jul 2013 07:04:16 -0000

The reason why the IMEI namespace is being registered as a GSMA namespace an=
d not as part of the 3GPP namespace is that the GSMA has the responsibility=
 for IMEI assignment and hence in maintaining uniqueness of the namespace. I=
t has nothing to do with IPR which was extensively discussed on the dispatch=
 list.

The primary purpose of the IMEI is for preventing use of stolen mobile phone=
s and enabling emergency calls to be made from mobiles that don't have a val=
id subscription. 

Andrew



----- Original Message -----
From: S Moonesamy [mailto:sm+ietf@elandsys.com]
Sent: Saturday, July 20, 2013 10:48 PM Central Standard Time=0A=
To: John C Klensin <john@jck.com>
Cc: Tim Bray <tbray@textuality.com>; ietf@ietf.org <ietf@ietf.org>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt

Hi John,
At 18:23 20-07-2013, John C Klensin wrote:
>See my earlier note, but mostly to aid in getting the
>documentation right.  For example, to the extent that the recent
>discussion results in a more complete treatment of privacy
>and/or security considerations in the documentation, that is a
>net improvement and added value.

There was a Last Call for draft-montemurro-gsma-imei-urn-01 in 
2007.  The draft was sponsored by an Apps 
AD.  draft-montemurro-gsma-imei-urn-04 was evaluated (I did not 
verify the details) in 2009.  An IPR disclosure, about a patent filed 
several years ago, was filed after that evaluation.  The DISCUSS got 
cleared automatically.  draft-montemurro-gsma-imei-urn-08  was 
dispatched to RAI in 2011.

3GPP was assigned a URN in 2008.  The shepherd write-up 
for  draft-montemurro-gsma-imei-urn-16 mentions that "this document 
is required for the 3GPP/IMS specification, thus any
vendor that implements the 3GPP specifications follows this 
specification".  The significant difference between the 3GPP URN and 
the requested GSMA URN is that there is an IPR disclosure on that latter.

One of the questions asked by Tim Bray was about the WiFi-only 
scenario.  That was raised previously through a DISCUSS as the softphone iss=
ue.

The privacy discussion might cause some discontent.  As for whether 
the draft will gain consensus, well, what can I say; if it is the 
consensus of the IETF to support state-sponsored surveillance there 
is nothing I can do about it. :-)

Regards,
S. Moonesamy 


---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential infor=
mation, privileged material (including material protected by the solicitor-c=
lient or other applicable privileges), or constitute non-public information.=
 Any use of this information by anyone other than the intended recipient is=
 prohibited. If you have received this transmission in error, please immedia=
tely reply to the sender and delete this information from your system. Use,=
 dissemination, distribution, or reproduction of this transmission by uninte=
nded recipients is not authorized and may be unlawful.

From prvs=6914b84e8f=aallen@blackberry.com  Sun Jul 21 00:12:49 2013
Return-Path: <prvs=6914b84e8f=aallen@blackberry.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8550321E8087 for <ietf@ietfa.amsl.com>; Sun, 21 Jul 2013 00:12:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.518
X-Spam-Level: 
X-Spam-Status: No, score=-5.518 tagged_above=-999 required=5 tests=[AWL=-0.315, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1l8lZzdvcI1i for <ietf@ietfa.amsl.com>; Sun, 21 Jul 2013 00:12:36 -0700 (PDT)
Received: from mhs061cnc.rim.net (mhs061cnc.rim.net [208.65.73.35]) by ietfa.amsl.com (Postfix) with ESMTP id 29BA111E80F2 for <ietf@ietf.org>; Sun, 21 Jul 2013 00:12:36 -0700 (PDT)
X-AuditID: 0a412830-b7fa06d000003f99-74-51eb89e3981a
Received: from XCT101ADS.rim.net (xct101ads.rim.net [10.67.111.42]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by mhs061cnc.rim.net (SBG) with SMTP id 1A.4E.16281.3E98BE15; Sun, 21 Jul 2013 02:12:35 -0500 (CDT)
Received: from XMB104ADS.rim.net ([fe80::2494:a63d:e3:723b]) by XCT101ADS.rim.net ([fe80::2c7e:1215:d554:35b5%20]) with mapi id 14.02.0328.009; Sun, 21 Jul 2013 02:12:34 -0500
From: Andrew Allen <aallen@blackberry.com>
To: "sm+ietf@elandsys.com" <sm+ietf@elandsys.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
Thread-Topic: Last call: draft-montemurro-gsma-imei-urn-16.txt
Thread-Index: AQHOhJEO4fYTwuVTOkCw8MDTXs0bMZlsOFEcgAGJd4CAACLcBIAAViUA///RAKSAADTH24AAeaUm
Date: Sun, 21 Jul 2013 07:12:34 +0000
Message-ID: <BBF5DDFE515C3946BC18D733B20DAD2338DD261D@XMB104ADS.rim.net>
In-Reply-To: <6.2.5.6.2.20130720155920.06cc9ce0@elandnews.com>
Accept-Language: en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.67.110.252]
Content-Type: text/plain; charset="iso-8859-1"
content-transfer-encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrCKsWRmVeSWpSXmKPExsXC5Zyvpfu483WgwdlTyhZ/129msXi2cT6L xbsdh9ksXvXfZLVY+mc+iwOrx703H5k8ds66y+6xZMlPJo9LSycze3y5/JktgDWqgdEmKbGk LDgzPU/fziYxLy+/JLEkVSEltTjZVsknNT0xRyGgKLMsMblSwSWzODknMTM3tUhJITPFVslE SaEgJzE5NTc1r8RWKbGgIDUvRcmOSwED2ACVZeYppOYl56dk5qXbKnkG++taWJha6hoq2ekm dPJkXJjzjb3gClfFwrbdjA2M/zi6GDk5JARMJNbc/MsOYYtJXLi3nq2LkYtDSKCNSeLm1j1Q zmZGiY+vTzCCVLEJaEnsPzydqYuRg0NEwFDi8GxtkBpmgQ+MEp8+XgGbJCxgK3H59B+wehEB O4nvBy+xQNhREidn7gWzWQRUJdqenWQFsXkFPCQO3PnNBGJzAtV/mbUELM4oICux++x1sDiz gLjErSfzmSAuFZBYsuc8M4QtKvHy8T9WCFtR4nFLNwtEvZ7EjalT2CBsbYllC18zQ+wSBLrh CcsERtFZSMbOQtIyC0nLLCQtCxhZVjEK5mYUG5gZJucl6xVl5urlpZZsYgQlE0cNgx2M799b HGIU4GBU4uHVrn8dKMSaWFZcmXuIUYKDWUmEV7cDKMSbklhZlVqUH19UmpNafIjRFRgSE5ml uJPzgYkuryTe2MAAN0dJnNf67NlAIYF0YPrJTk0tSC2CmcPEwQmyh0tKpBiYRFKLEktLMuJB qS6+GJjspBoYWQy0eFRC5faW3Df847ekx2zV9HWdJj9e+S384uj87cnjQ2ffBiZ9uhj80+BG SKyNgM/qtcs5zySKKNRoM8Z+DnLP35b5Lya2/8jqhva4/b2PqmKTWRxOr/+02zVI+Vf4heQJ P9ZcUpyybIL97jtLipS5Hj73nXpCL+72Cye1f+v3qEv+zhKYpcRSnJFoqMVcVJwIALagl0Bn AwAA
Cc: "tbray@textuality.com" <tbray@textuality.com>, "ietf@ietf.org" <ietf@ietf.org>, "draft-montemurro-gsma-imei-urn.all@tools.ietf.org" <draft-montemurro-gsma-imei-urn.all@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Jul 2013 07:12:49 -0000

http://datatracker.ietf.org/doc/draft-allen-dispatch-imei-urn-as-instanceid=
 is also required in order to use the IMEI as a SIP instance ID. So just not=
 registering the sub namespace doesn't avoid the IETF having to address the=
 issue.

As John pointed out having the sub namespace reviewed by IETF provides the o=
pportunity to add text to address privacy concerns with any inappropriate us=
age.


----- Original Message -----
From: S Moonesamy [mailto:sm+ietf@elandsys.com]
Sent: Saturday, July 20, 2013 06:50 PM Central Standard Time=0A=
To: Andrew Allen
Cc: scott.brim@gmail.com <scott.brim@gmail.com>; sm+ietf@elandsys.com <sm+ie=
tf@elandsys.com>; ietf@ietf.org <ietf@ietf.org>; tbray@textuality.com <tbray=
@textuality.com>; draft-montemurro-gsma-imei-urn.all@tools.ietf.org <draft-m=
ontemurro-gsma-imei-urn.all@tools.ietf.org>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt

Hi Andrew,
At 13:48 20-07-2013, Andrew Allen wrote:
>I think IANA registration of namespaces has a lot of value.

draft-montemurro-gsma-imei-urn-16 discusses about two namespaces:

  (i)  gsma

  (ii) imei

It is not possible to get a IANA registration for (ii) as according 
to draft-montemurro-gsma-imei-urn-16 (ii) is managed by (i).  In 
simple terms (ii) does not require IETF approval.

Regards,
S. Moonesamy 


---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential infor=
mation, privileged material (including material protected by the solicitor-c=
lient or other applicable privileges), or constitute non-public information.=
 Any use of this information by anyone other than the intended recipient is=
 prohibited. If you have received this transmission in error, please immedia=
tely reply to the sender and delete this information from your system. Use,=
 dissemination, distribution, or reproduction of this transmission by uninte=
nded recipients is not authorized and may be unlawful.

From prvs=4914dd5bcc=aallen@blackberry.com  Sun Jul 21 00:37:40 2013
Return-Path: <prvs=4914dd5bcc=aallen@blackberry.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F378A21F9E12 for <ietf@ietfa.amsl.com>; Sun, 21 Jul 2013 00:37:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.196
X-Spam-Level: 
X-Spam-Status: No, score=-6.196 tagged_above=-999 required=5 tests=[AWL=0.402,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BwhPaCdWOsKJ for <ietf@ietfa.amsl.com>; Sun, 21 Jul 2013 00:37:35 -0700 (PDT)
Received: from mhs060cnc.rim.net (mhs060cnc.rim.net [208.65.73.34]) by ietfa.amsl.com (Postfix) with ESMTP id 6E5EF21F9DFA for <ietf@ietf.org>; Sun, 21 Jul 2013 00:37:35 -0700 (PDT)
X-AuditID: 0a41282f-b7f9b6d000002847-b9-51eb8fb15299
Received: from XCT101ADS.rim.net (xct101ads.rim.net [10.67.111.42]) by mhs060cnc.rim.net (SBG) with SMTP id 50.B1.10311.1BF8BE15; Sun, 21 Jul 2013 02:37:22 -0500 (CDT)
Received: from XMB104ADS.rim.net ([fe80::2494:a63d:e3:723b]) by XCT101ADS.rim.net ([fe80::2c7e:1215:d554:35b5%20]) with mapi id 14.02.0328.009; Sun, 21 Jul 2013 02:37:21 -0500
From: Andrew Allen <aallen@blackberry.com>
To: "tbray@textuality.com" <tbray@textuality.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
Thread-Topic: Last call: draft-montemurro-gsma-imei-urn-16.txt
Thread-Index: AQHOhJEO4fYTwuVTOkCw8MDTXs0bMZlsItsKgABZfICAAYRS+oAAYPKA///D5waAAHA2AP///EWKgAAvJFE=
Date: Sun, 21 Jul 2013 07:37:20 +0000
Message-ID: <BBF5DDFE515C3946BC18D733B20DAD2338DD265C@XMB104ADS.rim.net>
In-Reply-To: <BBF5DDFE515C3946BC18D733B20DAD2338DD24D0@XMB104ADS.rim.net>
Accept-Language: en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.67.110.252]
Content-Type: multipart/alternative; boundary="_000_BBF5DDFE515C3946BC18D733B20DAD2338DD265CXMB104ADSrimnet_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrFKsWRmVeSWpSXmKPExsXC5Zyvpbup/3WgwZn5jBbPNs5nsVj6Zz6L A5PHkiU/mTwuLZ3MHMAU1cBok5RYUhacmZ6nb2eTmJeXX5JYkqqQklqcbKvkk5qemKMQUJRZ lphcqeCSWZyck5iZm1qkpJCZYqtkoqRQkJOYnJqbmldiq5RYUJCal6Jkx6WAAWyAyjLzFFLz kvNTMvPSbZU8g/11LSxMLXUNlex0Ezp5Mpb0fGcqeDKZseLg48lsDYxv+hm7GDk4JARMJLbP 0O5i5AQyxSQu3FvP1sXIxSEksJJR4v2MoywQzmZGiZMb1rGCVLEJaEnsPzydCaRZRMBQYtFe L5Aws4CyxNNNc5hAbGEBW4nLp/8wgtgiAnYS3w9eYoGwkyT27t8FZrMIqErs2/IMbCSvgIfE /dMf2UBsTgFPiTeTVoPVMArISuw+e50JYr64xK0n85kgDhWQWLLnPDOELSrx8vE/VghbUeJx SzcLRH2+xJFLb9gg5gtKnJz5hGUCo8gsJKNmISmbhaRsFtBnzAKaEut36UOUKEpM6X7IDmFr SLTOmcuOLL6AkX0Vo2BuRrGBmUFyXrJeUWauXl5qySZGUPpw1NDfwfj2vcUhRgEORiUe3l2N rwOFWBPLiitzDzFKcDArifDqdgCFeFMSK6tSi/Lji0pzUosPMQYBA2gisxR3cj4wteWVxBsb GBDJURLntTp7NlBIIB2YxrJTUwtSi2CGMnFwgizlkhIpBiaj1KLE0pKMeFDKjC8GJk2pBsYl /78ml7VvELl6JEVTWOVWkvZpt59SFXMFpd7V1gnHexTfmH7r6f/KZwHyO1qbvTOC+w62n1eo N9qd9KYiLzGSofekzq2EYMlY5rSewNokP6vI7m0chx6c2jW/Kj2Ja/fWNy37botF+3cdvrlP 0U6QL70xLHOLlYvvyiN33y3LmjbZyibytxJLcUaioRZzUXEiAOx8r/VtAwAA
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Jul 2013 07:37:40 -0000

--_000_BBF5DDFE515C3946BC18D733B20DAD2338DD265CXMB104ADSrimnet_
Content-Type: text/plain; charset="utf-8"
content-transfer-encoding: base64

DQpUaW0NCg0KU2VlbXMgdGhlIHRleHQgZ290IG11bmdlZCB3aXRoIHNvbWUgY29weSBwYXN0
aW5nIHNvIGhlcmUgaXQgaXMgY29ycmVjdGVkOg0KDQpGaXJzdGx5IGFzIHN0YXRlZCBpbg0K
aHR0cDovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1hbGxlbi1kaXNwYXRjaC1p
bWVpLXVybi1hcy1pbnN0YW5jZWlkLw0KdGhlIHVzZSBvZiB0aGUgSU1FSSBhcyBhIFNJUCBJ
bnN0YW5jZSBJRCBvbmx5IHBlcnRhaW5zIHRvIHVzYWdlIG9mIFNJUCB3aXRoIHRoZSAzR1BQ
IElNUyBhbmQgaWYgYSBkZXZpY2UgaXMgbm90IHVzaW5nIElNUyB3aXRob3V0IGFuIElNRUkg
dGhlbiBpdCB3aWxsIHVzZSBhIFVVSUQgYXMgdGhlIFNJUCBpbnN0YW5jZSBJRCBhcyBwZXIg
UkZDIDU2MjYuIElmIGEgZGV2aWNlIHdpdGhvdXQgYW4gSU1FSSB1c2VzIElNUyB0aGVuIGl0
IHdpbGwgYWxzbyBzdGlsbCB1c2UgYSBVVUlEIGFzIHRoZSBTSVAgaW5zdGFuY2UgSUQgYXMg
cGVyIFJGQyA1NjI2LiBUaGlzIGlzIHNwZWNpZmllZCBhbHNvIGluIHRoZSAzR1BQIElNUyBz
cGVjaWZpY2F0aW9uIFRTIDI0LjIyOSBhcyB3ZWxsIGFzIHRoZSBhYm92ZSBkcmFmdC4NCg0K
U28gYXBwbGljYXRpb25zIHJ1bm5pbmcgb24gZGV2aWNlcyB0aGF0IGRvbid0IGhhdmUgYW4g
SU1FSSBjYW4gc3RpbGwgdXNlIFNJUCBmb3Igc2Vzc2lvbnMuDQoNClRoZSBJTUVJIHdoaWNo
IGhhcyBiZWVuIHVzZWQgaW4gbW9iaWxlIGRldmljZXMgZm9yIDIwIHllYXJzIGFsc28gc3Vy
dml2ZXMgZGV2aWNlIHdpcGVzIGZvciB0aGUgY2lyY3VpdCBzd2l0Y2hlZCBjYWxsaW5nIGNh
cGFiaWxpdHkgYXMgdXNlZCBieSBiaWxsaW9ucyBvZiBtb2JpbGVzIHRvZGF5IHdpdGggMkcg
YW5kIDNHIG5ldHdvcmtzLiBTbyBhZ2FpbiBob3cgaXMgdGhpcyBtb3JlIGhhcm1mdWwgZm9y
IDRHIHRoYW4gdGhlIGN1cnJlbnQgc2l0dWF0aW9uIHdpdGggMkcgYW5kIDNHIGlmIGEgbW9i
aWxlIGRldmljZSBpcyB0cmFuc2ZlcnJlZCB0byBhIG5ldyBvd25lcj8NCg0KQW5kcmV3DQoN
Cg0KDQpGcm9tOiBBbmRyZXcgQWxsZW4gW21haWx0bzphYWxsZW5AYmxhY2tiZXJyeS5jb21d
DQpTZW50OiBTYXR1cmRheSwgSnVseSAyMCwgMjAxMyAxMTo0OCBQTSBDZW50cmFsIFN0YW5k
YXJkIFRpbWUNClRvOiB0YnJheUB0ZXh0dWFsaXR5LmNvbSA8dGJyYXlAdGV4dHVhbGl0eS5j
b20+DQpDYzogaWV0ZkBpZXRmLm9yZyA8aWV0ZkBpZXRmLm9yZz4NClN1YmplY3Q6IFJlOiBM
YXN0IGNhbGw6IGRyYWZ0LW1vbnRlbXVycm8tZ3NtYS1pbWVpLXVybi0xNi50eHQNCg0KDQpU
aW0NCg0KRmlyc3RseSBhcyBzdGF0ZWQgaW4NCmh0dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9y
Zy9kb2MvZHJhZnQtYWxsZW4tZGlzcGF0Y2gtaW1laS11cm4tYXMtaW5zdGFuY2VpZC8NCnRo
ZSB1c2Ugb2YgdGhlIElNRUkgYXMgYSBTSVAgSW5zdGFuY2UgSUQgb25seSBwZXJ0YWlucyB0
byB1c2FnZSBvZiBTSVAgd2l0aCB0aGUgM0dQUCBJTVMgYW5kIGlmIGEgZGV2aWNlIGlzIG5v
dCB1c2luZyBJTVMgc2luZyBJTVMgd2l0aG91dCBhbiBJTUVJIHVzZXMgSU1TIHRoZW4gaXQg
d2lsbCBzdGlsbCB1c2UgYSBVVUlEIGFzIHRoZSBTSVAgaW5zdGFuY2UgSUQgYXMgcGVyIFJG
QyA1NjI2LiBJZiBhIGRldmljZSB3aXRob3V0IGFuIElNRUkgdXNlcyBJTVMgdGhlbiBpdCB3
aWxsIGFsc28gc3RpbGwgdXNlIGEgVVVJRCBhcyB0aGUgU0lQIGluc3RhbmNlIElEIGFzIHBl
ciBSRkMgNTYyNi4gVGhpcyBpcyBzcGVjaWZpZWQgYWxzbyBpbiB0aGUgM0dQUCBJTVMgc3Bl
Y2lmaWNhdGlvbiBUUyAyNC4yMjkgYXMgd2VsbCBhcyB0aGUgYWJvdmUgZHJhZnQuDQoNClNv
IGFwcGxpY2F0aW9ucyBydW5uaW5nIG9uIGRldmljZXMgdGhhdCBkb24ndCBoYXZlIGFuIElN
RUkgY2FuIHN0aWxsIHVzZSBTSVAgZm9yIHNlc3Npb25zLg0KDQpUaGUgSU1FSSB3aGljaCBo
YXMgYmVlbiB1c2VkIGluIG1vYmlsZSBkZXZpY2VzIGZvciAyMCB5ZWFycyBhbHNvIHN1cnZp
dmVzIGRldmljZSB3aXBlcyBmb3IgdGhlIGNpcmN1aXQgc3dpdGNoZWQgY2FsbGluZyBjYXBh
YmlsaXR5IGFzIHVzZWQgYnkgYmlsbGlvbnMgb2YgbW9iaWxlcyB0b2RheSB3aXRoIDJHIGFu
ZCAzRyBuZXR3b3Jrcy4gU28gYWdhaW4gaG93IGlzIHRoaXMgbW9yZSBoYXJtZnVsIGZvciA0
RyB0aGFuIHRoZSBjdXJyZW50IHNpdHVhdGlvbiB3aXRoIDJHIGFuZCAzRyBpZiBhIG1vYmls
ZSBkZXZpY2UgaXMgdHJhbnNmZXJyZWQgdG8gYSBuZXcgb3duZXI/DQoNCkFuZHJldw0KDQpG
cm9tOiBUaW0gQnJheSBbbWFpbHRvOnRicmF5QHRleHR1YWxpdHkuY29tXQ0KU2VudDogU2F0
dXJkYXksIEp1bHkgMjAsIDIwMTMgMDc6MDEgUE0gQ2VudHJhbCBTdGFuZGFyZCBUaW1lDQpU
bzogQW5kcmV3IEFsbGVuDQpDYzogc2NvdHQuYnJpbUBnbWFpbC5jb20gPHNjb3R0LmJyaW1A
Z21haWwuY29tPjsgaWV0ZkBpZXRmLm9yZyA8aWV0ZkBpZXRmLm9yZz4NClN1YmplY3Q6IFJl
OiBMYXN0IGNhbGw6IGRyYWZ0LW1vbnRlbXVycm8tZ3NtYS1pbWVpLXVybi0xNi50eHQNCg0K
T24gU2F0LCBKdWwgMjAsIDIwMTMgYXQgMzoyMCBQTSwgQW5kcmV3IEFsbGVuIDxhYWxsZW5A
YmxhY2tiZXJyeS5jb208bWFpbHRvOmFhbGxlbkBibGFja2JlcnJ5LmNvbT4+IHdyb3RlOg0K
Q2FuIGl0IHBsZWFzZSBiZSBleHBsYWluZWQgaG93IHRoZSBJTUVJIFVSTiB3aGVuIHVzZWQg
YXMgc3RhdGVkIGluIGh0dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtYWxs
ZW4tZGlzcGF0Y2gtaW1laS11cm4tYXMtaW5zdGFuY2VpZC8NCklzIGFueSBtb3JlIGhhcm1m
dWwgdGhhbiBhcyB0aGUgSU1FSSBpcyB1c2VkIHRvZGF5IGJ5IG92ZXIgOTAlIG9mIG1vYmls
ZSBwaG9uZXMgaW4gdXNlIHRvZGF5IHdvcmxkd2lkZT8NCg0KSXQgc3Vydml2ZXMgZGV2aWNl
IHdpcGVzLCB3aGljaCB1c3VhbGx5IGhhcHBlbiB1cG9uIGNoYW5nZSBvZiBkZXZpY2Ugb3du
ZXJzaGlwLg0KDQpJ4oCZbSBub3QgYW4gZXhwZXJ0IGluIHlvdXIgYXBwbGljYXRpb24gZG9t
YWluLCBzbyBwYXJkb24gbWUgaWYgdGhpcyBxdWVzdGlvbiBpcyBob3BlbGVzc2x5IG5haXZl
OiBJdCBzZWVtcyB0aGF0IHRoaXMgaWRlbnRpZmllciBpcyByZWxhdGVkIGluIHNvbWUgd2F5
IHRvIFNJUCBzZXNzaW9ucy4gIEl0IHNlZW1zIHRoYXQgaXQgd291bGQgYmUgYSBjb21tb24g
b3BlcmF0aW9uIHRvIGxhdW5jaCBhIFNJUCBzZXNzaW9uIG9uIGEgZGV2aWNlIHN1Y2ggYXMg
YSBXaUZpLW9ubHkgdGFibGV0LCBvciBhbiBpUG9kIHRvdWNoLCB0aGF0IGRvZXNu4oCZdCBo
YXZlIGFuIElNRUkuICBJcyB0aGlzIGEgcHJvYmxlbT8NCg0KIC1UDQoNCg0KQW5kcmV3DQoN
Ci0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0NCkZyb206IFNjb3R0IEJyaW0gW21haWx0
bzpzY290dC5icmltQGdtYWlsLmNvbTxtYWlsdG86c2NvdHQuYnJpbUBnbWFpbC5jb20+XQ0K
U2VudDogU2F0dXJkYXksIEp1bHkgMjAsIDIwMTMgMDM6NTUgUE0gQ2VudHJhbCBTdGFuZGFy
ZCBUaW1lDQpUbzogQW5kcmV3IEFsbGVuDQpDYzogdGJyYXlAdGV4dHVhbGl0eS5jb208bWFp
bHRvOnRicmF5QHRleHR1YWxpdHkuY29tPiA8dGJyYXlAdGV4dHVhbGl0eS5jb208bWFpbHRv
OnRicmF5QHRleHR1YWxpdHkuY29tPj47IGlldGZAaWV0Zi5vcmc8bWFpbHRvOmlldGZAaWV0
Zi5vcmc+IDxpZXRmQGlldGYub3JnPG1haWx0bzppZXRmQGlldGYub3JnPj4NClN1YmplY3Q6
IFJlOiBMYXN0IGNhbGw6IGRyYWZ0LW1vbnRlbXVycm8tZ3NtYS1pbWVpLXVybi0xNi50eHQN
Cg0KT24gU2F0LCBKdWwgMjAsIDIwMTMgYXQgNDowOCBQTSwgQW5kcmV3IEFsbGVuIDxhYWxs
ZW5AYmxhY2tiZXJyeS5jb208bWFpbHRvOmFhbGxlbkBibGFja2JlcnJ5LmNvbT4+IHdyb3Rl
Og0KPiBUaW0NCj4NCj4gVGhlIHF1b3RlIGlzIGZyb20gUkZDIDU2MjYgd2hpY2ggYWxzbyBz
dGF0ZXM6DQo+DQo+ICIzLjEuIFN1bW1hcnkgb2YgTWVjaGFuaXNtDQo+DQo+IEVhY2ggVUEg
aGFzIGEgdW5pcXVlIGluc3RhbmNlLWlkIHRoYXQgc3RheXMgdGhlIHNhbWUgZm9yIHRoaXMg
VUEgZXZlbiBpZiB0aGUNCj4gVUEgcmVib290cyBvciBpcyBwb3dlciBjeWNsZWQuIg0KPg0K
PiBTaW5jZSB0aGUgVVVJRCBpbiB0aGUgaW5zdGFuY2UgSUQgaXMgYWxzbyBzdGF0aWMgaG93
IGlzIHRoaXMgc2lnbmlmaWNhbnRseQ0KPiBkaWZmZXJlbnQgaW4gdGVybXMgb2YgcHJpdmFj
eSBjb25jZXJucyBmcm9tIHRoZSBJTUVJIGJlaW5nIHVzZWQgYXMgYW4NCj4gaW5zdGFuY2Ug
SUQ/DQoNCllvdSdyZSBub3QgZGVtb25zdHJhdGluZyB0aGF0IGFuIElNRUkgaXMganVzdCBh
cyBnb29kLCB5b3UncmUNCmRlbW9uc3RyYXRpbmcgdGhhdCBhIFVVSUQgaXMganVzdCBhcyBi
YWQuDQoNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KVGhpcyB0cmFuc21pc3Npb24gKGluY2x1ZGluZyBh
bnkgYXR0YWNobWVudHMpIG1heSBjb250YWluIGNvbmZpZGVudGlhbCBpbmZvcm1hdGlvbiwg
cHJpdmlsZWdlZCBtYXRlcmlhbCAoaW5jbHVkaW5nIG1hdGVyaWFsIHByb3RlY3RlZCBieSB0
aGUgc29saWNpdG9yLWNsaWVudCBvciBvdGhlciBhcHBsaWNhYmxlIHByaXZpbGVnZXMpLCBv
ciBjb25zdGl0dXRlIG5vbi1wdWJsaWMgaW5mb3JtYXRpb24uIEFueSB1c2Ugb2YgdGhpcyBp
bmZvcm1hdGlvbiBieSBhbnlvbmUgb3RoZXIgdGhhbiB0aGUgaW50ZW5kZWQgcmVjaXBpZW50
IGlzIHByb2hpYml0ZWQuIElmIHlvdSBoYXZlIHJlY2VpdmVkIHRoaXMgdHJhbnNtaXNzaW9u
IGluIGVycm9yLCBwbGVhc2UgaW1tZWRpYXRlbHkgcmVwbHkgdG8gdGhlIHNlbmRlciBhbmQg
ZGVsZXRlIHRoaXMgaW5mb3JtYXRpb24gZnJvbSB5b3VyIHN5c3RlbS4gVXNlLCBkaXNzZW1p
bmF0aW9uLCBkaXN0cmlidXRpb24sIG9yIHJlcHJvZHVjdGlvbiBvZiB0aGlzIHRyYW5zbWlz
c2lvbiBieSB1bmludGVuZGVkIHJlY2lwaWVudHMgaXMgbm90IGF1dGhvcml6ZWQgYW5kIG1h
eSBiZSB1bmxhd2Z1bC4NCg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQpUaGlzIHRyYW5zbWlzc2lvbiAo
aW5jbHVkaW5nIGFueSBhdHRhY2htZW50cykgbWF5IGNvbnRhaW4gY29uZmlkZW50aWFsIGlu
Zm9ybWF0aW9uLCBwcml2aWxlZ2VkIG1hdGVyaWFsIChpbmNsdWRpbmcgbWF0ZXJpYWwgcHJv
dGVjdGVkIGJ5IHRoZSBzb2xpY2l0b3ItY2xpZW50IG9yIG90aGVyIGFwcGxpY2FibGUgcHJp
dmlsZWdlcyksIG9yIGNvbnN0aXR1dGUgbm9uLXB1YmxpYyBpbmZvcm1hdGlvbi4gQW55IHVz
ZSBvZiB0aGlzIGluZm9ybWF0aW9uIGJ5IGFueW9uZSBvdGhlciB0aGFuIHRoZSBpbnRlbmRl
ZCByZWNpcGllbnQgaXMgcHJvaGliaXRlZC4gSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyB0
cmFuc21pc3Npb24gaW4gZXJyb3IsIHBsZWFzZSBpbW1lZGlhdGVseSByZXBseSB0byB0aGUg
c2VuZGVyIGFuZCBkZWxldGUgdGhpcyBpbmZvcm1hdGlvbiBmcm9tIHlvdXIgc3lzdGVtLiBV
c2UsIGRpc3NlbWluYXRpb24sIGRpc3RyaWJ1dGlvbiwgb3IgcmVwcm9kdWN0aW9uIG9mIHRo
aXMgdHJhbnNtaXNzaW9uIGJ5IHVuaW50ZW5kZWQgcmVjaXBpZW50cyBpcyBub3QgYXV0aG9y
aXplZCBhbmQgbWF5IGJlIHVubGF3ZnVsLg0KDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NClRoaXMgdHJh
bnNtaXNzaW9uIChpbmNsdWRpbmcgYW55IGF0dGFjaG1lbnRzKSBtYXkgY29udGFpbiBjb25m
aWRlbnRpYWwgaW5mb3JtYXRpb24sIHByaXZpbGVnZWQgbWF0ZXJpYWwgKGluY2x1ZGluZyBt
YXRlcmlhbCBwcm90ZWN0ZWQgYnkgdGhlIHNvbGljaXRvci1jbGllbnQgb3Igb3RoZXIgYXBw
bGljYWJsZSBwcml2aWxlZ2VzKSwgb3IgY29uc3RpdHV0ZSBub24tcHVibGljIGluZm9ybWF0
aW9uLiBBbnkgdXNlIG9mIHRoaXMgaW5mb3JtYXRpb24gYnkgYW55b25lIG90aGVyIHRoYW4g
dGhlIGludGVuZGVkIHJlY2lwaWVudCBpcyBwcm9oaWJpdGVkLiBJZiB5b3UgaGF2ZSByZWNl
aXZlZCB0aGlzIHRyYW5zbWlzc2lvbiBpbiBlcnJvciwgcGxlYXNlIGltbWVkaWF0ZWx5IHJl
cGx5IHRvIHRoZSBzZW5kZXIgYW5kIGRlbGV0ZSB0aGlzIGluZm9ybWF0aW9uIGZyb20geW91
ciBzeXN0ZW0uIFVzZSwgZGlzc2VtaW5hdGlvbiwgZGlzdHJpYnV0aW9uLCBvciByZXByb2R1
Y3Rpb24gb2YgdGhpcyB0cmFuc21pc3Npb24gYnkgdW5pbnRlbmRlZCByZWNpcGllbnRzIGlz
IG5vdCBhdXRob3JpemVkIGFuZCBtYXkgYmUgdW5sYXdmdWwuDQo=

--_000_BBF5DDFE515C3946BC18D733B20DAD2338DD265CXMB104ADSrimnet_
Content-Type: text/html; charset="utf-8"
content-transfer-encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5Pg0KPGZvbnQg
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxicj4NClRpbTxicj4N
Cjxicj4NClNlZW1zIHRoZSB0ZXh0IGdvdCBtdW5nZWQgd2l0aCBzb21lIGNvcHkgcGFzdGlu
ZyBzbyBoZXJlIGl0IGlzIGNvcnJlY3RlZDo8YnI+DQo8YnI+DQpGaXJzdGx5IGFzIHN0YXRl
ZCBpbjxicj4NCmh0dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtYWxsZW4t
ZGlzcGF0Y2gtaW1laS11cm4tYXMtaW5zdGFuY2VpZC88YnI+DQp0aGUgdXNlIG9mIHRoZSBJ
TUVJIGFzIGEgU0lQIEluc3RhbmNlIElEIG9ubHkgcGVydGFpbnMgdG8gdXNhZ2Ugb2YgU0lQ
IHdpdGggdGhlIDNHUFAgSU1TIGFuZCBpZiBhIGRldmljZSBpcyBub3QgdXNpbmcgSU1TIHdp
dGhvdXQgYW4gSU1FSSB0aGVuIGl0IHdpbGwgdXNlIGEgVVVJRCBhcyB0aGUgU0lQIGluc3Rh
bmNlIElEIGFzIHBlciBSRkMgNTYyNi4gSWYgYSBkZXZpY2Ugd2l0aG91dCBhbiBJTUVJIHVz
ZXMgSU1TIHRoZW4gaXQgd2lsbCBhbHNvDQogc3RpbGwgdXNlIGEgVVVJRCBhcyB0aGUgU0lQ
IGluc3RhbmNlIElEIGFzIHBlciBSRkMgNTYyNi4gVGhpcyBpcyBzcGVjaWZpZWQgYWxzbyBp
biB0aGUgM0dQUCBJTVMgc3BlY2lmaWNhdGlvbiBUUyAyNC4yMjkgYXMgd2VsbCBhcyB0aGUg
YWJvdmUgZHJhZnQuPGJyPg0KPGJyPg0KU28gYXBwbGljYXRpb25zIHJ1bm5pbmcgb24gZGV2
aWNlcyB0aGF0IGRvbid0IGhhdmUgYW4gSU1FSSBjYW4gc3RpbGwgdXNlIFNJUCBmb3Igc2Vz
c2lvbnMuPGJyPg0KPGJyPg0KVGhlIElNRUkgd2hpY2ggaGFzIGJlZW4gdXNlZCBpbiBtb2Jp
bGUgZGV2aWNlcyBmb3IgMjAgeWVhcnMgYWxzbyBzdXJ2aXZlcyBkZXZpY2Ugd2lwZXMgZm9y
IHRoZSBjaXJjdWl0IHN3aXRjaGVkIGNhbGxpbmcgY2FwYWJpbGl0eSBhcyB1c2VkIGJ5IGJp
bGxpb25zIG9mIG1vYmlsZXMgdG9kYXkgd2l0aCAyRyBhbmQgM0cgbmV0d29ya3MuIFNvIGFn
YWluIGhvdyBpcyB0aGlzIG1vcmUgaGFybWZ1bCBmb3IgNEcgdGhhbiB0aGUgY3VycmVudCBz
aXR1YXRpb24NCiB3aXRoIDJHIGFuZCAzRyBpZiBhIG1vYmlsZSBkZXZpY2UgaXMgdHJhbnNm
ZXJyZWQgdG8gYSBuZXcgb3duZXI/PGJyPg0KPGJyPg0KQW5kcmV3PGJyPg0KJm5ic3A7PGJy
Pg0KPC9mb250Pjxicj4NCiZuYnNwOzxicj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2Jv
cmRlci10b3A6c29saWQgI0I1QzRERiAxLjBwdDtwYWRkaW5nOjMuMHB0IDBpbiAwaW4gMGlu
Ij4NCjxmb250IHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1Rh
aG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij48Yj5Gcm9tPC9iPjogQW5kcmV3
IEFsbGVuIFttYWlsdG86YWFsbGVuQGJsYWNrYmVycnkuY29tXQ0KPGJyPg0KPGI+U2VudDwv
Yj46IFNhdHVyZGF5LCBKdWx5IDIwLCAyMDEzIDExOjQ4IFBNIENlbnRyYWwgU3RhbmRhcmQg
VGltZTxicj4NCjxiPlRvPC9iPjogdGJyYXlAdGV4dHVhbGl0eS5jb20gJmx0O3RicmF5QHRl
eHR1YWxpdHkuY29tJmd0OyA8YnI+DQo8Yj5DYzwvYj46IGlldGZAaWV0Zi5vcmcgJmx0O2ll
dGZAaWV0Zi5vcmcmZ3Q7IDxicj4NCjxiPlN1YmplY3Q8L2I+OiBSZTogTGFzdCBjYWxsOiBk
cmFmdC1tb250ZW11cnJvLWdzbWEtaW1laS11cm4tMTYudHh0IDxicj4NCjwvZm9udD4mbmJz
cDs8YnI+DQo8L2Rpdj4NCjxmb250IHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjoj
MUY0OTdEIj48YnI+DQpUaW08YnI+DQo8YnI+DQpGaXJzdGx5IGFzIHN0YXRlZCBpbjxicj4N
Cmh0dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtYWxsZW4tZGlzcGF0Y2gt
aW1laS11cm4tYXMtaW5zdGFuY2VpZC88YnI+DQp0aGUgdXNlIG9mIHRoZSBJTUVJIGFzIGEg
U0lQIEluc3RhbmNlIElEIG9ubHkgcGVydGFpbnMgdG8gdXNhZ2Ugb2YgU0lQIHdpdGggdGhl
IDNHUFAgSU1TIGFuZCBpZiBhIGRldmljZSBpcyBub3QgdXNpbmcgSU1TIHNpbmcgSU1TIHdp
dGhvdXQgYW4gSU1FSSB1c2VzIElNUyB0aGVuIGl0IHdpbGwgc3RpbGwgdXNlIGEgVVVJRCBh
cyB0aGUgU0lQIGluc3RhbmNlIElEIGFzIHBlciBSRkMgNTYyNi4gSWYgYSBkZXZpY2Ugd2l0
aG91dCBhbiBJTUVJIHVzZXMNCiBJTVMgdGhlbiBpdCB3aWxsIGFsc28gc3RpbGwgdXNlIGEg
VVVJRCBhcyB0aGUgU0lQIGluc3RhbmNlIElEIGFzIHBlciBSRkMgNTYyNi4gVGhpcyBpcyBz
cGVjaWZpZWQgYWxzbyBpbiB0aGUgM0dQUCBJTVMgc3BlY2lmaWNhdGlvbiBUUyAyNC4yMjkg
YXMgd2VsbCBhcyB0aGUgYWJvdmUgZHJhZnQuPGJyPg0KPGJyPg0KU28gYXBwbGljYXRpb25z
IHJ1bm5pbmcgb24gZGV2aWNlcyB0aGF0IGRvbid0IGhhdmUgYW4gSU1FSSBjYW4gc3RpbGwg
dXNlIFNJUCBmb3Igc2Vzc2lvbnMuDQo8YnI+DQo8YnI+DQpUaGUgSU1FSSB3aGljaCBoYXMg
YmVlbiB1c2VkIGluIG1vYmlsZSBkZXZpY2VzIGZvciAyMCB5ZWFycyBhbHNvIHN1cnZpdmVz
IGRldmljZSB3aXBlcyBmb3IgdGhlIGNpcmN1aXQgc3dpdGNoZWQgY2FsbGluZyBjYXBhYmls
aXR5IGFzIHVzZWQgYnkgYmlsbGlvbnMgb2YgbW9iaWxlcyB0b2RheSB3aXRoIDJHIGFuZCAz
RyBuZXR3b3Jrcy4gU28gYWdhaW4gaG93IGlzIHRoaXMgbW9yZSBoYXJtZnVsIGZvciA0RyB0
aGFuIHRoZSBjdXJyZW50IHNpdHVhdGlvbg0KIHdpdGggMkcgYW5kIDNHIGlmIGEgbW9iaWxl
IGRldmljZSBpcyB0cmFuc2ZlcnJlZCB0byBhIG5ldyBvd25lcj88YnI+DQo8YnI+DQpBbmRy
ZXc8L2ZvbnQ+PGJyPg0KJm5ic3A7PGJyPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9y
ZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6My4wcHQgMGluIDBpbiAwaW4i
Pg0KPGZvbnQgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFo
b21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPjxiPkZyb208L2I+OiBUaW0gQnJh
eSBbbWFpbHRvOnRicmF5QHRleHR1YWxpdHkuY29tXQ0KPGJyPg0KPGI+U2VudDwvYj46IFNh
dHVyZGF5LCBKdWx5IDIwLCAyMDEzIDA3OjAxIFBNIENlbnRyYWwgU3RhbmRhcmQgVGltZTxi
cj4NCjxiPlRvPC9iPjogQW5kcmV3IEFsbGVuIDxicj4NCjxiPkNjPC9iPjogc2NvdHQuYnJp
bUBnbWFpbC5jb20gJmx0O3Njb3R0LmJyaW1AZ21haWwuY29tJmd0OzsgaWV0ZkBpZXRmLm9y
ZyAmbHQ7aWV0ZkBpZXRmLm9yZyZndDsNCjxicj4NCjxiPlN1YmplY3Q8L2I+OiBSZTogTGFz
dCBjYWxsOiBkcmFmdC1tb250ZW11cnJvLWdzbWEtaW1laS11cm4tMTYudHh0IDxicj4NCjwv
Zm9udD4mbmJzcDs8YnI+DQo8L2Rpdj4NCjxkaXYgZGlyPSJsdHIiPk9uIFNhdCwgSnVsIDIw
LCAyMDEzIGF0IDM6MjAgUE0sIEFuZHJldyBBbGxlbiA8c3BhbiBkaXI9Imx0ciI+Jmx0Ozxh
IGhyZWY9Im1haWx0bzphYWxsZW5AYmxhY2tiZXJyeS5jb20iIHRhcmdldD0iX2JsYW5rIj5h
YWxsZW5AYmxhY2tiZXJyeS5jb208L2E+Jmd0Ozwvc3Bhbj4gd3JvdGU6PGJyPg0KPGRpdiBj
bGFzcz0iZ21haWxfZXh0cmEiPg0KPGRpdiBjbGFzcz0iZ21haWxfcXVvdGUiPg0KPGJsb2Nr
cXVvdGUgY2xhc3M9ImdtYWlsX3F1b3RlIiBzdHlsZT0ibWFyZ2luOjAgMCAwIC44ZXg7Ym9y
ZGVyLWxlZnQ6MXB4ICNjY2Mgc29saWQ7cGFkZGluZy1sZWZ0OjFleCI+DQpDYW4gaXQgcGxl
YXNlIGJlIGV4cGxhaW5lZCBob3cgdGhlIElNRUkgVVJOIHdoZW4gdXNlZCBhcyBzdGF0ZWQg
aW4gPGEgaHJlZj0iaHR0cDovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1hbGxl
bi1kaXNwYXRjaC1pbWVpLXVybi1hcy1pbnN0YW5jZWlkLyIgdGFyZ2V0PSJfYmxhbmsiPg0K
aHR0cDovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1hbGxlbi1kaXNwYXRjaC1p
bWVpLXVybi1hcy1pbnN0YW5jZWlkLzwvYT48YnI+DQpJcyBhbnkgbW9yZSBoYXJtZnVsIHRo
YW4gYXMgdGhlIElNRUkgaXMgdXNlZCB0b2RheSBieSBvdmVyIDkwJSBvZiBtb2JpbGUgcGhv
bmVzIGluIHVzZSB0b2RheSB3b3JsZHdpZGU/PGJyPg0KPC9ibG9ja3F1b3RlPg0KPGRpdj48
YnI+DQo8L2Rpdj4NCjxkaXY+SXQgc3Vydml2ZXMgZGV2aWNlIHdpcGVzLCB3aGljaCB1c3Vh
bGx5IGhhcHBlbiB1cG9uIGNoYW5nZSBvZiBkZXZpY2Ugb3duZXJzaGlwLiZuYnNwOw0KPGJy
Pg0KPGJyPg0KSeKAmW0gbm90IGFuIGV4cGVydCBpbiB5b3VyIGFwcGxpY2F0aW9uIGRvbWFp
biwgc28gcGFyZG9uIG1lIGlmIHRoaXMgcXVlc3Rpb24gaXMgaG9wZWxlc3NseSBuYWl2ZTog
SXQgc2VlbXMgdGhhdCB0aGlzIGlkZW50aWZpZXIgaXMgcmVsYXRlZCBpbiBzb21lIHdheSB0
byBTSVAgc2Vzc2lvbnMuJm5ic3A7IEl0IHNlZW1zIHRoYXQgaXQgd291bGQgYmUgYSBjb21t
b24gb3BlcmF0aW9uIHRvIGxhdW5jaCBhIFNJUCBzZXNzaW9uIG9uIGEgZGV2aWNlIHN1Y2gg
YXMNCiBhIFdpRmktb25seSB0YWJsZXQsIG9yIGFuIGlQb2QgdG91Y2gsIHRoYXQgZG9lc27i
gJl0IGhhdmUgYW4gSU1FSS4mbmJzcDsgSXMgdGhpcyBhIHByb2JsZW0/PGJyPg0KPGJyPg0K
PC9kaXY+DQo8ZGl2PiZuYnNwOy1UPGJyPg0KPC9kaXY+DQo8ZGl2PiZuYnNwOzwvZGl2Pg0K
PGJsb2NrcXVvdGUgY2xhc3M9ImdtYWlsX3F1b3RlIiBzdHlsZT0ibWFyZ2luOjAgMCAwIC44
ZXg7Ym9yZGVyLWxlZnQ6MXB4ICNjY2Mgc29saWQ7cGFkZGluZy1sZWZ0OjFleCI+DQo8c3Bh
biBjbGFzcz0iSE9FblpiIj48Zm9udCBjb2xvcj0iIzg4ODg4OCI+PGJyPg0KQW5kcmV3PGJy
Pg0KPC9mb250Pjwvc3Bhbj4NCjxkaXYgY2xhc3M9ImltIEhPRW5aYiI+PGJyPg0KLS0tLS0g
T3JpZ2luYWwgTWVzc2FnZSAtLS0tLTxicj4NCkZyb206IFNjb3R0IEJyaW0gW21haWx0bzo8
YSBocmVmPSJtYWlsdG86c2NvdHQuYnJpbUBnbWFpbC5jb20iPnNjb3R0LmJyaW1AZ21haWwu
Y29tPC9hPl08YnI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9ImltIEhPRW5aYiI+U2VudDogU2F0
dXJkYXksIEp1bHkgMjAsIDIwMTMgMDM6NTUgUE0gQ2VudHJhbCBTdGFuZGFyZCBUaW1lPGJy
Pg0KVG86IEFuZHJldyBBbGxlbjxicj4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0iaW0gSE9Fblpi
Ij5DYzogPGEgaHJlZj0ibWFpbHRvOnRicmF5QHRleHR1YWxpdHkuY29tIj50YnJheUB0ZXh0
dWFsaXR5LmNvbTwvYT4gJmx0OzxhIGhyZWY9Im1haWx0bzp0YnJheUB0ZXh0dWFsaXR5LmNv
bSI+dGJyYXlAdGV4dHVhbGl0eS5jb208L2E+Jmd0OzsNCjxhIGhyZWY9Im1haWx0bzppZXRm
QGlldGYub3JnIj5pZXRmQGlldGYub3JnPC9hPiAmbHQ7PGEgaHJlZj0ibWFpbHRvOmlldGZA
aWV0Zi5vcmciPmlldGZAaWV0Zi5vcmc8L2E+Jmd0Ozxicj4NClN1YmplY3Q6IFJlOiBMYXN0
IGNhbGw6IGRyYWZ0LW1vbnRlbXVycm8tZ3NtYS1pbWVpLXVybi0xNi50eHQ8YnI+DQo8YnI+
DQo8L2Rpdj4NCjxkaXYgY2xhc3M9IkhPRW5aYiI+DQo8ZGl2IGNsYXNzPSJoNSI+T24gU2F0
LCBKdWwgMjAsIDIwMTMgYXQgNDowOCBQTSwgQW5kcmV3IEFsbGVuICZsdDs8YSBocmVmPSJt
YWlsdG86YWFsbGVuQGJsYWNrYmVycnkuY29tIj5hYWxsZW5AYmxhY2tiZXJyeS5jb208L2E+
Jmd0OyB3cm90ZTo8YnI+DQomZ3Q7IFRpbTxicj4NCiZndDs8YnI+DQomZ3Q7IFRoZSBxdW90
ZSBpcyBmcm9tIFJGQyA1NjI2IHdoaWNoIGFsc28gc3RhdGVzOjxicj4NCiZndDs8YnI+DQom
Z3Q7ICZxdW90OzMuMS4gU3VtbWFyeSBvZiBNZWNoYW5pc208YnI+DQomZ3Q7PGJyPg0KJmd0
OyBFYWNoIFVBIGhhcyBhIHVuaXF1ZSBpbnN0YW5jZS1pZCB0aGF0IHN0YXlzIHRoZSBzYW1l
IGZvciB0aGlzIFVBIGV2ZW4gaWYgdGhlPGJyPg0KJmd0OyBVQSByZWJvb3RzIG9yIGlzIHBv
d2VyIGN5Y2xlZC4mcXVvdDs8YnI+DQomZ3Q7PGJyPg0KJmd0OyBTaW5jZSB0aGUgVVVJRCBp
biB0aGUgaW5zdGFuY2UgSUQgaXMgYWxzbyBzdGF0aWMgaG93IGlzIHRoaXMgc2lnbmlmaWNh
bnRseTxicj4NCiZndDsgZGlmZmVyZW50IGluIHRlcm1zIG9mIHByaXZhY3kgY29uY2VybnMg
ZnJvbSB0aGUgSU1FSSBiZWluZyB1c2VkIGFzIGFuPGJyPg0KJmd0OyBpbnN0YW5jZSBJRD88
YnI+DQo8YnI+DQpZb3UncmUgbm90IGRlbW9uc3RyYXRpbmcgdGhhdCBhbiBJTUVJIGlzIGp1
c3QgYXMgZ29vZCwgeW91J3JlPGJyPg0KZGVtb25zdHJhdGluZyB0aGF0IGEgVVVJRCBpcyBq
dXN0IGFzIGJhZC48YnI+DQo8YnI+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0iSE9F
blpiIj4NCjxkaXYgY2xhc3M9Img1Ij4tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS08YnI+DQpUaGlzIHRyYW5z
bWlzc2lvbiAoaW5jbHVkaW5nIGFueSBhdHRhY2htZW50cykgbWF5IGNvbnRhaW4gY29uZmlk
ZW50aWFsIGluZm9ybWF0aW9uLCBwcml2aWxlZ2VkIG1hdGVyaWFsIChpbmNsdWRpbmcgbWF0
ZXJpYWwgcHJvdGVjdGVkIGJ5IHRoZSBzb2xpY2l0b3ItY2xpZW50IG9yIG90aGVyIGFwcGxp
Y2FibGUgcHJpdmlsZWdlcyksIG9yIGNvbnN0aXR1dGUgbm9uLXB1YmxpYyBpbmZvcm1hdGlv
bi4gQW55IHVzZSBvZiB0aGlzIGluZm9ybWF0aW9uDQogYnkgYW55b25lIG90aGVyIHRoYW4g
dGhlIGludGVuZGVkIHJlY2lwaWVudCBpcyBwcm9oaWJpdGVkLiBJZiB5b3UgaGF2ZSByZWNl
aXZlZCB0aGlzIHRyYW5zbWlzc2lvbiBpbiBlcnJvciwgcGxlYXNlIGltbWVkaWF0ZWx5IHJl
cGx5IHRvIHRoZSBzZW5kZXIgYW5kIGRlbGV0ZSB0aGlzIGluZm9ybWF0aW9uIGZyb20geW91
ciBzeXN0ZW0uIFVzZSwgZGlzc2VtaW5hdGlvbiwgZGlzdHJpYnV0aW9uLCBvciByZXByb2R1
Y3Rpb24gb2YgdGhpcyB0cmFuc21pc3Npb24NCiBieSB1bmludGVuZGVkIHJlY2lwaWVudHMg
aXMgbm90IGF1dGhvcml6ZWQgYW5kIG1heSBiZSB1bmxhd2Z1bC48YnI+DQo8L2Rpdj4NCjwv
ZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8YnI+DQo8L2Rpdj4NCjwvZGl2Pg0KLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tIDxicj4NClRoaXMgdHJhbnNtaXNzaW9uIChpbmNsdWRpbmcgYW55IGF0
dGFjaG1lbnRzKSBtYXkgY29udGFpbiBjb25maWRlbnRpYWwgaW5mb3JtYXRpb24sIHByaXZp
bGVnZWQgbWF0ZXJpYWwgKGluY2x1ZGluZyBtYXRlcmlhbCBwcm90ZWN0ZWQgYnkgdGhlIHNv
bGljaXRvci1jbGllbnQgb3Igb3RoZXIgYXBwbGljYWJsZSBwcml2aWxlZ2VzKSwgb3IgY29u
c3RpdHV0ZSBub24tcHVibGljIGluZm9ybWF0aW9uLiBBbnkgdXNlIG9mIHRoaXMgaW5mb3Jt
YXRpb24NCiBieSBhbnlvbmUgb3RoZXIgdGhhbiB0aGUgaW50ZW5kZWQgcmVjaXBpZW50IGlz
IHByb2hpYml0ZWQuIElmIHlvdSBoYXZlIHJlY2VpdmVkIHRoaXMgdHJhbnNtaXNzaW9uIGlu
IGVycm9yLCBwbGVhc2UgaW1tZWRpYXRlbHkgcmVwbHkgdG8gdGhlIHNlbmRlciBhbmQgZGVs
ZXRlIHRoaXMgaW5mb3JtYXRpb24gZnJvbSB5b3VyIHN5c3RlbS4gVXNlLCBkaXNzZW1pbmF0
aW9uLCBkaXN0cmlidXRpb24sIG9yIHJlcHJvZHVjdGlvbiBvZiB0aGlzIHRyYW5zbWlzc2lv
bg0KIGJ5IHVuaW50ZW5kZWQgcmVjaXBpZW50cyBpcyBub3QgYXV0aG9yaXplZCBhbmQgbWF5
IGJlIHVubGF3ZnVsLg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tIDxicj4NClRoaXMgdHJhbnNtaXNzaW9u
IChpbmNsdWRpbmcgYW55IGF0dGFjaG1lbnRzKSBtYXkgY29udGFpbiBjb25maWRlbnRpYWwg
aW5mb3JtYXRpb24sIHByaXZpbGVnZWQgbWF0ZXJpYWwgKGluY2x1ZGluZyBtYXRlcmlhbCBw
cm90ZWN0ZWQgYnkgdGhlIHNvbGljaXRvci1jbGllbnQgb3Igb3RoZXIgYXBwbGljYWJsZSBw
cml2aWxlZ2VzKSwgb3IgY29uc3RpdHV0ZSBub24tcHVibGljIGluZm9ybWF0aW9uLiBBbnkg
dXNlIG9mIHRoaXMgaW5mb3JtYXRpb24gYnkgYW55b25lIG90aGVyIHRoYW4gdGhlIGludGVu
ZGVkIHJlY2lwaWVudCBpcyBwcm9oaWJpdGVkLiBJZiB5b3UgaGF2ZSByZWNlaXZlZCB0aGlz
IHRyYW5zbWlzc2lvbiBpbiBlcnJvciwgcGxlYXNlIGltbWVkaWF0ZWx5IHJlcGx5IHRvIHRo
ZSBzZW5kZXIgYW5kIGRlbGV0ZSB0aGlzIGluZm9ybWF0aW9uIGZyb20geW91ciBzeXN0ZW0u
IFVzZSwgZGlzc2VtaW5hdGlvbiwgZGlzdHJpYnV0aW9uLCBvciByZXByb2R1Y3Rpb24gb2Yg
dGhpcyB0cmFuc21pc3Npb24gYnkgdW5pbnRlbmRlZCByZWNpcGllbnRzIGlzIG5vdCBhdXRo
b3JpemVkIGFuZCBtYXkgYmUgdW5sYXdmdWwuDQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_BBF5DDFE515C3946BC18D733B20DAD2338DD265CXMB104ADSrimnet_--

From brian@innovationslab.net  Sun Jul 21 05:34:34 2013
Return-Path: <brian@innovationslab.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A98A521E8088 for <ietf@ietfa.amsl.com>; Sun, 21 Jul 2013 05:34:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.849
X-Spam-Level: 
X-Spam-Status: No, score=-103.849 tagged_above=-999 required=5 tests=[AWL=0.750, BAYES_00=-2.599, GB_I_INVITATION=-2, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WZr+0HUwwu-9 for <ietf@ietfa.amsl.com>; Sun, 21 Jul 2013 05:34:29 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id A3A6921F9FDE for <ietf@ietf.org>; Sun, 21 Jul 2013 05:34:29 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 44F4C880E6 for <ietf@ietf.org>; Sun, 21 Jul 2013 05:34:29 -0700 (PDT)
Received: from Littlejohn.local (c-69-140-213-249.hsd1.md.comcast.net [69.140.213.249]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id DE075130003 for <ietf@ietf.org>; Sun, 21 Jul 2013 05:34:28 -0700 (PDT)
Message-ID: <51EBD553.5070202@innovationslab.net>
Date: Sun, 21 Jul 2013 08:34:27 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Mentoring Electronic Participants [was  Invitation to request an IETF mentor]
References: <20130717225841.14002.89245.idtracker@ietfa.amsl.com> <51EAB100.7090508@isdg.net>
In-Reply-To: <51EAB100.7090508@isdg.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Jul 2013 12:34:34 -0000

Hi Hector,

On 7/20/13 11:47 AM, Hector Santos wrote:
> Overall, I think the IETF has a marketing problem addressing its #1
> customer base - electronic participants.
>

By this term, I assume (based on later text) you mean remote participants...

> I was somewhat hoping to see more done in the mentor area of assisting
> electronic participants. Of coarse, this sort of electronic mentoring it
> could include an end goal to get folks more involved with the IETF
> directly, i.e. go to meetings, become leaders, etc, but overall assist
> with protocol standards development.

Since this is the first time we have tried to deploy a mentoring 
program, we wanted to limit the scope to keep things manageable.  If the 
mentoring program "succeeds" in Berlin, we will examine ways of 
expanding it.

<snip>

>
> Maybe I'm off-base, but it just seems the mentoring efforts is targeted
> at attracting full time IETF members, future leaders, etc and not just
> the specific technical person who might be just interested in various
> protocols of interest and no more.  Our products are internet based and
> hence has dozens of protocols implemented. I'm here really just to keep
> on top of them, assist with improvements, and if need be try to get an
> I-D written if only to prove a point or get an idea out there for
> consideration and creative synergism.  Not interested in become an IETF
> full time attendee nor "leader" per se.

Not at all.  The people we are targeting are the newcomers (folks who 
have attended less than 3 meetings or are registered as students).  One 
goal is to increase the number of active participants, but we are not 
turning away people with focused technical goals.

>
> The IETF needs to improved its market across the globe and that really
> can only feasibly be done electronically.  There are needs to take
> efforts of getting electronic participants more involved. I think it can
> start with first helping and mentoring I-D writers.

I believe your concerns go well beyond the scope of the mentoring 
program.  There have been discussions on how to increase the performance 
of our remote participants 
(http://www.ietf.org/mail-archive/web/ietf/current/msg77020.html).
>
> What generally happens when an individual I-D is submitted?   Is there
> an overseer of the submissions and decides there is something that
> interest the IETF?
>

No, there is no "overseer".  Each participant is free to read (and 
possibly support) any individual I-D they see published.  Typically, the 
author(s) will start by soliciting reviews of their individual I-D by 
other IETF participants.

Regards,
Brian


From presnick@qti.qualcomm.com  Sun Jul 21 06:48:02 2013
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D162221E8094 for <ietf@ietfa.amsl.com>; Sun, 21 Jul 2013 06:48:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.599
X-Spam-Level: 
X-Spam-Status: No, score=-107.599 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, GB_I_INVITATION=-2, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lneCr34zbU1r for <ietf@ietfa.amsl.com>; Sun, 21 Jul 2013 06:47:58 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id 765FF21E8088 for <ietf@ietf.org>; Sun, 21 Jul 2013 06:47:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1374414478; x=1405950478; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=9Nj9eFmkBJxdZiIZBJz1sRybbGUvrZlZqDRxVRtLEIA=; b=tjViZn5+WF1UHw5wXGKFnBjxAw4ADM5xDbFQpkdJEEQVIuCDBJ4aBu6+ k+MoyAMDlk7YpizEwZ9xD6bdrtmICnRAX5Zf+lPSpOdjTF35nMM0SF+9u u5zwLRUBmnAfpnCZjrfE3mhq/X3l9/DGGFeIHityJdDxsQX80KyCDnmjj k=;
X-IronPort-AV: E=Sophos;i="4.89,713,1367996400"; d="scan'208";a="63829071"
Received: from ironmsg03-r.qualcomm.com ([172.30.46.17]) by wolverine01.qualcomm.com with ESMTP; 21 Jul 2013 06:47:40 -0700
X-IronPort-AV: E=Sophos;i="4.89,713,1367996400"; d="scan'208";a="517876936"
Received: from nasanexhc03.na.qualcomm.com ([172.30.48.26]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 21 Jul 2013 06:47:39 -0700
Received: from nasanexhc05.na.qualcomm.com (172.30.48.2) by NASANEXHC03.na.qualcomm.com (172.30.48.26) with Microsoft SMTP Server (TLS) id 14.2.318.4; Sun, 21 Jul 2013 06:47:39 -0700
Received: from presnick-mac.local (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.2) with Microsoft SMTP Server (TLS) id 14.2.318.4; Sun, 21 Jul 2013 06:47:39 -0700
Message-ID: <51EBE67A.7080703@qti.qualcomm.com>
Date: Sun, 21 Jul 2013 08:47:38 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Hector Santos <hsantos@isdg.net>
Subject: Re: Mentoring Electronic Participants [was  Invitation to request an	IETF mentor]
References: <20130717225841.14002.89245.idtracker@ietfa.amsl.com> <51EAB100.7090508@isdg.net>
In-Reply-To: <51EAB100.7090508@isdg.net>
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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Jul 2013 13:48:03 -0000

On 7/20/13 10:47 AM, Hector Santos wrote:
> I was somewhat hoping to see more done in the mentor area of assisting 
> electronic participants. Of coarse, this sort of electronic mentoring 
> it could include an end goal to get folks more involved with the IETF 
> directly, i.e. go to meetings, become leaders, etc, but overall assist 
> with protocol standards development.

I think this would be a fabulous addition to the program. As Brian said, 
the mentoring program is just getting started, so a "meeting mentor" 
seems like a good starting point, but I have had many experiences with 
new electronic participants (be it remote meeting participants or simply 
active mailing list contributors) for whom a mentor would be a great 
thing. That said, one caveat:

> As I have been advised by some IETF vets, I'm sure it will help with 
> the process of getting others more comfortable with you and your work, 
> but is it really absolutely necessary to attend IETF meetings to get 
> an I-D moved thru the process?

It's certainly not necessary to attend face-to-face to get work done, 
but it sure does help develop a rapport with people. We are all humans, 
and electronic communications (especially elusively using email) are not 
ideal for getting our points across or convincing others without some 
face-to-face interaction. I know of several folks in the community that 
come across terribly in email and, if you didn't know them offline, 
understand their communication style, and know where to look in their 
email messages for the technical content, you'd have a terrible time 
getting them to be part of a consensus process. And that's the reason 
for the caveat I mentioned above: One of the big values of a mentoring 
program is that it allows the mentor to discover the mentee's 
communication style, help them interact (in person and electronically) 
with some of our more interesting characters with their interesting 
communication styles, and help the mentee figure out how to get 
technical points across effectively. Having a mentor for someone who 
they will not meet face-to-face makes that part of the metor-mentee 
relationship much harder to develop.

Even so, I definitely think that the expansion of the program you 
suggest is a great idea. Figuring out the logistics to make it effective 
will be tricky (maybe finding a mentor who is geographically close 
enough to the mentee to make a face-to-face meeting between them 
possible), but either way I think it is well worth doing.

pr

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


From tbray@textuality.com  Sun Jul 21 10:42:36 2013
Return-Path: <tbray@textuality.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1648A21E808B for <ietf@ietfa.amsl.com>; Sun, 21 Jul 2013 10:42:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.82
X-Spam-Level: 
X-Spam-Status: No, score=-2.82 tagged_above=-999 required=5 tests=[AWL=0.156,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1G5PQ--ZeMHc for <ietf@ietfa.amsl.com>; Sun, 21 Jul 2013 10:42:31 -0700 (PDT)
Received: from mail-ve0-f179.google.com (mail-ve0-f179.google.com [209.85.128.179]) by ietfa.amsl.com (Postfix) with ESMTP id 1C2E521E804D for <ietf@ietf.org>; Sun, 21 Jul 2013 10:42:31 -0700 (PDT)
Received: by mail-ve0-f179.google.com with SMTP id d10so4554805vea.38 for <ietf@ietf.org>; Sun, 21 Jul 2013 10:42:29 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=DSwnyiJSkQGM9uwEwxzTeTnB4TEF6VCr4sx4x/iOfIk=; b=DbRbDPWHuqQKKzB08cUVoskrw6c7NDYZn8yYjVo+xtIr1/XJdqRJf/54Ea3rOU0jEb fXWwN8+bSBG1v9AE1ObW3r7zQAqplMhILghu+XQgN1GQO1fq4QluqAy4tNJZhG+Z5lMy IgbN2L4yK3lekld6kkELOGxcMe/NFmyT5jy0hBV9AWpv2i3O7JdE4VrTqjfInT4KeBh4 LhhrwLZXcGtqh98iPjxq57abHpA50qxsCgYKkeDU3xskLd6XQGg8Ir5uGN3X/4rIrznP KRMVqO/zk1QzhsO3iziLI9XNMECpYaZXD/zSkWanh/l1NlqSqDnmzkzOhfvd7VnDUwv5 iyvA==
MIME-Version: 1.0
X-Received: by 10.58.2.137 with SMTP id 9mr8462356veu.50.1374428549289; Sun, 21 Jul 2013 10:42:29 -0700 (PDT)
Received: by 10.220.219.200 with HTTP; Sun, 21 Jul 2013 10:42:29 -0700 (PDT)
X-Originating-IP: [24.84.235.32]
In-Reply-To: <BBF5DDFE515C3946BC18D733B20DAD2338DD265C@XMB104ADS.rim.net>
References: <BBF5DDFE515C3946BC18D733B20DAD2338DD24D0@XMB104ADS.rim.net> <BBF5DDFE515C3946BC18D733B20DAD2338DD265C@XMB104ADS.rim.net>
Date: Sun, 21 Jul 2013 10:42:29 -0700
Message-ID: <CAHBU6ivPFGkb4h_fBF4RZ-qyf9CSkAEatXqY5wxGejds8nfvOA@mail.gmail.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
From: Tim Bray <tbray@textuality.com>
To: Andrew Allen <aallen@blackberry.com>
Content-Type: multipart/alternative; boundary=047d7b2e75cc73298104e20915a7
X-Gm-Message-State: ALoCoQmCfaezgofvxzIWQd9IwCb0vc1FEDFTME9duX0ayhUSxwqko3ybjHKeIsLVzQzSSBYdFDRm
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Jul 2013 17:42:36 -0000

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

Look, I don=E2=80=99t remotely understand the 3gpp universe, and I acknowle=
dge John
Klensin=E2=80=99s point about the advantages of registering things, in gene=
ral.

Having said that, I worry a little bit that URNs are URIs and there are
lots of specs out there that say =E2=80=9Cuse any URI=E2=80=9D and I sure w=
ouldn=E2=80=99t want to
see these things used anywhere near any application-level protocol.

If this were an Apps-Area thing and I thought that registering it would
increase the risk that these patent-encumbered, privacy-compromising,
operationally-fragile constructs had any chance of creeping into general
use by app developers, I=E2=80=99d be lying in the road screaming.  As it i=
s, I
think the issues with this draft have been raised sufficiently, so I=E2=80=
=99ll
shut up and leave further discussion to those who understand
domain-specific technical issues.

 -Tim



On Sun, Jul 21, 2013 at 12:37 AM, Andrew Allen <aallen@blackberry.com>wrote=
:

>
> Tim
>
> Seems the text got munged with some copy pasting so here it is corrected:
>
>
> Firstly as stated in
>
> http://datatracker.ietf.org/doc/draft-allen-dispatch-imei-urn-as-instance=
id/
> the use of the IMEI as a SIP Instance ID only pertains to usage of SIP
> with the 3GPP IMS and if a device is not using IMS without an IMEI then i=
t
> will use a UUID as the SIP instance ID as per RFC 5626. If a device witho=
ut
> an IMEI uses IMS then it will also still use a UUID as the SIP instance I=
D
> as per RFC 5626. This is specified also in the 3GPP IMS specification TS
> 24.229 as well as the above draft.
>
>
> So applications running on devices that don't have an IMEI can still use
> SIP for sessions.
>
> The IMEI which has been used in mobile devices for 20 years also survives
> device wipes for the circuit switched calling capability as used by
> billions of mobiles today with 2G and 3G networks. So again how is this
> more harmful for 4G than the current situation with 2G and 3G if a mobile
> device is transferred to a new owner?
>
> Andrew
>
>
>
>  *From*: Andrew Allen [mailto:aallen@blackberry.com]
> *Sent*: Saturday, July 20, 2013 11:48 PM Central Standard Time
> *To*: tbray@textuality.com <tbray@textuality.com>
> *Cc*: ietf@ietf.org <ietf@ietf.org>
> *Subject*: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
>
>
> Tim
>
> Firstly as stated in
>
> http://datatracker.ietf.org/doc/draft-allen-dispatch-imei-urn-as-instance=
id/
> the use of the IMEI as a SIP Instance ID only pertains to usage of SIP
> with the 3GPP IMS and if a device is not using IMS sing IMS without an IM=
EI
> uses IMS then it will still use a UUID as the SIP instance ID as per RFC
> 5626. If a device without an IMEI uses IMS then it will also still use a
> UUID as the SIP instance ID as per RFC 5626. This is specified also in th=
e
> 3GPP IMS specification TS 24.229 as well as the above draft.
>
> So applications running on devices that don't have an IMEI can still use
> SIP for sessions.
>
> The IMEI which has been used in mobile devices for 20 years also survives
> device wipes for the circuit switched calling capability as used by
> billions of mobiles today with 2G and 3G networks. So again how is this
> more harmful for 4G than the current situation with 2G and 3G if a mobile
> device is transferred to a new owner?
>
> Andrew
>
>  *From*: Tim Bray [mailto:tbray@textuality.com]
> *Sent*: Saturday, July 20, 2013 07:01 PM Central Standard Time
> *To*: Andrew Allen
> *Cc*: scott.brim@gmail.com <scott.brim@gmail.com>; ietf@ietf.org <
> ietf@ietf.org>
> *Subject*: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
>
>  On Sat, Jul 20, 2013 at 3:20 PM, Andrew Allen <aallen@blackberry.com>wro=
te:
>
>> Can it please be explained how the IMEI URN when used as stated in
>> http://datatracker.ietf.org/doc/draft-allen-dispatch-imei-urn-as-instanc=
eid/
>> Is any more harmful than as the IMEI is used today by over 90% of mobile
>> phones in use today worldwide?
>>
>
>  It survives device wipes, which usually happen upon change of device
> ownership.
>
> I=E2=80=99m not an expert in your application domain, so pardon me if thi=
s
> question is hopelessly naive: It seems that this identifier is related in
> some way to SIP sessions.  It seems that it would be a common operation t=
o
> launch a SIP session on a device such as a WiFi-only tablet, or an iPod
> touch, that doesn=E2=80=99t have an IMEI.  Is this a problem?
>
>   -T
>
>
>>
>> Andrew
>>
>> ----- Original Message -----
>> From: Scott Brim [mailto:scott.brim@gmail.com]
>>  Sent: Saturday, July 20, 2013 03:55 PM Central Standard Time
>> To: Andrew Allen
>>  Cc: tbray@textuality.com <tbray@textuality.com>; ietf@ietf.org <
>> ietf@ietf.org>
>> Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
>>
>>  On Sat, Jul 20, 2013 at 4:08 PM, Andrew Allen <aallen@blackberry.com>
>> wrote:
>> > Tim
>> >
>> > The quote is from RFC 5626 which also states:
>> >
>> > "3.1. Summary of Mechanism
>> >
>> > Each UA has a unique instance-id that stays the same for this UA even
>> if the
>> > UA reboots or is power cycled."
>> >
>> > Since the UUID in the instance ID is also static how is this
>> significantly
>> > different in terms of privacy concerns from the IMEI being used as an
>> > instance ID?
>>
>> You're not demonstrating that an IMEI is just as good, you're
>> demonstrating that a UUID is just as bad.
>>
>>   ---------------------------------------------------------------------
>> This transmission (including any attachments) may contain confidential
>> information, privileged material (including material protected by the
>> solicitor-client or other applicable privileges), or constitute non-publ=
ic
>> information. Any use of this information by anyone other than the intend=
ed
>> recipient is prohibited. If you have received this transmission in error=
,
>> please immediately reply to the sender and delete this information from
>> your system. Use, dissemination, distribution, or reproduction of this
>> transmission by unintended recipients is not authorized and may be unlaw=
ful.
>>
>
>  ---------------------------------------------------------------------
> This transmission (including any attachments) may contain confidential
> information, privileged material (including material protected by the
> solicitor-client or other applicable privileges), or constitute non-publi=
c
> information. Any use of this information by anyone other than the intende=
d
> recipient is prohibited. If you have received this transmission in error,
> please immediately reply to the sender and delete this information from
> your system. Use, dissemination, distribution, or reproduction of this
> transmission by unintended recipients is not authorized and may be
> unlawful.
> ---------------------------------------------------------------------
> This transmission (including any attachments) may contain confidential
> information, privileged material (including material protected by the
> solicitor-client or other applicable privileges), or constitute non-publi=
c
> information. Any use of this information by anyone other than the intende=
d
> recipient is prohibited. If you have received this transmission in error,
> please immediately reply to the sender and delete this information from
> your system. Use, dissemination, distribution, or reproduction of this
> transmission by unintended recipients is not authorized and may be
> unlawful.
>

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

<div dir=3D"ltr"><div>Look, I don=E2=80=99t remotely understand the 3gpp un=
iverse, and I acknowledge John Klensin=E2=80=99s point about the advantages=
 of registering things, in general.<br><br>Having said that, I worry a litt=
le bit that URNs are URIs and there are lots of specs out there that say =
=E2=80=9Cuse any URI=E2=80=9D and I sure wouldn=E2=80=99t want to see these=
 things used anywhere near any application-level protocol.=C2=A0 <br>
<br>If this were an Apps-Area thing and I thought that registering it would=
 increase the risk that these patent-encumbered, privacy-compromising, oper=
ationally-fragile constructs had any chance of creeping into general use by=
 app developers, I=E2=80=99d be lying in the road screaming.=C2=A0 As it is=
, I think the issues with this draft have been raised sufficiently, so I=E2=
=80=99ll shut up and leave further discussion to those who understand domai=
n-specific technical issues.<br>
<br></div>=C2=A0-Tim<br><div><br></div></div><div class=3D"gmail_extra"><br=
><br><div class=3D"gmail_quote">On Sun, Jul 21, 2013 at 12:37 AM, Andrew Al=
len <span dir=3D"ltr">&lt;<a href=3D"mailto:aallen@blackberry.com" target=
=3D"_blank">aallen@blackberry.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>
<font style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:#1f497d"><br>
Tim<br>
<br>
Seems the text got munged with some copy pasting so here it is corrected:<d=
iv class=3D"im"><br>
<br>
Firstly as stated in<br>
<a href=3D"http://datatracker.ietf.org/doc/draft-allen-dispatch-imei-urn-as=
-instanceid/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-allen=
-dispatch-imei-urn-as-instanceid/</a><br></div>
the use of the IMEI as a SIP Instance ID only pertains to usage of SIP with=
 the 3GPP IMS and if a device is not using IMS without an IMEI then it will=
 use a UUID as the SIP instance ID as per RFC 5626. If a device without an =
IMEI uses IMS then it will also
 still use a UUID as the SIP instance ID as per RFC 5626. This is specified=
 also in the 3GPP IMS specification TS 24.229 as well as the above draft.<d=
iv class=3D"im"><br>
<br>
So applications running on devices that don&#39;t have an IMEI can still us=
e SIP for sessions.<br>
<br>
The IMEI which has been used in mobile devices for 20 years also survives d=
evice wipes for the circuit switched calling capability as used by billions=
 of mobiles today with 2G and 3G networks. So again how is this more harmfu=
l for 4G than the current situation
 with 2G and 3G if a mobile device is transferred to a new owner?<br>
<br>
Andrew<br>
=C2=A0<br>
</div></font><br>
=C2=A0<br>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in =
0in 0in">
<font style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-s=
erif&quot;"><b>From</b>: Andrew Allen [mailto:<a href=3D"mailto:aallen@blac=
kberry.com" target=3D"_blank">aallen@blackberry.com</a>]
<br>
<b>Sent</b>: Saturday, July 20, 2013 11:48 PM Central Standard Time<br>
<b>To</b>: <a href=3D"mailto:tbray@textuality.com" target=3D"_blank">tbray@=
textuality.com</a> &lt;<a href=3D"mailto:tbray@textuality.com" target=3D"_b=
lank">tbray@textuality.com</a>&gt; <br>
<b>Cc</b>: <a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ietf.org=
</a> &lt;<a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ietf.org</=
a>&gt; <br><div><div class=3D"h5">
<b>Subject</b>: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt <br>
</div></div></font>=C2=A0<br>
</div><div><div class=3D"h5">
<font style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:#1f497d"><br>
Tim<br>
<br>
Firstly as stated in<br>
<a href=3D"http://datatracker.ietf.org/doc/draft-allen-dispatch-imei-urn-as=
-instanceid/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-allen=
-dispatch-imei-urn-as-instanceid/</a><br>
the use of the IMEI as a SIP Instance ID only pertains to usage of SIP with=
 the 3GPP IMS and if a device is not using IMS sing IMS without an IMEI use=
s IMS then it will still use a UUID as the SIP instance ID as per RFC 5626.=
 If a device without an IMEI uses
 IMS then it will also still use a UUID as the SIP instance ID as per RFC 5=
626. This is specified also in the 3GPP IMS specification TS 24.229 as well=
 as the above draft.<br>
<br>
So applications running on devices that don&#39;t have an IMEI can still us=
e SIP for sessions.
<br>
<br>
The IMEI which has been used in mobile devices for 20 years also survives d=
evice wipes for the circuit switched calling capability as used by billions=
 of mobiles today with 2G and 3G networks. So again how is this more harmfu=
l for 4G than the current situation
 with 2G and 3G if a mobile device is transferred to a new owner?<br>
<br>
Andrew</font><br>
=C2=A0<br>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in =
0in 0in">
<font style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-s=
erif&quot;"><b>From</b>: Tim Bray [mailto:<a href=3D"mailto:tbray@textualit=
y.com" target=3D"_blank">tbray@textuality.com</a>]
<br>
<b>Sent</b>: Saturday, July 20, 2013 07:01 PM Central Standard Time<br>
<b>To</b>: Andrew Allen <br>
<b>Cc</b>: <a href=3D"mailto:scott.brim@gmail.com" target=3D"_blank">scott.=
brim@gmail.com</a> &lt;<a href=3D"mailto:scott.brim@gmail.com" target=3D"_b=
lank">scott.brim@gmail.com</a>&gt;; <a href=3D"mailto:ietf@ietf.org" target=
=3D"_blank">ietf@ietf.org</a> &lt;<a href=3D"mailto:ietf@ietf.org" target=
=3D"_blank">ietf@ietf.org</a>&gt;
<br>
<b>Subject</b>: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt <br>
</font>=C2=A0<br>
</div>
<div dir=3D"ltr">On Sat, Jul 20, 2013 at 3:20 PM, Andrew Allen <span dir=3D=
"ltr">&lt;<a href=3D"mailto:aallen@blackberry.com" target=3D"_blank">aallen=
@blackberry.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">
Can it please be explained how the IMEI URN when used as stated in <a href=
=3D"http://datatracker.ietf.org/doc/draft-allen-dispatch-imei-urn-as-instan=
ceid/" target=3D"_blank">
http://datatracker.ietf.org/doc/draft-allen-dispatch-imei-urn-as-instanceid=
/</a><br>
Is any more harmful than as the IMEI is used today by over 90% of mobile ph=
ones in use today worldwide?<br>
</blockquote>
<div><br>
</div>
<div>It survives device wipes, which usually happen upon change of device o=
wnership.=C2=A0
<br>
<br>
I=E2=80=99m not an expert in your application domain, so pardon me if this =
question is hopelessly naive: It seems that this identifier is related in s=
ome way to SIP sessions.=C2=A0 It seems that it would be a common operation=
 to launch a SIP session on a device such as
 a WiFi-only tablet, or an iPod touch, that doesn=E2=80=99t have an IMEI.=
=C2=A0 Is this a problem?<br>
<br>
</div>
<div>=C2=A0-T<br>
</div>
<div>=C2=A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<span><font color=3D"#888888"><br>
Andrew<br>
</font></span>
<div><br>
----- Original Message -----<br>
From: Scott Brim [mailto:<a href=3D"mailto:scott.brim@gmail.com" target=3D"=
_blank">scott.brim@gmail.com</a>]<br>
</div>
<div>Sent: Saturday, July 20, 2013 03:55 PM Central Standard Time<br>
To: Andrew Allen<br>
</div>
<div>Cc: <a href=3D"mailto:tbray@textuality.com" target=3D"_blank">tbray@te=
xtuality.com</a> &lt;<a href=3D"mailto:tbray@textuality.com" target=3D"_bla=
nk">tbray@textuality.com</a>&gt;;
<a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ietf.org</a> &lt;<a=
 href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ietf.org</a>&gt;<br>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt<br>
<br>
</div>
<div>
<div>On Sat, Jul 20, 2013 at 4:08 PM, Andrew Allen &lt;<a href=3D"mailto:aa=
llen@blackberry.com" target=3D"_blank">aallen@blackberry.com</a>&gt; wrote:=
<br>
&gt; Tim<br>
&gt;<br>
&gt; The quote is from RFC 5626 which also states:<br>
&gt;<br>
&gt; &quot;3.1. Summary of Mechanism<br>
&gt;<br>
&gt; Each UA has a unique instance-id that stays the same for this UA even =
if the<br>
&gt; UA reboots or is power cycled.&quot;<br>
&gt;<br>
&gt; Since the UUID in the instance ID is also static how is this significa=
ntly<br>
&gt; different in terms of privacy concerns from the IMEI being used as an<=
br>
&gt; instance ID?<br>
<br>
You&#39;re not demonstrating that an IMEI is just as good, you&#39;re<br>
demonstrating that a UUID is just as bad.<br>
<br>
</div>
</div>
<div>
<div>---------------------------------------------------------------------<=
br>
This transmission (including any attachments) may contain confidential info=
rmation, privileged material (including material protected by the solicitor=
-client or other applicable privileges), or constitute non-public informati=
on. Any use of this information
 by anyone other than the intended recipient is prohibited. If you have rec=
eived this transmission in error, please immediately reply to the sender an=
d delete this information from your system. Use, dissemination, distributio=
n, or reproduction of this transmission
 by unintended recipients is not authorized and may be unlawful.<br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
--------------------------------------------------------------------- <br><=
/div></div>
This transmission (including any attachments) may contain confidential info=
rmation, privileged material (including material protected by the solicitor=
-client or other applicable privileges), or constitute non-public informati=
on. Any use of this information
 by anyone other than the intended recipient is prohibited. If you have rec=
eived this transmission in error, please immediately reply to the sender an=
d delete this information from your system. Use, dissemination, distributio=
n, or reproduction of this transmission
 by unintended recipients is not authorized and may be unlawful.
--------------------------------------------------------------------- <br><=
div class=3D"im">
This transmission (including any attachments) may contain confidential info=
rmation, privileged material (including material protected by the solicitor=
-client or other applicable privileges), or constitute non-public informati=
on. Any use of this information by anyone other than the intended recipient=
 is prohibited. If you have received this transmission in error, please imm=
ediately reply to the sender and delete this information from your system. =
Use, dissemination, distribution, or reproduction of this transmission by u=
nintended recipients is not authorized and may be unlawful.
</div></div>

</blockquote></div><br></div>

--047d7b2e75cc73298104e20915a7--

From sm@elandsys.com  Sun Jul 21 13:00:43 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9729421F9DBA for <ietf@ietfa.amsl.com>; Sun, 21 Jul 2013 13:00:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.593
X-Spam-Level: 
X-Spam-Status: No, score=-102.593 tagged_above=-999 required=5 tests=[AWL=-0.038, BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rnU+5PLq1Bxd for <ietf@ietfa.amsl.com>; Sun, 21 Jul 2013 13:00:43 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id EACC121F991E for <ietf@ietf.org>; Sun, 21 Jul 2013 13:00:41 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.146.202]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r6LK0Pan018334 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 21 Jul 2013 13:00:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1374436839; bh=AMn81WdZ/3jZGGVLa2KWS64CrC9oW6VkLwSRalXKL2w=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=a9Q5cHiXhBCq85tGq+2BAS/eIKLyKR0ASWc80A374XVnN/8I1KNL+DCIqkTG+Th3E CHr3vU34RBq4r29ob00A4r3YAwSwEK4Di7zfwSKUOkjmzZN7qqu8sHBsq/LhCM9lKh tkaTX3RDOqbFfWuyjVHrmvAvnNV7lkAq2XjG7HXc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1374436839; i=@elandsys.com; bh=AMn81WdZ/3jZGGVLa2KWS64CrC9oW6VkLwSRalXKL2w=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Vuytb3bsn9cpNUezFTtVkRRrjG2fFWvpatGfJ2X3WU58wn1qm7XscT4KRNqmYW4Kz FcHQgzxO4jGJLdHQkHZHkqVV6ZyNxzj+piug3hvghrjiHr3iRLZCqiR36dHphpUCXg Akbxd6V0dWwnsJzoDPYl1c8xhjZaNLAA6S50DxI8=
Message-Id: <6.2.5.6.2.20130721070808.0c808140@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 21 Jul 2013 09:38:24 -0700
To: ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
In-Reply-To: <BBF5DDFE515C3946BC18D733B20DAD2338DD2606@XMB104ADS.rim.net >
References: <6.2.5.6.2.20130720193906.06cdd008@resistor.net> <BBF5DDFE515C3946BC18D733B20DAD2338DD2606@XMB104ADS.rim.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: John C Klensin <john@jck.com>, tbray@textuality.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Jul 2013 20:00:43 -0000

At 00:03 21-07-2013, Andrew Allen wrote:
>The reason why the IMEI namespace is being registered as a GSMA 
>namespace and not as part of the 3GPP namespace is that the GSMA has 
>the responsibility for IMEI assignment and hence in maintaining 
>uniqueness of the namespace. It has nothing to do with IPR which was 
>extensively discussed on the dispatch list.

I read the dispatch mailing list.  I did not see the extensive 
discussion.  I saw the following comment "Surely that is just trying 
to turn the IETF into the policeman".

>The primary purpose of the IMEI is for preventing use of stolen 
>mobile phones and enabling emergency calls to be made from mobiles 
>that don't have a valid subscription.

 From what I read the main purpose of the IMEI is to be able to take 
measures against stolen phones and against equipment which the use 
cannot be accepted for technical or safety reasons.  The secondary 
purpose is the tracing of malicious calls.

There is an apps which sends the IMEI in a 
cryptographically-protected form over the network.  For what it is 
worth, it's MD5.

There has been some work in the IETF on emergency calls (see service URN).

At 00:12 21-07-2013, Andrew Allen wrote:
>As John pointed out having the sub namespace reviewed by IETF 
>provides the opportunity to add text to address privacy concerns 
>with any inappropriate usage.

I don't think that it is the role of the IETF to determine whether 
the usage of a sub-namespace is appropriate or not as it can cause 
namespace management issues.

I tried the explain the subtlety between privacy concerns and privacy 
considerations.  The IMEI can also be used as a customer identifier.

Regards,
S. Moonesamy  


From fred@cisco.com  Sun Jul 21 21:34:48 2013
Return-Path: <fred@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EB7E21F99F7; Sun, 21 Jul 2013 21:34:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.999
X-Spam-Level: 
X-Spam-Status: No, score=-111.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_INVITATION=-2, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZbJFQiGbhsHK; Sun, 21 Jul 2013 21:34:44 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 6F23F11E80BA; Sun, 21 Jul 2013 21:34:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6889; q=dns/txt; s=iport; t=1374467683; x=1375677283; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=Yq7f1oD/CPxon2SdXUUY1R0GXoEYZCioul0LGIoKbcg=; b=OlWL47Zb++54PTGHJ9sriaKNz/uD6L526BqMBv4SGmvlfOO+nigupNR/ KMCB6FQe6AO1Saq3fWhAyxqRMndeGAeWgH7WwJHCG0K+Gq466HRDoOnJU hFfXCzKWq0D9fhNHilSBi/XHxqSrEtC6yBj4p0+iD3bMec6Y0CJK96lDl w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFAFy17FGQ/khM/2dsb2JhbABQAQmDBjXBAIEPFnSCJAEBAQMBOj8FCwsOOFcGEQIUBodwBgy2RASOWgGBCDMHgxBuA5ddhiOLKoFZgTs6BA
X-IronPort-AV: E=Sophos;i="4.89,716,1367971200"; d="scan'208";a="157245298"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-1.cisco.com with ESMTP; 22 Jul 2013 04:34:41 +0000
Received: from [10.61.166.209] ([10.61.166.209]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r6M4Ybnu027776 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 22 Jul 2013 04:34:38 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Mentoring Electronic Participants [was Invitation to request an	IETF mentor]
From: Fred Baker <fred@cisco.com>
In-Reply-To: <51EAB100.7090508@isdg.net>
Date: Mon, 22 Jul 2013 06:34:36 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <1D644C45-600A-4FCC-8B5C-1CD8449F2F97@cisco.com>
References: <20130717225841.14002.89245.idtracker@ietfa.amsl.com> <51EAB100.7090508@isdg.net>
To: Hector Santos <hsantos@isdg.net>
X-Mailer: Apple Mail (2.1508)
Cc: IETF Chair <chair@ietf.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Jul 2013 04:34:48 -0000

On Jul 20, 2013, at 5:47 PM, Hector Santos <hsantos@isdg.net> wrote:

> What generally happens when an individual I-D is submitted?   Is there =
an overseer of the submissions and decides there is something that =
interest the IETF?

Hmm. Define "IETF". It is in some sense an organization (I call it a =
"disorganization"), and in some sense a community of people. When we =
talk about something being "interesting to the IETF", we're talking =
about it being interesting to people.

To my knowledge, no. When I see a general individual submission (of =
which there are more than a few; in my mirror, I have 2240 current =
drafts, of which the identifiers of 1729 contain the identify of a =
working group, and 675 are working group drafts, leaving 511 general =
submissions and 1054 individual submissions to various working groups), =
it is usually because someone brought it to my attention. In most cases, =
that means that they posted it without specifically targeting a working =
group or targeting the wrong working group, and are now shopping it =
around.

As a working group chair, I have mixed views on this. I'm certainly =
willing to look at general submissions; v6ops will discuss two of them =
this time around, one of which has been previously discussed in homenet =
and one has been discussed in RIPE. However, I have tooling to help me =
manage my working group that sees general submissions as noise. In the =
tool that updates and manages my mirror, I have another tool that =
notices a new -00 draft whose name contains my working group's =
identifier, and sends two emails, one to the working group mailer =
advising the group of the draft and inviting discussion, and another to =
the author(s) asking some pointed questions about it's applicability and =
charter relevance. This way, it doesn't depend on my being at the top of =
my game on the magic day, and it doesn't depend on the author contacting =
me; "I", for some value of that word, initiate the conversation upon =
posting of the draft. When I create my agenda, I have another tool that =
searches my mirror for drafts containing the identity of my working =
group and others I add, and sorting them into four buckets - those older =
than the last IETF's date and those newer, and within those, those with =
names that start with draft-ietf- and those that don't. Looking at =
https://datatracker.ietf.org/doc/search/?search_submit=3D&activeDrafts=3Do=
n&name=3Dv6ops&rfcs=3Don&sortBy=3Dstatus, which also looks for my =
working group's identity, I then manually reclassify some of them as "in =
the IESG's processes" or "in the RFC Editor's queue", and searching my =
mail database for the draft's base name (the name less the version =
extension) allows me to look at the history of discussion of the =
specific draft. The drafts that end up on my agenda have been written or =
updated since the last meeting, are "in the working group", and have had =
supportive list discussion. Anything else is a special case - and =
general submissions are always special cases.

I can't speak for other chairs. I would imagine they do something =
similar, but the way they do it is likely different.

So, if you don't know what working group your draft might be relevant =
to, by all means submit it as a general submission (e.g., with a name =
like "draft-<topic>-nn.txt"). When you have done so, it is your job to =
make people that might be interested in it aware of it, and to promote =
discussion. If you submit an individual submission to a working group =
(e.g., with a name like "draft-santos-<wg>-<topic>-nn.txt"), the =
secretariat does not announce it to the working group, but the working =
group chair should notice it at some point. You are well advised to send =
a note to the working group mailer promoting discussion. The only drafts =
that are automatically announced are working group drafts (e.g., with a =
name like "draft-ietf-<wg>-<topic>-nn.txt").=20

By the way, if you submit draft-<topic>-00.txt and subsequently submit =
draft-santos-<wg>-<topic>-00.txt, or submit =
draft-santos-<wg>-<topic>-nn.txt and subsequently submit =
draft-ietf-<wg>-<topic>-00.txt, or in general change the name of a =
draft, working group chairs appreciate your note to =
internet-drafts@ietf.org noting that "draft <this> replaces draft =
<that>". It helps us track drafts, and know what's on our plate and what =
isn't.

As a matter of statistics, since March 11 and coming into IETF 87, we =
have had 704 new (-00) Internet Drafts, of which 129 have been working =
group drafts, 374 have been individual submissions to working groups, =
and (the difference) 201 have been general submissions. For IETF 86, the =
submission breakout by month was:

                     individual
                     submission
                        to
          working     working     general
           group       group
    Nov     19          45          27
    Dec     19          39          19
    Jan     11          37          35
    Feb     27         185          49
    Mar      0           0           2

Which is to say that the vast majority of new drafts arrived more or =
less in a block in February, and they were by and large individual =
submissions to working groups. Oh, you wanted commentary, and you =
thought it was going to magically happen? How many of those new drafts =
did you notice and comment on? The IETF is, in this context, a community =
of people that read and comment on drafts...

Please note, all of that is about -00 drafts; I didn't look at updated =
drafts, which would be about 2/3 of drafts at any given time.

The best analogy to describe this, perhaps, is a news boy in Time =
Square, Trafalgar Square, or your favorite counterpart. You have a new =
idea or comment, and it might be a very useful or important one. The =
square is noisy, and there are a lot of people with comments that they =
think are important. We depend on crowd sourcing. If a lot of people say =
"hey, this is interesting, we should discuss it", we discuss it. If that =
doesn't happen... It's not because we like you, or we don't like you. =
It's not about you, or where you come from, or whatever. It's about =
whether your comment rises above the din. Trust me, area directors and =
working group chairs do what they do, and are chosen to do what they do, =
because they are interested, not because they want to prevent progress. =
If you make a comment, think about what mailers or people it might be =
appropriate to, and if that means creating a new working group or mailer =
context, so be it, think about the area it belongs in and what area =
director might take you where you want to go. Communities interested in =
a topic get attention. Create or contribute to one.=

From jari.arkko@piuha.net  Mon Jul 22 06:07:38 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1781E21E8091 for <ietf@ietfa.amsl.com>; Mon, 22 Jul 2013 06:07:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.426
X-Spam-Level: 
X-Spam-Status: No, score=-103.426 tagged_above=-999 required=5 tests=[AWL=1.173, BAYES_00=-2.599, GB_I_INVITATION=-2, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H65GI9tory3b for <ietf@ietfa.amsl.com>; Mon, 22 Jul 2013 06:07:32 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 3D7D111E8101 for <ietf@ietf.org>; Mon, 22 Jul 2013 06:07:32 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id C5EE62CC67; Mon, 22 Jul 2013 16:07:30 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aBsRVq1SPNuD; Mon, 22 Jul 2013 16:07:30 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 35ABC2CC65; Mon, 22 Jul 2013 16:07:30 +0300 (EEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Mentoring Electronic Participants [was Invitation to request an IETF mentor]
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <51EAB100.7090508@isdg.net>
Date: Mon, 22 Jul 2013 16:07:30 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <0F23A27F-35D8-471D-AE49-B9FE0D2426C6@piuha.net>
References: <20130717225841.14002.89245.idtracker@ietfa.amsl.com> <51EAB100.7090508@isdg.net>
To: Hector Santos <hsantos@isdg.net>
X-Mailer: Apple Mail (2.1508)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Jul 2013 13:07:38 -0000

Hector,

You raise an important point - and one that isn't just about mentoring, =
but the overall approach in our ability to involve more remote =
participation. We have and will continue to improve the facilities to =
improve the remote participation experience. Looking back, one big =
change in the way of working at the IETF in the last couple of years has =
been that many working groups have virtual meetings. Not so much as a =
replacement of the physical meetings, but as a place to do the =
day-to-day or month-to-month work. Like you, I believe the future is in =
over-the-Internet collaboration :-) Though as in any human interaction =
the physical meeting still have a place as well=85 And the success of =
the IETF depends on the ease of bringing good ideas here and getting =
them adopted. Including the ability to start things without always =
having to wait for a meeting and attending it physically.

It is true that the mentoring trial is more focused on the participants =
in the meeting. See the response from Brian. Perhaps it would be useful =
to consider extending it in the future to cover those who are doing work =
in some of our working groups but not attending the meetings. But I do =
think that the mentor program is focused on making people capable of =
getting their work done at the IETF, including both those who might =
spend a large part of their day with it as well as those with a narrower =
interest in a specific topic. It is always useful to understand the =
process and get to know others involved in it. As you know, most =
Internet technology efforts will in any case involve multiple aspects, =
such as the functionality itself, operations, security, etc.

As for your questions about individual I-Ds, the answer is that usually =
nothing happens on its own. Whether you are on site or attending =
remotely or just participating in mailing list discussions, the =
procedure is the same. The IETF is about standards, and standards are =
about groups of people agreeing to some common ideas. In order to make =
this happen, you need to find your group of like-minded people who have =
an interest in achieving something similar. Usually you find this from =
your colleagues in other organisations, from others in hallway =
discussions, or by sending a proposal to a working group and getting =
others interested in it. Ultimately, a proposal has to be brought =
formally to a working group or a new working group charted for the work. =
If adopted, it will be worked on and eventually comes out as an RFC.

Any of the above things - starting new work, talking about I-Ds, finding =
like-minded people can and has been done remotely. Although there are =
some things that are easier when you are there in person. As a result, =
most IETF work involves some amount of activity in the physical =
meetings. I'd love to see ideas on how we can make it easier for people =
to participate without necessarily attending the meetings.

Jari


From stefan.winter@restena.lu  Mon Jul 22 08:20:42 2013
Return-Path: <stefan.winter@restena.lu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B79711E80AE for <ietf@ietfa.amsl.com>; Mon, 22 Jul 2013 08:20:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.974
X-Spam-Level: 
X-Spam-Status: No, score=-1.974 tagged_above=-999 required=5 tests=[AWL=0.025,  BAYES_00=-2.599, J_CHICKENPOX_36=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A6RXIKj-75Wd for <ietf@ietfa.amsl.com>; Mon, 22 Jul 2013 08:20:41 -0700 (PDT)
Received: from smtprelay.restena.lu (smtprelay.restena.lu [IPv6:2001:a18:1::62]) by ietfa.amsl.com (Postfix) with ESMTP id 20F2911E80F6 for <ietf@ietf.org>; Mon, 22 Jul 2013 08:20:36 -0700 (PDT)
Received: from smtprelay.restena.lu (localhost [127.0.0.1]) by smtprelay.restena.lu (Postfix) with ESMTP id 0618A1058E for <ietf@ietf.org>; Mon, 22 Jul 2013 17:20:35 +0200 (CEST)
Received: from aragorn.restena.lu (aragorn.restena.lu [IPv6:2001:a18:1:8::155]) by smtprelay.restena.lu (Postfix) with ESMTPS id EA3861058C for <ietf@ietf.org>; Mon, 22 Jul 2013 17:20:34 +0200 (CEST)
Message-ID: <51ED4DBC.5000409@restena.lu>
Date: Mon, 22 Jul 2013 17:20:28 +0200
From: Stefan Winter <stefan.winter@restena.lu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: 'IETF Discussion Mailing List' <ietf@ietf.org>
Subject: Re: Last Call: <draft-ietf-emu-eap-tunnel-method-07.txt> (Tunnel EAP	Method (TEAP) Version 1) to Proposed Standard
X-Enigmail-Version: 1.5.1
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="----enig2INGWVHLSFGKNKTJCHCSM"
X-Virus-Scanned: ClamAV
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Jul 2013 15:20:42 -0000

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

Hello,

I didn't follow TEAP's creation process in enough detail, so may have
missed some information. Apologies if what I write below is noise.

I have two questions about TEAP Version 1 which I don't find
satisfactorily answered in the draft. I wonder if they are worth a
discussion.

Q1: How to determine Server-ID /deterministically/ ?
=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=3D=3D=
=3D=3D
One crucial check for an EAP peer to execute is whether it is talking to
the server it expects to; the primary means are:
a) is the server certificate issued by a CA the EAP peer trusts for the
purposes of EAP?
b) is the name of the server the expected one?

a) is pretty clear, RFC5280 section 6 provides for an algorithm to
determine whether a given certificate was issued by a trusted anchor;
and that RFC is referenced in the TEAP draft.

b) is less clear. The TEAP draft in section 3.4 states
  "the Server-Id is determined in a similar fashion as stated
   above for the Peer-Id; e.g., the subject or subjectAltName field in
   the server certificate defines the Server-Id."

First of all, I think the "e.g." should be an "i.e." because these two
fields are the only part of the certificate that yields server identity
information.

More important than that though is the deliberately indeterministic "or"
in that sentence.

Certificates may carry only a Subject DN, or only subjectAltNames, or
both; if they carry both names, the CN part of the DN may be the same as
one of the subjectAltName values, or it may not.

With the sentence being an "or", EAP peer implementations which are
configured to trust a sever name "aaa.foo.bar" can be presented the same
certificate, but come to different conclusions whether this is the
server they expect, depending on
1) the order in which they inspect the fields (first DN, or first sANs)
2) how they behave if their preferred field does not match or is not
part of the certificate (bail out, or try the other field)
3) how they behave if they observe discrepancies between the two (e.g.
CN matches, but there are sANs and none of them matches the CN).

The draft could make this behaviour deterministic with a few simple rules=
=2E

1) prefer the set of subjectAltName:DNS fields over CN
2) fallback to CN if none of the subjectAltName fields matches
3) discrepancies between the two fields are not enforced

Of course, some EAP peer might be configured for "strange" other sANs;
maybe sAN:iPAddr. The validation rules above would then be analogous for
these fields.

Q2: Does the draft need text regarding i18n in EAP-Response/Identity?
=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=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
In the recent discussion about ABFAB's eapapplicability document, we
concluded that either EAP or all the EAP methods need patching up to
prevent an encoding/normalisation mess. With TEAP being in IETF LC, I
took a look at how it handles User-Name encoding, normalisation, and
whether there is a nice place inside the TEAP spec to nail things.

TEAP takes the (sensible) approach of not caring how its own context
came to be. It states in its Protocol Overview:

  "TEAP authentication occurs in two phases after the initial EAP
   Identity request/response exchange."

I.e. it simply assumes that EAP peer and EAP server "somehow" found each
other and decided to use TEAP.

It defines Peer ID's in its phase two; for basic auth it sanely mandates
UTF-8 encoding for these (but no word about normalisation); section 4.2.1=
5.

Where TEAPs inner method is EAP - there are no provisions regarding
encoding or normalisation. That is the same situation that EAP (outside)
has as well; TEAP basically becomes an EAP lower layer itself. I guess
the draft expects that the inner method has some notion of a username,
and the inner method will export it to the EAP-Response/Identity of
TEAP's phase 2 EAP exchange.

So in phase 2 of TEAP, there's either UTF-8, or an unknown encoding
inherited from an inner EAP method.
[As an aside: If the inner method if EAP-TLS, then the ambiguity from
question 1 occurs again: the Peer-Id is the subject "or" a
subjectAltName (if there's a set of subjectAltNames in the certificate
*which* is considered the Peer-Id? That should be clarified in the draft)=
=2E]

TEAP mentions that username privacy is optional. If username privacy is
not used, then the common way of constructing EAP-Identity is by taking
the string that is going to used during phase 2 and put that into the
EAP-Response/Identity. In that case, the encoding being used for that
EAP-Response/Identity is unknown with TEAP; because it may depend on an
inner EAP method which is not known to TEAP, and where TEAP cannot
mandate UTF-8.

If username privacy is used, there is no relation to the phase 2
identity and what's put into EAP-Response/Identity. In particular, the
encoding is not fixed.

TEAP mentions in its section on that topic that NAIs exist, and
references RFC4282, which has known deficiencies in terms of i18n. I
believe it would be better not to mention RFC4282.

It is good that NAIs are not mentioned normatively in that section;
after all Peer-Ids and also anonymous outer identities may or may not be
NAI realms - they can also be simple strings with no particular
structure. But since they can be just that - simple strings with no
structure - there is also no encoding known for these incoming strings.

I know, TEAP doesn't (and doesn't *have to*) care about the outer
identities, because they happen outside of itself and are not of
importance for neither its phase 1 or 2.

And still, some spec needs to say something about the encoding! Or we'll
never have clarity about what's coming in.

After taking a step back, looking at where to properly fix things, I'm
becoming more and more convinced that chasing individual EAP methods to
include normative language about something that happens outside their
own method-protocol; and in TEAP's case being at the whim that some
other EAP method which happens to have been configured as TEAPs inner
method has already done its homework to include provisions about
exporting its inner IDs in a sane format for the TEAP exchange as a
whole to become deterministically encoded is - impractical.

The much more straightforward approach is to mandate EAP (core) to
always force use of UTF-8 for EAP-Response/Identity.

In summary (kudos for reading this far!)
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
IMHO, TEAP should fix the following points

* Peer-Id and Server-Id should become deterministic.
* When discussing NAIs, mentions of RFC4282 should be removed, or
qualified so that readers of spec are urged to read (exclusively) its
successor as soon as it becomes available.

Things that might be tackled in TEAP, but my personal preference would
be to do that in EAP core:

* Specify the encoding in which phase 2's Peer-Id is used during the EAP
negotiation that precedes the TEAP exchange. If Peer-Ids are not used
(i.e. identity privacy support is enabled), specify in which encoding
the privacy-preserving identity hints are expected.

Thanks for reading this :-)

Note how I did not go into detail about normalization; similar
principles apply here, but the mail is long enough.

Greetings,

Stefan Winter

--=20
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education National=
e et
de la Recherche
6, rue Richard Coudenhove-Kalergi
L-1359 Luxembourg

Tel: +352 424409 1
Fax: +352 422473


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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlHtTcIACgkQ+jm90f8eFWYDFQCfe9BF5QJbZz0lXkP7M5m7yMqB
ixEAnjSYNYzetAUmThqLfhqwaTAh7qrp
=Tw7O
-----END PGP SIGNATURE-----

------enig2INGWVHLSFGKNKTJCHCSM--

From kewisch@gmail.com  Mon Jul 22 04:55:30 2013
Return-Path: <kewisch@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C855B21E8064; Mon, 22 Jul 2013 04:55:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x+cbDWmCKXYb; Mon, 22 Jul 2013 04:55:29 -0700 (PDT)
Received: from mail-bk0-x22d.google.com (mail-bk0-x22d.google.com [IPv6:2a00:1450:4008:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 25B7D21E8056; Mon, 22 Jul 2013 04:55:27 -0700 (PDT)
Received: by mail-bk0-f45.google.com with SMTP id je9so2450445bkc.18 for <multiple recipients>; Mon, 22 Jul 2013 04:55:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type; bh=PZaHTgAq9MYzJSbmvadviiQu/6RvvxuUoJgoVz0svHI=; b=ezRR0lZMQMdvg/75ZI7FihrSUhgITCVlqk+z4l25vzO/MC6Tt5SB0IsWkpQAq430nw dvc5TMa30qb2u857IhJHE2O/3gungbZUi63ivNJcgcmUJ3+atBlhZZSHhaAwFRkY+l8/ qKzaL4rkjPIDW1Mt3/IXyCrTetnP+Wl+PIi2ruqV8yxczH9C6vezqVIb83IQMCTnIQ0k N6Zw8a5KjhBJQNoeVwgA59MM1Ekun9cw2UjesvsVUhGi8UdHVIoT3Opi0NxlJCWHytVt HrHA4Z+Juixqy45sTdc5MJ4IXEqW1aA1NcxwjAgzZjseKMRJO3MIq98T7ZgJ+E2C+mU3 EX5g==
X-Received: by 10.204.231.137 with SMTP id jq9mr3927043bkb.150.1374494127029;  Mon, 22 Jul 2013 04:55:27 -0700 (PDT)
Received: from oskar.lan (f054118207.adsl.alicedsl.de. [78.54.118.207]) by mx.google.com with ESMTPSA id eu16sm6805174bkc.0.2013.07.22.04.55.25 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 22 Jul 2013 04:55:26 -0700 (PDT)
Message-ID: <51ED1DAD.90904@gmail.com>
Date: Mon, 22 Jul 2013 13:55:25 +0200
From: Philipp Kewisch <kewisch@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:22.0) Gecko/20100101 Thunderbird/22.0
MIME-Version: 1.0
To: Ben Campbell <ben@nostrum.com>,  draft-ietf-jcardcal-jcard.all@tools.ietf.org
Subject: Re: Gen-ART LC/Telechat Review of draft-ietf-jcardcal-jcard-04
References: <E8A52EC5-BF67-4F5B-A810-0D69D01377AA@nostrum.com>
In-Reply-To: <E8A52EC5-BF67-4F5B-A810-0D69D01377AA@nostrum.com>
Content-Type: multipart/alternative; boundary="------------070106020800040203080502"
X-Mailman-Approved-At: Mon, 22 Jul 2013 08:28:35 -0700
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>, IETF-Discussion list <ietf@ietf.org>, "jcardcal@ietf.org" <jcardcal@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Jul 2013 11:55:31 -0000

This is a multi-part message in MIME format.
--------------070106020800040203080502
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


On 7/17/13 12:27 AM, Ben Campbell 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 wait for direction from your document shepherd
> or AD before posting a new version of the draft.
>
> Document:  draft-ietf-jcardcal-jcard-04
> Reviewer:  Ben Campbell
> Review Date:  2013-07-16
> IETF LC End Date: 2013-07-18
> IESG Telechat date: 2013-07-18
>
> Note: This draft is on the IESG Telechat agenda on the same date as it completes IETF Last Call. Therefore, this review serves both purposes.
>
> Summary: This draft is almost ready for publication as a proposed standard. There are a few minor issues and editorial nits that should be considered prior to publication.
>
> Major issues:
>
> -- None
>
> Minor issues:
>
> -- Section 1, design considerations:
>
> You mention that the semantic results should survive round-tripping, but the order of fields might not. I gather there are other changes that might occur from the literal text, right? (e.g. Case changes, some optional parameter usage). If so, it might be worth clarifying that.
Yes, thanks. I've added the case changes since even though upper-case is 
RECOMMENDED in rfc6350, it is indeed information that is lost. Could you 
elaborate which optional parameters you mean? If you mean the GROUP 
parameter, this parameter is to be removed when converting back into 
vCard, so there is no change to the original group construct.

I neither found nor recall any other examples where it would be 
necessary to add anything.

>
> -- 3.1, 2nd paragraph:
>
> I assume the removal of escaping means that one renders the escaped text, not simply removes it, right? Is that as simple as removing the escape characters in vCards? I assume this doesn't apply to any content-specific escaping inside vCard fields, e.g. URI escaping, right? If so, it might be worth mentioning.
I agree "removed" isn't the best word, I wasn't really happy with the 
alternatives though, maybe "unescape" will work out (not sure if that is 
a real word?). If not, then I'd go with your "render", although to me 
that always suggests it is actually displayed. I'm happy for more 
suggestions though:

OLD:
           When converting from vCard to jCard, lines MUST be unfolded 
first.
           Afterwards, vCard escaping MUST be removed.  The only 
escaping that
           may be applied is any escaping mandated by JSON (e.g., for 
control
           characters).

           The reverse order applies when converting from jCard to 
vCard. First,
           JSON escaping MUST be removed. Afterwards, vCard escaping MUST be
           applied. Finally, long lines SHOULD be folded as described in 
[RFC6350].

NEW:

           When converting from vCard to jCard, lines MUST be unfolded 
first.
           Afterwards, vCard escaping MUST be unescaped. The only 
escaping that
           may be applied is any escaping mandated by JSON (e.g., for 
control
           characters) and any content-specific escaping inside vCard 
values,
           e.g. URI escaping.

           The reverse order applies when converting from jCard to 
vCard. First,
           JSON escaping MUST be unescaped. Afterwards, vCard escaping 
MUST be
           applied. Finally, long lines SHOULD be folded as described in 
[RFC6350].
> -- 3.2.1.1:
>
> What happens for future versions of vCard? Do you simply use the new version number, or would we need a new version of this spec? I suspect the latter. If true, it might be worth mentioning that, or somewhere early in the draft mention that this spec is for vCard 4.0 only.
I'd love to hear from the WG here, but given vCard 5.0 can at least in 
theory be completely different, I think the correct thing to do would be 
to restrict this jCard document to 4.x and when 5.x comes around create 
a revision of the document. Of course the text could be changed so that 
its "valid until revised by another document", in case the changes in 
5.x are minor enough that no change in jCard is needed.

In any case, there should be a text change that any 4.x revision is 
allowed. For example, I recently read a suggestion for signed vCards 
that might use a version "4.0s".
> -- sections 3.4.3 and 3.4.4:
>
> Is the included ABNF a quotation of that in the referenced RFCs, or is it new and authoritative? If the former, it would be helpful to mention that in the text. (I note you did say that about the ABNF in the appendix).
The ISO specs don't provide a direct BNF for any of their constructs. 
Instead they show examples in the form:
Basic format: YYYYMMDD Example: 19850412
Extended format: YYYY-MM-DD Example: 1985-04-12

The ABNF in jCard mimics this format, so it is not new, but given it 
matches I guess we could say its authoritative. Unless someone tells me 
otherwise (I'm still a bit uncertain when something can be called 
authoritative), I'll change it by changing the hangText "ABNF Schema:" 
to "ABNF Schema (authoritative):" in both sections.

> -- 3.4.11:
>
> If RFC6350 says that use of the timezone offset is NOT RECOMMENDED, can you elaborate on why it's included here? (I can guess it's because people may still use it in vCards since it was a "MUST NOT", but it would be good to say something to that effect in the text.)
There is no other vCard property that uses a utc-offset as a type, so 
this is just for the sake of an example. RFC6350 Section 6.5.1 has the 
details, it says utc-offset SHOULD NOT be used on a TZ property. The 
alternative would be to use an x-property for the example, i.e

["x-clock-offset", {}, "utc-offset", "-05:00"]

Do you think we should use this instead?

>
> Nits/editorial comments:
>
> -- Section 1, paragraph 1:
>
> Please expand JSON on first mention.
Doing this in the introduction since you reference Section 1, paragraph 
1. It already appears in the abstract, should I expand it there 
instead/in addition?

As the first mention uses "JSON-based", I've reworded these two paragraphs:

OLD:
    As certain similarities exist between vCard and the iCalendar data
    format [RFC5545], there is also an effort to define a JSON-based data
    format for calendar information called jCal [I-D.ietf-jcardcal-jcal]
    that parallels the format defined in this specification.

    The purpose of this specification is to define "jCard", a JSON format
    for vCard data.  One main advantage to using a JSON-based format as
    defined in [RFC4627] over the classic vCard format is easier
    processing for JavaScript based widgets and libraries, especially in
    the scope of web-based applications.

NEW:
    As certain similarities exist between vCard and the iCalendar data
    format [RFC5545], there is also an effort to define a JSON-based data
    format for calendar information called jCal [I-D.ietf-jcardcal-jcal]
    that parallels the format defined in this specification.  The term
    JSON describes the JavaScript Object Notation defined in [RFC4627].

    The purpose of this specification is to define "jCard", a JSON format
    for vCard data.  One main advantage to using a JSON-based format over
    the classic vCard format is easier processing for JavaScript based
    widgets and libraries, especially in the scope of web-based
    applications.


>
> -- Section 1, paragraph 3:
>
> This paragraph seems redundant to paragraph 1.
Yes, the duplicate is now removed. Sorry about that!
>
> -- 1, paragraph 7: " Preserve the semantics of the vCard data."
>
> Imperative form sentence is confusing in context, and inconsistent with surrounding text.
OLD:
       Preserve the semantics of the vCard data.  While a simple consumer
       can easily browse the data in jCard, a full understanding of vCard
       is still required in order to modify and/or fully comprehend the
       directory data.

NEW:
      The vCard data semantics are to be preserved, allowing a simple
       consumer to easily browse the data in jCard.  A full understanding
       of vCard is still required in order to modify and/or fully
       comprehend the directory data.

>
> -- 1, paragraph 8:
>
> Sentence Fragment.
The original intent was to make this a list of considerations, but as 
the first sentences are full I agree this makes it seem weird. How is 
this? I'm a little unsure about the "must not", but since this is just a 
consideration for the document and not an order for the consumer I think 
its ok with this casing:

OLD:
       Ability to handle many extensions to the underlying vCard
       specification without requiring an update to this document.
NEW:
       Extensions to the underlying vCard specification must not lead to
       requiring an update to jCard.

>
> -- 3.2, Last Paragraph: "... for a parser check the data type..."
>
> Missing "to"?
Done

>
> -- 3.2.1.2, last paragraph before example:
>
> Should the "iCalendar" reference be "vCard" instead?
Yes, copy/paste fail from jCal. Fixed.
> -- 3.2.1.3, Last Paragraph:
>
> RFCTODO? I gather in the IANA section, that may be a placeholder for "this RFC", but that doesn't seem to fit here.
My intention was to keep the registration template as general as 
possible, RFCTODO indeed references "this RFC", I've defined an entity 
for it in the source. Do you want me to replace it with "this document" 
instead? I was thinking if the registration template is maybe copied out 
of the document and gathered somewhere, it would make sense to reference 
the document by its rfc number.

> -- 3.3.2: "Example 1:"
>
> Other examples are not numbered.
Fixed

> -- 5:
>
> More occurrences of RFCTODO
Same reason, they appear in a registration template. I'm happy to 
replace with "this document" in case I'm told the registration template 
is never extracted from the document without any processing.

Thank you for the review!


--------------070106020800040203080502
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 text="#000000" bgcolor="#FFFFFF">
    <br>
    <div class="moz-cite-prefix">On 7/17/13 12:27 AM, Ben Campbell
      wrote:<br>
    </div>
    <blockquote
      cite="mid:E8A52EC5-BF67-4F5B-A810-0D69D01377AA@nostrum.com"
      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 wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document:  draft-ietf-jcardcal-jcard-04
Reviewer:  Ben Campbell
Review Date:  2013-07-16
IETF LC End Date: 2013-07-18
IESG Telechat date: 2013-07-18

Note: This draft is on the IESG Telechat agenda on the same date as it completes IETF Last Call. Therefore, this review serves both purposes.

Summary: This draft is almost ready for publication as a proposed standard. There are a few minor issues and editorial nits that should be considered prior to publication.

Major issues:

-- None

Minor issues:

-- Section 1, design considerations:

You mention that the semantic results should survive round-tripping, but the order of fields might not. I gather there are other changes that might occur from the literal text, right? (e.g. Case changes, some optional parameter usage). If so, it might be worth clarifying that.</pre>
    </blockquote>
    Yes, thanks. I've added the case changes since even though
    upper-case is RECOMMENDED in rfc6350, it is indeed information that
    is lost. Could you elaborate which optional parameters you mean? If
    you mean the GROUP parameter, this parameter is to be removed when
    converting back into vCard, so there is no change to the original
    group construct.<br>
    <br>
    I neither found nor recall any other examples where it would be
    necessary to add anything.<br>
    <br>
    <blockquote
      cite="mid:E8A52EC5-BF67-4F5B-A810-0D69D01377AA@nostrum.com"
      type="cite">
      <pre wrap="">

-- 3.1, 2nd paragraph:

I assume the removal of escaping means that one renders the escaped text, not simply removes it, right? Is that as simple as removing the escape characters in vCards? I assume this doesn't apply to any content-specific escaping inside vCard fields, e.g. URI escaping, right? If so, it might be worth mentioning.</pre>
    </blockquote>
    I agree "removed" isn't the best word, I wasn't really happy with
    the alternatives though, maybe "unescape" will work out (not sure if
    that is a real word?). If not, then I'd go with your "render",
    although to me that always suggests it is actually displayed. I'm
    happy for more suggestions though:<br>
    <br>
    OLD:<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; When converting from vCard to jCard, lines MUST be
    unfolded first.<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Afterwards, vCard escaping MUST be removed.&nbsp; The only
    escaping that<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; may be applied is any escaping mandated by JSON (e.g., for
    control<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; characters).<br>
    <br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The reverse order applies when converting from jCard to
    vCard. First,<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; JSON escaping MUST be removed. Afterwards, vCard escaping
    MUST be<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; applied. Finally, long lines SHOULD be folded as described
    in [RFC6350].<br>
    <br>
    NEW:<br>
    <br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; &nbsp; When converting from vCard to jCard, lines MUST be
    unfolded first.<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Afterwards, vCard escaping MUST be unescaped. The only
    escaping that<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; may be applied is any escaping mandated by JSON (e.g., for
    control<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; characters) and any content-specific escaping inside vCard
    values,<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; e.g. URI escaping.<br>
    <br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The reverse order applies when converting from jCard to
    vCard. First,<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; JSON escaping MUST be unescaped. Afterwards, vCard
    escaping MUST be<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; applied. Finally, long lines SHOULD be folded as described
    in [RFC6350].<br>
    <blockquote
      cite="mid:E8A52EC5-BF67-4F5B-A810-0D69D01377AA@nostrum.com"
      type="cite">
      <pre wrap="">-- 3.2.1.1:

What happens for future versions of vCard? Do you simply use the new version number, or would we need a new version of this spec? I suspect the latter. If true, it might be worth mentioning that, or somewhere early in the draft mention that this spec is for vCard 4.0 only.</pre>
    </blockquote>
    I'd love to hear from the WG here, but given vCard 5.0 can at least
    in theory be completely different, I think the correct thing to do
    would be to restrict this jCard document to 4.x and when 5.x comes
    around create a revision of the document. Of course the text could
    be changed so that its "valid until revised by another document", in
    case the changes in 5.x are minor enough that no change in jCard is
    needed.<br>
    <br>
    In any case, there should be a text change that any 4.x revision is
    allowed. For example, I recently read a suggestion for signed vCards
    that might use a version "4.0s".<br>
    <blockquote
      cite="mid:E8A52EC5-BF67-4F5B-A810-0D69D01377AA@nostrum.com"
      type="cite">
      <pre wrap="">-- sections 3.4.3 and 3.4.4:

Is the included ABNF a quotation of that in the referenced RFCs, or is it new and authoritative? If the former, it would be helpful to mention that in the text. (I note you did say that about the ABNF in the appendix).</pre>
    </blockquote>
    The ISO specs don't provide a direct BNF for any of their
    constructs. Instead they show examples in the form:<br>
    <meta http-equiv="Content-Type" content="text/html;
      charset=ISO-8859-1">
    Basic format: YYYYMMDD Example: 19850412<br>
    Extended format: YYYY-MM-DD Example: 1985-04-12<br>
    <br>
    The ABNF in jCard mimics this format, so it is not new, but given it
    matches I guess we could say its authoritative. Unless someone tells
    me otherwise (I'm still a bit uncertain when something can be called
    authoritative), I'll change it by changing the hangText "ABNF
    Schema:" to "ABNF Schema (authoritative):" in both sections.<br>
    <br>
    <blockquote
      cite="mid:E8A52EC5-BF67-4F5B-A810-0D69D01377AA@nostrum.com"
      type="cite">
      <pre wrap="">-- 3.4.11:

If RFC6350 says that use of the timezone offset is NOT RECOMMENDED, can you elaborate on why it's included here? (I can guess it's because people may still use it in vCards since it was a "MUST NOT", but it would be good to say something to that effect in the text.)</pre>
    </blockquote>
    There is no other vCard property that uses a utc-offset as a type,
    so this is just for the sake of an example. RFC6350 Section 6.5.1
    has the details, it says utc-offset SHOULD NOT be used on a TZ
    property. The alternative would be to use an x-property for the
    example, i.e<br>
    <br>
    ["x-clock-offset", {}, "utc-offset", "-05:00"]<br>
    <br>
    Do you think we should use this instead?<br>
    <br>
    <blockquote
      cite="mid:E8A52EC5-BF67-4F5B-A810-0D69D01377AA@nostrum.com"
      type="cite">
      <pre wrap="">

Nits/editorial comments:

-- Section 1, paragraph 1:

Please expand JSON on first mention.</pre>
    </blockquote>
    Doing this in the introduction since you reference Section 1,
    paragraph 1. It already appears in the abstract, should I expand it
    there instead/in addition?<br>
    <br>
    As the first mention uses "JSON-based", I've reworded these two
    paragraphs:<br>
    <br>
    OLD:<br>
    &nbsp;&nbsp; As certain similarities exist between vCard and the iCalendar
    data<br>
    &nbsp;&nbsp; format [RFC5545], there is also an effort to define a JSON-based
    data<br>
    &nbsp;&nbsp; format for calendar information called jCal
    [I-D.ietf-jcardcal-jcal]<br>
    &nbsp;&nbsp; that parallels the format defined in this specification.<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>
    &nbsp;&nbsp; The purpose of this specification is to define "jCard", a JSON
    format<br>
    &nbsp;&nbsp; for vCard data.&nbsp; One main advantage to using a JSON-based format
    as<br>
    &nbsp;&nbsp; defined in [RFC4627] over the classic vCard format is easier<br>
    &nbsp;&nbsp; processing for JavaScript based widgets and libraries, especially
    in<br>
    &nbsp;&nbsp; the scope of web-based applications.<br>
    <br>
    NEW:<br>
    &nbsp;&nbsp; As certain similarities exist between vCard and the iCalendar
    data<br>
    &nbsp;&nbsp; format [RFC5545], there is also an effort to define a JSON-based
    data<br>
    &nbsp;&nbsp; format for calendar information called jCal
    [I-D.ietf-jcardcal-jcal]<br>
    &nbsp;&nbsp; that parallels the format defined in this specification.&nbsp; The
    term<br>
    &nbsp;&nbsp; JSON describes the JavaScript Object Notation defined in
    [RFC4627].<br>
    &nbsp;&nbsp; <br>
    &nbsp;&nbsp; The purpose of this specification is to define "jCard", a JSON
    format<br>
    &nbsp;&nbsp; for vCard data.&nbsp; One main advantage to using a JSON-based format
    over<br>
    &nbsp;&nbsp; the classic vCard format is easier processing for JavaScript
    based<br>
    &nbsp;&nbsp; widgets and libraries, especially in the scope of web-based<br>
    &nbsp;&nbsp; applications.<br>
    <br>
    <br>
    <blockquote
      cite="mid:E8A52EC5-BF67-4F5B-A810-0D69D01377AA@nostrum.com"
      type="cite">
      <pre wrap="">

-- Section 1, paragraph 3:

This paragraph seems redundant to paragraph 1.</pre>
    </blockquote>
    Yes, the duplicate is now removed. Sorry about that!<br>
    <blockquote
      cite="mid:E8A52EC5-BF67-4F5B-A810-0D69D01377AA@nostrum.com"
      type="cite">
      <pre wrap="">

-- 1, paragraph 7: " Preserve the semantics of the vCard data."

Imperative form sentence is confusing in context, and inconsistent with surrounding text.</pre>
    </blockquote>
    OLD:<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Preserve the semantics of the vCard data.&nbsp; While a simple
    consumer<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; can easily browse the data in jCard, a full understanding of
    vCard<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; is still required in order to modify and/or fully comprehend
    the<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; directory data.<br>
    <br>
    NEW:<br>
    &nbsp;&nbsp;&nbsp;&nbsp; The vCard data semantics are to be preserved, allowing a simple<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; consumer to easily browse the data in jCard.&nbsp; A full
    understanding<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; of vCard is still required in order to modify and/or fully<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; comprehend the directory data.<br>
    <br>
    <blockquote
      cite="mid:E8A52EC5-BF67-4F5B-A810-0D69D01377AA@nostrum.com"
      type="cite">
      <pre wrap="">

-- 1, paragraph 8:

Sentence Fragment.</pre>
    </blockquote>
    The original intent was to make this a list of considerations, but
    as the first sentences are full I agree this makes it seem weird.
    How is this? I'm a little unsure about the "must not", but since
    this is just a consideration for the document and not an order for
    the consumer I think its ok with this casing:<br>
    <br>
    OLD:<br>
    &nbsp; &nbsp; &nbsp; Ability to handle many extensions to the underlying vCard<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; specification without requiring an update to this document.<br>
    NEW:<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Extensions to the underlying vCard specification must not lead
    to<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; requiring an update to jCard.<br>
    <br>
    <blockquote
      cite="mid:E8A52EC5-BF67-4F5B-A810-0D69D01377AA@nostrum.com"
      type="cite">
      <pre wrap="">

-- 3.2, Last Paragraph: "... for a parser check the data type..."

Missing "to"?</pre>
    </blockquote>
    Done<br>
    <br>
    <blockquote
      cite="mid:E8A52EC5-BF67-4F5B-A810-0D69D01377AA@nostrum.com"
      type="cite">
      <pre wrap="">

-- 3.2.1.2, last paragraph before example:

Should the "iCalendar" reference be "vCard" instead?</pre>
    </blockquote>
    Yes, copy/paste fail from jCal. Fixed.<br>
    <blockquote
      cite="mid:E8A52EC5-BF67-4F5B-A810-0D69D01377AA@nostrum.com"
      type="cite">
      <pre wrap="">-- 3.2.1.3, Last Paragraph:

RFCTODO? I gather in the IANA section, that may be a placeholder for "this RFC", but that doesn't seem to fit here.</pre>
    </blockquote>
    My intention was to keep the registration template as general as
    possible, RFCTODO indeed references "this RFC", I've defined an
    entity for it in the source. Do you want me to replace it with "this
    document" instead? I was thinking if the registration template is
    maybe copied out of the document and gathered somewhere, it would
    make sense to reference the document by its rfc number.<br>
    <br>
    <blockquote
      cite="mid:E8A52EC5-BF67-4F5B-A810-0D69D01377AA@nostrum.com"
      type="cite">
      <pre wrap="">-- 3.3.2: "Example 1:"

Other examples are not numbered.</pre>
    </blockquote>
    Fixed<br>
    <br>
    <blockquote
      cite="mid:E8A52EC5-BF67-4F5B-A810-0D69D01377AA@nostrum.com"
      type="cite">
      <pre wrap="">-- 5:

More occurrences of RFCTODO</pre>
    </blockquote>
    Same reason, they appear in a registration template. I'm happy to
    replace with "this document" in case I'm told the registration
    template is never extracted from the document without any
    processing.<br>
    <br>
    Thank you for the review!<br>
    <br>
  </body>
</html>

--------------070106020800040203080502--

From simon.perreault@viagenie.ca  Mon Jul 22 09:14:22 2013
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 066D721E80A7; Mon, 22 Jul 2013 09:14:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.533
X-Spam-Level: 
X-Spam-Status: No, score=-2.533 tagged_above=-999 required=5 tests=[AWL=0.067,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cn9vYbOHkSnZ; Mon, 22 Jul 2013 09:14:21 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 56A7C21E8099; Mon, 22 Jul 2013 09:14:21 -0700 (PDT)
Received: from [IPv6:::1] (unknown [IPv6:2001:660:3001:4012:245a:a34b:600:fe8b]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 324384712A; Mon, 22 Jul 2013 12:14:20 -0400 (EDT)
Message-ID: <51ED5A5A.2060702@viagenie.ca>
Date: Mon, 22 Jul 2013 18:14:18 +0200
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Philipp Kewisch <kewisch@gmail.com>
Subject: Re: Gen-ART LC/Telechat Review of draft-ietf-jcardcal-jcard-04
References: <E8A52EC5-BF67-4F5B-A810-0D69D01377AA@nostrum.com> <51ED1DAD.90904@gmail.com>
In-Reply-To: <51ED1DAD.90904@gmail.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>, draft-ietf-jcardcal-jcard.all@tools.ietf.org, IETF-Discussion list <ietf@ietf.org>, "jcardcal@ietf.org" <jcardcal@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Jul 2013 16:14:22 -0000

Le 2013-07-22 13:55, Philipp Kewisch a 閏rit :
>> -- 3.2.1.1:
>>
>> What happens for future versions of vCard? Do you simply use the new version number, or would we need a new version of this spec? I suspect the latter. If true, it might be worth mentioning that, or somewhere early in the draft mention that this spec is for vCard 4.0 only.
> I'd love to hear from the WG here, but given vCard 5.0 can at least in
> theory be completely different, I think the correct thing to do would be
> to restrict this jCard document to 4.x and when 5.x comes around create
> a revision of the document. Of course the text could be changed so that
> its "valid until revised by another document", in case the changes in
> 5.x are minor enough that no change in jCard is needed.
> 
> In any case, there should be a text change that any 4.x revision is
> allowed. For example, I recently read a suggestion for signed vCards
> that might use a version "4.0s".

I'd prefer "valid until revised by another document", which is
equivalent to not saying anything since that's how RFCs work. Therefore,
my suggestion would be to simply remove this sentence: "Similarly, the
value of the version property MUST be "4.0"."

Simon

From martin.thomson@gmail.com  Mon Jul 22 10:57:31 2013
Return-Path: <martin.thomson@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CC3711E80D9 for <ietf@ietfa.amsl.com>; Mon, 22 Jul 2013 10:57:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q7-1Kn87ZiLg for <ietf@ietfa.amsl.com>; Mon, 22 Jul 2013 10:57:31 -0700 (PDT)
Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) by ietfa.amsl.com (Postfix) with ESMTP id E699611E80DE for <ietf@ietf.org>; Mon, 22 Jul 2013 10:57:30 -0700 (PDT)
Received: by mail-wi0-f169.google.com with SMTP id c10so3039981wiw.0 for <ietf@ietf.org>; Mon, 22 Jul 2013 10:57:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=is9JG6I8F8wJWKNLfbszP+QGCnEFOXoR0zpfF96VaCQ=; b=a7Epn+NPxC1kpbbISB8+Fs+BEmu9o1OKKUHgEfUF9kEAZ5tXJVKrIj60TrnipeZ2Vl dPAoq2isWmV5sBrt2bse5cRKcinRUhR2qFCv11OH3VpfbFbzqEXsLEUu8KVcsCNMl4tE ZsS6Z1j/YxO4fg4Uu5qsz0URcZ15oZVF02wGJxsuH6Amy1QIor66v+bU7Sa2HO6YUVfJ nV+R1/rV4tOwlww2b3MYxWfBqXKmD4BcCxBQojgA4sk5qN8Gt1XVMvH7CXJkTCvfwaMX eqVUdYGpix5MzRjyctmiLO820cenxmCkCc+97Q7/9o3TUqOd0MltEN6Kmn9pOaiR183d vQLA==
MIME-Version: 1.0
X-Received: by 10.194.110.6 with SMTP id hw6mr20666583wjb.3.1374515848869; Mon, 22 Jul 2013 10:57:28 -0700 (PDT)
Received: by 10.194.60.46 with HTTP; Mon, 22 Jul 2013 10:57:28 -0700 (PDT)
In-Reply-To: <BBF5DDFE515C3946BC18D733B20DAD2338DD23C3@XMB104ADS.rim.net>
References: <CABkgnnUk9kvtAoFYDsgDAsdeYmd7QUFv5P28H3sbc5HpsgBmjg@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD2338DD23C3@XMB104ADS.rim.net>
Date: Mon, 22 Jul 2013 10:57:28 -0700
Message-ID: <CABkgnnV8Xbf_O08OTZ11GFHRNDfMOmj67Zpc4sVC-kSVmFvPsw@mail.gmail.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
From: Martin Thomson <martin.thomson@gmail.com>
To: Andrew Allen <aallen@blackberry.com>
Content-Type: text/plain; charset=UTF-8
Cc: "tbray@textuality.com" <tbray@textuality.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Jul 2013 17:57:31 -0000

On 20 July 2013 15:34, Andrew Allen <aallen@blackberry.com> wrote:
> There are obviously always alternative design choices but why would you want to include both a pre assigned device ID and a generated device ID in the same message?

I think that reading this thread should provide you with ample reasons.

The instance ID in outbound has certain stability requirements that do
not strictly correspond to the lifetime of the hardware in use.  The
other use cases answer very different questions, which include: is
this a stolen device, is this device authorized to use the networks,
etc...   I'm certain those questions can be answered without a device
identifier traversing the network.

From sm@elandsys.com  Mon Jul 22 11:37:42 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B19F21F999B for <ietf@ietfa.amsl.com>; Mon, 22 Jul 2013 11:37:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HZ73+OZbnyBU for <ietf@ietfa.amsl.com>; Mon, 22 Jul 2013 11:37:36 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id DD63521F8546 for <ietf@ietf.org>; Mon, 22 Jul 2013 11:37:35 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.150.27]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r6MIbJbi021581 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Mon, 22 Jul 2013 11:37:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1374518250; bh=xgVi22k1h2ltMkvqN8TcXuA9r1s8d+XNPILpInzc2n0=; h=Date:To:From:Subject:In-Reply-To:References; b=1WNJGgURkfyaXlBbCbkm9u8ciCIGr3DYrDgRuVN/2VE82+3tw51hkSK/FzzRuu2de 7X+tPJSnJh9Civft4h5eyvQkXQRJyjUs37i2QcjpQjdszU2Y0EjqL/ES0GfIG4nNfw xbnFEAziAmcBDMtn6Ua86q1ZB85h3G+h2M0SmUzA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1374518250; i=@elandsys.com; bh=xgVi22k1h2ltMkvqN8TcXuA9r1s8d+XNPILpInzc2n0=; h=Date:To:From:Subject:In-Reply-To:References; b=mCf4XVDPVeM21K1mZhKXSDBaNQo4gA+AYGm7MOLvnWSvoc/Zn2t/NRGFD7VDRGdKM PoaD4CG9Nh0mp1aY7coXnbYwWqw7JkJmcgEiUdWsX1YXSdGCZGjAqx03gUgOgefHlC 98oUZXBEjaK4MTMjxla/MmuJwRH+cQnILyqfs7ZA=
Message-Id: <6.2.5.6.2.20130722075411.0be85798@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 22 Jul 2013 10:42:00 -0700
To: ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Last Call: <draft-allen-dispatch-imei-urn-as-instanceid-10.txt> (Using the International Mobile station Equipment Identity(IMEI)URN as an Instance ID) to Informational RFC
In-Reply-To: <20130719143530.8387.71840.idtracker@ietfa.amsl.com>
References: <20130719143530.8387.71840.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Jul 2013 18:37:42 -0000

At 07:35 19-07-2013, The IESG wrote:
>The IESG has received a request from an individual submitter to consider
>the following document:
>- 'Using the International Mobile station Equipment Identity(IMEI)URN as
>    an Instance ID'
>   <draft-allen-dispatch-imei-urn-as-instanceid-10.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 2013-08-16. Exceptionally, comments may be

Section 4 describes the 3GPP use case as:

   "The mobile device includes its IMEI in the SIP REGISTER request
    so that the registrar can perform a check of the Equipment Identity
    Register (EIR) to verify if this mobile device is allowed or barred
    from accessing the network for non-emergency services"

The draft then argues that non-REGISTER requests except in case of an 
emergency.

In Section 5:

   'A UAC MUST NOT include the "sip.instance" media feature tag
    containing the GSMA IMEI URN in the Contact header field of non-
    REGISTER requests except when the request is related to an emergency
    session.  Regulatory requirements can require the IMEI to be provided
    to the Public Safety Answering Point (PSAP).  Any future exceptions
    to this prohibition require a RFC that addresses how privacy is not
    violated by such a usage.'

My reading of the above is there is a privacy violation but that 
violation is considered acceptable in the use case mentioned 
above.  Any other use case requires a RFC to be published.  There is 
an additional requirement; the RFC has to address how privacy is not 
violated.  It is an unusual requirement in a RFC.

 From Section 9:

   'In particular, the "sip.instance" media feature tag containing the
    GSMA IMEI URN MUST NOT be included in requests or responses intended
    to convey any level of anonymity.'

The above can be interpreted in various ways.  The problem might be 
that the draft builds upon RFC 5626 which states that "some other 
privacy concern requires that the UA not reveal its identity".  It 
may be better to state that there is a violation of privacy.

The draft does not discuss about the weakness of the mechanism or how 
what it proposes can be used for wiretapping.

Regards,
S. Moonesamy  


From brian.e.carpenter@gmail.com  Mon Jul 22 12:59:06 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F165511E8112; Mon, 22 Jul 2013 12:59:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nWfw4qKxRkyk; Mon, 22 Jul 2013 12:59:05 -0700 (PDT)
Received: from mail-pb0-x231.google.com (mail-pb0-x231.google.com [IPv6:2607:f8b0:400e:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id 13A5221F8F07; Mon, 22 Jul 2013 12:59:02 -0700 (PDT)
Received: by mail-pb0-f49.google.com with SMTP id jt11so7493556pbb.22 for <multiple recipients>; Mon, 22 Jul 2013 12:59:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=DraUZDG8bKVaE03QsuWBzDH+bAXC3oTPpJNghIinGGo=; b=UkuQhxfhl5tn5f8DE/joOn5ETzGOk6lQsLbEtTQatE0y477PkdH4OCf3CyVnKw3It6 +e0DoVNhmKVyMrIaV89bIh6z2HhUQ+hH1GcdCabhMJ2E9ydUVCAQl6t8J6nmwtT7jjy8 slaQKMldOFrhPDWPlJIjcJ65KolYiHi4CwAsbn4mpUDGDYniX2GBG8KbCPUwaa1dwwLz pqORaWSBzkKA8LVz5s9c+tYC9cRhyzHt6omvqCiC/HY4KnJKvxgGZnneUE1OkE+8pXpC esjAjp/cHtotK17bM5uNOgF1U4u/w5326K9e9u9Aora5wA4d6lECbZPCDImYY0gGGjSe gKWg==
X-Received: by 10.66.219.135 with SMTP id po7mr34017495pac.21.1374523141827; Mon, 22 Jul 2013 12:59:01 -0700 (PDT)
Received: from [192.168.178.23] (147.192.69.111.dynamic.snap.net.nz. [111.69.192.147]) by mx.google.com with ESMTPSA id sp4sm37363437pbc.45.2013.07.22.12.58.59 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 22 Jul 2013 12:59:01 -0700 (PDT)
Message-ID: <51ED8F04.9020408@gmail.com>
Date: Tue, 23 Jul 2013 07:59:00 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF 87 Technical Plenary Experiment
References: <B85030F8-A92E-4D7C-85E0-E79D4A092799@iab.org>
In-Reply-To: <B85030F8-A92E-4D7C-85E0-E79D4A092799@iab.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 87all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Jul 2013 19:59:06 -0000

The wiki page uses the phrase "WebRTC-compatible browser".

For those who know zilch about WebRTC,  a list of such browsers
would be handy. Also a test page for OPUS, since otherwise people
will have exactly 5 minutes before the session to get set up.

Finally, is the list 87all of any help to non-attendees? Don't we need
a list for 87remote attendees?

Regards
   Brian

On 23/07/2013 07:03, IAB Chair wrote:
> The OPUS codec, defined in RFC 6716, can scale from low bit-rate narrowband speech to very high quality stereo music, making it suitable for a wide range of audio applications. The IETF 87 Technical Plenary session will cover the past and future of Opus as well as the lessons learned from the standardization process that could apply to future IETF work.
>  
> To provide additional materials relating to the plenary topic, the IAB has created a wiki. If you have material relevant to the plenary topic (such as papers or test data relating to OPUS), please contribute it to the wiki, either by editing it yourself, or sending it to the IAB <iab at iab.org>.
>  
> Also, during the IETF 87 Technical Plenary, the MeetEcho team will be running an experiment to enable remote participation in the Technical Plenary using the OPUS codec.  Information on how to access on the Remote Participation experiment is also available on the IAB wiki page: 
> http://trac.tools.ietf.org/group/iab/trac/wiki/IETF-87#IETF87TechnicalPlenary:OPUSCodec
> 
> On behalf of the IAB,
>   Russ Housley
>   IAB Chair

From ted.ietf@gmail.com  Mon Jul 22 13:12:48 2013
Return-Path: <ted.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F6AA11E813F; Mon, 22 Jul 2013 13:12:48 -0700 (PDT)
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=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Yftz1DyqYr5; Mon, 22 Jul 2013 13:12:47 -0700 (PDT)
Received: from mail-ie0-x234.google.com (mail-ie0-x234.google.com [IPv6:2607:f8b0:4001:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id 30A9611E814E; Mon, 22 Jul 2013 13:12:47 -0700 (PDT)
Received: by mail-ie0-f180.google.com with SMTP id f4so16144889iea.39 for <multiple recipients>; Mon, 22 Jul 2013 13:12:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=hH8y/O/Kp3vQQTbZ1X29j5XY+ivb6xChyIw8B1Fj/fM=; b=bWUTwAlL7hYbAweKSaQaDcl81Py80zOCZQh3rBriNU2FimAbaePk3vipETP8hm29O/ OOSiB3GKVfcppDzf3LmoDZshc+pkpQGcGSxlm0nvRyovid+fkDKSOJ3Vr/r9m4QEFWLV PaStm6r66rr7+JfP5pkQTDWMSqtpooseQqbaP06HML8u82QB5H1z3Mq3rodZuR89MAQh 2W/O8PDEC3c9ZhQ2Uvt+k6yzEGpC0p86oVrrOX4HgHQE3Lw5fAAETv13xgoCLYNmzyUE 3KAldzJVzyhqOAUN5iY+JLMa+RyRKUdAoqePIHVuKVLonYRwsaMVs5e/kC1J8Fw13TQN skbQ==
MIME-Version: 1.0
X-Received: by 10.50.66.210 with SMTP id h18mr20365841igt.19.1374523966759; Mon, 22 Jul 2013 13:12:46 -0700 (PDT)
Received: by 10.42.29.202 with HTTP; Mon, 22 Jul 2013 13:12:46 -0700 (PDT)
In-Reply-To: <51ED8F04.9020408@gmail.com>
References: <B85030F8-A92E-4D7C-85E0-E79D4A092799@iab.org> <51ED8F04.9020408@gmail.com>
Date: Mon, 22 Jul 2013 13:12:46 -0700
Message-ID: <CA+9kkMDMrHAaCrwWn2hPmGJE7g4cSOR9doLsg3BBD8NHoJg5yQ@mail.gmail.com>
Subject: Re: IETF 87 Technical Plenary Experiment
From: Ted Hardie <ted.ietf@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=047d7bdca468c6767204e21f4cc5
Cc: ietf@ietf.org, 87all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Jul 2013 20:12:48 -0000

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

On Mon, Jul 22, 2013 at 12:59 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> The wiki page uses the phrase "WebRTC-compatible browser".
>

For those who know zilch about WebRTC,  a list of such browsers
> would be handy. Also a test page for OPUS, since otherwise people
> will have exactly 5 minutes before the session to get set up.
>

Both Chrome and Firefox stable branches currently support WebRTC.


regards,

Ted

Finally, is the list 87all of any help to non-attendees? Don't we need
> a list for 87remote attendees?
>
> Regards
>    Brian
>
> On 23/07/2013 07:03, IAB Chair wrote:
> > The OPUS codec, defined in RFC 6716, can scale from low bit-rate
> narrowband speech to very high quality stereo music, making it suitable for
> a wide range of audio applications. The IETF 87 Technical Plenary session
> will cover the past and future of Opus as well as the lessons learned from
> the standardization process that could apply to future IETF work.
> >
> > To provide additional materials relating to the plenary topic, the IAB
> has created a wiki. If you have material relevant to the plenary topic
> (such as papers or test data relating to OPUS), please contribute it to the
> wiki, either by editing it yourself, or sending it to the IAB <iab at
> iab.org>.
> >
> > Also, during the IETF 87 Technical Plenary, the MeetEcho team will be
> running an experiment to enable remote participation in the Technical
> Plenary using the OPUS codec.  Information on how to access on the Remote
> Participation experiment is also available on the IAB wiki page:
> >
> http://trac.tools.ietf.org/group/iab/trac/wiki/IETF-87#IETF87TechnicalPlenary:OPUSCodec
> >
> > On behalf of the IAB,
> >   Russ Housley
> >   IAB Chair
>

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

On Mon, Jul 22, 2013 at 12:59 PM, Brian E Carpenter <span dir=3D"ltr">&lt;<=
a href=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_blank">brian.e.car=
penter@gmail.com</a>&gt;</span> wrote:<br><div class=3D"gmail_quote"><block=
quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
 solid;padding-left:1ex">
The wiki page uses the phrase &quot;WebRTC-compatible browser&quot;.<br>
=A0</blockquote><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex">
For those who know zilch about WebRTC, =A0a list of such browsers<br>
would be handy. Also a test page for OPUS, since otherwise people<br>
will have exactly 5 minutes before the session to get set up.<br>
</blockquote><div>=A0</div><div>Both Chrome and Firefox stable branches cur=
rently support WebRTC.<br>=A0<br><br>regards,<br><br>Ted<br><br></div><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #cc=
c solid;padding-left:1ex">
Finally, is the list 87all of any help to non-attendees? Don&#39;t we need<=
br>
a list for 87remote attendees?<br>
<br>
Regards<br>
<span class=3D"HOEnZb"><font color=3D"#888888">=A0 =A0Brian<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
On 23/07/2013 07:03, IAB Chair wrote:<br>
&gt; The OPUS codec, defined in RFC 6716, can scale from low bit-rate narro=
wband speech to very high quality stereo music, making it suitable for a wi=
de range of audio applications. The IETF 87 Technical Plenary session will =
cover the past and future of Opus as well as the lessons learned from the s=
tandardization process that could apply to future IETF work.<br>

&gt;<br>
&gt; To provide additional materials relating to the plenary topic, the IAB=
 has created a wiki. If you have material relevant to the plenary topic (su=
ch as papers or test data relating to OPUS), please contribute it to the wi=
ki, either by editing it yourself, or sending it to the IAB &lt;iab at <a h=
ref=3D"http://iab.org" target=3D"_blank">iab.org</a>&gt;.<br>

&gt;<br>
&gt; Also, during the IETF 87 Technical Plenary, the MeetEcho team will be =
running an experiment to enable remote participation in the Technical Plena=
ry using the OPUS codec. =A0Information on how to access on the Remote Part=
icipation experiment is also available on the IAB wiki page:<br>

&gt; <a href=3D"http://trac.tools.ietf.org/group/iab/trac/wiki/IETF-87#IETF=
87TechnicalPlenary:OPUSCodec" target=3D"_blank">http://trac.tools.ietf.org/=
group/iab/trac/wiki/IETF-87#IETF87TechnicalPlenary:OPUSCodec</a><br>
&gt;<br>
&gt; On behalf of the IAB,<br>
&gt; =A0 Russ Housley<br>
&gt; =A0 IAB Chair<br>
</div></div></blockquote></div><br>

--047d7bdca468c6767204e21f4cc5--

From ben@nostrum.com  Mon Jul 22 13:25:13 2013
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACF0C21F8447; Mon, 22 Jul 2013 13:25:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MRW1p7xIBRnO; Mon, 22 Jul 2013 13:25:12 -0700 (PDT)
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 2A68E11E813A; Mon, 22 Jul 2013 13:25:06 -0700 (PDT)
Received: from [172.20.10.7] (mobile-166-147-070-058.mycingular.net [166.147.70.58]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r6MKP0so066690 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 22 Jul 2013 15:25:00 -0500 (CDT) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Gen-ART LC/Telechat Review of draft-ietf-jcardcal-jcard-04
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <51ED1DAD.90904@gmail.com>
Date: Mon, 22 Jul 2013 15:24:54 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <4A2C7748-D31C-46FA-BCD2-1CC6069F20A7@nostrum.com>
References: <E8A52EC5-BF67-4F5B-A810-0D69D01377AA@nostrum.com> <51ED1DAD.90904@gmail.com>
To: Philipp Kewisch <kewisch@gmail.com>
X-Mailer: Apple Mail (2.1508)
Received-SPF: pass (shaman.nostrum.com: 166.147.70.58 is authenticated by a trusted mechanism)
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>, draft-ietf-jcardcal-jcard.all@tools.ietf.org, IETF-Discussion list <ietf@ietf.org>, "jcardcal@ietf.org" <jcardcal@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Jul 2013 20:25:13 -0000

Thanks for the response. A few comments inline. I removed sections that =
don't seem to need further comment.

On Jul 22, 2013, at 6:55 AM, Philipp Kewisch <kewisch@gmail.com> wrote:

>=20
> On 7/17/13 12:27 AM, Ben Campbell wrote:

[...]

>> -- 3.2.1.1:
>>=20
>> What happens for future versions of vCard? Do you simply use the new =
version number, or would we need a new version of this spec? I suspect =
the latter. If true, it might be worth mentioning that, or somewhere =
early in the draft mention that this spec is for vCard 4.0 only.
>>=20
> I'd love to hear from the WG here, but given vCard 5.0 can at least in =
theory be completely different, I think the correct thing to do would be =
to restrict this jCard document to 4.x and when 5.x comes around create =
a revision of the document. Of course the text could be changed so that =
its "valid until revised by another document", in case the changes in =
5.x are minor enough that no change in jCard is needed.
>=20
> In any case, there should be a text change that any 4.x revision is =
allowed. For example, I recently read a suggestion for signed vCards =
that might use a version "4.0s".

Pending the opinions of the work group, I'm happy with that approach.

>> -- sections 3.4.3 and 3.4.4:
>>=20
>> Is the included ABNF a quotation of that in the referenced RFCs, or =
is it new and authoritative? If the former, it would be helpful to =
mention that in the text. (I note you did say that about the ABNF in the =
appendix).
>>=20
> The ISO specs don't provide a direct BNF for any of their constructs. =
Instead they show examples in the form:
> Basic format: YYYYMMDD Example: 19850412
> Extended format: YYYY-MM-DD Example: 1985-04-12
>=20
> The ABNF in jCard mimics this format, so it is not new, but given it =
matches I guess we could say its authoritative. Unless someone tells me =
otherwise (I'm still a bit uncertain when something can be called =
authoritative), I'll change it by changing the hangText "ABNF Schema:" =
to "ABNF Schema (authoritative):" in both sections.

By "authoritative", I don't mean anything particularly formal. It's =
really a matter of where the normative text lies. So, for someone =
implementing _this_ draft, would you expect them to look at the included =
ABNF only, or is it a case of the ABNF being here for convenience but a =
careful implementor should  also look at the ISO specs?


>=20
>> -- 3.4.11:
>>=20
>> If RFC6350 says that use of the timezone offset is NOT RECOMMENDED, =
can you elaborate on why it's included here? (I can guess it's because =
people may still use it in vCards since it was a "MUST NOT", but it =
would be good to say something to that effect in the text.)

oops, I think I meant to say "SHOULD NOT".

>>=20
> There is no other vCard property that uses a utc-offset as a type, so =
this is just for the sake of an example. RFC6350 Section 6.5.1 has the =
details, it says utc-offset SHOULD NOT be used on a TZ property. The =
alternative would be to use an x-property for the example, i.e
>=20
> ["x-clock-offset", {}, "utc-offset", "-05:00"]
>=20
> Do you think we should use this instead?

I don't have strong feelings either way, other than if you include a =
"NOT RECOMMENDED" example, it might be wise to put in a sentence or two =
giving the reasoning.

>=20
>>=20
>> Nits/editorial comments:
>>=20
>> -- Section 1, paragraph 1:
>>=20
>> Please expand JSON on first mention.
>>=20
> Doing this in the introduction since you reference Section 1, =
paragraph 1. It already appears in the abstract, should I expand it =
there instead/in addition?

I think the general approach is that the abstract doesn't "count" for =
this purpose. That is, if you separated the abstract and the body into =
two different documents, they should both still make sense.

>=20
> As the first mention uses "JSON-based", I've reworded these two =
paragraphs:
>=20
> OLD:
>    As certain similarities exist between vCard and the iCalendar data
>    format [RFC5545], there is also an effort to define a JSON-based =
data
>    format for calendar information called jCal =
[I-D.ietf-jcardcal-jcal]
>    that parallels the format defined in this specification.
>                      =20
>    The purpose of this specification is to define "jCard", a JSON =
format
>    for vCard data.  One main advantage to using a JSON-based format as
>    defined in [RFC4627] over the classic vCard format is easier
>    processing for JavaScript based widgets and libraries, especially =
in
>    the scope of web-based applications.
>=20
> NEW:
>    As certain similarities exist between vCard and the iCalendar data
>    format [RFC5545], there is also an effort to define a JSON-based =
data
>    format for calendar information called jCal =
[I-D.ietf-jcardcal-jcal]
>    that parallels the format defined in this specification.  The term
>    JSON describes the JavaScript Object Notation defined in [RFC4627].
>   =20
>    The purpose of this specification is to define "jCard", a JSON =
format
>    for vCard data.  One main advantage to using a JSON-based format =
over
>    the classic vCard format is easier processing for JavaScript based
>    widgets and libraries, especially in the scope of web-based
>    applications.

That works for me.

[...]

>=20
>>=20
>> -- 1, paragraph 8:
>>=20
>> Sentence Fragment.
>>=20
> The original intent was to make this a list of considerations, but as =
the first sentences are full I agree this makes it seem weird. How is =
this? I'm a little unsure about the "must not", but since this is just a =
consideration for the document and not an order for the consumer I think =
its ok with this casing:
>=20
> OLD:
>       Ability to handle many extensions to the underlying vCard
>       specification without requiring an update to this document.
> NEW:
>       Extensions to the underlying vCard specification must not lead =
to
>       requiring an update to jCard.
>=20

WFM.

[...]

>> -- 3.2.1.3, Last Paragraph:
>>=20
>> RFCTODO? I gather in the IANA section, that may be a placeholder for =
"this RFC", but that doesn't seem to fit here.
>>=20
> My intention was to keep the registration template as general as =
possible, RFCTODO indeed references "this RFC", I've defined an entity =
for it in the source. Do you want me to replace it with "this document" =
instead? I was thinking if the registration template is maybe copied out =
of the document and gathered somewhere, it would make sense to reference =
the document by its rfc number.

By registration template, you are talking about the use in the IANA =
Considerations, right? My comment was about its use in sections 3.2.1.3 =
and 5. I think it makes sense in the IANA considerations (perhaps with a =
note to the RFC Editor to replace it with the actual RFC number), but =
"this document" would make more sense in 3.2.1.3 and 5.

[...]=

From housley@vigilsec.com  Mon Jul 22 15:17:04 2013
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4C3C11E8180 for <ietf@ietfa.amsl.com>; Mon, 22 Jul 2013 15:17:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rZFmR3yLmM0U for <ietf@ietfa.amsl.com>; Mon, 22 Jul 2013 15:16:59 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 4CF4A11E817C for <ietf@ietf.org>; Mon, 22 Jul 2013 15:16:53 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id E14DBF24089; Mon, 22 Jul 2013 18:16:54 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id R6ppgNyvPr0Q; Mon, 22 Jul 2013 18:16:51 -0400 (EDT)
Received: from [192.168.2.109] (pool-96-241-154-95.washdc.fios.verizon.net [96.241.154.95]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 6E7ECF2407E; Mon, 22 Jul 2013 18:16:53 -0400 (EDT)
Subject: Re: IETF 87 Technical Plenary Experiment
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <51ED8F04.9020408@gmail.com>
Date: Mon, 22 Jul 2013 18:16:50 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <3EFF12CC-6A1E-461D-AB65-A64CADF5849D@vigilsec.com>
References: <B85030F8-A92E-4D7C-85E0-E79D4A092799@iab.org> <51ED8F04.9020408@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1085)
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Jul 2013 22:17:04 -0000

Brian:

The message as also sent to IETF Announce, so I hope that reaches the =
remote attendees.

Russ


On Jul 22, 2013, at 3:59 PM, Brian E Carpenter wrote:

> The wiki page uses the phrase "WebRTC-compatible browser".
>=20
> For those who know zilch about WebRTC,  a list of such browsers
> would be handy. Also a test page for OPUS, since otherwise people
> will have exactly 5 minutes before the session to get set up.
>=20
> Finally, is the list 87all of any help to non-attendees? Don't we need
> a list for 87remote attendees?
>=20
> Regards
>   Brian
>=20
> On 23/07/2013 07:03, IAB Chair wrote:
>> The OPUS codec, defined in RFC 6716, can scale from low bit-rate =
narrowband speech to very high quality stereo music, making it suitable =
for a wide range of audio applications. The IETF 87 Technical Plenary =
session will cover the past and future of Opus as well as the lessons =
learned from the standardization process that could apply to future IETF =
work.
>>=20
>> To provide additional materials relating to the plenary topic, the =
IAB has created a wiki. If you have material relevant to the plenary =
topic (such as papers or test data relating to OPUS), please contribute =
it to the wiki, either by editing it yourself, or sending it to the IAB =
<iab at iab.org>.
>>=20
>> Also, during the IETF 87 Technical Plenary, the MeetEcho team will be =
running an experiment to enable remote participation in the Technical =
Plenary using the OPUS codec.  Information on how to access on the =
Remote Participation experiment is also available on the IAB wiki page:=20=

>> =
http://trac.tools.ietf.org/group/iab/trac/wiki/IETF-87#IETF87TechnicalPlen=
ary:OPUSCodec
>>=20
>> On behalf of the IAB,
>>  Russ Housley
>>  IAB Chair


From housley@vigilsec.com  Mon Jul 22 15:51:51 2013
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA12611E8189; Mon, 22 Jul 2013 15:51:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.239
X-Spam-Level: 
X-Spam-Status: No, score=-102.239 tagged_above=-999 required=5 tests=[AWL=-0.240, BAYES_00=-2.599, J_CHICKENPOX_53=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F52F13a6ic8E; Mon, 22 Jul 2013 15:51:47 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 2D60911E8182; Mon, 22 Jul 2013 15:51:47 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 45751F240BA; Mon, 22 Jul 2013 18:52:06 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id fMHVhAr4n2WY; Mon, 22 Jul 2013 18:51:40 -0400 (EDT)
Received: from [192.168.2.109] (pool-96-241-154-95.washdc.fios.verizon.net [96.241.154.95]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 66F7BF24089; Mon, 22 Jul 2013 18:52:04 -0400 (EDT)
Subject: Call for Community Input on the ICANN Nominating Committee Volunteers
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <5607FF5A-75CB-4A4B-9B3C-2798D6DF9BFB@iab.org>
Date: Mon, 22 Jul 2013 18:51:41 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <FB547022-D50B-41BC-BB5C-048E5F89B624@vigilsec.com>
References: <5607FF5A-75CB-4A4B-9B3C-2798D6DF9BFB@iab.org>
To: IETF Announce <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1085)
Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Jul 2013 22:51:52 -0000

As previously announced, the IAB is planning to select a person to serve =
on the ICANN NOMCOM for a one year term. The following people are =
candidates for that role (in alphabetical order):

    Arbogast Ishemo Fabian
    Stephen Kent
    John Levine
    S Moonesamy
    Russ Mundy
    Mark Townsley
    Samuel Weiler
    Hassan Zaheer

The community is invited to send comments about this selection to the =
IAB chair <iab-chair at iab.org> and the IAB Executive Director <execd =
at iab.org>. We expect to make a decision within the next few weeks.

Thanks in advance,
  Russ Housley
  IAB Chair


On Jun 27, 2013, at 10:36 PM, IAB Chair wrote:

> Please forward to all interested parties.
>=20
> Dear Colleagues,
>=20
> The IAB (on behalf of the IETF) has been asked to supply a member to =
the 2014 ICANN Nominating Committee (NomCom) by 15 August 2013. We would =
therefore like to ask the community for volunteers to serve on the ICANN =
NomCom. If you are interested, please send a short e-mail to iab-chair =
at iab.org with a copy to execd at iab.org with your motivation and =
information concerning your familiarity with the IETF and ICANN.  The =
deadline for volunteering is 19 July 2013.
>=20
> The IAB will select from the available candidates, taking into account =
the familiarity with ICANN and the IETF, their roles, and their =
processes. The selected candidate will serve on the ICANN NomCom on =
personal title; however, we will be looking for a candidate who has an =
understanding of the interests of the technical community.
>=20
> The ICANN NomCom process itself is governed by the ICANN bylaws; an =
abstract of the relevant articles can be found at =
http://nomcom.icann.org/bylaws.htm.  In addition, each NomCom determines =
a number of its own operational procedures, including the role of the =
NomCom in recruiting and selecting candidates.
>=20
> The ICANN Nominating Committee typically meets in person at or around =
three consecutive ICANN meetings. The first of these meetings, when the=20=

> committee is formally established, will be held  22-23 November 2013 =
following the Buenos Aires ICANN meeting on 17-21 November. The =
committee will next attend the "Spring" ICANN meeting, which in 2014 =
will be in Singapore on 23-27 March 2014. Finally, the committee will =
meet during and after the "Summer" ICANN meeting in London on 22-26 June =
2014 where the final slate of candidates for the ICANN Board, the GNSO, =
ccNSO,and ALAC will be agreed upon.
>=20
> Candidates should be able to join monthly teleconferences (typically =
at UTC 14:00), with the expectation that these teleconferences will held =
weekly during the candidate assessment process in May-June.
>=20
> NOTE: ICANN does cover travel and hotel costs for a pre-determined =
number of days at each of the 3 consecutive ICANN meetings.
>=20
> For more information about the ICANN NomCom see: =
http://nomcom.icann.org/.  If you are willing to be considered or would =
like to nominate someone for the position, please send an email to =
iab-chair at iab.org and execd at iab.org.
>=20
> On behalf of the IAB,
>  Russ Housley
>  IAB Chair


From jari.arkko@piuha.net  Tue Jul 23 04:41:46 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A4DE11E820B for <ietf@ietfa.amsl.com>; Tue, 23 Jul 2013 04:41:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z0tv8mx-V8vL for <ietf@ietfa.amsl.com>; Tue, 23 Jul 2013 04:41:42 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id C551C11E8180 for <ietf@ietf.org>; Tue, 23 Jul 2013 04:41:41 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id A2AE62CC48 for <ietf@ietf.org>; Tue, 23 Jul 2013 14:41:40 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qr00nNYNLzq0 for <ietf@ietf.org>; Tue, 23 Jul 2013 14:41:40 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id EC1F32CC3C for <ietf@ietf.org>; Tue, 23 Jul 2013 14:41:39 +0300 (EEST)
From: Jari Arkko <jari.arkko@piuha.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: recent blog articles
Message-Id: <F4A79EA0-EA69-4F67-A08B-4EDB18469096@piuha.net>
Date: Tue, 23 Jul 2013 14:41:39 +0300
To: "ietf@ietf.org list" <ietf@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 23 Jul 2013 11:41:46 -0000

Hi,

I just wanted to send pointers to two recent blog articles that I wrote:

A Different Internet		http://www.ietf.org/blog/2013/07/a-different-internet/

The Web of Things		http://www.ietf.org/blog/2013/07/the-web-of-things/

Jari


From martin.thomson@gmail.com  Tue Jul 23 10:05:22 2013
Return-Path: <martin.thomson@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CE4211E82EC for <ietf@ietfa.amsl.com>; Tue, 23 Jul 2013 10:05:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h2WxD20YRgMS for <ietf@ietfa.amsl.com>; Tue, 23 Jul 2013 10:05:21 -0700 (PDT)
Received: from mail-wg0-x231.google.com (mail-wg0-x231.google.com [IPv6:2a00:1450:400c:c00::231]) by ietfa.amsl.com (Postfix) with ESMTP id 568C221E80C9 for <ietf@ietf.org>; Tue, 23 Jul 2013 10:05:19 -0700 (PDT)
Received: by mail-wg0-f49.google.com with SMTP id a12so7184030wgh.28 for <ietf@ietf.org>; Tue, 23 Jul 2013 10:05:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=D5reLWyGBnuJ4gEejjU1i5WyX5ufPFlVlJ4AO50kdX4=; b=FVU0N9hEXYZZzBJBerhUUTg6HAVIjCaLfGvNaJyeop/GQ5yndtOt98XKLR/Ihr4EZ0 Nj0OOZh4duMv5VkQM6SHtPbcZc4Yo//wvltNyqouWJOh+vGYiAPfHA28gLgbGW16IlI0 NzlB4ylC0CR+A64+PilrjdsPkk6OE11e1QgDPgaDTYbysVnccdaMiqMA9JJw75dPQQF4 TjrdppJ7FJjMt5n3rYor/PSobTthuNVFUuSfkyFMSJfB4nnxLEfco3XXh71ivvYeoP9Y 3QLlyCTmXOSvM25jMzwaA5fsbDZZD16GH3MGs1tb3BmZHdNT0QmT0JhL1U0mXo2sVyHz nx7Q==
MIME-Version: 1.0
X-Received: by 10.194.110.6 with SMTP id hw6mr24109084wjb.3.1374599117217; Tue, 23 Jul 2013 10:05:17 -0700 (PDT)
Received: by 10.194.60.46 with HTTP; Tue, 23 Jul 2013 10:05:17 -0700 (PDT)
In-Reply-To: <CE0C5727.C4BC%bdickson@verisign.com>
References: <CE0C5727.C4BC%bdickson@verisign.com>
Date: Tue, 23 Jul 2013 10:05:17 -0700
Message-ID: <CABkgnnX7T=V3Obyr=KJJpzrDTY=g-ZwhT_g3GxjoBmmpjmBKUQ@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-geopriv-res-gw-lis-discovery-05.txt> (Location Information Server (LIS) Discovery using IP address and Reverse DNS) to Informational RFC
From: Martin Thomson <martin.thomson@gmail.com>
To: "Dickson, Brian" <bdickson@verisign.com>
Content-Type: text/plain; charset=UTF-8
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 23 Jul 2013 17:05:22 -0000

Hi Brian,

I apologize for not responding sooner, your mail went into the
ietf@ietf.org bucket, which generally gets ignored.  (Thanks to Ray
for pointing this out.)

On 17 July 2013 11:14, Dickson, Brian <bdickson@verisign.com> wrote:
>   o    What domain name is to be used, in the SRV query ("_stun._udp.domain"
> or "_stuns._tcp.domain" -- what value of "domain" is to be used in the
> query)?
>
> Without that being specified, implementers/users have nothing specific to
> try, and without that, I do not see how STUN could be used at all.
>
> Similarly, recommending that STUN be provisioned (section 4.6) leaves the
> question of "under which domain", unanswered and ambiguous.

STUN does define a discovery mechanism, but that mechanism depends on
configuration of an input domain, as you rightly identified.  However,
no local discovery method has been defined for STUN, partly because
that can be somewhat self-defeating, depending as it does on the
server being outside of any local access.

The normal practice for STUN is, as you fear, configuration (see for
example, the information at http://stunserver.org/).  On the upside, a
STUN server is relatively cheap to operate.  Such a server can live
almost anywhere in the network.

--Martin

From chair@ietf.org  Tue Jul 23 11:07:44 2013
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3483911E833B; Tue, 23 Jul 2013 11:07:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kIPZKoDSMTxy; Tue, 23 Jul 2013 11:07:43 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:15]) by ietfa.amsl.com (Postfix) with ESMTP id D7B5711E8335; Tue, 23 Jul 2013 11:07:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id E8503A8AC0; Tue, 23 Jul 2013 11:06:29 -0700 (PDT)
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 D_36Lpb4MpHF; Tue, 23 Jul 2013 11:06:29 -0700 (PDT)
Received: from [10.30.0.100] (unknown [83.150.71.93]) by c9a.amsl.com (Postfix) with ESMTPSA id 0387CA8913; Tue, 23 Jul 2013 11:06:28 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Subject: Cisco Commits More Than US$2 Million to Support Open Internet Standards Development
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: IETF Chair <chair@ietf.org>
Date: Tue, 23 Jul 2013 21:07:35 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <612D35BD-9D92-4531-AEC7-AD169395F44F@ietf.org>
To: "ietf-announce@ietf.org" <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1508)
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "ietf@ietf.org 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: Tue, 23 Jul 2013 18:07:44 -0000

I would like to highlight an announcement that we sent today, detailing =
a multi-year hosting commitment that was first presented at IETF-86. I =
would like to thank Cisco for its significant contribution to the IETF. =
Thank you!

> Cisco Commits More Than US$2 Million to Support Open Internet =
Standards Development
> 23 July 2013
>=20
> IETF defines the standards for the global network that connects more =
than 2 billion people
>=20
> [Washington, D.C. and Geneva, Switzerland] =96 23 July 2013 =96 The =
Internet Engineering Task Force (IETF), the Internet's premier standards =
organization, and Cisco, the worldwide leader in information technology, =
today announced an agreement to provide up to US$2.2 million in support =
for the IETF's work and meetings through 2019.
>=20
> The IETF brings together leading Internet engineers and technologists =
from around the world to develop standards that form the foundation of =
the global Internet and enable yet unimagined products and services. The =
IETF developed the standards for capabilities such as internationalized =
domain names, email, and instant messaging. Since its first meeting was =
held on January 16, 1986 in San Diego, California, the IETF has =
published more than 4500 documents that describe standards for the =
fundamental technologies and widely used services on today's global =
Internet.    =20
> The IETF is open to any interested individual and seeks broad =
participation from across the globe. While the work of the IETF mainly =
takes place online to reduce barriers to participation and to maximize =
contributions from around the world, its meetings bring together over =
1000 participants. Cisco's commitment of more than US$2 million will =
provide support for both in-person meetings and remote participation =
technology to enable even broader participation in the IETF.
>=20
> "The IETF is focused on developing timely, relevant, and technically =
excellent open standards that provide a platform for the continued =
growth and evolution of the global Internet," said Jari Arkko, Chair of =
the IETF. "Unique among standards organizations, the IETF invites all =
interested parties to participate, and makes every draft and final =
standards available online without charge. Cisco's support will help to =
further expand participation in the IETF by encouraging involvement in =
meetings in-person and through collaboration technology built on =
IETF-developed standards."
>=20
> The Internet Society is the administrative home of the IETF. With its =
commitment, Cisco is recognized as the Internet Society=92s newest =
Corporate Partner. Corporate Partnership is a special program developed =
by the Internet Society to recognize organizations that have provided =
support that warrants the highest level of value and recognition, and a =
customized method for mapping a longer-term strategy across multiple =
areas of support.
>=20
> "We welcome Cisco's expanding commitment to the IETF as it reflects =
the strategic importance that open Internet standards represent for =
continued economic and social development around the world," said Lynn =
St. Amour, President and CEO of the Internet Society.
>=20
> About the Internet Engineering Task Force
>=20
> The Internet Engineering Task Force (IETF) is the Internet=92s premier =
technical standards body. It gathers a large open international =
community of network designers, engineers, operators, vendors, and =
researchers concerned with the evolution of the Internet architecture =
and the smooth operation of the Internet. The IETF seeks broad =
participation. The work of the IETF takes place online, largely through =
email lists, reducing barriers to participation and maximizing =
contributions from around the world. IETF Working Groups (WGs) are =
organized by topic into several areas (e.g., routing, transport, =
security, etc.).
>=20
> For more information, see: http://www.ietf.org/
>=20
> About the Internet Society
>=20
> The Internet Society is the trusted independent source for Internet =
information and thought leadership from around the world. With its =
principled vision and substantial technological foundation, the Internet =
Society promotes open dialogue on Internet policy, technology, and =
future development among users, companies, governments, and other =
organizations. Working with its members and Chapters around the world, =
the Internet Society enables the continued evolution and growth of the =
Internet for everyone. For more information, see: =
http://www.internetsociety.org
>=20
> Contact:
> Greg Wood
> wood@isoc.org
> +1703-625-3917

Source: =
http://www.internetsociety.org/news/cisco-commits-more-us2-million-support=
-open-internet-standards-development

Jari Arkko
IETF Chair


From narten@us.ibm.com  Tue Jul 23 16:21:44 2013
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD79611E8171 for <ietf@ietfa.amsl.com>; Tue, 23 Jul 2013 16:21:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.535
X-Spam-Level: 
X-Spam-Status: No, score=-108.535 tagged_above=-999 required=5 tests=[AWL=-2.064, BAYES_50=0.001, RCVD_IN_DNSWL_HI=-8, UPPERCASE_75_100=1.528, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TCAT7xZcr57Q for <ietf@ietfa.amsl.com>; Tue, 23 Jul 2013 16:21:38 -0700 (PDT)
Received: from e32.co.us.ibm.com (e32.co.us.ibm.com [32.97.110.150]) by ietfa.amsl.com (Postfix) with ESMTP id E70DA11E816F for <ietf@ietf.org>; Tue, 23 Jul 2013 16:21:30 -0700 (PDT)
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>; Tue, 23 Jul 2013 17:21:30 -0600
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;  Tue, 23 Jul 2013 17:21:28 -0600
Received: from d03relay01.boulder.ibm.com (d03relay01.boulder.ibm.com [9.17.195.226]) by d03dlp01.boulder.ibm.com (Postfix) with ESMTP id BB0261FF001C for <ietf@ietf.org>; Tue, 23 Jul 2013 17:16:05 -0600 (MDT)
Received: from d03av03.boulder.ibm.com (d03av03.boulder.ibm.com [9.17.195.169]) by d03relay01.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r6NNLRIR101330 for <ietf@ietf.org>; Tue, 23 Jul 2013 17:21:27 -0600
Received: from d03av03.boulder.ibm.com (loopback [127.0.0.1]) by d03av03.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r6NNLQl0031259 for <ietf@ietf.org>; Tue, 23 Jul 2013 17:21:26 -0600
Received: from cichlid.raleigh.ibm.com (sig-9-76-83-27.mts.ibm.com [9.76.83.27]) by d03av03.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r6NNLPeh031213 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 23 Jul 2013 17:21:26 -0600
Received: from cichlid.raleigh.ibm.com (localhost [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id r6NNLNYL001647; Tue, 23 Jul 2013 19:21:24 -0400
Message-Id: <201307232321.r6NNLNYL001647@cichlid.raleigh.ibm.com>
To: Doug Barton <dougb@dougbarton.us>
Subject: Google on dotless domains [was Re: IAB Statement on Dotless Domains]
In-reply-to: <51E36E43.4050102@dougbarton.us>
References: <20130712162348.9441.qmail@joyce.lan> <51E06965.7010203@gmail.com> <alpine.BSF.2.00.1307121737360.13717@joyce.lan> <51E368F9.70404@dougbarton.us> <51E36B9F.2020404@dcrocker.net> <51E36E43.4050102@dougbarton.us>
Comments: In-reply-to Doug Barton <dougb@dougbarton.us> message dated "Sun, 14 Jul 2013 20:36:35 -0700."
Date: Tue, 23 Jul 2013 19:21:23 -0400
From: Thomas Narten <narten@us.ibm.com>
X-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13072323-5406-0000-0000-00000AB78E39
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 23 Jul 2013 23:21:44 -0000

> Google is pushing for dotless-dot-search, so you can guarantee it will 
> work in chromium (with or without ICANN's blessing).

Here is what a Google employee actually said about Google and dotless
domains at last week's ICANN public forum in Durban:

>>JORDYN BUCHANAN: HELLO. I'M JORDYN BUCHANAN WITH GOOGLE. I'D LIKE TO
>> MAKE SOME OF THE SSR CONVERSATIONS WE'VE HAD TODAY A LITTLE MORE
>> CONCRETE AT LEAST WITH A COUPLE EXAMPLES THAT WE'RE HAPPY TO
>> DISCUSS AS AN APPLICANT FOR NEW gTLDs.  FIRST, I'D LIKE TO VERY
>> BRIEFLY ADDRESS DOTLESS TLDS. AS PEOPLE MAY KNOW, WE HAVE SUBMITTED
>> A APPLICATION AMENDMENT FOR OUR DOT SEARCH TLD THAT DOES INCLUDE A
>> REGISTRY SERVICE THAT INCLUDES DOTLESS AND A DOTLESS ELEMENT.  WE
>> FULLY EXPECT -- AND I UNDERSTAND THAT THE GUIDEBOOK PROVIDES THAT
>> IF AN APPLICANT PROPOSES TO OPERATE A DOTLESS SERVICE, THAT THERE
>> WILL BE ADDITIONAL SCRUTINY AND THAT ICANN WILL REVIEW THAT PROCESS
>> AND MAKE SURE THAT ANY SECURITY CONCERNS ARE MITIGATED. WE
>> APPRECIATE THAT THERE ARE POTENTIAL SSR CONCERNS AND WE ARE
>> DELIGHTED THAT ICANN WILL FULLY REVIEW THAT BEFORE DECIDING WHETHER
>> OR NOT TO ALLOW THAT SERVICE TO BE OPERATED. WE DO NOT INTEND TO
>> BYPASS THE PROCESS OR OTHERWISE HAVE OUR AMENDMENT APPROVED PRIOR
>> TO THE FULL EVALUATION OF THE PROPOSED SERVICE.  SECOND, I'D LIKE
>> TO POINT OUT WE ARE -- WE'RE THE APPLICANT FOR DOT ADS. IT HAS A
>> LOW PRIORITY NUMBER, 392.  IT'S UNCONTENDED. THERE ARE NO
>> OBJECTIONS. I EXPECT THAT UNDER NORMAL CIRCUMSTANCES, WE MIGHT BE
>> ABLE TO START TO OPERATE IT IN THE RELATIVELY NEAR FUTURE, BUT IT'S
>> NOT QUITE NORMAL CIRCUMSTANCES. BECAUSE IT ALSO APPEARS ON THE TOP
>> HANDFUL OF POTENTIAL NAME COLLISIONS IDENTIFIED IN THE INTERAISLE
>> REPORT OR AT LEAST THE PREVIEW OF IT THAT WE'VE SEEN. TO THAT
>> EXTENT I'M HERE TO COMMIT TODAY WE'RE NOT GOING TO OPERATE DOT ADS
>> PRIOR TO A FULL EVALUATION OF ANY POTENTIAL SECURITY
>> INTERACTIONSMENT WE'D LOVE TO TALK TO AMY AND OTHERS IN THE
>> COMMUNITY THAT MAY HAVE ISSUES AND WE'LL START TO WORK ON
>> MITIGATION NOW. WE HAVE A CONCRETE EXAMPLE, LET'S START TO WORK ON
>> THE PROCESS AND MAKE SURE THAT BY THE TIME WE GET TO THE POINT THAT
>> WE'RE READY TO START TO WORK THROUGH SOME OF THE OTHER TLDS THAT
>> OTHER PEOPLE OPERATE OR ARE CON TENTDED WE WORK THROUGH THIS
>> ISSUE. WE WON'T DELEGATE IT UNTIL IT'S SOLVED.

[ APPLAUSE. ]

>>CHERINE CHALABY: THANK YOU, JORDYN. ANYONE WISH TO COMMENT ON
>>JORDYN'S -- FADI.

>>FADI CHEHADE: YEAH, JORDYN, JUST TO SAY THANK YOU FOR THE
>>RESPONSIBLE APPROACH YOU'RE TAKING AND GOOGLE IS TAKING HERE. IT'S
>>APPRECIATED. AND I THINK EVEN AMY AND OTHERS WOULD APPRECIATE THE
>>WAY WE ARE DEALING WITH THESE POTENTIAL ISSUES. SO REALLY, THAT'S
>>THE WAY I HOPE ALL OF US WILL COOPERATE TO ADDRESS THESE ISSUES AS A
>>COMMUNITY. THANK YOU FOR THAT.

>>CHERINE CHALABY: THANK YOU, FADI. NEXT SPEAKER, PLEASE.




From john-ietf@jck.com  Wed Jul 24 01:15:53 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46F3211E8393 for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 01:15:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GDjlDGIANSrJ for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 01:15:45 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 0556E11E83A9 for <ietf@ietf.org>; Wed, 24 Jul 2013 01:15:37 -0700 (PDT)
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 1V1uEM-000549-3C for ietf@ietf.org; Wed, 24 Jul 2013 04:15:30 -0400
Date: Wed, 24 Jul 2013 04:15:25 -0400
From: John C Klensin <john-ietf@jck.com>
To: ietf@ietf.org
Subject: Re: BOF posters in the welcome reception
Message-ID: <2129CC69EEF207CADC2421AC@JcK-HP8200.jck.com>
In-Reply-To: <A6B9C627-A141-416B-AB39-469FDA86A875@ietf.org>
References: <A6B9C627-A141-416B-AB39-469FDA86A875@ietf.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Jul 2013 08:15:53 -0000

--On Wednesday, July 24, 2013 09:22 +0300 IETF Chair
<chair@ietf.org> wrote:

> I wanted to let you know about an experiment we are trying out
> in Berlin.
>...
> But we want as many people as possible to become involved in
> these efforts, or at least provide their feedback during the
> week. So we have given an opportunity for the BOFs to display
> a poster in the Welcome Reception (Sunday 5pm to 7pm). If you
> are attending the reception, take a look at the posters and
> look for topics that interest you. Someone running the BOF is
> also likely standing by, so you can also get directly involved
> in discussions, sign up to help, etc. We hope that this helps
> you all network with others even more :-)

In the interest of encouraging remote participation and
involvement in those BOFs, could these posters be made available
online before the reception?   Will they eventually be
incorporated into the minutes?

And, incidentally, is there a way for remote participants to
sign up for one or both meeting-related mailing lists without
registering (or using a "remote participation registration"
mechanism, which would be my preference for other reasons)?

thanks,
   john




From jari.arkko@piuha.net  Wed Jul 24 01:17:54 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9A9A11E8128 for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 01:17:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c7KdAasymXAQ for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 01:17:47 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 75B9A11E83A6 for <ietf@ietf.org>; Wed, 24 Jul 2013 01:17:42 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id E02E62CC48; Wed, 24 Jul 2013 11:17:26 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PtmONbq-U9Jx; Wed, 24 Jul 2013 11:17:26 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 2165C2CC3C; Wed, 24 Jul 2013 11:17:26 +0300 (EEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: BOF posters in the welcome reception
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <2129CC69EEF207CADC2421AC@JcK-HP8200.jck.com>
Date: Wed, 24 Jul 2013 11:17:25 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <CC160C56-5D74-4309-AD3D-FB88FEB60B01@piuha.net>
References: <A6B9C627-A141-416B-AB39-469FDA86A875@ietf.org> <2129CC69EEF207CADC2421AC@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1508)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Jul 2013 08:17:54 -0000

John,

> In the interest of encouraging remote participation and
> involvement in those BOFs, could these posters be made available
> online before the reception?   Will they eventually be
> incorporated into the minutes?

Good questions. We can work on that=85

> And, incidentally, is there a way for remote participants to
> sign up for one or both meeting-related mailing lists without
> registering (or using a "remote participation registration"
> mechanism, which would be my preference for other reasons)?

I sent the mail to ietf-announce, so I would guess many non-attendees =
got it as well.

Jari


From john-ietf@jck.com  Wed Jul 24 01:30:52 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C05DE11E839A for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 01:30:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QsNrwEMdxBni for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 01:30:46 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 6D3D511E83A3 for <ietf@ietf.org>; Wed, 24 Jul 2013 01:30:45 -0700 (PDT)
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 1V1uT7-00055L-37; Wed, 24 Jul 2013 04:30:45 -0400
Date: Wed, 24 Jul 2013 04:30:40 -0400
From: John C Klensin <john-ietf@jck.com>
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: BOF posters in the welcome reception
Message-ID: <96F611AF0497CDC862CF30D4@JcK-HP8200.jck.com>
In-Reply-To: <CC160C56-5D74-4309-AD3D-FB88FEB60B01@piuha.net>
References: <A6B9C627-A141-416B-AB39-469FDA86A875@ietf.org> <2129CC69EEF207CADC2421AC@JcK-HP8200.jck.com> <CC160C56-5D74-4309-AD3D-FB88FEB60B01@piuha.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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Jul 2013 08:30:52 -0000

--On Wednesday, July 24, 2013 11:17 +0300 Jari Arkko
<jari.arkko@piuha.net> wrote:

>> And, incidentally, is there a way for remote participants to
>> sign up for one or both meeting-related mailing lists without
>> registering (or using a "remote participation registration"
>> mechanism, which would be my preference for other reasons)?
> 
> I sent the mail to ietf-announce, so I would guess many
> non-attendees got it as well.

Yes.  I was thinking a bit more generally.  For example,
schedule changes during the meeting week, IIR, go to NNall, and
not ietf-announce.   As a remote participant, one might prefer
to avoid the usual (and interminable) discussions about coffee
shops, weather, and the diameter of the cookies, but it seems to
me that there is a good deal of material that goes to the two
meeting lists that would be of use.  Since I'm on those lists in
spite of being remote (registered and then cancelled), I can try
to keep track of whether anything significant to remote
participants appears on the meeting discuss list this time if it
would help.

best,
   john





From zehn.cao@gmail.com  Wed Jul 24 03:27:09 2013
Return-Path: <zehn.cao@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81E0F11E8103 for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 03:27:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.353
X-Spam-Level: 
X-Spam-Status: No, score=-1.353 tagged_above=-999 required=5 tests=[AWL=0.797,  BAYES_00=-2.599, GB_I_LETTER=-2, MIME_CHARSET_FARAWAY=2.45, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PM9NRT-IpeAG for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 03:27:08 -0700 (PDT)
Received: from mail-ob0-x22b.google.com (mail-ob0-x22b.google.com [IPv6:2607:f8b0:4003:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id DAA0911E8140 for <ietf@ietf.org>; Wed, 24 Jul 2013 03:27:07 -0700 (PDT)
Received: by mail-ob0-f171.google.com with SMTP id dn14so12749080obc.30 for <ietf@ietf.org>; Wed, 24 Jul 2013 03:27:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=9H7IFWwliwoKwqmfbFkW+vBvOgwP0eF4Oxci6vRgEQ0=; b=Q5HlQLN0isJPVsMDR0obBL5Bk7kbsiXIeR2rrhqoBSjzrmiW3T+3cq+IqZYJqsShWN 2OcqWMPGbOhXs2ZxUtCVLW7VoiF3jxW0OrgPANk9wkvHWqFjOGL97DE7jiGDG7ONynjo Srpx3Ai1vObP3+lgSkATDrrV0lBT6HdwaTy1PJ1HODPXEiOLb1SxjZBDdTJAFpNcSRb7 7paqcui8coYYQpEYBCuamN+VG5KNEObPwa5XR5blAseRavY4R15H91ZLzYALxJWrem0p 6h4ceLGDb7B8lTvHmMAvKu4XMsyrej4d5vlyuA++VVDJfSoxu44ChP2ravetzO09kb7M 0Y6g==
MIME-Version: 1.0
X-Received: by 10.182.32.4 with SMTP id e4mr29644839obi.16.1374661627375; Wed, 24 Jul 2013 03:27:07 -0700 (PDT)
Received: by 10.182.13.68 with HTTP; Wed, 24 Jul 2013 03:27:07 -0700 (PDT)
In-Reply-To: <CADRqEyqMtW5rFS_az895DOroN8P7Bh5w9QuBv7549Bb_D_pjaw@mail.gmail.com>
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com> <CA+9kkMDZoX0Eq4TcbpP=+YMPmq-F3CAGB1dSogYJa6V2F-irbQ@mail.gmail.com> <CANF0JMCA+HQ7=xEXjDkgxLt2iqUj3Wdq_+2+KFsPg34a0m+nxQ@mail.gmail.com> <CA+9kkMCqRL5R8v5RivjRkNHQtMFiKs3Rhva+X5NogMB6_qMaSQ@mail.gmail.com> <CAProHASRwM8-Nnd6rPsXtXk85Vb9gNeBshppFjUQxpnLTJsjDg@mail.gmail.com> <CADRqEyqMtW5rFS_az895DOroN8P7Bh5w9QuBv7549Bb_D_pjaw@mail.gmail.com>
Date: Wed, 24 Jul 2013 18:27:07 +0800
Message-ID: <CAProHARhhwAmbmF5i2tcujM7OHsC4LeE-GuAQtLi80DbVGk8Ww@mail.gmail.com>
Subject: Re: Regarding call Chinese names
From: "Cao,Zhen" <zehn.cao@gmail.com>
To: Joseph Yee <joseph.yee@gmail.com>
Content-Type: text/plain; charset=Big5
Content-Transfer-Encoding: quoted-printable
Cc: Ted Hardie <ted.ietf@gmail.com>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Jul 2013 10:27:10 -0000

>> > other than pinyin which are common and normatively correct.  For those
>> > Chinese people, your document does not apply.  As an example, the
>> > current
>> > chief executive of Hong Kong is properly called Leung Chun Ying (=B1=
=E7=AE=B6=AD^);
>> > his
>> > predecessor  in that role was Tung Chee Hwa (=B8=B3=AB=D8=B5=D8).   Si=
milar situations
>> > arise in Taiwan and in many territories where Chinese people are
>> > themselves
>> > national minorities.
>>
>> That's not Pinyin system. I have a question for you, do you think
>> these spellings are self pronounciable?
>
>
> You mean how accurate they sound?  They sound right for the intended
> dialect, just they are not Mandarin.

No, I am curious how the translation system maps the sound (i know
it's Cantonese) to English letters.

Pinyin is not self pronounceable . Because by reading the letters,
English speakers do not know how to pronounce.

From tterribe@xiph.org  Wed Jul 24 03:57:46 2013
Return-Path: <tterribe@xiph.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87D2711E80DC; Wed, 24 Jul 2013 03:57:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.077
X-Spam-Level: 
X-Spam-Status: No, score=-2.077 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cwmb0RLDGDBZ; Wed, 24 Jul 2013 03:57:32 -0700 (PDT)
Received: from smtp.mozilla.org (mx2.corp.phx1.mozilla.com [63.245.216.70]) by ietfa.amsl.com (Postfix) with ESMTP id E7EB311E839F; Wed, 24 Jul 2013 03:57:32 -0700 (PDT)
Received: from [172.17.0.5] (50-78-100-113-static.hfc.comcastbusiness.net [50.78.100.113]) (Authenticated sender: tterriberry@mozilla.com) by mx2.mail.corp.phx1.mozilla.com (Postfix) with ESMTPSA id 79E6CF20BA;  Wed, 24 Jul 2013 03:57:31 -0700 (PDT)
Message-ID: <51EFB31A.3010506@xiph.org>
Date: Wed, 24 Jul 2013 03:57:30 -0700
From: "Timothy B. Terriberry" <tterribe@xiph.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 SeaMonkey/2.16
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [payload] Last Call: <draft-ietf-payload-vp8-08.txt> (RTP Payload Format for	VP8 Video) to Proposed Standard
References: <20130604222555.32402.16024.idtracker@ietfa.amsl.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1135E7A62@xmb-aln-x02.cisco.com>
In-Reply-To: <C5E08FE080ACFD4DAE31E4BDBF944EB1135E7A62@xmb-aln-x02.cisco.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "payload@ietf.org" <payload@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Jul 2013 10:57:46 -0000

Cullen Jennings (fluffy) wrote:
> There is one thing that as far as I can tell that all the implementors agree on. None of the implications control the resolution using
>
>    m=video 62537 RTP/SAVPF 96
>    a=rtpmap:96 VP8/90000
>    a=fmtp:96 max-fr=30;max-fs=3600
>
> What resolution do you think "max-fs=3600" is? I have no idea. It is not possible to implement so it is not surprising no one is doing  it. However, this draft-ietf-payload-vp8 draft says the resolution is specified using the max-fs and max-fr.

I can't speak for other implementations, but here at Mozilla, our 
interpretation of RFC 6236 was that the values specified in imageattr 
can be completely ignored by either side, if they so choose. That leaves 
max-fs and max-fr as the only mechanism to indicate a resource 
constraint that cannot be ignored, and we plan to use it as such.

See <https://bugzilla.mozilla.org/show_bug.cgi?id=881935> for details.

From jgunn6@csc.com  Wed Jul 24 07:26:25 2013
Return-Path: <jgunn6@csc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9898111E8151; Wed, 24 Jul 2013 07:26:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jkt235rGXqjH; Wed, 24 Jul 2013 07:26:19 -0700 (PDT)
Received: from mail170.messagelabs.com (mail170.messagelabs.com [216.82.253.227]) by ietfa.amsl.com (Postfix) with ESMTP id EEDA111E80FC; Wed, 24 Jul 2013 07:26:18 -0700 (PDT)
X-Env-Sender: jgunn6@csc.com
X-Msg-Ref: server-2.tower-170.messagelabs.com!1374675945!18617333!1
X-Originating-IP: [20.137.2.88]
X-StarScan-Received: 
X-StarScan-Version: 6.9.11; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 10162 invoked from network); 24 Jul 2013 14:25:45 -0000
Received: from amer-mta102.csc.com (HELO amer-mta102.csc.com) (20.137.2.88) by server-2.tower-170.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 24 Jul 2013 14:25:45 -0000
Received: from amer-gw09.amer.csc.com (amer-gw09.amer.csc.com [20.6.39.245]) by amer-mta102.csc.com (8.13.8/8.13.8) with ESMTP id r6OENn05003867; Wed, 24 Jul 2013 10:23:49 -0400
In-Reply-To: <96F611AF0497CDC862CF30D4@JcK-HP8200.jck.com>
References: <A6B9C627-A141-416B-AB39-469FDA86A875@ietf.org>	<2129CC69EEF207CADC2421AC@JcK-HP8200.jck.com> <CC160C56-5D74-4309-AD3D-FB88FEB60B01@piuha.net> <96F611AF0497CDC862CF30D4@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
MIME-Version: 1.0
Subject: Remote participants access to Meeting Mailing Lists was Re: BOF posters in the welcome reception
X-KeepSent: 68BD4951:D37EA2D7-85257BB2:004EEDF0; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.5.2FP4 SHF97 March 26, 2012
From: Janet P Gunn <jgunn6@csc.com>
Message-ID: <OF68BD4951.D37EA2D7-ON85257BB2.004EEDF0-85257BB2.004F4E5A@csc.com>
Date: Wed, 24 Jul 2013 10:25:42 -0400
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 8.5.2FP3 HF204|September 20, 2011) at 07/24/2013 10:19:21 AM, Serialize complete at 07/24/2013 10:19:21 AM
Content-Type: multipart/alternative; boundary="=_alternative 004F4E2885257BB2_="
Cc: ietf-bounces@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Jul 2013 14:26:25 -0000

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

I am another remote participant who would like to be able to subscribe to 
the meeting-specific mailing list. 

 I can skip (myself)  the ones about coffee and cookies, but definitely 
want to read the ones about schedule changes, etc.

And even the other messages give me a taste of "what it would be like to 
be there".

Janet


ietf-bounces@ietf.org wrote on 07/24/2013 04:30:40 AM:

> From: John C Klensin <john-ietf@jck.com>
> To: Jari Arkko <jari.arkko@piuha.net>
> Cc: ietf@ietf.org
> Date: 07/24/2013 04:31 AM
> Subject: Re: BOF posters in the welcome reception
> Sent by: ietf-bounces@ietf.org
> 
> 
> 
> --On Wednesday, July 24, 2013 11:17 +0300 Jari Arkko
> <jari.arkko@piuha.net> wrote:
> 
> >> And, incidentally, is there a way for remote participants to
> >> sign up for one or both meeting-related mailing lists without
> >> registering (or using a "remote participation registration"
> >> mechanism, which would be my preference for other reasons)?
> > 
> > I sent the mail to ietf-announce, so I would guess many
> > non-attendees got it as well.
> 
> Yes.  I was thinking a bit more generally.  For example,
> schedule changes during the meeting week, IIR, go to NNall, and
> not ietf-announce.   As a remote participant, one might prefer
> to avoid the usual (and interminable) discussions about coffee
> shops, weather, and the diameter of the cookies, but it seems to
> me that there is a good deal of material that goes to the two
> meeting lists that would be of use.  Since I'm on those lists in
> spite of being remote (registered and then cancelled), I can try
> to keep track of whether anything significant to remote
> participants appears on the meeting discuss list this time if it
> would help.
> 
> best,
>    john
> 
> 
> 
> 

--=_alternative 004F4E2885257BB2_=
Content-Type: text/html; charset="US-ASCII"

<font size=2 face="sans-serif">I am another remote participant who would
like to be able to subscribe to the meeting-specific mailing list. </font>
<br>
<br><font size=2 face="sans-serif">&nbsp;I can skip (myself) &nbsp;the
ones about coffee and cookies, but definitely want to read the ones about
schedule changes, etc.</font>
<br>
<br><font size=2 face="sans-serif">And even the other messages give me
a taste of &quot;what it would be like to be there&quot;.</font>
<br>
<br><font size=2 face="sans-serif">Janet<br>
</font>
<br>
<br><tt><font size=2>ietf-bounces@ietf.org wrote on 07/24/2013 04:30:40
AM:<br>
<br>
&gt; From: John C Klensin &lt;john-ietf@jck.com&gt;</font></tt>
<br><tt><font size=2>&gt; To: Jari Arkko &lt;jari.arkko@piuha.net&gt;</font></tt>
<br><tt><font size=2>&gt; Cc: ietf@ietf.org</font></tt>
<br><tt><font size=2>&gt; Date: 07/24/2013 04:31 AM</font></tt>
<br><tt><font size=2>&gt; Subject: Re: BOF posters in the welcome reception</font></tt>
<br><tt><font size=2>&gt; Sent by: ietf-bounces@ietf.org</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; <br>
&gt; <br>
&gt; --On Wednesday, July 24, 2013 11:17 +0300 Jari Arkko<br>
&gt; &lt;jari.arkko@piuha.net&gt; wrote:<br>
&gt; <br>
&gt; &gt;&gt; And, incidentally, is there a way for remote participants
to<br>
&gt; &gt;&gt; sign up for one or both meeting-related mailing lists without<br>
&gt; &gt;&gt; registering (or using a &quot;remote participation registration&quot;<br>
&gt; &gt;&gt; mechanism, which would be my preference for other reasons)?<br>
&gt; &gt; <br>
&gt; &gt; I sent the mail to ietf-announce, so I would guess many<br>
&gt; &gt; non-attendees got it as well.<br>
&gt; <br>
&gt; Yes. &nbsp;I was thinking a bit more generally. &nbsp;For example,<br>
&gt; schedule changes during the meeting week, IIR, go to NNall, and<br>
&gt; not ietf-announce. &nbsp; As a remote participant, one might prefer<br>
&gt; to avoid the usual (and interminable) discussions about coffee<br>
&gt; shops, weather, and the diameter of the cookies, but it seems to<br>
&gt; me that there is a good deal of material that goes to the two<br>
&gt; meeting lists that would be of use. &nbsp;Since I'm on those lists
in<br>
&gt; spite of being remote (registered and then cancelled), I can try<br>
&gt; to keep track of whether anything significant to remote<br>
&gt; participants appears on the meeting discuss list this time if it<br>
&gt; would help.<br>
&gt; <br>
&gt; best,<br>
&gt; &nbsp; &nbsp;john<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
</font></tt>
--=_alternative 004F4E2885257BB2_=--

From melinda.shore@gmail.com  Wed Jul 24 07:44:43 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EF9311E80AE for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 07:44:43 -0700 (PDT)
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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GnCdGylNWw-Q for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 07:44:42 -0700 (PDT)
Received: from mail-pa0-x229.google.com (mail-pa0-x229.google.com [IPv6:2607:f8b0:400e:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id 01BEF11E80F4 for <ietf@ietf.org>; Wed, 24 Jul 2013 07:43:46 -0700 (PDT)
Received: by mail-pa0-f41.google.com with SMTP id bj3so742829pad.14 for <ietf@ietf.org>; Wed, 24 Jul 2013 07:43:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=e72bI2auYwA0eEf1I/dueFCRUHQ/w5qOxG9D6q4QiN4=; b=m3LmEbFEanvMTLYRwWvVq9DTOsDzn09wEoKs31y8mbuEjX9fOJwcMQUDMDtZcCQ+8t z+1KorzIgAwZzGxRed9MXm3K902BAVIV/1j3PcAJMI35UzljCiITzr2uUKjMno+JPwSI OzpEt29csEDE42mpQbxf4OSkTbqB55vmH1bQJVddfrkg8AQNZLa0uPNZwnN5JUDvVMLj dEh+Qrcp6q+PLyAJA6r0L8IHmubkakEO6nOcDzC+gGGlhCUxpR8lSj7qwMRfWNSf+PD4 wjq9rqKTK7vWPfdw0XZ2dyw8JK0U0ww/Pcj8WZx/WPwn5QAjLeZqQCd9u9yBLMlXkbW8 2iyQ==
X-Received: by 10.66.9.71 with SMTP id x7mr44196566paa.37.1374677026682; Wed, 24 Jul 2013 07:43:46 -0700 (PDT)
Received: from spandex.local (66-230-83-206-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.83.206]) by mx.google.com with ESMTPSA id om2sm48268896pbb.34.2013.07.24.07.43.44 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 24 Jul 2013 07:43:45 -0700 (PDT)
Message-ID: <51EFE81F.6030803@gmail.com>
Date: Wed, 24 Jul 2013 06:43:43 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: BOF posters in the welcome reception
References: <A6B9C627-A141-416B-AB39-469FDA86A875@ietf.org> <2129CC69EEF207CADC2421AC@JcK-HP8200.jck.com> <CC160C56-5D74-4309-AD3D-FB88FEB60B01@piuha.net> <96F611AF0497CDC862CF30D4@JcK-HP8200.jck.com>
In-Reply-To: <96F611AF0497CDC862CF30D4@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Jul 2013 14:44:43 -0000

On 7/24/13 12:30 AM, John C Klensin wrote:
> Yes.  I was thinking a bit more generally.  For example,
> schedule changes during the meeting week, IIR, go to NNall, and
> not ietf-announce.   As a remote participant, one might prefer
> to avoid the usual (and interminable) discussions about coffee
> shops, weather, and the diameter of the cookies, but it seems to
> me that there is a good deal of material that goes to the two
> meeting lists that would be of use.  Since I'm on those lists in
> spite of being remote (registered and then cancelled), I can try
> to keep track of whether anything significant to remote
> participants appears on the meeting discuss list this time if it
> would help.

Yes, the meeting mailing lists are here:
http://www.ietf.org/meeting/email-list.html

Melinda



From jari.arkko@piuha.net  Wed Jul 24 08:19:36 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82A7621F849C for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 08:19:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DWRbvS3DQ8yh for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 08:19:30 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id AD0A611E80DF for <ietf@ietf.org>; Wed, 24 Jul 2013 08:19:24 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 33D192CC60; Wed, 24 Jul 2013 18:18:45 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vVFhKh2VChEG; Wed, 24 Jul 2013 18:18:44 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 9223F2CC48; Wed, 24 Jul 2013 18:18:44 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Remote participants access to Meeting Mailing Lists was Re: BOF posters in the welcome reception
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <OF68BD4951.D37EA2D7-ON85257BB2.004EEDF0-85257BB2.004F4E5A@csc.com>
Date: Wed, 24 Jul 2013 18:18:44 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <94EA01D5-C6BE-40B3-84C1-C707522627AB@piuha.net>
References: <A6B9C627-A141-416B-AB39-469FDA86A875@ietf.org>	<2129CC69EEF207CADC2421AC@JcK-HP8200.jck.com> <CC160C56-5D74-4309-AD3D-FB88FEB60B01@piuha.net> <96F611AF0497CDC862CF30D4@JcK-HP8200.jck.com> <OF68BD4951.D37EA2D7-ON85257BB2.004EEDF0-85257BB2.004F4E5A@csc.com>
To: Janet P Gunn <jgunn6@csc.com>
X-Mailer: Apple Mail (2.1508)
Cc: John C Klensin <john-ietf@jck.com>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Jul 2013 15:19:36 -0000

Janet,

> I am another remote participant who would like to be able to subscribe =
to the meeting-specific mailing list.=20
>=20
>  I can skip (myself)  the ones about coffee and cookies, but =
definitely want to read the ones about schedule changes, etc.=20
>=20
> And even the other messages give me a taste of "what it would be like =
to be there".=20

Understood. I'm wondering if this points to a need to get on the meeting =
list easily. Either without registering, or having a registration flag =
of being interested in the meeting while not intending to be there.

We could create another mailing list too, but I'm a little sensitive for =
creating many slightly different mailing lists (duplicate messages, =
posting accidentally on the wrong one, etc)

Jari


From ford@isoc.org  Wed Jul 24 08:24:13 2013
Return-Path: <ford@isoc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10F7611E822D for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 08:24:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sGK-NXPGEo+Z for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 08:24:03 -0700 (PDT)
Received: from smtp117.iad.emailsrvr.com (smtp117.iad.emailsrvr.com [207.97.245.117]) by ietfa.amsl.com (Postfix) with ESMTP id BC22711E824C for <ietf@ietf.org>; Wed, 24 Jul 2013 08:23:02 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp41.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id 21E272903D6; Wed, 24 Jul 2013 11:22:53 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp41.relay.iad1a.emailsrvr.com (Authenticated sender: ford-AT-isoc.org) with ESMTPSA id 7ABA429039B;  Wed, 24 Jul 2013 11:22:52 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Subject: IETF Journal Volume 9 Issue 1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Matthew Ford <ford@isoc.org>
Date: Wed, 24 Jul 2013 16:22:50 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <0B4A5020-59A1-4D67-9591-101EE37AD661@isoc.org>
To: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-Mailer: Apple Mail (2.1508)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "ietfjournal@isoc.org" <ietfjournal@isoc.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, 24 Jul 2013 15:24:13 -0000

Hi,

The latest issue of the IETF Journal (Volume 9, Issue 1) is available =
online:

	http://internetsociety.org/ietfjournal

Among many others it contains articles on software-defined networking, =
WebRTC and the Networking History BoF.

In addition you will find summary reports of the IETF 86 meeting held in =
Orlando, regular columns submitted by the IETF, the IAB and the IRTF =
chairs, summaries of the plenary sessions, and articles on the =
fellowships to IETF and the Applied Networking Research Prize.

You can read this publication online or download the full issue in PDF =
format. You can also keep up to date with the latest issue by =
subscribing to the IETF Journal as an email edition or have it delivered =
to your postal address in hardcopy.

Many thanks to all our contributors. Please send any comments or =
suggestions for future issues to ietfjournal@isoc.org.

Regards,
Mat

Mat Ford
Managing Editor
IETF Journal
http://internetsociety.org/ietfjournal=

From john-ietf@jck.com  Wed Jul 24 09:07:57 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 786AF11E8101 for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 09:07:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aGqnCqBS3rwY for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 09:07:52 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 1A61811E80DF for <ietf@ietf.org>; Wed, 24 Jul 2013 09:07:52 -0700 (PDT)
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 1V21bS-0005df-Q7; Wed, 24 Jul 2013 12:07:50 -0400
Date: Wed, 24 Jul 2013 12:07:45 -0400
From: John C Klensin <john-ietf@jck.com>
To: Melinda Shore <melinda.shore@gmail.com>, ietf@ietf.org
Subject: Remote participation and meeting mailing lists (was: Re: BOF posters in the welcome reception)
Message-ID: <0A8B19DB5964EFCD8668352E@JcK-HP8200.jck.com>
In-Reply-To: <51EFE81F.6030803@gmail.com>
References: <A6B9C627-A141-416B-AB39-469FDA86A875@ietf.org> <2129CC69EEF207CADC2421AC@JcK-HP8200.jck.com> <CC160C56-5D74-4309-AD3D-FB88FEB60B01@piuha.net> <96F611AF0497CDC862CF30D4@JcK-HP8200.jck.com> <51EFE81F.6030803@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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Jul 2013 16:07:57 -0000

--On Wednesday, July 24, 2013 06:43 -0800 Melinda Shore
<melinda.shore@gmail.com> wrote:

> On 7/24/13 12:30 AM, John C Klensin wrote:
>> Yes.  I was thinking a bit more generally.  For example,
>> schedule changes during the meeting week, IIR, go to NNall,
>> and not ietf-announce.   As a remote participant, one might
>> prefer to avoid the usual (and interminable) discussions
>...

> Yes, the meeting mailing lists are here:
> http://www.ietf.org/meeting/email-list.html

Yes, but...

(1) A hypothetical remote participating newcomer is expected to
find that how?  I note that the IETF home page links to mailing
lists do not list either 87all or 87attendees in any of the
obvious places.

(2) That page provides a mechanism for subscribing to
87attendees (the cookies and coffee and, I assume,
bumped-from-hotel-attendees very soon, discussion list) but not
a link to the far more important for remote folks 87all.   If
there is a way to subscribe to that without registering, I
haven't found it.

Note to remote participants:   The cookies and coffee list is
also where a lot of comments about the meeting network and
related facilities appears.  While most remote participants
don't need to know how poorly the network works in some
alternate hotel, information about Meetecho and Webex status
tends to appear there too.

    john




From tjc@ecs.soton.ac.uk  Wed Jul 24 09:46:18 2013
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8D2711E8219 for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 09:46:18 -0700 (PDT)
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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mZSk2eF-imjd for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 09:46:17 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 6EDE911E8111 for <ietf@ietf.org>; Wed, 24 Jul 2013 09:46:16 -0700 (PDT)
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 r6OGk6A3026258;  Wed, 24 Jul 2013 17:46:06 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r6OGk6A3026258
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1374684367; bh=w7L1ot5V5wAoqwlpQWdG0gzFBgI=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=q9kz6eirntGYKsrpOpLnsXOzBkR+KTJNU7PQu4dSNsEiwBBGQ0rH9fNsoEY73nRHa gBtBRVGHADIdxHXp9u1+G2Tw0ZcXSYejzRX8v4MX7YZJ9HNJMzM+IwUEmFu5rluxGt Uha6yhp6cegj69mK3ekiiinoUrHOkQPMhxcqtnRw=
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 p6NHk60544548597DE ret-id none; Wed, 24 Jul 2013 17:46:07 +0100
Received: from [192.168.1.110] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r6OGk0HA030081 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 24 Jul 2013 17:46:00 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Remote participants access to Meeting Mailing Lists was Re: BOF posters in the welcome reception
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <94EA01D5-C6BE-40B3-84C1-C707522627AB@piuha.net>
Date: Wed, 24 Jul 2013 17:46:02 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|07b43bbc00e6dd8decb147cb113c10dfp6NHk603tjc|ecs.soton.ac.uk|F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk>
References: <A6B9C627-A141-416B-AB39-469FDA86A875@ietf.org>	<2129CC69EEF207CADC2421AC@JcK-HP8200.jck.com> <CC160C56-5D74-4309-AD3D-FB88FEB60B01@piuha.net> <96F611AF0497CDC862CF30D4@JcK-HP8200.jck.com> <OF68BD4951.D37EA2D7-ON85257BB2.004EEDF0-85257BB2.004F4E5A@csc.com> <94EA01D5-C6BE-40B3-84C1-C707522627AB@piuha.net> <F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk>
To: Jari Arkko <jari.arkko@piuha.net>
X-Mailer: Apple Mail (2.1508)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p6NHk6054454859700; tid=p6NHk60544548597DE; 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: r6OGk6A3026258
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: John C Klensin <john-ietf@jck.com>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Jul 2013 16:46:19 -0000

On 24 Jul 2013, at 16:18, Jari Arkko <jari.arkko@piuha.net> wrote:

> Janet,
>=20
>> I am another remote participant who would like to be able to =
subscribe to the meeting-specific mailing list.=20
>>=20
>> I can skip (myself)  the ones about coffee and cookies, but =
definitely want to read the ones about schedule changes, etc.=20
>>=20
>> And even the other messages give me a taste of "what it would be like =
to be there".=20
>=20
> Understood. I'm wondering if this points to a need to get on the =
meeting list easily. Either without registering, or having a =
registration flag of being interested in the meeting while not intending =
to be there.
>=20
> We could create another mailing list too, but I'm a little sensitive =
for creating many slightly different mailing lists (duplicate messages, =
posting accidentally on the wrong one, etc)

I see no reason why the 87attendees@ietf.org list shouldn't be open to =
remote participants. Is that not the case already? We should be doing =
all we can to encourage participation.

I would share the concerns of duplication if an 87remote@ietf.org list =
were set up, but it might be useful for those who aren't there to be =
able to discuss issues, tips, etc with remote participation.

A lot of meeting topics do come up on the main ietf list too, of course.

Tim=

From jari.arkko@piuha.net  Wed Jul 24 09:59:05 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A47811E80DF for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 09:59:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9dr5WPsuIPBL for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 09:58:59 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id BD4D221F843F for <ietf@ietf.org>; Wed, 24 Jul 2013 09:58:58 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 15B9A2CC66; Wed, 24 Jul 2013 19:58:58 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7V9uZnvqn7cF; Wed, 24 Jul 2013 19:58:57 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 595042CC64; Wed, 24 Jul 2013 19:58:57 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Remote participants access to Meeting Mailing Lists was Re: BOF posters in the welcome reception
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <EMEW3|07b43bbc00e6dd8decb147cb113c10dfp6NHk603tjc|ecs.soton.ac.uk|F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk>
Date: Wed, 24 Jul 2013 19:58:57 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <9EF4BF5A-3E32-4DBA-9742-59A92EA43CFA@piuha.net>
References: <A6B9C627-A141-416B-AB39-469FDA86A875@ietf.org>	<2129CC69EEF207CADC2421AC@JcK-HP8200.jck.com> <CC160C56-5D74-4309-AD3D-FB88FEB60B01@piuha.net> <96F611AF0497CDC862CF30D4@JcK-HP8200.jck.com> <OF68BD4951.D37EA2D7-ON85257BB2.004EEDF0-85257BB2.004F4E5A@csc.com> <94EA01D5-C6BE-40B3-84C1-C707522627AB@piuha.net> <F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk> <EMEW3|07b43bbc00e6dd8decb147cb113c10dfp6NHk603tjc|ecs.soton.ac.uk|F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk>
To: Tim Chown <tjc@ecs.soton.ac.uk>
X-Mailer: Apple Mail (2.1508)
Cc: John C Klensin <john-ietf@jck.com>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Jul 2013 16:59:05 -0000

>=20
> I see no reason why the 87attendees@ietf.org list shouldn't be open to =
remote participants. Is that not the case already? We should be doing =
all we can to encourage participation.

Several people pointed out already (in private e-mail) that the list =
might be all that is needed, and it probably is already open. Maybe it =
just needs better advertising. <sign up here if you want to follow =
discussions about the meeting, even if you are a remote attendee>

Jari


From scott.brim@gmail.com  Wed Jul 24 10:01:35 2013
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF74D11E80F2 for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 10:01:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zn38aeYoL-ds for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 10:01:34 -0700 (PDT)
Received: from mail-ea0-x229.google.com (mail-ea0-x229.google.com [IPv6:2a00:1450:4013:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id EFEF321F843F for <ietf@ietf.org>; Wed, 24 Jul 2013 10:01:33 -0700 (PDT)
Received: by mail-ea0-f169.google.com with SMTP id h15so384806eak.28 for <ietf@ietf.org>; Wed, 24 Jul 2013 10:01:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=ISQ/N3MXAzmqE34zkEctMTFhqCLdYKx7CT/y5OF/8Ms=; b=vl0nNNqLTiLDIVYJ19AB3LwLCw2FKU35BCXtaAelbdIZZCI8Z51I3M1DsFUXc5xGzv Xb56rS1PxXqEUo5d9tY4eQU7RDSDk487GZ+2jdmD54Jsp836kf4Hw0r61IBzH85t1AKD tj845GfKB5kim9jGSIZREdaE8LBg91YpqTTZfN69HaQymp0cbWAecIos1FSmqHCsVa5l SNYYjszKdREmXUbKEHCJNQyRRwbdecXH3PeHqiALaECQqmZoYOWlf9egJv9dQ5YL9MTw tCvZgZDmZo7QtAJwl5zofCnq10FlB0XwMEMgaHnkFuaJqJpJnVFatPgdKxwz/ISX9YN8 kJ8w==
X-Received: by 10.15.81.136 with SMTP id x8mr38606677eey.4.1374685293032; Wed, 24 Jul 2013 10:01:33 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.14.175.197 with HTTP; Wed, 24 Jul 2013 10:01:11 -0700 (PDT)
In-Reply-To: <EMEW3|07b43bbc00e6dd8decb147cb113c10dfp6NHk603tjc|ecs.soton.ac.uk|F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk>
References: <A6B9C627-A141-416B-AB39-469FDA86A875@ietf.org> <2129CC69EEF207CADC2421AC@JcK-HP8200.jck.com> <CC160C56-5D74-4309-AD3D-FB88FEB60B01@piuha.net> <96F611AF0497CDC862CF30D4@JcK-HP8200.jck.com> <OF68BD4951.D37EA2D7-ON85257BB2.004EEDF0-85257BB2.004F4E5A@csc.com> <F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk> <94EA01D5-C6BE-40B3-84C1-C707522627AB@piuha.net> <EMEW3|07b43bbc00e6dd8decb147cb113c10dfp6NHk603tjc|ecs.soton.ac.uk|F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk>
From: Scott Brim <scott.brim@gmail.com>
Date: Wed, 24 Jul 2013 13:01:11 -0400
Message-ID: <CAPv4CP-L1VCV4__f=EAXan-odWhV6Qo=QoMBOPUOS1R1F0NhPA@mail.gmail.com>
Subject: Re: Remote participants access to Meeting Mailing Lists was Re: BOF posters in the welcome reception
To: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1
Cc: John C Klensin <john-ietf@jck.com>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Jul 2013 17:01:35 -0000

The point of having a separate list for participants was to avoid
spamming the ietf list.

It can be open to everyone to subscribe to, since anyone can see the
archives, HOWEVER I recommend that only registered participants be
allowed to post.

Scott

From joelja@bogus.com  Wed Jul 24 10:26:34 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F012A11E8105 for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 10:26:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 31o+UB0c3i1w for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 10:26:33 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 91BFA11E8151 for <ietf@ietf.org>; Wed, 24 Jul 2013 10:26:27 -0700 (PDT)
Received: from joels-MacBook-Air.local (host-64-47-153-50.masergy.com [64.47.153.50]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r6OHQOcP081000 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Wed, 24 Jul 2013 17:26:25 GMT (envelope-from joelja@bogus.com)
Message-ID: <51F00E3B.2040209@bogus.com>
Date: Wed, 24 Jul 2013 10:26:19 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:23.0) Gecko/20100101 Thunderbird/23.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>, Melinda Shore <melinda.shore@gmail.com>, ietf@ietf.org
Subject: Re: Remote participation and meeting mailing lists
References: <A6B9C627-A141-416B-AB39-469FDA86A875@ietf.org>	<2129CC69EEF207CADC2421AC@JcK-HP8200.jck.com>	<CC160C56-5D74-4309-AD3D-FB88FEB60B01@piuha.net>	<96F611AF0497CDC862CF30D4@JcK-HP8200.jck.com>	<51EFE81F.6030803@gmail.com> <0A8B19DB5964EFCD8668352E@JcK-HP8200.jck.com>
In-Reply-To: <0A8B19DB5964EFCD8668352E@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.2.7 (nagasaki.bogus.com [147.28.0.81]); Wed, 24 Jul 2013 17:26:26 +0000 (UTC)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Jul 2013 17:26:34 -0000

On 7/24/13 9:07 AM, John C Klensin wrote:
>
> --On Wednesday, July 24, 2013 06:43 -0800 Melinda Shore
> <melinda.shore@gmail.com> wrote:
>
>> On 7/24/13 12:30 AM, John C Klensin wrote:
>>> Yes.  I was thinking a bit more generally.  For example,
>>> schedule changes during the meeting week, IIR, go to NNall,
>>> and not ietf-announce.   As a remote participant, one might
>>> prefer to avoid the usual (and interminable) discussions
>> ...
>> Yes, the meeting mailing lists are here:
>> http://www.ietf.org/meeting/email-list.html
> Yes, but...
>
> (1) A hypothetical remote participating newcomer is expected to
> find that how?  I note that the IETF home page links to mailing
> lists do not list either 87all or 87attendees in any of the
> obvious places.
>
> (2) That page provides a mechanism for subscribing to
> 87attendees (the cookies and coffee and, I assume,
> bumped-from-hotel-attendees very soon, discussion list) but not
> a link to the far more important for remote folks 87all.   If
> there is a way to subscribe to that without registering, I
> haven't found it.
>
> Note to remote participants:   The cookies and coffee list is
> also where a lot of comments about the meeting network and
> related facilities appears.  While most remote participants
> don't need to know how poorly the network works in some
> alternate hotel, information about Meetecho and Webex status
> tends to appear there too.
We try to keep that in the IETF list since it's of presumed utility to 
the entire ietf  community.
>      john
>
>
>


From john-ietf@jck.com  Wed Jul 24 11:26:46 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CDCD11E8236 for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 11:26:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SHDZ56Q2gnwD for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 11:26:33 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 282CD11E8125 for <ietf@ietf.org>; Wed, 24 Jul 2013 11:26:33 -0700 (PDT)
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 1V23la-0005ng-9j; Wed, 24 Jul 2013 14:26:26 -0400
Date: Wed, 24 Jul 2013 14:26:21 -0400
From: John C Klensin <john-ietf@jck.com>
To: Tim Chown <tjc@ecs.soton.ac.uk>, Jari Arkko <jari.arkko@piuha.net>
Subject: Re: Remote participants access to Meeting Mailing Lists was Re: BOF posters in the welcome reception
Message-ID: <4402A8BCBCF8C54CF188B4AA@JcK-HP8200.jck.com>
In-Reply-To: <EMEW3|07b43bbc00e6dd8decb147cb113c10dfp6NHk603tjc|ecs.soton.ac.uk|F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk>
References: <A6B9C627-A141-416B-AB39-469FDA86A875@ietf.org> <2129CC69EEF207CADC2421AC@JcK-HP8200.jck.com> <CC160C56-5D74-4309-AD3D-FB88FEB60B01@piuha.net> <96F611AF0497CDC862CF30D4@JcK-HP8200.jck.com> <OF68BD4951.D37EA2D7-ON85257BB2.004EEDF0-85257BB2.004F4E5A@csc.com> <94EA01D5-C6BE-40B3-84C1-C707522627AB@piuha.net> <F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk> <EMEW3|07b43bbc00e6dd8decb147cb113c10dfp6NHk603tjc|ecs.soton.ac.uk|F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.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
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Jul 2013 18:26:46 -0000

--On Wednesday, July 24, 2013 17:46 +0100 Tim Chown
<tjc@ecs.soton.ac.uk> wrote:

> I see no reason why the 87attendees@ietf.org list shouldn't be
> open to remote participants. Is that not the case already? We
> should be doing all we can to encourage participation.

It is already.  It is a bit hard to find, but it is there and
open.

>...

Unfortunately 87all@ietf.org --the "announce" version of the
list-- is where the really important things, like schedule
changes, show up.  And, at least as far as I can tell, there is
no way for a non-registrant to get on that list.
>...

best,
  john


From eric.gray@ericsson.com  Wed Jul 24 11:36:05 2013
Return-Path: <eric.gray@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1792511E8242 for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 11:36:05 -0700 (PDT)
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=[AWL=0.001,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a76sf3qgKkEa for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 11:35:58 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id 7458611E80FB for <ietf@ietf.org>; Wed, 24 Jul 2013 11:35:58 -0700 (PDT)
X-AuditID: c6180641-b7f986d000007a82-c6-51f01e8da360
Received: from EUSAAHC004.ericsson.se (Unknown_Domain [147.117.188.84]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 1C.D4.31362.D8E10F15; Wed, 24 Jul 2013 20:35:58 +0200 (CEST)
Received: from EUSAAMB104.ericsson.se ([147.117.188.121]) by EUSAAHC004.ericsson.se ([147.117.188.84]) with mapi id 14.02.0328.009; Wed, 24 Jul 2013 14:35:55 -0400
From: Eric Gray <eric.gray@ericsson.com>
To: John C Klensin <john-ietf@jck.com>, Tim Chown <tjc@ecs.soton.ac.uk>, "Jari Arkko" <jari.arkko@piuha.net>
Subject: RE: Remote participants access to Meeting Mailing Lists	was Re: BOF posters in the welcome reception
Thread-Topic: Remote participants access to Meeting Mailing Lists	was Re: BOF posters in the welcome reception
Thread-Index: AQHOiJucBstkq/b+NUOnsHkdHlvRXJl0JtrQ
Date: Wed, 24 Jul 2013 18:35:55 +0000
Message-ID: <48E1A67CB9CA044EADFEAB87D814BFF63FAC35@eusaamb104.ericsson.se>
References: <A6B9C627-A141-416B-AB39-469FDA86A875@ietf.org> <2129CC69EEF207CADC2421AC@JcK-HP8200.jck.com> <CC160C56-5D74-4309-AD3D-FB88FEB60B01@piuha.net> <96F611AF0497CDC862CF30D4@JcK-HP8200.jck.com> <OF68BD4951.D37EA2D7-ON85257BB2.004EEDF0-85257BB2.004F4E5A@csc.com> <94EA01D5-C6BE-40B3-84C1-C707522627AB@piuha.net> <F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk> <EMEW3|07b43bbc00e6dd8decb147cb113c10dfp6NHk603tjc|ecs.soton.ac.uk|F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk> <4402A8BCBCF8C54CF188B4AA@JcK-HP8200.jck.com>
In-Reply-To: <4402A8BCBCF8C54CF188B4AA@JcK-HP8200.jck.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.135]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrPLMWRmVeSWpSXmKPExsUyuXRPiG6f3IdAg0mdrBbPNs5nsZixbwWb ReulP2wWh/Y8Z3Ng8fi7ztVjyZKfTB6XV75m9ti6ZDpbAEsUl01Kak5mWWqRvl0CV8bD9gOM BSt4Ks7u38/WwHiHs4uRk0NCwETi+sJ5jBC2mMSFe+vZQGwhgaOMEhMfW3YxcgHZyxkl7h6d AFbEJqAhcezOWjBbRCBP4vCOP2A2M1D8zdkOJhBbWCBfYsW3rexdjBxANQUS/XOFIcqNJGY+ n84GEmYRUJV49l4NJMwr4C0xbeI1JohVq1kkHl+7ygKS4BSwktj9ayoziM0IdNv3U2uYIFaJ S9x6Mp8J4mYBiSV7zjND2KISLx//Y4WwlSW+z3nEAlGvI7Fg9yc2CFtbYtnC18wQiwUlTs58 wjKBUWwWkrGzkLTMQtIyC0nLAkaWVYwcpcWpZbnpRoabGIGRdEyCzXEH44JPlocYpTlYlMR5 N+idCRQSSE8sSc1OTS1ILYovKs1JLT7EyMTBKdXAaLLwkafT/XO82S7dSuf/+09vfvhN5dIv l5lBnFtXnTgrMHmLl4rg50t8qqvnLXvu0eax7Fv+piXsSbd/KN4Paw+X+780+4id2o9zz5Zn ivIdWXbMvP0hq/ri3jat66ZvPX9n/Lnmybx3sdnWE6FzPq+SbYy4H1r5xv+t2plZXws0z3Nd 4br6iVOJpTgj0VCLuag4EQDNE8DJcgIAAA==
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Jul 2013 18:36:05 -0000

John,

	As I understand it, the meeting-specific mailing lists are used either mos=
tly
or exclusively for "chatting" about stuff at the meeting that is most relev=
ant to folks
at the meeting.  Stuff like network/power/room issues, potential social act=
ivities,
etc.

	If folks that are not at the meeting want to read stuff like that, and it'=
s=20
possible for them to do so, great.  But why jump through hoops on either si=
de to
make that possible?

	These lists are not - AFAIK - intended for "meeting participation" anywher=
e
near as much as they are for meeting logisitics.

--
Eric

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Joh=
n C Klensin
Sent: Wednesday, July 24, 2013 2:26 PM
To: Tim Chown; Jari Arkko
Cc: ietf@ietf.org list
Subject: Re: Remote participants access to Meeting Mailing Lists was Re: BO=
F posters in the welcome reception



--On Wednesday, July 24, 2013 17:46 +0100 Tim Chown <tjc@ecs.soton.ac.uk> w=
rote:

> I see no reason why the 87attendees@ietf.org list shouldn't be open to=20
> remote participants. Is that not the case already? We should be doing=20
> all we can to encourage participation.

It is already.  It is a bit hard to find, but it is there and open.

>...

Unfortunately 87all@ietf.org --the "announce" version of the
list-- is where the really important things, like schedule changes, show up=
.  And, at least as far as I can tell, there is no way for a non-registrant=
 to get on that list.
>...

best,
  john


From barryleiba.mailing.lists@gmail.com  Wed Jul 24 11:36:10 2013
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 027E611E8242 for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 11:36:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.948
X-Spam-Level: 
X-Spam-Status: No, score=-101.948 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mEb779DuCKZN for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 11:36:09 -0700 (PDT)
Received: from mail-vb0-x229.google.com (mail-vb0-x229.google.com [IPv6:2607:f8b0:400c:c02::229]) by ietfa.amsl.com (Postfix) with ESMTP id 69E1611E80FB for <ietf@ietf.org>; Wed, 24 Jul 2013 11:36:09 -0700 (PDT)
Received: by mail-vb0-f41.google.com with SMTP id g17so196904vbg.0 for <ietf@ietf.org>; Wed, 24 Jul 2013 11:36:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=ysmH5BFqCRGeLi36FhdMEmdTNl/WxtNidQOtBMIL66o=; b=GN4kN7nGcdE7+ycUVzDxDcijWuglEZKN9+MPPWUE6f7EG97JiJCxsplLTS6gnCoTOv bLmZUd5BS2cikb4es2rRM6O13nOqXPV6FzTNAa15flWAgFIdrZfM9GuDL3F/k9oQe7UM NVjBMtYwp7X5k7mqKap7MYIte+vtAmOWfkrN+3OHAkdEva8zKDPCbgQHm6hc5YJIUj7W YbvDa2O9RLAyWNKiXItJ4vJxZrc90qBwFPN7nDDPcMTUaR9O8jtC7MBzpasrScYYbIFu PTY+duS8Ip97qx5VLw0WET605hhkFlXNT7/TFZUSp9438U3mggGy0GGuyiqFZLDdg1fi zsrA==
MIME-Version: 1.0
X-Received: by 10.58.211.7 with SMTP id my7mr15283363vec.54.1374690967638; Wed, 24 Jul 2013 11:36:07 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.137.227 with HTTP; Wed, 24 Jul 2013 11:36:07 -0700 (PDT)
In-Reply-To: <4402A8BCBCF8C54CF188B4AA@JcK-HP8200.jck.com>
References: <A6B9C627-A141-416B-AB39-469FDA86A875@ietf.org> <2129CC69EEF207CADC2421AC@JcK-HP8200.jck.com> <CC160C56-5D74-4309-AD3D-FB88FEB60B01@piuha.net> <96F611AF0497CDC862CF30D4@JcK-HP8200.jck.com> <OF68BD4951.D37EA2D7-ON85257BB2.004EEDF0-85257BB2.004F4E5A@csc.com> <94EA01D5-C6BE-40B3-84C1-C707522627AB@piuha.net> <F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk> <EMEW3|07b43bbc00e6dd8decb147cb113c10dfp6NHk603tjc|ecs.soton.ac.uk|F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk> <4402A8BCBCF8C54CF188B4AA@JcK-HP8200.jck.com>
Date: Wed, 24 Jul 2013 14:36:07 -0400
X-Google-Sender-Auth: gB2ohiQOxD3kSqLDNnvC9cyting
Message-ID: <CAC4RtVCyN4QCzCepdw2fqwwGFOsve9Zdy+K-a7UPtYvetZhVSw@mail.gmail.com>
Subject: Re: Remote participants access to Meeting Mailing Lists was Re: BOF posters in the welcome reception
From: Barry Leiba <barryleiba@computer.org>
To: John C Klensin <john-ietf@jck.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Jul 2013 18:36:10 -0000

> Unfortunately 87all@ietf.org --the "announce" version of the
> list-- is where the really important things, like schedule
> changes, show up.  And, at least as far as I can tell, there is
> no way for a non-registrant to get on that list.

Has anyone tried to subscribe on the listinfo page?:
https://www.ietf.org/mailman/listinfo/87all

I just did, using another email address, and that email address got
the normal "click here to confirm" response.

Barry

From ajs@anvilwalrusden.com  Wed Jul 24 11:54:25 2013
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6272211E8144 for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 11:54:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.84
X-Spam-Level: 
X-Spam-Status: No, score=-0.84 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6+GbFq4Y+cvA for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 11:54:14 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id CF8AB11E8215 for <ietf@ietf.org>; Wed, 24 Jul 2013 11:54:10 -0700 (PDT)
Received: from mx1.yitter.info (c-75-69-155-67.hsd1.nh.comcast.net [75.69.155.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id B71C48A031 for <ietf@ietf.org>; Wed, 24 Jul 2013 18:54:08 +0000 (UTC)
Date: Wed, 24 Jul 2013 14:54:07 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Remote participants access to Meeting Mailing Lists was Re: BOF posters in the welcome reception
Message-ID: <20130724185407.GK43220@mx1.yitter.info>
References: <A6B9C627-A141-416B-AB39-469FDA86A875@ietf.org> <2129CC69EEF207CADC2421AC@JcK-HP8200.jck.com> <CC160C56-5D74-4309-AD3D-FB88FEB60B01@piuha.net> <96F611AF0497CDC862CF30D4@JcK-HP8200.jck.com> <OF68BD4951.D37EA2D7-ON85257BB2.004EEDF0-85257BB2.004F4E5A@csc.com> <94EA01D5-C6BE-40B3-84C1-C707522627AB@piuha.net> <F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk> <EMEW3|07b43bbc00e6dd8decb147cb113c10dfp6NHk603tjc|ecs.soton.ac.uk|F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk> <4402A8BCBCF8C54CF188B4AA@JcK-HP8200.jck.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4402A8BCBCF8C54CF188B4AA@JcK-HP8200.jck.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Jul 2013 18:54:27 -0000

On Wed, Jul 24, 2013 at 02:26:21PM -0400, John C Klensin wrote:
> Unfortunately 87all@ietf.org --the "announce" version of the
> list-- is where the really important things, like schedule
> changes, show up.  And, at least as far as I can tell, there is
> no way for a non-registrant to get on that list.

This could be solved by the simple expedient of creating an additional
class of attendee, "remote".  We already have classes.  This would
also get remoters on the registration list, which would be an
additional benefit.  It'd probably need an additional field in display
[Remote Y/N] of participants, though.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From sm@resistor.net  Wed Jul 24 12:50:36 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D16711E8105; Wed, 24 Jul 2013 12:50:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sqj3vnPQEHas; Wed, 24 Jul 2013 12:50:29 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 00A3111E80A2; Wed, 24 Jul 2013 12:50:25 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r6OJoJ5r011022; Wed, 24 Jul 2013 12:50:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1374695424; bh=zPjBDaCu4Dhvdhone/Ke1/oo4E7x2u/LUZAF1oeL8+k=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Uhl4kaf/4eo9SSShTJ8F/uxxAq27Ge/IW7UZFNmVedN6qx0JdLd+HFELy5R4JDfuX +8VaI1r9GXj+lN8Tjl1cGEm4KvedudJ0L63mXCFLnJN9hRyHcQ26h2JhW7q8kjchyq fRVBXTtRmvrLxvaiFnuHfkaAA1e7RdosRD6+uvzs=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1374695424; i=@resistor.net; bh=zPjBDaCu4Dhvdhone/Ke1/oo4E7x2u/LUZAF1oeL8+k=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=N5o5kxNhpphUk1O1/M+cTlQQSVzaOl8awyge6q95EZjzJk5wYQUWWAjCPGG9bLJRr eLPQMnJmHTKpDc8bNLwzU9DH5IaNkC5FxCz8Zp6/Xy2AUrYZuUmyVMGn1yoYvYYV6q 33oxyukhERNJ4uc51kNXsHLG0e2o5/U2gRGQi6pk=
Message-Id: <6.2.5.6.2.20130724111528.0d2bf428@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 24 Jul 2013 12:21:24 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-weirds-rdap-sec-04.txt> (Security Services for the Registration Data Access Protocol) to Proposed Standard
In-Reply-To: <20130715230614.25146.34230.idtracker@ietfa.amsl.com>
References: <20130715230614.25146.34230.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: weirds@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Jul 2013 19:50:37 -0000

At 16:06 15-07-2013, The IESG wrote:
>The IESG has received a request from the Web Extensible Internet
>Registration Data Service WG (weirds) to consider the following document:
>- 'Security Services for the Registration Data Access Protocol'
>   <draft-ietf-weirds-rdap-sec-04.txt> as Proposed Standard
>
>The IESG plans to make a decision in the next few weeks, and solicits
>final comments on this action. Please send substantive comments to the
>ietf@ietf.org mailing lists by 2013-07-29. Exceptionally, comments may be

According to Section 1, the Registration Data Access Protocol is a 
Lookup Format,
JSON Responses and HTTP usage.  This looks like a weird protocol to 
me.  If the said protocol is HTTP + JSON (responses) it would be 
clearer to the reader to explain that in one specification.  Section 
1 mentions that:

   "One goal of RDAP is to provide security services that do not exist in
    the WHOIS"

I don't see how adding a fourth document helps to achieve that goal.

In Section 3.1:

   'To that end, RDAP clients and servers MUST implement the
    authentication framework specified in "HTTP Authentication:
    Basic and Digest Access Authentication" [RFC2617].'

This draft refers to the above authentication framework as the RDAP 
authentication framework.  The draft then explains how the "basic" 
and "digest" schemes work.  This is "how-to" stuff.  The draft sets 
the following requirement:

   'If the "basic" scheme is used, HTTP Over TLS [RFC2818] MUST be used
    to protect the client's credentials from disclosure while in transit
   (see Section 3.4).'

If I understood correctly HTTPS is needed for security only if the 
"basic" scheme" is used.

   "RDAP SHOULD be capable of supporting future authentication methods
    defined for use with HTTP."

That sounds like a "SHOULD CONSIDER".  Given how ill-defined the 
protocol is I doubt that the above is actionable.

In Section 3.1.1:

   "RDAP MAY include a federated authentication mechanism that permits
    a client to access multiple RDAP servers in the same federation
    with one credential."

Using an upper-case "may" does not bring much in terms of 
security.  The draft takes the stance that security is an optional feature.

Section 3.1.1 looks like an executive summary for federated authentication.

In Section 3.3:

   "An RDAP service has to be available to be useful.  There are no RDAP-
    unique requirements to provide availability, but as a general
    security consideration a service operator needs to be aware of the
    issues associated with denial of service."

The text says that the service must be available to be useful and 
that there isn't any requirement for the service to be available.

In Section 3.4:

   "Web services such as RDAP commonly use HTTP Over TLS [RFC2818] to
    provide that protection by encrypting all traffic sent on the
    connection between client and server."

The above describes the protocol as a web service.

   "When this scheme is used, HTTP Over TLS MUST be used to protect the
    client's credentials from disclosure while in transit.'

The above repeats a "MUST" mentioned in a previous section.

In Section 5:

   "RDAP might need to be extended to provide this service in the future."

This does not look like a security consideration.

   "Code injection refers to adding code into a computer system
    or program to alter the course of execution."

I can only wonder about who is the target audience after reading the above.

The security considerations section seems like an attempt to write 
something about security as there isn't nothing to say about the protocol.

Overall, the draft does not look like a technical specification.  It 
looks like the working group took FYI 36 as a template for designing 
a security service instead of thinking about security and designing a 
security service.

Regards,
-sm 


From brian.e.carpenter@gmail.com  Wed Jul 24 12:56:15 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC6B611E80A2 for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 12:56:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.574
X-Spam-Level: 
X-Spam-Status: No, score=-102.574 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uHuV829cOSAJ for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 12:56:15 -0700 (PDT)
Received: from mail-pa0-x236.google.com (mail-pa0-x236.google.com [IPv6:2607:f8b0:400e:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id 3B51C21F847C for <ietf@ietf.org>; Wed, 24 Jul 2013 12:56:15 -0700 (PDT)
Received: by mail-pa0-f54.google.com with SMTP id kx1so784771pab.41 for <ietf@ietf.org>; Wed, 24 Jul 2013 12:56:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=ZyFCqoBLpVfipoYA96WNz3niisp2zRa5GZvtjAeQoFM=; b=v425rCM31xNa81itFs8D1sARAgLXsNxQYCfjjnB4sTcmSIn6f5O+e9lEq3DINyNFWv /yICWXtHgl/DvKg86M1ylwEiUOMMtmjdbp6XpAAYg0BjklXtjCgx6/2edKioAeCdrCxw 8NmotVlMTKtgLnUzGKpflN4uc7tWZmlIs8z8jd2YQ/rqdkg2l0wtvVFMrn7lGICDmpXU HOpipW2wHA3Mym4cfuXe9vF9siesuUszYdMY9joljgDAkVxEhnS5wxrt67v5zj34su+R VObQOQzUqAgzzTFQSX+R2Ttto2xCZODE8uV2FRKYZ+SJcBYamTPQqLDkABwvdjlGnY3J HL0g==
X-Received: by 10.68.211.233 with SMTP id nf9mr41454536pbc.26.1374695774836; Wed, 24 Jul 2013 12:56:14 -0700 (PDT)
Received: from [192.168.178.23] (16.197.69.111.dynamic.snap.net.nz. [111.69.197.16]) by mx.google.com with ESMTPSA id zv11sm53231728pab.3.2013.07.24.12.56.12 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 24 Jul 2013 12:56:14 -0700 (PDT)
Message-ID: <51F0315D.4050307@gmail.com>
Date: Thu, 25 Jul 2013 07:56:13 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: Remote participants access to Meeting Mailing Lists was Re: BOF posters in the welcome reception
References: <A6B9C627-A141-416B-AB39-469FDA86A875@ietf.org>	<2129CC69EEF207CADC2421AC@JcK-HP8200.jck.com>	<CC160C56-5D74-4309-AD3D-FB88FEB60B01@piuha.net>	<96F611AF0497CDC862CF30D4@JcK-HP8200.jck.com>	<OF68BD4951.D37EA2D7-ON85257BB2.004EEDF0-85257BB2.004F4E5A@csc.com>	<F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk>	<94EA01D5-C6BE-40B3-84C1-C707522627AB@piuha.net>	<EMEW3|07b43bbc00e6dd8decb147cb113c10dfp6NHk603tjc|ecs.soton.ac.uk|F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk> <CAPv4CP-L1VCV4__f=EAXan-odWhV6Qo=QoMBOPUOS1R1F0NhPA@mail.gmail.com>
In-Reply-To: <CAPv4CP-L1VCV4__f=EAXan-odWhV6Qo=QoMBOPUOS1R1F0NhPA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: John C Klensin <john-ietf@jck.com>, Tim Chown <tjc@ecs.soton.ac.uk>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Jul 2013 19:56:15 -0000

On 25/07/2013 05:01, Scott Brim wrote:
> The point of having a separate list for participants was to avoid
> spamming the ietf list.
> 
> It can be open to everyone to subscribe to, since anyone can see the
> archives, HOWEVER I recommend that only registered participants be
> allowed to post.

Ahem. Either remote participants are allowed to post, or they need
a list of their own. I would envisage a fair amount of chatter about
specific remote-participation issues, like "this new codec isn't
working for me, is it OK for anyone else using <browser version> on
<operating system version>?"

  Brian

From Ted.Lemon@nominum.com  Wed Jul 24 12:59:05 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7B5711E821E for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 12:59:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yprxM0W9CxSl for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 12:58:57 -0700 (PDT)
Received: from exprod7og114.obsmtp.com (exprod7og114.obsmtp.com [64.18.2.215]) by ietfa.amsl.com (Postfix) with ESMTP id B3F2011E80AD for <ietf@ietf.org>; Wed, 24 Jul 2013 12:58:57 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob114.postini.com ([64.18.6.12]) with SMTP ID DSNKUfAyAUGe5vQrKTA+x3atm+yZD1el069F@postini.com; Wed, 24 Jul 2013 12:58:57 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 1BBF41B8274 for <ietf@ietf.org>; Wed, 24 Jul 2013 12:58:57 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id C33D1190068; Wed, 24 Jul 2013 12:58:55 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Wed, 24 Jul 2013 12:58:55 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Remote participants access to Meeting Mailing Lists was Re: BOF posters in the welcome reception
Thread-Topic: Remote participants access to Meeting Mailing Lists was Re: BOF	posters in the welcome reception
Thread-Index: AQHOiHnrm7T9e+LzG0Kw5vPCutzbUJl0ZpAAgAAYZACAAAQ8gIAAMOeAgAAAwAA=
Date: Wed, 24 Jul 2013 19:58:54 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775222FF9@mbx-01.win.nominum.com>
References: <A6B9C627-A141-416B-AB39-469FDA86A875@ietf.org> <2129CC69EEF207CADC2421AC@JcK-HP8200.jck.com> <CC160C56-5D74-4309-AD3D-FB88FEB60B01@piuha.net> <96F611AF0497CDC862CF30D4@JcK-HP8200.jck.com> <OF68BD4951.D37EA2D7-ON85257BB2.004EEDF0-85257BB2.004F4E5A@csc.com> <F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk> <94EA01D5-C6BE-40B3-84C1-C707522627AB@piuha.net> <EMEW3|07b43bbc00e6dd8decb147cb113c10dfp6NHk603tjc|ecs.soton.ac.uk|F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk> <CAPv4CP-L1VCV4__f=EAXan-odWhV6Qo=QoMBOPUOS1R1F0NhPA@mail.gmail.com> <51F0315D.4050307@gmail.com>
In-Reply-To: <51F0315D.4050307@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <37FA6B3E7EF7BB4CB5A748B9469E493D@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: John C Klensin <john-ietf@jck.com>, Tim Chown <tjc@ecs.soton.ac.uk>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Jul 2013 19:59:05 -0000

On Jul 24, 2013, at 3:56 PM, Brian E Carpenter <brian.e.carpenter@gmail.com=
> wrote:
> I would envisage a fair amount of chatter about
> specific remote-participation issues, like "this new codec isn't
> working for me, is it OK for anyone else using <browser version> on
> <operating system version>?"

We get that on the attendees list anyway sometimes, and I think it's probab=
ly not a bad thing, although I'm pretty sure there's an email address for g=
etting support of this type.


From christer.holmberg@ericsson.com  Wed Jul 24 13:55:12 2013
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE8AF11E824A for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 13:55:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.232
X-Spam-Level: 
X-Spam-Status: No, score=-6.232 tagged_above=-999 required=5 tests=[AWL=0.016,  BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SLTpxVvgb4QL for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 13:55:03 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id A3E8A11E80FF for <ietf@ietf.org>; Wed, 24 Jul 2013 13:54:57 -0700 (PDT)
X-AuditID: c1b4fb2d-b7f0b6d0000002d5-bd-51f03f205d86
Received: from ESESSHC009.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 92.33.00725.02F30F15; Wed, 24 Jul 2013 22:54:56 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.135]) by ESESSHC009.ericsson.se ([153.88.183.45]) with mapi id 14.02.0328.009; Wed, 24 Jul 2013 22:54:56 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Scott Brim <scott.brim@gmail.com>
Subject: Re: Remote participants access to Meeting Mailing Lists was Re: BOF posters in the welcome reception
Thread-Topic: Remote participants access to Meeting Mailing Lists was Re: BOF	posters in the welcome reception
Thread-Index: AQHOiHnxjNxMKPMHdEetb+wp6YvWvZlzz7AAgAAYZQCAAAQ7gIAAMOiAgAAx7io=
Date: Wed, 24 Jul 2013 20:54:55 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C408542@ESESSMB209.ericsson.se>
References: <A6B9C627-A141-416B-AB39-469FDA86A875@ietf.org> <2129CC69EEF207CADC2421AC@JcK-HP8200.jck.com> <CC160C56-5D74-4309-AD3D-FB88FEB60B01@piuha.net> <96F611AF0497CDC862CF30D4@JcK-HP8200.jck.com> <OF68BD4951.D37EA2D7-ON85257BB2.004EEDF0-85257BB2.004F4E5A@csc.com> <F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk> <94EA01D5-C6BE-40B3-84C1-C707522627AB@piuha.net> <EMEW3|07b43bbc00e6dd8decb147cb113c10dfp6NHk603tjc|ecs.soton.ac.uk|F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk> <CAPv4CP-L1VCV4__f=EAXan-odWhV6Qo=QoMBOPUOS1R1F0NhPA@mail.gmail.com>, <51F0315D.4050307@gmail.com>
In-Reply-To: <51F0315D.4050307@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1C408542ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrPLMWRmVeSWpSXmKPExsUyM+Jvra6C/YdAgztvNS3aLu5jsni2cT6L ReulP2wW73YcZrM4tOc5mwOrx991rh47Z91l91iy5CeTx+WVr5kDWKK4bFJSczLLUov07RK4 Mn61PmIsuKtW8XEpewPjYsUuRk4OCQETiXNrehghbDGJC/fWs3UxcnEICRxmlJi24wMrSEJI YAmjxNN1mV2MHBxsAhYS3f+0QcIiAhESh5c8YAGxmQVyJY73T2cCsYUF8iX2//7OAlFTIHHl wGV2CNtPYv73TrAaFgFViceLLoLt5RXwlXjXNpkdYu99FonzP4+BJTgFNCUeNm1jA7EZgY77 fmoNE8QycYlbT+YzQRwtILFkz3lmCFtU4uXjf6wQNfkSZ9fPYoFYIChxcuYTlgmMIrOQtM9C UjYLSRlEXEdiwe5PbBC2tsSyha+ZYewzBx4zIYsvYGRfxciem5iZk15uuIkRGGkHt/zW3cF4 6pzIIUZpDhYlcd5NemcChQTSE0tSs1NTC1KL4otKc1KLDzEycXBKNTBKKLLp8G4vfSgwjflv X+j1MnmDPdw7wyxnPXgme3fqFamvCbFXJ39Z9EH/dMXasOehuu0rLyjWsyyzXFWzcXqnR8Jb vh82s8LtM99IP3W9alPWaNbyUiU5fvHLLzXs/Sku8a+9Ux9O+PX1ls/2S5XSW8KY0l4ouZ7Y +jVl0e/IaW89j/P8/3JEiaU4I9FQi7moOBEA79rakoICAAA=
Cc: John C Klensin <john-ietf@jck.com>, Tim Chown <tjc@ecs.soton.ac.uk>, "ietf_ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Jul 2013 20:55:13 -0000

--_000_7594FB04B1934943A5C02806D1A2204B1C408542ESESSMB209erics_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

Why couldn't remote participants register to the meeting like all other par=
ticipants?

Remote participation would of course still be free, but it would allow remo=
te participants to subscribe to the attendee list in the same way as other =
participants.

In addition, it would provide better knowledge to IETF about the number of =
remote participants, where they are physically located (which might be usef=
ul input when planning future meeting locations) etc.

Regards,

Christer



Sent from Windows using TouchDown (www.nitrodesk.com)

-----Original Message-----
From: Brian E Carpenter [brian.e.carpenter@gmail.com]
To: Scott Brim [scott.brim@gmail.com]
CC: John C Klensin [john-ietf@jck.com]; Tim Chown [tjc@ecs.soton.ac.uk]; ie=
tf@ietf.org list [ietf@ietf.org]
Subject: Re: Remote participants access to Meeting Mailing Lists was Re: BO=
F posters in the welcome reception
On 25/07/2013 05:01, Scott Brim wrote:
> The point of having a separate list for participants was to avoid
> spamming the ietf list.
>
> It can be open to everyone to subscribe to, since anyone can see the
> archives, HOWEVER I recommend that only registered participants be
> allowed to post.

Ahem. Either remote participants are allowed to post, or they need
a list of their own. I would envisage a fair amount of chatter about
specific remote-participation issues, like "this new codec isn't
working for me, is it OK for anyone else using <browser version> on
<operating system version>?"

  Brian

--_000_7594FB04B1934943A5C02806D1A2204B1C408542ESESSMB209erics_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; pad=
ding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div style=3D"font-family:Calibri,Arial,Helvetica,sans-serif; font-size:11p=
t; color:black">
<div><span style=3D"color:black; font-family:Calibri,Arial,Helvetica,sans-s=
erif; font-size:11pt">Hi,</span></div>
<div>&nbsp;</div>
<div><font face=3D"Calibri">Why couldn't</font><font face=3D"Calibri">&nbsp=
;remote participants register to the meeting like all other participants?</=
font></div>
<div><font face=3D"Calibri"></font>&nbsp;</div>
<div><font face=3D"Calibri">Remote participation would of course still be f=
ree, but it would allow remote participants to subscribe to the attendee li=
st in the same way as other participants.
</font></div>
<div><font face=3D"Calibri"></font>&nbsp;</div>
<div><font face=3D"Calibri">In addition, it would provide better knowledge =
to IETF about the number of remote participants, where they are physically =
located (which might be useful input when planning future meeting locations=
) etc.</font></div>
<div><font face=3D"Calibri"></font>&nbsp;</div>
<div><font face=3D"Calibri">Regards,</font></div>
<div><font face=3D"Calibri"></font>&nbsp;</div>
<div><font face=3D"Calibri">Christer</font></div>
<span style=3D"color:black; font-family:Calibri,Arial,Helvetica,sans-serif;=
 font-size:11pt">
<div>&nbsp;</div>
<div><br>
<br>
Sent from <b><i>Windows</i></b> using <b style=3D"color:blue">TouchDown</b>=
 (www.nitrodesk.com)</div>
</span>
<div></div>
<br>
<span style=3D"color:black">-----Original Message-----<br>
<b>From:</b> Brian E Carpenter [brian.e.carpenter@gmail.com]<br>
<b>To:</b> Scott Brim [scott.brim@gmail.com]<br>
<b>CC:</b> John C Klensin [john-ietf@jck.com]; Tim Chown [tjc@ecs.soton.ac.=
uk]; ietf@ietf.org list [ietf@ietf.org]<br>
<b>Subject:</b> Re: Remote participants access to Meeting Mailing Lists was=
 Re: BOF posters in the welcome reception</span></div>
<font size=3D"2"><span style=3D"font-size:10pt;">
<div class=3D"PlainText">On 25/07/2013 05:01, Scott Brim wrote:<br>
&gt; The point of having a separate list for participants was to avoid<br>
&gt; spamming the ietf list.<br>
&gt; <br>
&gt; It can be open to everyone to subscribe to, since anyone can see the<b=
r>
&gt; archives, HOWEVER I recommend that only registered participants be<br>
&gt; allowed to post.<br>
<br>
Ahem. Either remote participants are allowed to post, or they need<br>
a list of their own. I would envisage a fair amount of chatter about<br>
specific remote-participation issues, like &quot;this new codec isn't<br>
working for me, is it OK for anyone else using &lt;browser version&gt; on<b=
r>
&lt;operating system version&gt;?&quot;<br>
<br>
&nbsp; Brian<br>
</div>
</span></font>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1C408542ESESSMB209erics_--

From yding@cs.helsinki.fi  Wed Jul 24 14:59:23 2013
Return-Path: <yding@cs.helsinki.fi>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28DC711E80E1 for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 14:59:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.998
X-Spam-Level: 
X-Spam-Status: No, score=-5.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_84=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vOr8Y-nAnkCH for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 14:59:15 -0700 (PDT)
Received: from courier.cs.helsinki.fi (courier.cs.helsinki.fi [128.214.9.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6BF211E8145 for <ietf@ietf.org>; Wed, 24 Jul 2013 14:59:14 -0700 (PDT)
X-DKIM: Courier DKIM Filter v0.50+pk-2013-06-17 courier.cs.helsinki.fi Thu Jul 25 00:58:58 2013
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cs.helsinki.fi; h=message-id:date:from:mime-version:to:cc:subject:references :in-reply-to:content-type; s=dkim20130528; bh=JaU7uWOrzFRU/MVVVK 3ESUmWryFWQDdiYNDgcWLUzkM=; b=csGVvdEVeBGtccKLZGjOO+v06Jtjia4xT7 VI3bHfoQZUlCRh5seII+tQWtlV1VuaqoCH3c2N8c5YockQa6JkH8pgZ2PR2G2N6/ LoON1/U3frZDEexWDTfAABLXeK0F2SFfwSI/XmbjBmNQMyjsFtcRR3x9DODQG+Xj HAlgnwXNs=
Received: from [131.111.218.40] (s218i40.wolfson.cam.ac.uk [131.111.218.40]) (AUTH: PLAIN yding, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by mail.cs.helsinki.fi with esmtp; Thu, 25 Jul 2013 00:58:58 +0300 id 00068B63.51F04E22.00005F24
Message-ID: <51F04E21.9050904@cs.helsinki.fi>
Date: Wed, 24 Jul 2013 22:58:57 +0100
From: Aaron Yi DING <yding@cs.helsinki.fi>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>, Jari Arkko <jari.arkko@piuha.net>
Subject: Re: BOF posters in the welcome reception
References: <A6B9C627-A141-416B-AB39-469FDA86A875@ietf.org> <2129CC69EEF207CADC2421AC@JcK-HP8200.jck.com> <CC160C56-5D74-4309-AD3D-FB88FEB60B01@piuha.net> <96F611AF0497CDC862CF30D4@JcK-HP8200.jck.com>
In-Reply-To: <96F611AF0497CDC862CF30D4@JcK-HP8200.jck.com>
Content-Type: multipart/alternative; boundary="------------050205030006040202000501"
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Jul 2013 21:59:23 -0000

This is a multi-part message in MIME format.
--------------050205030006040202000501
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 24/07/13 09:30, John C Klensin wrote:
>
> --On Wednesday, July 24, 2013 11:17 +0300 Jari Arkko
> <jari.arkko@piuha.net> wrote:
>
>>> And, incidentally, is there a way for remote participants to
>>> sign up for one or both meeting-related mailing lists without
>>> registering (or using a "remote participation registration"
>>> mechanism, which would be my preference for other reasons)?
>> I sent the mail to ietf-announce, so I would guess many
>> non-attendees got it as well.
> Yes.  I was thinking a bit more generally.  For example,
> schedule changes during the meeting week, IIR, go to NNall, and
> not ietf-announce.   As a remote participant, one might prefer
> to avoid the usual (and interminable) discussions about coffee
> shops, weather, and the diameter of the cookies, but it seems to
> me that there is a good deal of material that goes to the two
> meeting lists that would be of use.  Since I'm on those lists in
> spite of being remote (registered and then cancelled), I can try
> to keep track of whether anything significant to remote
> participants appears on the meeting discuss list this time if it
> would help.


One thing that may also benefit both Remote and Meeting participants:

An anchor point to distribute live update about IETF week, e.g., 
schedule change, latest bits-n-bytes info, WG/BoF agenda changes/slides 
uploaded(with embedded link), highlight/awards at plenary, emergent 
notice for facility issues/weather/traffic/hotel stealing...

Most of those could be found if digging hard enough from hundreds of 
mails during IETF week, but a quick link definitely helps.

It can be a "live update" bullet on the front page of IETF meeting
http://www.ietf.org/meeting/87/

Cheers,
Aaron


> best,
>     john
>
>
>
>


--------------050205030006040202000501
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 text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">On 24/07/13 09:30, John C Klensin
      wrote:<br>
    </div>
    <blockquote cite="mid:96F611AF0497CDC862CF30D4@JcK-HP8200.jck.com"
      type="cite">
      <pre wrap="">

--On Wednesday, July 24, 2013 11:17 +0300 Jari Arkko
<a class="moz-txt-link-rfc2396E" href="mailto:jari.arkko@piuha.net">&lt;jari.arkko@piuha.net&gt;</a> wrote:

</pre>
      <blockquote type="cite">
        <blockquote type="cite">
          <pre wrap="">And, incidentally, is there a way for remote participants to
sign up for one or both meeting-related mailing lists without
registering (or using a "remote participation registration"
mechanism, which would be my preference for other reasons)?
</pre>
        </blockquote>
        <pre wrap="">
I sent the mail to ietf-announce, so I would guess many
non-attendees got it as well.
</pre>
      </blockquote>
      <pre wrap="">
Yes.  I was thinking a bit more generally.  For example,
schedule changes during the meeting week, IIR, go to NNall, and
not ietf-announce.   As a remote participant, one might prefer
to avoid the usual (and interminable) discussions about coffee
shops, weather, and the diameter of the cookies, but it seems to
me that there is a good deal of material that goes to the two
meeting lists that would be of use.  Since I'm on those lists in
spite of being remote (registered and then cancelled), I can try
to keep track of whether anything significant to remote
participants appears on the meeting discuss list this time if it
would help.
</pre>
    </blockquote>
    <br>
    <br>
    One thing that may also benefit both Remote and Meeting
    participants: <br>
    <br>
    An anchor point to distribute live update about IETF week, e.g.,
    schedule change, latest bits-n-bytes info, WG/BoF agenda
    changes/slides uploaded(with embedded link), highlight/awards at
    plenary, emergent notice for facility issues/weather/traffic/hotel
    stealing...<br>
    <br>
    Most of those could be found if digging hard enough from hundreds of
    mails during IETF week, but a quick link definitely helps.<br>
    <br>
    It can be a "live update" bullet on the front page of IETF meeting<br>
    <meta http-equiv="content-type" content="text/html;
      charset=ISO-8859-1">
    <a href="http://www.ietf.org/meeting/87/">http://www.ietf.org/meeting/87/</a><br>
    <br>
    Cheers,<br>
    Aaron<br>
    <br>
    &nbsp;<br>
    <blockquote cite="mid:96F611AF0497CDC862CF30D4@JcK-HP8200.jck.com"
      type="cite">
      <pre wrap="">
best,
   john




</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------050205030006040202000501--

From sm@resistor.net  Wed Jul 24 15:54:51 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CE6011E8158 for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 15:54:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uzEN8g1i+W3R for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 15:54:48 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 49BBC11E811E for <ietf@ietf.org>; Wed, 24 Jul 2013 15:54:41 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r6OMsSB2021570; Wed, 24 Jul 2013 15:54:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1374706473; bh=uRTsyP/qAgLQTK4IRGmSy8YebVgGV3NjugjtgtimzOE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=etCiKlaNE7Hp46HugdKg4/0qxM5c0XuFnbM0kW91S2hWJdT5NDgIsedM7I8XlWXI5 eCrLYVGePYiKrxbl/yPg4is9UHxn2JfpyIwVNnjmzAwtgsSNTvMgpZ7blRtm80ou+R BSnQLoukefjG0Z9u2tvzMz1egmYWjIl+hd6LlGdw=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1374706473; i=@resistor.net; bh=uRTsyP/qAgLQTK4IRGmSy8YebVgGV3NjugjtgtimzOE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=297b4f8ZOVwYe4r5NA7XL9XKrFbiun/dO2JX4Ys/VT5SsW398+3Rzbu9gY41ob1NK UAvVjvrhpOJIEgyNyN9mlAmHpWqmf8t8oodKfKfdzOYPF2yTCn6aGtYPnDZ56PB0Ai DPD4RTU4C8svCldaWwovo3t+368qsyLCmrG9CW8M=
Message-Id: <6.2.5.6.2.20130724144751.0b6eded0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 24 Jul 2013 15:54:26 -0700
To: Christer Holmberg <christer.holmberg@ericsson.com>
From: SM <sm@resistor.net>
Subject: Re: Remote participants access to Meeting Mailing Lists was Re: BOF posters in the welcome reception
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C408542@ESESSMB209.ericss on.se>
References: <A6B9C627-A141-416B-AB39-469FDA86A875@ietf.org> <2129CC69EEF207CADC2421AC@JcK-HP8200.jck.com> <CC160C56-5D74-4309-AD3D-FB88FEB60B01@piuha.net> <96F611AF0497CDC862CF30D4@JcK-HP8200.jck.com> <OF68BD4951.D37EA2D7-ON85257BB2.004EEDF0-85257BB2.004F4E5A@csc.com> <F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk> <94EA01D5-C6BE-40B3-84C1-C707522627AB@piuha.net> <EMEW3|07b43bbc00e6dd8decb147cb113c10dfp6NHk603tjc|ecs.soton.ac.uk|F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk> <CAPv4CP-L1VCV4__f=EAXan-odWhV6Qo=QoMBOPUOS1R1F0NhPA@mail.gmail.com> <51F0315D.4050307@gmail.com> <7594FB04B1934943A5C02806D1A2204B1C408542@ESESSMB209.ericsson.se>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Jul 2013 22:54:51 -0000

Hi Christer,
At 13:54 24-07-2013, Christer Holmberg wrote:
>Why couldn't remote participants register to the meeting like all 
>other participants?
>
>Remote participation would of course still be free, but it would 
>allow remote participants to subscribe to the attendee list in the 
>same way as other participants.

A quick scan of that list shows the following topics:

   - coffee, sims

   - mailing list for IETF women

and the following comment:

   "I'm not sure why I should be required to give my contact information to
    get a document prepared by the Brussels airport for Brussels passengers."

>In addition, it would provide better knowledge to IETF about the 
>number of remote participants, where they are physically located 
>(which might be useful input when planning future meeting locations) etc.

I doubt that the IETF chooses its meeting location based on where the 
remote participants are located.

I'll go off-topic first.  Mr Reschke once asked "I was just trying to 
understand *why* the archive can't be at 
<http://www.ietf.org/tao/archive>".  Mr Housley replied that "I was 
told that we cannot have http://www.ietf.org/tao directed to the 
document and also be the directory containing the archive 
directory".  Mr Hansen provided some technical details about how that 
can be done.  The point here is it might be better to have a good 
answer as some IETF participant might deconstruct the answer and find 
the flaw in it.

Mr Klensin's message was about how to find out about the 87all 
mailing list.  Participants within the inner circle know how to find 
it.  The rest of the participants will not be able to find that 
information as it is not easily accessible through the www.ietf.org 
web site.  There is probably a lack of information about what 
information is provided through the ietf-announce@ mailing list.

Regards,
-sm



From john-ietf@jck.com  Wed Jul 24 15:56:50 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8412F11E811B for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 15:56:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lPRw2foTUfkj for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 15:56:44 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 5745B11E814D for <ietf@ietf.org>; Wed, 24 Jul 2013 15:56:44 -0700 (PDT)
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 1V27z1-000666-I0; Wed, 24 Jul 2013 18:56:35 -0400
Date: Wed, 24 Jul 2013 18:56:30 -0400
From: John C Klensin <john-ietf@jck.com>
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: Remote participants access to Meeting Mailing Lists was Re: BOF posters in the welcome reception
Message-ID: <A267B1B422B975D55F9160D5@JcK-HP8200.jck.com>
In-Reply-To: <CAC4RtVCyN4QCzCepdw2fqwwGFOsve9Zdy+K-a7UPtYvetZhVSw@mail.gmail.com>
References: <A6B9C627-A141-416B-AB39-469FDA86A875@ietf.org> <2129CC69EEF207CADC2421AC@JcK-HP8200.jck.com> <CC160C56-5D74-4309-AD3D-FB88FEB60B01@piuha.net> <96F611AF0497CDC862CF30D4@JcK-HP8200.jck.com> <OF68BD4951.D37EA2D7-ON85257BB2.004EEDF0-85257BB2.004F4E5A@csc.com> <94EA01D5-C6BE-40B3-84C1-C707522627AB@piuha.net> <F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk> <EMEW3|07b43bbc00e6dd8decb147cb113c10dfp6NHk603tjc|ecs.soton.ac.uk|F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk> <4402A8BCBCF8C54CF188B4AA@JcK-HP8200.jck.com> <CAC4RtVCyN4QCzCepdw2fqwwGFOsve9Zdy+K-a7UPtYvetZhVSw@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: Tim Chown <tjc@ecs.soton.ac.uk>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Jul 2013 22:56:50 -0000

--On Wednesday, July 24, 2013 14:36 -0400 Barry Leiba
<barryleiba@computer.org> wrote:

>> Unfortunately 87all@ietf.org --the "announce" version of the
>> list-- is where the really important things, like schedule
>> changes, show up.  And, at least as far as I can tell, there
>> is no way for a non-registrant to get on that list.
> 
> Has anyone tried to subscribe on the listinfo page?:
> https://www.ietf.org/mailman/listinfo/87all
> 
> I just did, using another email address, and that email
> address got the normal "click here to confirm" response.

Barry,

I'm sorry to be difficult about this, but the point I was trying
to make was about access by relatively remote relative
newcomers.  For them, at least, the question is not "does the
listinfo page work if one can find it or guess at its URL".
Instead, suppose such a person goes looking with reasonable
knowledge of the information on the IETF home page, the meeting
main page, and perhaps even the Tao and previous Newcomer's
Introduction slides.

So, first she goes to the Meetings page for this meeting
(http://www.ietf.org/meeting/87/index.html).   Seems like
"Meeting Communication" would be a reasonable place to look,
and, lo, there is a "Mailing Lists" entry there.  It points to
87attendees (plus runners, companions, and food links).   Dead
end.

So, back to the mail IETF page and the "Mailing Lists" entry and
its links.  87all is an "Announcement List", but that page
http://www.ietf.org/list/announcement.html) discusses only
IETF-Announce, I-D-Announce, and IPR-Announce plus the IESG
Agenda Distribution.  No joy.  If this lucky newcomer figures
out that it is not a discussion list, she skips the Discussion
List link (http://www.ietf.org/list/discussion.html) but all
that is there is another link to
http://www.ietf.org/meeting/email-list.html and hence
information about 87attendees, etc.  Not a hint so far that
87all even exists.

So her (most IETF-type men would have run out of patience by
now) adventure then takes her to the Non-WG Lists page
(http://www.ietf.org/list/nonwg.html).  It starts out by
assuring the reader that, if the list exists, it will be listed
(or at least that is how I would interpret "attempts to list all
the active, publicly visible lists that are considered to be
related to the IETF, but are not the main list of any working
group, in alphabetical order by list name." as a rather strong
indicate that 87all and 87announce ought to be listed there:
they are certainly active and publicly visible and it would be
hard to claim that they are not "relate to the IETF".  No joy...
neither list appears there.

If we are serious about remote participants, that list should be
known, advertised, and accessible unless it really isn't used
for anything but local logistical information (as Joel
suggests).  But it didn't take me long to find examples of
announcements there (and apparently nowhere else) that would be
of interest to remote participants.   Examples:

* At IETF 86, the Thursday Lunchtime Panel was announced there
and apparently nowhere else
(http://www.ietf.org/mail-archive/web/86all/current/msg00033.html).
I don't know if it was made available to remove participants or
not but, if it wasn't and I were a remote participant with
significant interest in the subject matter, I'd want to know
about the presentation and have ample time to ask that
appropriate arrangements be made.

* I also found an agenda change announcement
(http://www.ietf.org/mail-archive/web/86all/current/msg00031.html)
that was apparently posted only there.  This one might not count
if the change was made before the meeting started.  

* However, if I go back a few more meetings, I find
http://www.ietf.org/mail-archive/web/84all/current/msg00010.html,
which is a meeting room change. And meeting room changes affect
audiocasts.  Wanda's note about the web agenda is relevant, but
our hypothetical newcomer isn't given that warning on the
meeting page or, since she has been unable to subscribe to
NNall, the announcements there.

Recommendations, with some comment about things that aren't
rocket science included by reference:

(1) Put 87all and 87attendees on the Non-WG mailing list page.
Or, perhaps better yet, mention there (as well as on the main
discussion list page) that there are meeting-specific lists and
include a link to the "Meeting Email Lists page".  It couldn't
hurt and might help.

(2) Modify the meeting email lists page to discuss NNall as well
as NNattendees and explain what it is for and that, while there
will be some local logistics (maybe mostly local logistics),
remote participants should probably keep an eye on it as well as
ietf-announce.

(3) While it is almost certainly too late to populate it before
Berlin, I think the meeting page template could use a "Remote
Participants" main section with pointers to hints and other
relevant materials, including which mailing lists one should
watch and that the web version of the meeting agenda should be
refreshed at least daily.  Wouldn't hurt to repeat the
instructions about what to do if the feeds go bad there either.

FWIW, I believe that doing the above would consume less net
energy than has already been spent explaining why we don't need
to do anything :-(

   john

p.s. While my reasons for not being in Berlin didn't include
examining our remote participation arrangements in practice, I
think it is going to be educational, at least for me.







From barryleiba@gmail.com  Wed Jul 24 16:04:41 2013
Return-Path: <barryleiba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F36911E8123 for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 16:04:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.959
X-Spam-Level: 
X-Spam-Status: No, score=-101.959 tagged_above=-999 required=5 tests=[AWL=0.018, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pPVwDPq-Eynb for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 16:04:41 -0700 (PDT)
Received: from mail-qa0-x235.google.com (mail-qa0-x235.google.com [IPv6:2607:f8b0:400d:c00::235]) by ietfa.amsl.com (Postfix) with ESMTP id D28F911E811E for <ietf@ietf.org>; Wed, 24 Jul 2013 16:04:40 -0700 (PDT)
Received: by mail-qa0-f53.google.com with SMTP id hu14so249358qab.5 for <ietf@ietf.org>; Wed, 24 Jul 2013 16:04:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=7rAwk0sYbsHhE7x44h7f2GzLsbWFUTnGUHW+q34t5Ts=; b=wabWvp2hFwdG9ypESj7Y3A5rJW0iXPpWdLTUDtrCFvmmD+EzgwtzKzFIl4BEvsYVrA VJluZv8xp6Ykz+zKLG0gvMoKC5nHJamCz/44kLa99sGLYqXiTnuyZsS+2wNYq/5mtq7O xlhxF/AS1a5H+Xiq8XAe0deMlzcysvwY+mJVEKopeMTvsM/58BAhvjxYdi0PYlzttxri fk1ro432ZiQJVWiHEoysjnLulAhFSyWeOaVNYq6qaFuc4lDFjpP7Xx5wgVDzvILjqL37 Bw3HTBcLQdUmuBeatL3K9dhLDcVdPxK55n/6I5TSsjUeYudKE0BHwf/5tRjU1podLBuz scSg==
MIME-Version: 1.0
X-Received: by 10.224.115.5 with SMTP id g5mr47124647qaq.53.1374707075943; Wed, 24 Jul 2013 16:04:35 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.224.59.211 with HTTP; Wed, 24 Jul 2013 16:04:35 -0700 (PDT)
In-Reply-To: <A267B1B422B975D55F9160D5@JcK-HP8200.jck.com>
References: <A6B9C627-A141-416B-AB39-469FDA86A875@ietf.org> <2129CC69EEF207CADC2421AC@JcK-HP8200.jck.com> <CC160C56-5D74-4309-AD3D-FB88FEB60B01@piuha.net> <96F611AF0497CDC862CF30D4@JcK-HP8200.jck.com> <OF68BD4951.D37EA2D7-ON85257BB2.004EEDF0-85257BB2.004F4E5A@csc.com> <94EA01D5-C6BE-40B3-84C1-C707522627AB@piuha.net> <F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk> <EMEW3|07b43bbc00e6dd8decb147cb113c10dfp6NHk603tjc|ecs.soton.ac.uk|F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk> <4402A8BCBCF8C54CF188B4AA@JcK-HP8200.jck.com> <CAC4RtVCyN4QCzCepdw2fqwwGFOsve9Zdy+K-a7UPtYvetZhVSw@mail.gmail.com> <A267B1B422B975D55F9160D5@JcK-HP8200.jck.com>
Date: Wed, 24 Jul 2013 19:04:35 -0400
X-Google-Sender-Auth: 59YcXbc1v3ajPzK-fizWJqwf0WM
Message-ID: <CALaySJL82KLFa8F+Wtuskp48dUWS3XEYkyR5AK5S_4nZbnSV3w@mail.gmail.com>
Subject: Re: Remote participants access to Meeting Mailing Lists was Re: BOF posters in the welcome reception
From: Barry Leiba <barryleiba@computer.org>
To: John C Klensin <john-ietf@jck.com>
Content-Type: multipart/alternative; boundary=047d7bdc9514ee934704e249eea5
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Jul 2013 23:04:41 -0000

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

>> Has anyone tried to subscribe on the listinfo page?:
>> https://www.ietf.org/mailman/listinfo/87all
>
> I'm sorry to be difficult about this, but the point I was trying
> to make was about access by relatively remote relative
> newcomers.  For them, at least, the question is not "does the
> listinfo page work if one can find it or guess at its URL".

Of course I know that, and better advertising of the lists would be great.
 I was simply confirming for those who are reading that one CAN subscribe
without registering for the meeting.  That's all.

Barry

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

<font><span style=3D"line-height:normal;background-color:rgba(255,255,255,0=
)">&gt;&gt; Has anyone tried to subscribe on the listinfo page?:<br>&gt;&gt=
;=A0<a href=3D"https://www.ietf.org/mailman/listinfo/87all" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/87all</a><br>
&gt;<br>&gt;=A0I&#39;m sorry to be difficult about this, but the point I wa=
s trying<br>&gt;=A0to make was about access by relatively remote relative<b=
r>&gt;=A0newcomers. =A0For them, at least, the question is not &quot;does t=
he<br>
&gt;=A0listinfo page work if one can find it or guess at its URL&quot;.</sp=
an></font><div><font><span style=3D"line-height:normal;background-color:rgb=
a(255,255,255,0)"><br></span></font></div><div><font><span style=3D"line-he=
ight:normal;background-color:rgba(255,255,255,0)">Of course I know that, an=
d better advertising of the lists would be great. =A0I was simply confirmin=
g for those who are reading that one CAN subscribe without registering for =
the meeting. =A0That&#39;s all.</span></font></div>
<div><font><span style=3D"line-height:normal;background-color:rgba(255,255,=
255,0)"><br></span></font></div><div><font><span style=3D"line-height:norma=
l;background-color:rgba(255,255,255,0)">Barry<span></span></span></font></d=
iv>

--047d7bdc9514ee934704e249eea5--

From scott.brim@gmail.com  Wed Jul 24 16:27:06 2013
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC28621F860B for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 16:27:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tbfi2hZA274Q for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 16:27:06 -0700 (PDT)
Received: from mail-oa0-x234.google.com (mail-oa0-x234.google.com [IPv6:2607:f8b0:4003:c02::234]) by ietfa.amsl.com (Postfix) with ESMTP id 251E121F860A for <ietf@ietf.org>; Wed, 24 Jul 2013 16:27:05 -0700 (PDT)
Received: by mail-oa0-f52.google.com with SMTP id g12so2619507oah.11 for <ietf@ietf.org>; Wed, 24 Jul 2013 16:27:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=u1vEL8cQ1qA4i2AreT5TDeEaPJn3Kjtsrf6QZNuEjbM=; b=opXoJLALHwRuzYd26nJyIxpGjZP6hJXZmgheec50n73Y8HuJb403SkHiaODkMWpizN 71tZZNW2EjBs+tYaLqR464tqkikXcHULNFJfinbe3NY/DWjmhZ8MuXY3PmXfUNa6pwSm w9jGjw2JZJ79civj2+yYlkodybEicfy3ihUdz3uX2rbDI/PCDkwgWgSBtrT0LAhh2rx9 dO1t4BNLkGPdQBk46xzXEKD/iG3/uEIqftc0cwnZcPSEL8xSJrKx4u0/JDIPotdKeDBc IcwOfxtlpgp+Tx2mU7erHrJmsb1w+zibk2sEDM1462cnec3DXQoqUi3iqzFS3O/cNXul yKRQ==
MIME-Version: 1.0
X-Received: by 10.60.51.230 with SMTP id n6mr9859472oeo.54.1374708425621; Wed, 24 Jul 2013 16:27:05 -0700 (PDT)
Received: by 10.182.251.226 with HTTP; Wed, 24 Jul 2013 16:27:05 -0700 (PDT)
Received: by 10.182.251.226 with HTTP; Wed, 24 Jul 2013 16:27:05 -0700 (PDT)
In-Reply-To: <51F0315D.4050307@gmail.com>
References: <A6B9C627-A141-416B-AB39-469FDA86A875@ietf.org> <2129CC69EEF207CADC2421AC@JcK-HP8200.jck.com> <CC160C56-5D74-4309-AD3D-FB88FEB60B01@piuha.net> <96F611AF0497CDC862CF30D4@JcK-HP8200.jck.com> <OF68BD4951.D37EA2D7-ON85257BB2.004EEDF0-85257BB2.004F4E5A@csc.com> <F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk> <94EA01D5-C6BE-40B3-84C1-C707522627AB@piuha.net> <EMEW3|07b43bbc00e6dd8decb147cb113c10dfp6NHk603tjc|ecs.soton.ac.uk|F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk> <CAPv4CP-L1VCV4__f=EAXan-odWhV6Qo=QoMBOPUOS1R1F0NhPA@mail.gmail.com> <51F0315D.4050307@gmail.com>
Date: Wed, 24 Jul 2013 19:27:05 -0400
Message-ID: <CAPv4CP9b7V54JYYY2T96wG9DJXnCMSsOGiAZdKvGkEkp3Kykyw@mail.gmail.com>
Subject: Re: Remote participants access to Meeting Mailing Lists was Re: BOF posters in the welcome reception
From: Scott Brim <scott.brim@gmail.com>
To: Brian Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c30c7c61098a04e24a3fff
Cc: John C Klensin <john-ietf@jck.com>, Tim Chown <tjc@ecs.soton.ac.uk>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Jul 2013 23:27:06 -0000

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

Brian: yes but non-registered thus non-ifentifiable subscribers, spammers
etc don't.
On Jul 24, 2013 3:56 PM, "Brian E Carpenter" <brian.e.carpenter@gmail.com>
wrote:

> On 25/07/2013 05:01, Scott Brim wrote:
> > The point of having a separate list for participants was to avoid
> > spamming the ietf list.
> >
> > It can be open to everyone to subscribe to, since anyone can see the
> > archives, HOWEVER I recommend that only registered participants be
> > allowed to post.
>
> Ahem. Either remote participants are allowed to post, or they need
> a list of their own. I would envisage a fair amount of chatter about
> specific remote-participation issues, like "this new codec isn't
> working for me, is it OK for anyone else using <browser version> on
> <operating system version>?"
>
>   Brian
>

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

<p dir=3D"ltr">Brian: yes but non-registered thus non-ifentifiable subscrib=
ers, spammers etc don&#39;t. </p>
<div class=3D"gmail_quote">On Jul 24, 2013 3:56 PM, &quot;Brian E Carpenter=
&quot; &lt;<a href=3D"mailto:brian.e.carpenter@gmail.com">brian.e.carpenter=
@gmail.com</a>&gt; wrote:<br type=3D"attribution"><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex">
On 25/07/2013 05:01, Scott Brim wrote:<br>
&gt; The point of having a separate list for participants was to avoid<br>
&gt; spamming the ietf list.<br>
&gt;<br>
&gt; It can be open to everyone to subscribe to, since anyone can see the<b=
r>
&gt; archives, HOWEVER I recommend that only registered participants be<br>
&gt; allowed to post.<br>
<br>
Ahem. Either remote participants are allowed to post, or they need<br>
a list of their own. I would envisage a fair amount of chatter about<br>
specific remote-participation issues, like &quot;this new codec isn&#39;t<b=
r>
working for me, is it OK for anyone else using &lt;browser version&gt; on<b=
r>
&lt;operating system version&gt;?&quot;<br>
<br>
=A0 Brian<br>
</blockquote></div>

--001a11c30c7c61098a04e24a3fff--

From melinda.shore@gmail.com  Wed Jul 24 20:10:58 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C991321F98AD for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 20:10:58 -0700 (PDT)
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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eO+UNsKTnT0D for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 20:10:58 -0700 (PDT)
Received: from mail-pa0-x236.google.com (mail-pa0-x236.google.com [IPv6:2607:f8b0:400e:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id 6517B21F93D4 for <ietf@ietf.org>; Wed, 24 Jul 2013 20:10:58 -0700 (PDT)
Received: by mail-pa0-f54.google.com with SMTP id kx1so1159834pab.27 for <ietf@ietf.org>; Wed, 24 Jul 2013 20:10:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=Y1HCrLmxrdR/UJAjLHEJQwjcjRRlQ158vLytBkicBV0=; b=Wo3jjvoOYRFf6UpgFXH+WpAfig75HTizDToRMPDlxJIRAhf2udAHObCyvdsBZQB092 aYjQYRO3N4hXPsLRE4XF/0oLcIZWseXY1BA/1QgTxsNSKPC/9MC9x6z2FrM9ioRAPmp4 9ymW3HgxBXQelWGCHdZtkcHU38P4UgD136UZ9C6ryWmbw+8d6dxnBeUpr/rfRrIgoauH dtd0m/cjBqebG8bqQbrUOXOLhCLvd/5mqjIojVVSPIBJVIi/hX37b0XBnLooAMG1KfSQ lhFwG4URsIHj0I0IbdTU34OSEMut3cKv5ZRk0P+T953vYBEPWk4C3yObhQAnvPQrZQ1Y pn3Q==
X-Received: by 10.68.164.69 with SMTP id yo5mr45320859pbb.96.1374721858175; Wed, 24 Jul 2013 20:10:58 -0700 (PDT)
Received: from spandex.local (66-230-83-143-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.83.143]) by mx.google.com with ESMTPSA id sz3sm22751074pbc.5.2013.07.24.20.10.56 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 24 Jul 2013 20:10:57 -0700 (PDT)
Message-ID: <51F0973E.7070102@gmail.com>
Date: Wed, 24 Jul 2013 19:10:54 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Remote participants access to Meeting Mailing Lists	was Re: BOF posters in the welcome reception
References: <A6B9C627-A141-416B-AB39-469FDA86A875@ietf.org> <2129CC69EEF207CADC2421AC@JcK-HP8200.jck.com> <CC160C56-5D74-4309-AD3D-FB88FEB60B01@piuha.net> <96F611AF0497CDC862CF30D4@JcK-HP8200.jck.com> <OF68BD4951.D37EA2D7-ON85257BB2.004EEDF0-85257BB2.004F4E5A@csc.com> <94EA01D5-C6BE-40B3-84C1-C707522627AB@piuha.net> <F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk> <EMEW3|07b43bbc00e6dd8decb147cb113c10dfp6NHk603tjc|ecs.soton.ac.uk|F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk> <4402A8BCBCF8C54CF188B4AA@JcK-HP8200.jck.com> <48E1A67CB9CA044EADFEAB87D814BFF63FAC35@eusaamb104.ericsson.se>
In-Reply-To: <48E1A67CB9CA044EADFEAB87D814BFF63FAC35@eusaamb104.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Jul 2013 03:10:58 -0000

On 7/24/13 10:35 AM, Eric Gray wrote:
> These lists are not - AFAIK - intended for "meeting participation"
> anywhere near as much as they are for meeting logisitics.

My experience has been that they're for both, and while
I'll be a remote participant this time I've already
subscribed to the 87attendees list.

I don't think it's accurate to describe putting up a mailing
list to which people may or may not choose to subscribe as
"jumping through hoops," although I will say that I think
we should be "jumping through hoops" to enable broader
participation and to improve remote participation.

Melinda

From brian.e.carpenter@gmail.com  Wed Jul 24 21:12:14 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D335721F9A29 for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 21:12:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.58
X-Spam-Level: 
X-Spam-Status: No, score=-102.58 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bSnRQR5-eXZL for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 21:12:13 -0700 (PDT)
Received: from mail-pd0-x235.google.com (mail-pd0-x235.google.com [IPv6:2607:f8b0:400e:c02::235]) by ietfa.amsl.com (Postfix) with ESMTP id C505D21F8A67 for <ietf@ietf.org>; Wed, 24 Jul 2013 21:12:11 -0700 (PDT)
Received: by mail-pd0-f181.google.com with SMTP id g12so681468pdj.40 for <ietf@ietf.org>; Wed, 24 Jul 2013 21:12:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=6jsZYgxEa9AJXHyAXkUROpz3zQ3irPaOCs5+uSVWhm4=; b=wcmqsZO+W1agImLGUbYLUmq0YDJDmhszKzzb6zZ6NelKUmcWnS+ZTMfF/+tBbD2RW0 cOF62OFwmeo2hXlZ46JG8KO694n5X/6hP1mVrtZ/VnenSEcf9kZoNSCzKgP8j8pPtTf2 PzzR0/8eaQXIuJChCxG5Pq7bVRicvjUDTntNjotpae+LLJV83/+Mo7TYnoRvV/mNS783 bBspVefQjLHoObfGgZSWRY2V2Li8F9TmzEODnzuFO4hIbhJz+PIkSduZ3fkqJMdOggot HNi86IFvQIVAfD9UeEURvSZd9VQxUcinytaktqsYgyYs/x2R6e4thEGPtX8Pm2PllXKl wYyQ==
X-Received: by 10.66.156.100 with SMTP id wd4mr35611572pab.5.1374725529264; Wed, 24 Jul 2013 21:12:09 -0700 (PDT)
Received: from [192.168.178.23] (16.197.69.111.dynamic.snap.net.nz. [111.69.197.16]) by mx.google.com with ESMTPSA id y9sm51263251pbb.46.2013.07.24.21.12.05 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 24 Jul 2013 21:12:08 -0700 (PDT)
Message-ID: <51F0A59D.3010405@gmail.com>
Date: Thu, 25 Jul 2013 16:12:13 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: Remote participants access to Meeting Mailing Lists was Re: BOF posters in the welcome reception
References: <A6B9C627-A141-416B-AB39-469FDA86A875@ietf.org>	<2129CC69EEF207CADC2421AC@JcK-HP8200.jck.com>	<CC160C56-5D74-4309-AD3D-FB88FEB60B01@piuha.net>	<96F611AF0497CDC862CF30D4@JcK-HP8200.jck.com>	<OF68BD4951.D37EA2D7-ON85257BB2.004EEDF0-85257BB2.004F4E5A@csc.com>	<F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk>	<94EA01D5-C6BE-40B3-84C1-C707522627AB@piuha.net>	<EMEW3|07b43bbc00e6dd8decb147cb113c10dfp6NHk603tjc|ecs.soton.ac.uk|F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk>	<CAPv4CP-L1VCV4__f=EAXan-odWhV6Qo=QoMBOPUOS1R1F0NhPA@mail.gmail.com>	<51F0315D.4050307@gmail.com> <CAPv4CP9b7V54JYYY2T96wG9DJXnCMSsOGiAZdKvGkEkp3Kykyw@mail.gmail.com>
In-Reply-To: <CAPv4CP9b7V54JYYY2T96wG9DJXnCMSsOGiAZdKvGkEkp3Kykyw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: John C Klensin <john-ietf@jck.com>, Tim Chown <tjc@ecs.soton.ac.uk>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Jul 2013 04:12:14 -0000

On 25/07/2013 11:27, Scott Brim wrote:
> Brian: yes but non-registered thus non-ifentifiable subscribers, spammers
> etc don't.

We're talking about a list with a useful lifetime of perhaps 3 weeks.
I really don't think spam is a big issue. Trolls might be, but they
would be *our* trolls ;-)

Anyway - as John Klensin said, we should come up with a reasonably
complete and welcoming set of info and facilities for the remotes.
That may well include pro forma registration.

    Brian

> On Jul 24, 2013 3:56 PM, "Brian E Carpenter" <brian.e.carpenter@gmail.com>
> wrote:
> 
>> On 25/07/2013 05:01, Scott Brim wrote:
>>> The point of having a separate list for participants was to avoid
>>> spamming the ietf list.
>>>
>>> It can be open to everyone to subscribe to, since anyone can see the
>>> archives, HOWEVER I recommend that only registered participants be
>>> allowed to post.
>> Ahem. Either remote participants are allowed to post, or they need
>> a list of their own. I would envisage a fair amount of chatter about
>> specific remote-participation issues, like "this new codec isn't
>> working for me, is it OK for anyone else using <browser version> on
>> <operating system version>?"
>>
>>   Brian
>>
> 

From kathleen.moriarty@emc.com  Wed Jul 24 21:27:45 2013
Return-Path: <kathleen.moriarty@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 506E921F92B8 for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 21:27:45 -0700 (PDT)
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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UoT2Za1cQ0AK for <ietf@ietfa.amsl.com>; Wed, 24 Jul 2013 21:27:29 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 592DA21F9A70 for <ietf@ietf.org>; Wed, 24 Jul 2013 21:27:29 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r6P4RLdP021099 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 25 Jul 2013 00:27:21 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd01.lss.emc.com [10.254.221.251]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Thu, 25 Jul 2013 00:27:09 -0400
Received: from mxhub08.corp.emc.com (mxhub08.corp.emc.com [128.222.70.205]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r6P4R605016793; Thu, 25 Jul 2013 00:27:06 -0400
Received: from mx15a.corp.emc.com ([169.254.1.184]) by mxhub08.corp.emc.com ([128.222.70.205]) with mapi; Thu, 25 Jul 2013 00:27:05 -0400
From: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Date: Thu, 25 Jul 2013 00:27:01 -0400
Subject: Re: Remote participants access to Meeting Mailing Lists was Re: BOF posters in the welcome reception
Thread-Topic: Remote participants access to Meeting Mailing Lists was Re: BOF	posters in the welcome reception
Thread-Index: Ac6I7zhohKgVmGE3Sta+E+nTgvB5/w==
Message-ID: <A9F1E7F1-C555-4790-B2D3-3A7A93FD2E1F@emc.com>
References: <A6B9C627-A141-416B-AB39-469FDA86A875@ietf.org> <2129CC69EEF207CADC2421AC@JcK-HP8200.jck.com> <CC160C56-5D74-4309-AD3D-FB88FEB60B01@piuha.net> <96F611AF0497CDC862CF30D4@JcK-HP8200.jck.com> <OF68BD4951.D37EA2D7-ON85257BB2.004EEDF0-85257BB2.004F4E5A@csc.com> <F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk> <94EA01D5-C6BE-40B3-84C1-C707522627AB@piuha.net> <EMEW3|07b43bbc00e6dd8decb147cb113c10dfp6NHk603tjc|ecs.soton.ac.uk|F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk> <CAPv4CP-L1VCV4__f=EAXan-odWhV6Qo=QoMBOPUOS1R1F0NhPA@mail.gmail.com> <51F0315D.4050307@gmail.com> <CAPv4CP9b7V54JYYY2T96wG9DJXnCMSsOGiAZdKvGkEkp3Kykyw@mail.gmail.com> <51F0A59D.3010405@gmail.com>
In-Reply-To: <51F0A59D.3010405@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: John C Klensin <john-ietf@jck.com>, Tim Chown <tjc@ecs.soton.ac.uk>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Jul 2013 04:27:45 -0000

I like Aaron's suggestion to update the web with important information abou=
t a meeting.  There is a lot of mail on the list and that could be a useful=
 way to communicate updates, etc.

Best regards,
Kathleen=20

Sent from my iPhone

On Jul 25, 2013, at 12:12 AM, "Brian E Carpenter" <brian.e.carpenter@gmail.=
com> wrote:

> On 25/07/2013 11:27, Scott Brim wrote:
>> Brian: yes but non-registered thus non-ifentifiable subscribers, spammer=
s
>> etc don't.
>=20
> We're talking about a list with a useful lifetime of perhaps 3 weeks.
> I really don't think spam is a big issue. Trolls might be, but they
> would be *our* trolls ;-)
>=20
> Anyway - as John Klensin said, we should come up with a reasonably
> complete and welcoming set of info and facilities for the remotes.
> That may well include pro forma registration.
>=20
>    Brian
>=20
>> On Jul 24, 2013 3:56 PM, "Brian E Carpenter" <brian.e.carpenter@gmail.co=
m>
>> wrote:
>>=20
>>> On 25/07/2013 05:01, Scott Brim wrote:
>>>> The point of having a separate list for participants was to avoid
>>>> spamming the ietf list.
>>>>=20
>>>> It can be open to everyone to subscribe to, since anyone can see the
>>>> archives, HOWEVER I recommend that only registered participants be
>>>> allowed to post.
>>> Ahem. Either remote participants are allowed to post, or they need
>>> a list of their own. I would envisage a fair amount of chatter about
>>> specific remote-participation issues, like "this new codec isn't
>>> working for me, is it OK for anyone else using <browser version> on
>>> <operating system version>?"
>>>=20
>>>  Brian
>=20

From sm@resistor.net  Thu Jul 25 00:03:22 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7A0921F8934 for <ietf@ietfa.amsl.com>; Thu, 25 Jul 2013 00:03:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.783
X-Spam-Level: 
X-Spam-Status: No, score=-101.783 tagged_above=-999 required=5 tests=[AWL=-0.816, BAYES_00=-2.599, FS_START_DOYOU2=1.633, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ax4lgSvFNj1u for <ietf@ietfa.amsl.com>; Thu, 25 Jul 2013 00:03:22 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1101B21F85EB for <ietf@ietf.org>; Thu, 25 Jul 2013 00:03:20 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r6P73ETE026948; Thu, 25 Jul 2013 00:03:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1374735799; bh=aZA5VEe5hLZK53AGXjouohm0haHO+H7cNeO5y2Y7zDA=; h=Date:To:From:Subject:Cc; b=HqJqvE25vNXDbnPrNFkMVJm5PpZ23Z6TRMH1EGEjtV88E38QDvRva0MpFeh2lTxmU msF1BUbSlapUEbvacHpoHiz0LGpMS6nlDITRGJPUsiZeskRBM6YdrktSkTEv3fE6Xq rtrz3U7z0dHT5fsswlouM6gKFRDvA5i8YAZjM5OE=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1374735799; i=@resistor.net; bh=aZA5VEe5hLZK53AGXjouohm0haHO+H7cNeO5y2Y7zDA=; h=Date:To:From:Subject:Cc; b=EWGLXNz8MdUk3JD+5Fvu/Pq1flSUaxiOBHXgZG7PWsEZgXG0s97eLhxJ9YxuRFQOw ZHm0mHqOCHNwH3F8+jujHw2Xa1xfgXJLcP8xcw9k54TmOZNFmiiyhA9b1OOe9yWQ1G XYSPRAcnQcwXlC40nYNi419xhjQS6PcFHkvqxS+Y=
Message-Id: <6.2.5.6.2.20130725000255.0c2f3fd0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 25 Jul 2013 00:03:08 -0700
To: Jose Saldana <jsaldana@unizar.es>
From: SM <sm@resistor.net>
Subject: Do you want to know what it is?
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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Jul 2013 07:03:22 -0000

Hi Jose,

As I would like to know what it is I watched 
http://www.youtube.com/watch?v=QAnW9HTkbsI  It was a pleasant 
surprise to see a new approach instead of the usual boring 
presentations.  People who are old might feel left out though.  :-)

Here a quote from Jack Haverty:

   "If you always win, it means you're not taking enough risks."

The IETF might say that it does not scale [1].  Who am I to prove 
that the IETF is wrong? :-)

Regards,
-sm

1. People who are old will actually understand the quote.


From jari.arkko@piuha.net  Thu Jul 25 01:18:25 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9DD521F8994 for <ietf@ietfa.amsl.com>; Thu, 25 Jul 2013 01:18:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oOMM7epOM3xU for <ietf@ietfa.amsl.com>; Thu, 25 Jul 2013 01:18:19 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id E810221F937E for <ietf@ietf.org>; Thu, 25 Jul 2013 01:18:18 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 493E02CC48; Thu, 25 Jul 2013 11:18:17 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v19gKAwSc0sU; Thu, 25 Jul 2013 11:18:16 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 7311E2CC3C; Thu, 25 Jul 2013 11:18:16 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Do you want to know what it is?
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <6.2.5.6.2.20130725000255.0c2f3fd0@resistor.net>
Date: Thu, 25 Jul 2013 11:18:16 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <E062F21C-DE26-4499-98DA-1D13A2DE4B77@piuha.net>
References: <6.2.5.6.2.20130725000255.0c2f3fd0@resistor.net>
To: SM <sm@resistor.net>, Jose Saldana <jsaldana@unizar.es>
X-Mailer: Apple Mail (2.1508)
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Jul 2013 08:18:25 -0000

>=20
> As I would like to know what it is I watched =
http://www.youtube.com/watch?v=3DQAnW9HTkbsI  It was a pleasant surprise =
to see a new approach instead of the usual boring presentations.=20

Very nice indeed. Thanks for doing it!

(There's also http://www.youtube.com/watch?v=3D_G96ULX7Iak)

Jari



From christer.holmberg@ericsson.com  Thu Jul 25 01:30:18 2013
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BDB921F9C70 for <ietf@ietfa.amsl.com>; Thu, 25 Jul 2013 01:30:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.062
X-Spam-Level: 
X-Spam-Status: No, score=-6.062 tagged_above=-999 required=5 tests=[AWL=0.187,  BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gO+fRv-FnZ-e for <ietf@ietfa.amsl.com>; Thu, 25 Jul 2013 01:30:11 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id D90D121F9C82 for <ietf@ietf.org>; Thu, 25 Jul 2013 01:30:05 -0700 (PDT)
X-AuditID: c1b4fb2d-b7f0b6d0000002d5-c1-51f0e20c7c6e
Received: from ESESSHC012.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id CD.BE.00725.C02E0F15; Thu, 25 Jul 2013 10:30:04 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.135]) by ESESSHC012.ericsson.se ([153.88.183.54]) with mapi id 14.02.0328.009; Thu, 25 Jul 2013 10:30:03 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: SM <sm@resistor.net>
Subject: Re: Remote participants access to Meeting Mailing Lists was  Re: BOF posters in the welcome reception
Thread-Topic: Remote participants access to Meeting Mailing Lists was  Re: BOF posters in the welcome reception
Thread-Index: AQHOiMDFzWYvwFxWpE6YlRgHGMuSjJl1ENDo
Date: Thu, 25 Jul 2013 08:30:03 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C408B29@ESESSMB209.ericsson.se>
References: <A6B9C627-A141-416B-AB39-469FDA86A875@ietf.org> <2129CC69EEF207CADC2421AC@JcK-HP8200.jck.com> <CC160C56-5D74-4309-AD3D-FB88FEB60B01@piuha.net> <96F611AF0497CDC862CF30D4@JcK-HP8200.jck.com> <OF68BD4951.D37EA2D7-ON85257BB2.004EEDF0-85257BB2.004F4E5A@csc.com> <F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk> <94EA01D5-C6BE-40B3-84C1-C707522627AB@piuha.net> <EMEW3|07b43bbc00e6dd8decb147cb113c10dfp6NHk603tjc|ecs.soton.ac.uk|F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk> <CAPv4CP-L1VCV4__f=EAXan-odWhV6Qo=QoMBOPUOS1R1F0NhPA@mail.gmail.com> <51F0315D.4050307@gmail.com> <7594FB04B1934943A5C02806D1A2204B1C408542@ESESSMB209.ericsson.se>, <6.2.5.6.2.20130724144751.0b6eded0@resistor.net>
In-Reply-To: <6.2.5.6.2.20130724144751.0b6eded0@resistor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1C408B29ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrILMWRmVeSWpSXmKPExsUyM+JvrS7Pow+BBn96JCyebZzPYtF66Q+b xfENh9gdmD2WLPnJ5HF55Wtmj/fdz9gCmKO4bFJSczLLUov07RK4MmaefMJYcNWs4tnLZtYG xk69LkZODgkBE4kdDceZIWwxiQv31rN1MXJxCAkcZpTY/Gg6C4SzhFHi+9tdQBkODjYBC4nu f9ogDSICEhJ7N65kAgkzC7hKLJskAxIWFiiQmLTqMwtIWESgUOLOZ2eIaiOJMyv2s4DYLAKq Epd6N4Ot5RXwlbj4eD8jxKZrrBKN854zgiQ4BWwlPu/qZAKxGYFu+35qDZjNLCAucevJfCaI mwUkluw5D3W/qMTLx/9YIWryJWZemMMOsUBQ4uTMJywTGEVmIWmfhaRsFpIyiLiOxILdn9gg bG2JZQtfM8PYZw48ZkIWX8DIvoqRPTcxMye93HATIzCaDm75rbuD8dQ5kUOM0hwsSuK8m/TO BAoJpCeWpGanphakFsUXleakFh9iZOLglGpgDG2dmxFyrPe2+LklF9j4zcN/3OsUaz726HXT 7Qxh7YPtDRv9CnxfqPycGb76sqmQ1kyFlKMV5i2Fkpe6p3iyPgqtWb30QIC/wa+Xqw/J/Xt4 q9Qq/fVD1eT+5qqnacpTGremz+Y6kvfqpkXN9LCf4U+fL9k6z/JX03l1tRWed2OrtLTyekPX K7EUZyQaajEXFScCABT7FRx0AgAA
Cc: John C Klensin <john-ietf@jck.com>, "ietf_ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Jul 2013 08:30:18 -0000

--_000_7594FB04B1934943A5C02806D1A2204B1C408B29ESESSMB209erics_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

Whatever the information is used for, or not used for, I think it would be =
useful to know the number of remote participants, and where they are locate=
d.

Regards,

Christer



Sent from Windows using TouchDown (www.nitrodesk.com)

-----Original Message-----
From: SM [sm@resistor.net]
To: Christer Holmberg [christer.holmberg@ericsson.com]
CC: John C Klensin [john-ietf@jck.com]; ietf@ietf.org [ietf@ietf.org]
Subject: Re: Remote participants access to Meeting Mailing Lists was Re: BO=
F posters in the welcome reception
Hi Christer,
At 13:54 24-07-2013, Christer Holmberg wrote:
>Why couldn't remote participants register to the meeting like all
>other participants?
>
>Remote participation would of course still be free, but it would
>allow remote participants to subscribe to the attendee list in the
>same way as other participants.

A quick scan of that list shows the following topics:

   - coffee, sims

   - mailing list for IETF women

and the following comment:

   "I'm not sure why I should be required to give my contact information to
    get a document prepared by the Brussels airport for Brussels passengers=
."

>In addition, it would provide better knowledge to IETF about the
>number of remote participants, where they are physically located
>(which might be useful input when planning future meeting locations) etc.

I doubt that the IETF chooses its meeting location based on where the
remote participants are located.

I'll go off-topic first.  Mr Reschke once asked "I was just trying to
understand *why* the archive can't be at
<http://www.ietf.org/tao/archive>".  Mr Housley replied that "I was
told that we cannot have http://www.ietf.org/tao directed to the
document and also be the directory containing the archive
directory".  Mr Hansen provided some technical details about how that
can be done.  The point here is it might be better to have a good
answer as some IETF participant might deconstruct the answer and find
the flaw in it.

Mr Klensin's message was about how to find out about the 87all
mailing list.  Participants within the inner circle know how to find
it.  The rest of the participants will not be able to find that
information as it is not easily accessible through the www.ietf.org<http://=
www.ietf.org>
web site.  There is probably a lack of information about what
information is provided through the ietf-announce@ mailing list.

Regards,
-sm



--_000_7594FB04B1934943A5C02806D1A2204B1C408B29ESESSMB209erics_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; pad=
ding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div style=3D"font-family:Calibri,Arial,Helvetica,sans-serif; font-size:11p=
t; color:black">
<div><span style=3D"color:black; font-family:Calibri,Arial,Helvetica,sans-s=
erif; font-size:11pt">Hi,</span></div>
<div>&nbsp;</div>
<div><font face=3D"Calibri">Whatever the information is used for, or not us=
ed for, I think it would be useful to know the number of remote participant=
s, and where they are located.</font></div>
<div><font face=3D"Calibri"></font>&nbsp;</div>
<div><font face=3D"Calibri">Regards,</font></div>
<div><font face=3D"Calibri"></font>&nbsp;</div>
<div><font face=3D"Calibri">Christer</font></div>
<span style=3D"color:black; font-family:Calibri,Arial,Helvetica,sans-serif;=
 font-size:11pt">
<div>&nbsp;</div>
<div><br>
<br>
Sent from <b><i>Windows</i></b> using <b style=3D"color:blue">TouchDown</b>=
 (www.nitrodesk.com)</div>
</span>
<div></div>
<br>
<span style=3D"color:black">-----Original Message-----<br>
<b>From:</b> SM [sm@resistor.net]<br>
<b>To:</b> Christer Holmberg [christer.holmberg@ericsson.com]<br>
<b>CC:</b> John C Klensin [john-ietf@jck.com]; ietf@ietf.org [ietf@ietf.org=
]<br>
<b>Subject:</b> Re: Remote participants access to Meeting Mailing Lists was=
 Re: BOF posters in the welcome reception</span></div>
<font size=3D"2"><span style=3D"font-size:10pt;">
<div class=3D"PlainText">Hi Christer,<br>
At 13:54 24-07-2013, Christer Holmberg wrote:<br>
&gt;Why couldn't remote participants register to the meeting like all <br>
&gt;other participants?<br>
&gt;<br>
&gt;Remote participation would of course still be free, but it would <br>
&gt;allow remote participants to subscribe to the attendee list in the <br>
&gt;same way as other participants.<br>
<br>
A quick scan of that list shows the following topics:<br>
<br>
&nbsp;&nbsp; - coffee, sims<br>
<br>
&nbsp;&nbsp; - mailing list for IETF women<br>
<br>
and the following comment:<br>
<br>
&nbsp;&nbsp; &quot;I'm not sure why I should be required to give my contact=
 information to<br>
&nbsp;&nbsp;&nbsp; get a document prepared by the Brussels airport for Brus=
sels passengers.&quot;<br>
<br>
&gt;In addition, it would provide better knowledge to IETF about the <br>
&gt;number of remote participants, where they are physically located <br>
&gt;(which might be useful input when planning future meeting locations) et=
c.<br>
<br>
I doubt that the IETF chooses its meeting location based on where the <br>
remote participants are located.<br>
<br>
I'll go off-topic first.&nbsp; Mr Reschke once asked &quot;I was just tryin=
g to <br>
understand *why* the archive can't be at <br>
&lt;<a href=3D"http://www.ietf.org/tao/archive">http://www.ietf.org/tao/arc=
hive</a>&gt;&quot;.&nbsp; Mr Housley replied that &quot;I was
<br>
told that we cannot have <a href=3D"http://www.ietf.org/tao">http://www.iet=
f.org/tao</a> directed to the
<br>
document and also be the directory containing the archive <br>
directory&quot;.&nbsp; Mr Hansen provided some technical details about how =
that <br>
can be done.&nbsp; The point here is it might be better to have a good <br>
answer as some IETF participant might deconstruct the answer and find <br>
the flaw in it.<br>
<br>
Mr Klensin's message was about how to find out about the 87all <br>
mailing list.&nbsp; Participants within the inner circle know how to find <=
br>
it.&nbsp; The rest of the participants will not be able to find that <br>
information as it is not easily accessible through the <a href=3D"http://ww=
w.ietf.org">
www.ietf.org</a> <br>
web site.&nbsp; There is probably a lack of information about what <br>
information is provided through the ietf-announce@ mailing list.<br>
<br>
Regards,<br>
-sm<br>
<br>
<br>
</div>
</span></font>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1C408B29ESESSMB209erics_--

From Josh.Howlett@ja.net  Thu Jul 25 06:27:05 2013
Return-Path: <Josh.Howlett@ja.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EE7F21F9AFE; Thu, 25 Jul 2013 06:27:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0DrUoeoljHjo; Thu, 25 Jul 2013 06:26:59 -0700 (PDT)
Received: from egw001.ukerna.ac.uk (egw001.ukerna.ac.uk [194.82.140.74]) by ietfa.amsl.com (Postfix) with ESMTP id 188E821F9AFA; Thu, 25 Jul 2013 06:26:58 -0700 (PDT)
Received: from egw001.ukerna.ac.uk (localhost.localdomain [127.0.0.1]) by localhost (Email Security Appliance) with SMTP id 9CD2E1AC595A_1F127A1B; Thu, 25 Jul 2013 13:26:57 +0000 (GMT)
Received: from EXC001.atlas.ukerna.ac.uk (exc001.atlas.ukerna.ac.uk [193.62.83.37]) by egw001.ukerna.ac.uk (Sophos Email Appliance) with ESMTP id 5AC1E1AC5959_1F127A1F; Thu, 25 Jul 2013 13:26:57 +0000 (GMT)
Received: from EXC001.atlas.ukerna.ac.uk ([193.62.83.37]) by EXC001 ([193.62.83.37]) with mapi id 14.02.0247.003; Thu, 25 Jul 2013 14:26:56 +0100
From: Josh Howlett <Josh.Howlett@ja.net>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Emu] Last Call: <draft-ietf-emu-eap-tunnel-method-07.txt> (Tunnel EAP Method (TEAP) Version 1) to Proposed Standard
Thread-Topic: [Emu] Last Call: <draft-ietf-emu-eap-tunnel-method-07.txt> (Tunnel EAP Method (TEAP) Version 1) to Proposed Standard
Thread-Index: AQHOiTqho2f1WzAyiUaQlrNJcTfyFQ==
Date: Thu, 25 Jul 2013 13:26:55 +0000
Message-ID: <CE16DCB4.22F46%Josh.Howlett@ja.net>
In-Reply-To: <20130716141951.26241.35307.idtracker@ietfa.amsl.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.6.130613
x-originating-ip: [194.82.140.76]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <55201231F1AD6242A0CF31AFD074FD77@ukerna.ac.uk>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "emu@ietf.org" <emu@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Jul 2013 13:27:05 -0000

Section 3.2 of draft-wierenga-ietf-eduroam describes the issues presented
by EAP's spartan support for error condition handling. Although these are
described in the context of a particular roaming operator's experiences, I
believe this is also likely to be true for other non-trivial deployments.

To its credit this document (draft-ietf-emu-eap-tunnel-method) does
address error handling more comprehensively than previous EAP methods, but
I am not confident that it will yield error handling outcomes that could
be understood and corrected by an end user. For example, from my
understanding of the document, the most common failure modes (e.g.,
incorrect password; account locked; backend database offline, etc) will
all yield an "Inner_Method_Error". The other error messages are equally
vague ("General_PKI_Error") or cryptic from an end user's perspective.

Is this something that could be discussed in Berlin next week?

Josh.

On 16/07/2013 15:19, "The IESG" <iesg-secretary@ietf.org> wrote:

>
>The IESG has received a request from the EAP Method Update WG (emu) to
>consider the following document:
>- 'Tunnel EAP Method (TEAP) Version 1'
>  <draft-ietf-emu-eap-tunnel-method-07.txt> as Proposed Standard
>
>The IESG plans to make a decision in the next few weeks, and solicits
>final comments on this action. Please send substantive comments to the
>ietf@ietf.org mailing lists by 2013-07-30. 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 Tunnel Extensible Authentication Protocol
>   (TEAP) version 1.  TEAP is a tunnel based EAP method that enables
>   secure communication between a peer and a server by using the
>   Transport Layer Security (TLS) protocol to establish a mutually
>   authenticated tunnel.  Within the tunnel, Type-Length-Value (TLV)
>   objects are used to convey authentication related data between the
>   EAP peer and the EAP server.
>
>
>
>
>The file can be obtained via
>http://datatracker.ietf.org/doc/draft-ietf-emu-eap-tunnel-method/
>
>IESG discussion can be tracked via
>http://datatracker.ietf.org/doc/draft-ietf-emu-eap-tunnel-method/ballot/
>
>
>The following IPR Declarations may be related to this I-D:
>
>   http://datatracker.ietf.org/ipr/1902/
>
>
>
>_______________________________________________
>Emu mailing list
>Emu@ietf.org
>https://www.ietf.org/mailman/listinfo/emu


Janet(UK) is a trading name of Jisc Collections and Janet Limited, a=20
not-for-profit company which is registered in England under No. 2881024=20
and whose Registered Office is at Lumen House, Library Avenue,
Harwell Oxford, Didcot, Oxfordshire. OX11 0SG. VAT No. 614944238


From yding@cs.helsinki.fi  Thu Jul 25 06:41:38 2013
Return-Path: <yding@cs.helsinki.fi>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 970E521F9AC9 for <ietf@ietfa.amsl.com>; Thu, 25 Jul 2013 06:41:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level: 
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_84=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B8iU9HLfawq7 for <ietf@ietfa.amsl.com>; Thu, 25 Jul 2013 06:41:34 -0700 (PDT)
Received: from courier.cs.helsinki.fi (courier.cs.helsinki.fi [128.214.9.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4103E21F9AF5 for <ietf@ietf.org>; Thu, 25 Jul 2013 06:41:32 -0700 (PDT)
X-DKIM: Courier DKIM Filter v0.50+pk-2013-06-17 courier.cs.helsinki.fi Thu Jul 25 16:40:50 2013
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cs.helsinki.fi; h=message-id:date:from:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; s= dkim20130528; bh=fkUnEb8g3skt18WBI674N9ACc8N00O8oP72zWErR95I=; b= OdrcBdhI91DtFUdfaNwoAjy6zU/JTyR6+m+FLRDDZerMHFymii79B0EG0122dbbJ Tt1Xb++wqtv2JStNJ+IORQLa/5T4WWQPBveIsL89AI8Bov8k9RzascHtRxScE4EM 5MInDTkRAfQPgoEdr14re9h5hz5JLT4u1rpHnKpTpjE=
Received: from [128.232.100.160] (c0160.aw.cl.cam.ac.uk [128.232.100.160]) (AUTH: PLAIN yding, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by mail.cs.helsinki.fi with esmtp; Thu, 25 Jul 2013 16:40:50 +0300 id 00068A86.51F12AE2.00002116
Message-ID: <51F12AE1.9060807@cs.helsinki.fi>
Date: Thu, 25 Jul 2013 14:40:49 +0100
From: Aaron Yi DING <yding@cs.helsinki.fi>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, John C Klensin <john-ietf@jck.com>, Tim Chown <tjc@ecs.soton.ac.uk>
Subject: Re: Remote participants access to Meeting Mailing Lists was Re: BOF posters in the welcome reception
References: <A6B9C627-A141-416B-AB39-469FDA86A875@ietf.org> <2129CC69EEF207CADC2421AC@JcK-HP8200.jck.com> <CC160C56-5D74-4309-AD3D-FB88FEB60B01@piuha.net> <96F611AF0497CDC862CF30D4@JcK-HP8200.jck.com> <OF68BD4951.D37EA2D7-ON85257BB2.004EEDF0-85257BB2.004F4E5A@csc.com> <F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk> <94EA01D5-C6BE-40B3-84C1-C707522627AB@piuha.net> <EMEW3|07b43bbc00e6dd8decb147cb113c10dfp6NHk603tjc|ecs.soton.ac.uk|F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk> <CAPv4CP-L1VCV4__f=EAXan-odWhV6Qo=QoMBOPUOS1R1F0NhPA@mail.gmail.com> <51F0315D.4050307@gmail.com> <CAPv4CP9b7V54JYYY2T96wG9DJXnCMSsOGiAZdKvGkEkp3Kykyw@mail.gmail.com> <51F0A59D.3010405@gmail.com> <A9F1E7F1-C555-4790-B2D3-3A7A93FD2E1F@emc.com>
In-Reply-To: <A9F1E7F1-C555-4790-B2D3-3A7A93FD2E1F@emc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Jul 2013 13:41:38 -0000

On 25/07/13 05:27, Moriarty, Kathleen wrote:
> I like Aaron's suggestion to update the web with important information about a meeting.  There is a lot of mail on the list and that could be a useful way to communicate updates, etc.

Thanks, in case the previous mail is down in the pile already...

"
One thing that may also benefit both Remote and Meeting participants:

An anchor point to distribute live update about IETF week, e.g., 
schedule change, latest bits-n-bytes info, WG/BoF agenda changes/slides 
uploaded(with embedded link), highlight/awards at plenary, emergent 
notice for facility issues/weather/traffic/hotel stealing...

Most of those could be found if digging hard enough from hundreds of 
mails during IETF week, but a quick link definitely helps.

It can be a "live update" bullet on the front page of IETF meeting
http://www.ietf.org/meeting/87/
"

Cheers,
Aaron


> Best regards,
> Kathleen
>
> Sent from my iPhone
>
> On Jul 25, 2013, at 12:12 AM, "Brian E Carpenter" <brian.e.carpenter@gmail.com> wrote:
>
>> On 25/07/2013 11:27, Scott Brim wrote:
>>> Brian: yes but non-registered thus non-ifentifiable subscribers, spammers
>>> etc don't.
>> We're talking about a list with a useful lifetime of perhaps 3 weeks.
>> I really don't think spam is a big issue. Trolls might be, but they
>> would be *our* trolls ;-)
>>
>> Anyway - as John Klensin said, we should come up with a reasonably
>> complete and welcoming set of info and facilities for the remotes.
>> That may well include pro forma registration.
>>
>>     Brian
>>
>>> On Jul 24, 2013 3:56 PM, "Brian E Carpenter" <brian.e.carpenter@gmail.com>
>>> wrote:
>>>
>>>> On 25/07/2013 05:01, Scott Brim wrote:
>>>>> The point of having a separate list for participants was to avoid
>>>>> spamming the ietf list.
>>>>>
>>>>> It can be open to everyone to subscribe to, since anyone can see the
>>>>> archives, HOWEVER I recommend that only registered participants be
>>>>> allowed to post.
>>>> Ahem. Either remote participants are allowed to post, or they need
>>>> a list of their own. I would envisage a fair amount of chatter about
>>>> specific remote-participation issues, like "this new codec isn't
>>>> working for me, is it OK for anyone else using <browser version> on
>>>> <operating system version>?"
>>>>
>>>>   Brian


From jsalowey@cisco.com  Thu Jul 25 09:07:47 2013
Return-Path: <jsalowey@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10FF121F84D9; Thu, 25 Jul 2013 09:07:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1aMCuAFFERSJ; Thu, 25 Jul 2013 09:07:42 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id EEE5121F84E3; Thu, 25 Jul 2013 09:07:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3271; q=dns/txt; s=iport; t=1374768462; x=1375978062; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=1ncK8hSQ2QLE2uRb5yw9BMPjKAY1V1gKkWiLMb32FWs=; b=b1j/JZYolf2vo0KuopK853JZnrYg9JIst/AI9oXJfMHvzOsyyJAYiLlH ah/vHdWi5pQECWlcwTKS2sgDWzZrs5iSfeL9F8FlT8kTsEB0BqfvtT/yK oRSbgUwCN2btigxf2C6ysHA3myEMoe99c2Fea4DPhmbwDJIUB6kW7QIq6 o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhMFAH5M8VGtJV2d/2dsb2JhbABSCIMGNVC9XYEWFnSCJAEBAQMBAQEBNzQLBQsCAQgYCgsDBgULJwslAgQOBQiIAgYMuVmOSAKBAAIxBwoOgnpuA5kIkCSBW4E5gWhC
X-IronPort-AV: E=Sophos;i="4.89,744,1367971200"; d="scan'208";a="239245149"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-1.cisco.com with ESMTP; 25 Jul 2013 16:07:41 +0000
Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id r6PG7fiu029955 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 25 Jul 2013 16:07:41 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.235]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.02.0318.004; Thu, 25 Jul 2013 11:07:41 -0500
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: Josh Howlett <Josh.Howlett@ja.net>
Subject: Re: [Emu] Last Call: <draft-ietf-emu-eap-tunnel-method-07.txt> (Tunnel EAP Method (TEAP) Version 1) to Proposed Standard
Thread-Topic: [Emu] Last Call: <draft-ietf-emu-eap-tunnel-method-07.txt> (Tunnel EAP Method (TEAP) Version 1) to Proposed Standard
Thread-Index: AQHOiTqho2f1WzAyiUaQlrNJcTfyFZl144eA
Date: Thu, 25 Jul 2013 16:07:40 +0000
Message-ID: <A95B4818FD85874D8F16607F1AC7C628D856D1@xmb-rcd-x09.cisco.com>
References: <CE16DCB4.22F46%Josh.Howlett@ja.net>
In-Reply-To: <CE16DCB4.22F46%Josh.Howlett@ja.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.33.249.159]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <8ADA0080ED726B458C1AAADA932B4DED@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>, "emu@ietf.org" <emu@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Jul 2013 16:07:47 -0000

Yes, this document is the main thing on the agenda.=20
On Jul 25, 2013, at 6:26 AM, Josh Howlett <Josh.Howlett@ja.net>
 wrote:

> Section 3.2 of draft-wierenga-ietf-eduroam describes the issues presented
> by EAP's spartan support for error condition handling. Although these are
> described in the context of a particular roaming operator's experiences, =
I
> believe this is also likely to be true for other non-trivial deployments.
>=20
> To its credit this document (draft-ietf-emu-eap-tunnel-method) does
> address error handling more comprehensively than previous EAP methods, bu=
t
> I am not confident that it will yield error handling outcomes that could
> be understood and corrected by an end user. For example, from my
> understanding of the document, the most common failure modes (e.g.,
> incorrect password; account locked; backend database offline, etc) will
> all yield an "Inner_Method_Error". The other error messages are equally
> vague ("General_PKI_Error") or cryptic from an end user's perspective.
>=20
> Is this something that could be discussed in Berlin next week?
>=20
> Josh.
>=20
> On 16/07/2013 15:19, "The IESG" <iesg-secretary@ietf.org> wrote:
>=20
>>=20
>> The IESG has received a request from the EAP Method Update WG (emu) to
>> consider the following document:
>> - 'Tunnel EAP Method (TEAP) Version 1'
>> <draft-ietf-emu-eap-tunnel-method-07.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 2013-07-30. Exceptionally, comments may b=
e
>> 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 defines the Tunnel Extensible Authentication Protocol
>>  (TEAP) version 1.  TEAP is a tunnel based EAP method that enables
>>  secure communication between a peer and a server by using the
>>  Transport Layer Security (TLS) protocol to establish a mutually
>>  authenticated tunnel.  Within the tunnel, Type-Length-Value (TLV)
>>  objects are used to convey authentication related data between the
>>  EAP peer and the EAP server.
>>=20
>>=20
>>=20
>>=20
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-ietf-emu-eap-tunnel-method/
>>=20
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-ietf-emu-eap-tunnel-method/ballot/
>>=20
>>=20
>> The following IPR Declarations may be related to this I-D:
>>=20
>>  http://datatracker.ietf.org/ipr/1902/
>>=20
>>=20
>>=20
>> _______________________________________________
>> Emu mailing list
>> Emu@ietf.org
>> https://www.ietf.org/mailman/listinfo/emu
>=20
>=20
> Janet(UK) is a trading name of Jisc Collections and Janet Limited, a=20
> not-for-profit company which is registered in England under No. 2881024=20
> and whose Registered Office is at Lumen House, Library Avenue,
> Harwell Oxford, Didcot, Oxfordshire. OX11 0SG. VAT No. 614944238
>=20
> _______________________________________________
> Emu mailing list
> Emu@ietf.org
> https://www.ietf.org/mailman/listinfo/emu


From brian.e.carpenter@gmail.com  Thu Jul 25 13:16:11 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CAC921F938E for <ietf@ietfa.amsl.com>; Thu, 25 Jul 2013 13:16:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.582
X-Spam-Level: 
X-Spam-Status: No, score=-102.582 tagged_above=-999 required=5 tests=[AWL=0.017, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oLxNaJuk0j+0 for <ietf@ietfa.amsl.com>; Thu, 25 Jul 2013 13:16:11 -0700 (PDT)
Received: from mail-pb0-x22d.google.com (mail-pb0-x22d.google.com [IPv6:2607:f8b0:400e:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 0C3D621F9371 for <ietf@ietf.org>; Thu, 25 Jul 2013 13:16:10 -0700 (PDT)
Received: by mail-pb0-f45.google.com with SMTP id mc8so1172235pbc.18 for <ietf@ietf.org>; Thu, 25 Jul 2013 13:16:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=qJnwWJXRs+veRhLmq967BXC5cQ1SwcWyeIlH/2cBJlc=; b=eC9oqtZEE1WdyhdxzXyZ+PU34pwgwOQvlCNQq9FK4gHSnTdnHlSDQTfSKj+GYc7aoZ of/7JyYA3S698TzFzfGrrLrN7zzVZxAUieWouAr7by0vf4MncmNABafG1fB15j/unOha 1op+9N605QVAKXBXQve528H3DxI/ETGcntF9jg/fnhOokNgEHAG9chUoOCw8sqepr2Qg Ip3KL9qqhONJcN4/wRL4D0UoIEewHWC73uQ595+Ui7MZL2RTTpLMMsV51SNsCWOlHYJb VG4puApmvqGZ2357OcFUVaYS3tMZZ9RiXRik0wyZoX7kxR1UY/F18hPCPC0q1lFoAadX ln6g==
X-Received: by 10.68.162.36 with SMTP id xx4mr5437869pbb.47.1374783370558; Thu, 25 Jul 2013 13:16:10 -0700 (PDT)
Received: from [192.168.178.23] (42.199.69.111.dynamic.snap.net.nz. [111.69.199.42]) by mx.google.com with ESMTPSA id ts6sm3604369pbc.12.2013.07.25.13.16.08 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 25 Jul 2013 13:16:09 -0700 (PDT)
Message-ID: <51F1878D.1010903@gmail.com>
Date: Fri, 26 Jul 2013 08:16:13 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: IETF discussion list <ietf@ietf.org>
Subject: IEEE Internet Award winner: Jon Crowcroft
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Jul 2013 20:16:11 -0000

Some people here will remember that Jon was an IETF participant and an
IAB member a number of years ago.

   Brian

................................

2014 IEEE Technical Field Award Recipients and Citations

IEEE INTERNET AWARD-recognizes exceptional contributions to the advancement of Internet technology for network architecture,
mobility, and/or end-use applications-sponsored by Nokia Corporation-to
JON CROWCROFT (FIEEE)-Professor, University of Cambridge, Cambridge, United Kingdom
"For contributions to research in and teaching of Internet protocols, including multicast, transport, quality of service,
security, mobility, and opportunistic networking."

(from http://www.ieee.org/about/awards/news/2014_ieee_tfa_recipients_and_citations_list.pdf)






From dmm@1-4-5.net  Thu Jul 25 13:28:23 2013
Return-Path: <dmm@1-4-5.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4CEF21F9377 for <ietf@ietfa.amsl.com>; Thu, 25 Jul 2013 13:28:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iBcd9XURvHdh for <ietf@ietfa.amsl.com>; Thu, 25 Jul 2013 13:28:18 -0700 (PDT)
Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by ietfa.amsl.com (Postfix) with ESMTP id 8E01521F8517 for <ietf@ietf.org>; Thu, 25 Jul 2013 13:28:13 -0700 (PDT)
Received: by mail-ob0-f182.google.com with SMTP id wo10so2608699obc.27 for <ietf@ietf.org>; Thu, 25 Jul 2013 13:28:12 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=ZmQpLxA7FgFP0kUFQcNBfvKnlUx4CAUntbVXQ7RFboo=; b=csZgo4V+Ml3dFok9v9pPR1Gw5r/xnJl8n78KTer/s90Bieeriji9agRJenzWQz0QE8 NcBHo5dlOJoN1m6RNkYJFiKropEknb6zDr9oe7atvYMtDUJHEcwON3ZSBLRMoBmv/zb2 0yPotsvOfkKwc7NPYQVJ5wR1MkiYnafb0Wox1m8+pBk+hqVjH0Vx21E53vadIOt3l5GF ljsaPdbkLdilEUCU84z7sxYK+IB9Of2W6PhHMyP094tOCU2FDMp/oEbPaPwD6p96OB7t e//dHBJ6Nj/vS8q2wYLVWJwvjKzLyoYEg/xMQ8ZUcE/PMI+MYN0fqsmsFy3r8IidTZ9Y ctPA==
MIME-Version: 1.0
X-Received: by 10.182.53.234 with SMTP id e10mr37498065obp.47.1374784092424; Thu, 25 Jul 2013 13:28:12 -0700 (PDT)
Received: by 10.182.31.68 with HTTP; Thu, 25 Jul 2013 13:28:12 -0700 (PDT)
X-Originating-IP: [24.21.216.213]
In-Reply-To: <51F1878D.1010903@gmail.com>
References: <51F1878D.1010903@gmail.com>
Date: Thu, 25 Jul 2013 13:28:12 -0700
Message-ID: <CAHiKxWiPi7922WFVouOPnfDKkhmwm8SrDFWQEitpQA1Zwym3Gw@mail.gmail.com>
Subject: Re: IEEE Internet Award winner: Jon Crowcroft
From: David Meyer <dmm@1-4-5.net>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQngIqjjd7i+SO9IoeKUTw+kmRkaTsjY9ZevsVAgB9u5mBwwS79r2SBVKtx0IQNXJ6+beJJF
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Jul 2013 20:28:23 -0000

On Thu, Jul 25, 2013 at 1:16 PM, Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:
> Some people here will remember that Jon was an IETF participant and an
> IAB member a number of years ago.

Well deserved. Congrats Jon!

--dmm

>
>    Brian
>
> ................................
>
> 2014 IEEE Technical Field Award Recipients and Citations
>
> IEEE INTERNET AWARD-recognizes exceptional contributions to the advancement of Internet technology for network architecture,
> mobility, and/or end-use applications-sponsored by Nokia Corporation-to
> JON CROWCROFT (FIEEE)-Professor, University of Cambridge, Cambridge, United Kingdom
> "For contributions to research in and teaching of Internet protocols, including multicast, transport, quality of service,
> security, mobility, and opportunistic networking."
>
> (from http://www.ieee.org/about/awards/news/2014_ieee_tfa_recipients_and_citations_list.pdf)
>
>
>
>
>

From narten@us.ibm.com  Thu Jul 25 21:53:36 2013
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDAB921F8F07 for <ietf@ietfa.amsl.com>; Thu, 25 Jul 2013 21:53:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p-Nv77N3SU0i for <ietf@ietfa.amsl.com>; Thu, 25 Jul 2013 21:53:29 -0700 (PDT)
Received: from e39.co.us.ibm.com (e39.co.us.ibm.com [32.97.110.160]) by ietfa.amsl.com (Postfix) with ESMTP id E138A21F9943 for <ietf@ietf.org>; Thu, 25 Jul 2013 21:53:28 -0700 (PDT)
Received: from /spool/local by e39.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Thu, 25 Jul 2013 22:53:06 -0600
Received: from d01dlp01.pok.ibm.com (9.56.250.166) by e39.co.us.ibm.com (192.168.1.139) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 25 Jul 2013 22:53:05 -0600
Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234]) by d01dlp01.pok.ibm.com (Postfix) with ESMTP id CF75C38C8027 for <ietf@ietf.org>; Fri, 26 Jul 2013 00:53:03 -0400 (EDT)
Received: from d01av02.pok.ibm.com (d01av02.pok.ibm.com [9.56.224.216]) by d01relay02.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r6Q4r5PI155872 for <ietf@ietf.org>; Fri, 26 Jul 2013 00:53:05 -0400
Received: from d01av02.pok.ibm.com (loopback [127.0.0.1]) by d01av02.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r6Q4r4wq032763 for <ietf@ietf.org>; Fri, 26 Jul 2013 01:53:04 -0300
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d01av02.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r6Q4r4Nx032746 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 26 Jul 2013 01:53:04 -0300
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 r6Q4r33u004353 for <ietf@ietf.org>; Fri, 26 Jul 2013 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.7/8.14.7/Submit) id r6Q4r3c8004331 for ietf@ietf.org; Fri, 26 Jul 2013 00:53:03 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201307260453.r6Q4r3c8004331@rotala.raleigh.ibm.com>
Date: Fri, 26 Jul 2013 00:53:03 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13072604-3620-0000-0000-000003B07EBF
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jul 2013 04:53:36 -0000

Total of 109 messages in the last 7 days.
 
script run at: Fri Jul 26 00:53:03 EDT 2013
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 13.76% |   15 | 21.67% |   210921 | aallen@blackberry.com
  9.17% |   10 | 12.47% |   121366 | tbray@textuality.com
  8.26% |    9 |  5.89% |    57325 | john-ietf@jck.com
  5.50% |    6 |  4.62% |    44943 | sm+ietf@elandsys.com
  5.50% |    6 |  3.65% |    35534 | jari.arkko@piuha.net
  4.59% |    5 |  3.33% |    32388 | scott.brim@gmail.com
  3.67% |    4 |  2.80% |    27207 | brian.e.carpenter@gmail.com
  3.67% |    4 |  2.55% |    24814 | stephen.farrell@cs.tcd.ie
  2.75% |    3 |  2.30% |    22369 | sm@resistor.net
  2.75% |    3 |  1.93% |    18799 | martin.thomson@gmail.com
  1.83% |    2 |  2.54% |    24758 | christer.holmberg@ericsson.com
  0.92% |    1 |  3.11% |    30309 | kewisch@gmail.com
  1.83% |    2 |  1.92% |    18643 | narten@us.ibm.com
  1.83% |    2 |  1.89% |    18402 | yding@cs.helsinki.fi
  1.83% |    2 |  1.53% |    14864 | housley@vigilsec.com
  1.83% |    2 |  1.48% |    14368 | barryleiba@computer.org
  1.83% |    2 |  1.34% |    13036 | melinda.shore@gmail.com
  1.83% |    2 |  1.09% |    10638 | dougb@dougbarton.us
  1.83% |    2 |  1.08% |    10477 | randy@psg.com
  0.92% |    1 |  1.35% |    13094 | stefan.winter@restena.lu
  0.92% |    1 |  1.24% |    12041 | fred@cisco.com
  0.92% |    1 |  1.20% |    11680 | ben@nostrum.com
  0.92% |    1 |  1.11% |    10772 | david.black@emc.com
  0.92% |    1 |  1.01% |     9859 | jgunn6@csc.com
  0.92% |    1 |  1.01% |     9791 | fluffy@cisco.com
  0.92% |    1 |  1.01% |     9790 | ted.ietf@gmail.com
  0.92% |    1 |  0.99% |     9631 | d3e3e3@gmail.com
  0.92% |    1 |  0.97% |     9427 | chair@ietf.org
  0.92% |    1 |  0.94% |     9194 | jsalowey@cisco.com
  0.92% |    1 |  0.92% |     8995 | hsantos@isdg.net
  0.92% |    1 |  0.86% |     8343 | presnick@qti.qualcomm.com
  0.92% |    1 |  0.82% |     7966 | eric.gray@ericsson.com
  0.92% |    1 |  0.82% |     7933 | josh.howlett@ja.net
  0.92% |    1 |  0.80% |     7752 | tjc@ecs.soton.ac.uk
  0.92% |    1 |  0.79% |     7722 | kathleen.moriarty@emc.com
  0.92% |    1 |  0.78% |     7598 | brian@innovationslab.net
  0.92% |    1 |  0.72% |     7008 | ted.lemon@nominum.com
  0.92% |    1 |  0.68% |     6631 | zehn.cao@gmail.com
  0.92% |    1 |  0.68% |     6610 | joelja@bogus.com
  0.92% |    1 |  0.64% |     6216 | dmm@1-4-5.net
  0.92% |    1 |  0.62% |     6060 | garbakora@gmail.com
  0.92% |    1 |  0.59% |     5790 | simon.perreault@viagenie.ca
  0.92% |    1 |  0.59% |     5731 | ajs@anvilwalrusden.com
  0.92% |    1 |  0.58% |     5663 | tterribe@xiph.org
  0.92% |    1 |  0.58% |     5617 | ford@isoc.org
  0.92% |    1 |  0.52% |     5085 | john@jck.com
--------+------+--------+----------+------------------------
100.00% |  109 |100.00% |   973160 | Total


From abdussalambaryun@gmail.com  Thu Jul 25 23:07:20 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CD4E21F8934 for <ietf@ietfa.amsl.com>; Thu, 25 Jul 2013 23:07:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kHw-kAA-ayYR for <ietf@ietfa.amsl.com>; Thu, 25 Jul 2013 23:07:06 -0700 (PDT)
Received: from mail-we0-x234.google.com (mail-we0-x234.google.com [IPv6:2a00:1450:400c:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id 5400821F8887 for <ietf@ietf.org>; Thu, 25 Jul 2013 23:07:06 -0700 (PDT)
Received: by mail-we0-f180.google.com with SMTP id p61so1278162wes.11 for <ietf@ietf.org>; Thu, 25 Jul 2013 23:07:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=DDjZQeItYHjkbUcVAovJv9rUaVBZ21BcKRZTOk9S9v4=; b=CxIX2bWsK5Uaev+0KNaqagjPLcwjQWcYU8QCivCROITLYW8WS2txs60ZYmIQK8swIm 2FqjNzoF8zptKfXK8QS0sLzOBsp5QN2oB/0eqMRKt0MV60E1bi1OoSK+1k91LLDiHcLM Rn/2s6yVhQmkTQsUKduTWNNtrSmKU+/4COYwgjBV4j9O68l7Jx8d5GOuhnkdLU4gAoxw WzgLG6Ph/Nijm5Kr7H9xLY8E1t+ODkVARNt6GHQxDj/XiphQ4BCvuhkvRol5zQyNkIbP wGSm7dOQfLxFTpzGS3gEN64rjDrFLt/5HnXj/vZM1pYdNN3AiOiiH226K5+42VDKkaAD 7myg==
MIME-Version: 1.0
X-Received: by 10.194.173.71 with SMTP id bi7mr33305717wjc.2.1374818823010; Thu, 25 Jul 2013 23:07:03 -0700 (PDT)
Received: by 10.180.3.232 with HTTP; Thu, 25 Jul 2013 23:07:02 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C408B29@ESESSMB209.ericsson.se>
References: <A6B9C627-A141-416B-AB39-469FDA86A875@ietf.org> <2129CC69EEF207CADC2421AC@JcK-HP8200.jck.com> <CC160C56-5D74-4309-AD3D-FB88FEB60B01@piuha.net> <96F611AF0497CDC862CF30D4@JcK-HP8200.jck.com> <OF68BD4951.D37EA2D7-ON85257BB2.004EEDF0-85257BB2.004F4E5A@csc.com> <F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk> <94EA01D5-C6BE-40B3-84C1-C707522627AB@piuha.net> <EMEW3|07b43bbc00e6dd8decb147cb113c10dfp6NHk603tjc|ecs.soton.ac.uk|F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk> <CAPv4CP-L1VCV4__f=EAXan-odWhV6Qo=QoMBOPUOS1R1F0NhPA@mail.gmail.com> <51F0315D.4050307@gmail.com> <7594FB04B1934943A5C02806D1A2204B1C408542@ESESSMB209.ericsson.se> <6.2.5.6.2.20130724144751.0b6eded0@resistor.net> <7594FB04B1934943A5C02806D1A2204B1C408B29@ESESSMB209.ericsson.se>
Date: Fri, 26 Jul 2013 08:07:02 +0200
Message-ID: <CADnDZ89FT6178QjMwx3hi+wPaa79diDXY-nwvqgz+1TS7qVSdQ@mail.gmail.com>
Subject: Re: Remote participants access to Meeting Mailing Lists was Re: BOF posters in the welcome reception
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: SM <sm@resistor.net>, "ietf_ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jul 2013 06:07:20 -0000

I agree with your suggestion Christer. Remote-participants have right
to register their attendance because they do attend remotely and IETF
SHOULD register their information if available. Last meetings I did
not like that I was not registered because I am remote, but now I feel
more welcomed.

 I think the location of remote participant at the meeting time can be
variable per participant (so can be distracting). Even participants
that attend some meeting sessions may be remote in others or attend
both ways at same time, so I think it is better to know/register how
many are only-remote and at which group-sessions and for how long, and
how many remote inputs per session. Then the registered info are
useful for IETF to improve it participation per meetings or
meeting-locations.

AB

On 7/25/13, Christer Holmberg <christer.holmberg@ericsson.com> wrote:
> Hi,
>
> Whatever the information is used for, or not used for, I think it would be
> useful to know the number of remote participants, and where they are
> located.
>
> Regards,
>
> Christer
>
>
>
> Sent from Windows using TouchDown (www.nitrodesk.com)
>
> -----Original Message-----
> From: SM [sm@resistor.net]
> To: Christer Holmberg [christer.holmberg@ericsson.com]
> CC: John C Klensin [john-ietf@jck.com]; ietf@ietf.org [ietf@ietf.org]
> Subject: Re: Remote participants access to Meeting Mailing Lists was Re: BOF
> posters in the welcome reception
> Hi Christer,
> At 13:54 24-07-2013, Christer Holmberg wrote:
>>Why couldn't remote participants register to the meeting like all
>>other participants?
>>
>>Remote participation would of course still be free, but it would
>>allow remote participants to subscribe to the attendee list in the
>>same way as other participants.
>
> A quick scan of that list shows the following topics:
>
>    - coffee, sims
>
>    - mailing list for IETF women
>
> and the following comment:
>
>    "I'm not sure why I should be required to give my contact information to
>     get a document prepared by the Brussels airport for Brussels
> passengers."
>
>>In addition, it would provide better knowledge to IETF about the
>>number of remote participants, where they are physically located
>>(which might be useful input when planning future meeting locations) etc.
>
> I doubt that the IETF chooses its meeting location based on where the
> remote participants are located.
>
> I'll go off-topic first.  Mr Reschke once asked "I was just trying to
> understand *why* the archive can't be at
> <http://www.ietf.org/tao/archive>".  Mr Housley replied that "I was
> told that we cannot have http://www.ietf.org/tao directed to the
> document and also be the directory containing the archive
> directory".  Mr Hansen provided some technical details about how that
> can be done.  The point here is it might be better to have a good
> answer as some IETF participant might deconstruct the answer and find
> the flaw in it.
>
> Mr Klensin's message was about how to find out about the 87all
> mailing list.  Participants within the inner circle know how to find
> it.  The rest of the participants will not be able to find that
> information as it is not easily accessible through the
> www.ietf.org<http://www.ietf.org>
> web site.  There is probably a lack of information about what
> information is provided through the ietf-announce@ mailing list.
>
> Regards,
> -sm
>
>
>

From abdussalambaryun@gmail.com  Thu Jul 25 23:36:31 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E73A11E80D1 for <ietf@ietfa.amsl.com>; Thu, 25 Jul 2013 23:36:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x1xgUawP3Dcz for <ietf@ietfa.amsl.com>; Thu, 25 Jul 2013 23:36:30 -0700 (PDT)
Received: from mail-wi0-x235.google.com (mail-wi0-x235.google.com [IPv6:2a00:1450:400c:c05::235]) by ietfa.amsl.com (Postfix) with ESMTP id 6BB2F21F85F4 for <ietf@ietf.org>; Thu, 25 Jul 2013 23:36:30 -0700 (PDT)
Received: by mail-wi0-f181.google.com with SMTP id en1so340754wid.2 for <ietf@ietf.org>; Thu, 25 Jul 2013 23:36:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=pf6xoCcebXv4XRrSEz2Ax1xzAYp29/dzNym2MG/WTLs=; b=hxW6YI3NcDuNPwhUdNiqfNBukxmBeIECFyuqfIK/vAmxWcjpOAyOanM7zk+sq1Z03L DEC/ivrM+kgYcpX+3F+zAz2MPG5Yw8V9+USbCgB0REDzwOUu7v7sfoArumsBw31PHAjj vHehitHydOIbwp6t7b9Y/gjuLWeEhzmOawG2015Vn1eAhXMPRz3FHmgi3gqgG+ZNjiP8 WnxscTqRGtoQV645WDJjxyjnARRpb5zjjsj+DSd+h6uGz6kycEBhCIJdBuS5oAtVN9gT RfexxsJYGVitdLs+C3zMR90J5Z363/3rH4AyMi/lvtiNu1npf8Sq1y7coey3I8rYy6eF hu6A==
MIME-Version: 1.0
X-Received: by 10.180.182.229 with SMTP id eh5mr4476574wic.63.1374820589581; Thu, 25 Jul 2013 23:36:29 -0700 (PDT)
Received: by 10.180.3.232 with HTTP; Thu, 25 Jul 2013 23:36:29 -0700 (PDT)
In-Reply-To: <2129CC69EEF207CADC2421AC@JcK-HP8200.jck.com>
References: <A6B9C627-A141-416B-AB39-469FDA86A875@ietf.org> <2129CC69EEF207CADC2421AC@JcK-HP8200.jck.com>
Date: Fri, 26 Jul 2013 08:36:29 +0200
Message-ID: <CADnDZ89ZnoL0eW=dZBBYLCVRSEvx3fz4hVXvhU4os88Cgh8vvw@mail.gmail.com>
Subject: Re: BOF posters in the welcome reception
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: John C Klensin <john-ietf@jck.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jul 2013 06:36:31 -0000

On 7/24/13, John C Klensin <john-ietf@jck.com> wrote:
>
>
> --On Wednesday, July 24, 2013 09:22 +0300 IETF Chair
> <chair@ietf.org> wrote:
>
>> I wanted to let you know about an experiment we are trying out
>> in Berlin.
>>...
>> But we want as many people as possible to become involved in
>> these efforts, or at least provide their feedback during the
>> week. So we have given an opportunity for the BOFs to display
>> a poster in the Welcome Reception (Sunday 5pm to 7pm). If you
>> are attending the reception, take a look at the posters and
>> look for topics that interest you.

What about each poster state which WG/RFCs it is mostly
depending-on/related (if applicable), this can make an easier way to
know if I am interested or should be interested.

>> Someone running the BOF is
>> also likely standing by, so you can also get directly involved
>> in discussions, sign up to help, etc. We hope that this helps
>> you all network with others even more :-)

How can I access the live discuss while remote? The remote live
networking with BOF is still not-clear/difficult. I as remote would
like to know how many attended and interested per BOF.

>
> In the interest of encouraging remote participation and
> involvement in those BOFs, could these posters be made available
> online before the reception?   Will they eventually be
> incorporated into the minutes?

Agree, and I will be more encouraged to participate if I know an
estimate community rank (not sure how to evaluate may be from IESG), a
similar way of poster presentation format per all BOFs (helps to read
through, save time, and get more involve in more BOFs), how much work
was done so far.

>
> And, incidentally, is there a way for remote participants to
> sign up for one or both meeting-related mailing lists without
> registering (or using a "remote participation registration"
> mechanism, which would be my preference for other reasons)?

Agree, but to clarify; if not registered then the remote participant
is still not sure to be involved, but if registered then means he/she
is interested.

AB

From leaf.yeh.sdo@gmail.com  Fri Jul 26 00:04:50 2013
Return-Path: <leaf.yeh.sdo@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF3A811E80E1 for <ietf@ietfa.amsl.com>; Fri, 26 Jul 2013 00:04:50 -0700 (PDT)
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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EXD70UyuFF9E for <ietf@ietfa.amsl.com>; Fri, 26 Jul 2013 00:04:49 -0700 (PDT)
Received: from mail-pb0-x22a.google.com (mail-pb0-x22a.google.com [IPv6:2607:f8b0:400e:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id E5AD611E80A2 for <ietf@ietf.org>; Fri, 26 Jul 2013 00:04:47 -0700 (PDT)
Received: by mail-pb0-f42.google.com with SMTP id un1so1720166pbc.1 for <ietf@ietf.org>; Fri, 26 Jul 2013 00:04:47 -0700 (PDT)
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:x-mailer :thread-index:content-language; bh=yqG3YK62ZjwCrETLmofOlv33WdObj7n53942c+43lO8=; b=HOYauqYazY9IMhUFmIBSC5cN6iVsH3RIYR7HbHxqkW5R2xgYwGKHFaHhVblf/NwLZ2 cJCMDMtkZKzgapViltIE4dDNGTdKMmkPsIFufu+rev1wr/ORIjVE/lJp91/bGttSO+xY aoNZ610WzX/uugAlB8eoR7S9B2bKHCI07UyBUIzeD0hSzxG2UiiHAgjwHHzZ7gvuBt7i tBc7rfHUoLaIbRTSmEgbRkRssU0yjbCjzNm5zHeBuAXUr/svuIqhu93tHv5fbYaOZOnF 7Uu0yxfags/eg2M6rop0OiAMq7R4JA4d7ildF7NAP00hKDybrMAcLGqDgBKMThtjrFwE BOig==
X-Received: by 10.68.210.103 with SMTP id mt7mr51875083pbc.179.1374822287485;  Fri, 26 Jul 2013 00:04:47 -0700 (PDT)
Received: from PC ([114.248.234.99]) by mx.google.com with ESMTPSA id mr3sm58353216pbb.27.2013.07.26.00.04.44 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Fri, 26 Jul 2013 00:04:46 -0700 (PDT)
From: "Leaf Yeh" <leaf.yeh.sdo@gmail.com>
To: "'Hui Deng'" <denghui02@gmail.com>, "'George, Wes'" <wesley.george@twcable.com>
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com>	<0B65E3C66FCF4F459F93A1A5767BB35A034AD02C@lhreml514-mbx>	<alpine.DEB.2.00.1307111201190.8891@uplift.swm.pp.se>	<CANF0JMAuRm2c+-L0SzD902vAt4gdsWqawVMt6=MLkkNkmza6RQ@mail.gmail.com>	<51DEE55A.4050402@gmail.com>	<2671C6CDFBB59E47B64C10B3E0BD5923043722F56B@PRVPEXVS15.corp.twcable.com> <CANF0JMBbEhW25+CEZYgWCZ7PB=8gMJy2VzvkYyJ0V-SBTe39CQ@mail.gmail.com>
In-Reply-To: <CANF0JMBbEhW25+CEZYgWCZ7PB=8gMJy2VzvkYyJ0V-SBTe39CQ@mail.gmail.com>
Subject: RE: Regarding call Chinese names
Date: Fri, 26 Jul 2013 15:04:40 +0800
Message-ID: <51f21f8e.a37d440a.7e71.35f9@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac6A8z0NXimIBqKsTIO1AWkVmKqGAgI2bRSA
Content-Language: zh-cn
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jul 2013 07:04:50 -0000

Hui,

I bet you are wrong this time. :-)

George, Wes should be Mr. Wesley GEORGE of Time Warner Cable.=20


Best Regards,
Leaf



From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of =
Hui
Deng
Sent: Monday, July 15, 2013 8:36 AM
To: George, Wes
Cc: ietf@ietf.org
Subject: Re: Regarding call Chinese names

I guess that George is your given name. Wes is your family name. Hope I =
am
not wrong.:)
=A0
-Hui

2013/7/11 George, Wes <wesley.george@twcable.com>
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf =
Of
> Melinda Shore

> I agree
> that this is probably not appropriate for publication as an RFC
> but it would certainly be useful to find someplace for it in the
> wiki. =A0The chairs wiki might be an option but I think it's of
> broader interest and use.
>
> Melinda
[WEG] I think writing language documentation isn't really a good use of =
IETF
resources, even at an individual level, because neither the problem nor =
the
knowledge necessary to address it is specific to the IETF, nor is the
problem limited to Mandarin participants. As others have noted, this is =
just
one of many languages represented by IETFers that we'd have to treat
similarly.
Further, an I-D is not a particularly useful format in which to present =
the
info. Raw text in the form of "$phoneme as in $English_word" may not =
always
be helpful, especially to nonnative English speakers who now have to =
work
through two layers of pronunciation. =A0Being able to click on a button =
to
hear sample pronunciations, especially in the case of words where tones
matter, is very helpful.

So if pronunciation guides end up in the Wiki or the Tao or some other =
yet
to be written Diversity and Cultural guide hosted within IETF, I think =
it's
more useful to simply reference things already extant instead of =
generating
our own. Those representing the language in question could certainly =
help us
to source and vet the information, but that's much quicker and more
efficient than writing it themselves.
Protocol reuse, hurray! :-)
e.g.
http://mandarin.about.com/od/pronunciation/a/How-To-Pronounce-Mandarin-Ch=
ine
se.htm
http://en.wikibooks.org/wiki/Japanese/Pronunciation
http://en.wikipedia.org/wiki/Swedish_phonology

To be clear, I'm not saying that this doesn't expose a real problem, and =
the
draft certainly drew attention to it, but I also don't think that more
documentation will solve it, especially since the information is already
readily available in more accessible formats. I think what you'll find =
is
that there are two types of folks (in IETF and generally) - those who =
see an
attempt at proper pronunciation and cultural awareness as important and
worth making extra effort to learn proactively, and those who believe =
that
if it's an issue, the person on the receiving end will correct them when
they get it wrong (and hopefully not repeat the mistake).
Not making a value judgment on either, merely an observation.

Thanks
Wes George

PS: guess which one is my given name and which my surname? Even native
English speakers aren't immune from name confusion. :-)


Anything below this line has been added by my company's mail server, I =
have
no control over it.
-----------------

This E-mail and any of its attachments may contain Time Warner Cable
proprietary information, which is privileged, confidential, or subject =
to
copyright belonging to Time Warner Cable. This E-mail is intended solely =
for
the use of the individual or entity to which it is addressed. If you are =
not
the intended recipient of this E-mail, you are hereby notified that any
dissemination, distribution, copying, or action taken in relation to the
contents of and attachments to this E-mail is strictly prohibited and =
may be
unlawful. If you have received this E-mail in error, please notify the
sender immediately and permanently delete the original and any copy of =
this
E-mail and any printout.



From tjc@ecs.soton.ac.uk  Fri Jul 26 00:45:39 2013
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A6EF21F8456 for <ietf@ietfa.amsl.com>; Fri, 26 Jul 2013 00:45:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[AWL=-0.698, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2M12KfeQR1l4 for <ietf@ietfa.amsl.com>; Fri, 26 Jul 2013 00:45:38 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 8690C21F9263 for <ietf@ietf.org>; Fri, 26 Jul 2013 00:45:35 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost.ecs.soton.ac.uk [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r6Q7jTbU024140; Fri, 26 Jul 2013 08:45:29 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r6Q7jTbU024140
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1374824730; bh=RDyNRALQzRQvHhn5emttHNg51Ec=; h=References:Mime-Version:In-Reply-To:Cc:From:Subject:Date:To; b=XcrV12HrEF75wfoDUtUKj9ufutu24DO4V/wx2GuYKNfG6Ahfu9xSGLPyXPTIGNxXu Vh7Fx+A5Eo65BVVtV9oaMwjjF79HvJjOozNv5RLR/aG6A0VB+f1vfUkSWf0OlyNmeb gGU1vM/d1xAI74T5BrBrhprfBnEJqg7sFy2sE+vg=
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 p6P8jY0544501398sW ret-id none; Fri, 26 Jul 2013 08:45:30 +0100
Received: from [192.168.1.101] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r6Q7jOiL015657 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 26 Jul 2013 08:45:25 +0100
References: <A6B9C627-A141-416B-AB39-469FDA86A875@ietf.org> <2129CC69EEF207CADC2421AC@JcK-HP8200.jck.com> <CADnDZ89ZnoL0eW=dZBBYLCVRSEvx3fz4hVXvhU4os88Cgh8vvw@mail.gmail.com> <BF486EEC-36A7-4363-B365-57939A2C309B@ecs.soton.ac.uk>
Mime-Version: 1.0 (1.0)
In-Reply-To: <CADnDZ89ZnoL0eW=dZBBYLCVRSEvx3fz4hVXvhU4os88Cgh8vvw@mail.gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|99389fc9a2867355f79896409d5c5b34p6P8jY03tjc|ecs.soton.ac.uk|BF486EEC-36A7-4363-B365-57939A2C309B@ecs.soton.ac.uk>
X-Mailer: iPad Mail (10B329)
From: Tim Chown <tjc@ecs.soton.ac.uk>
Subject: Re: BOF posters in the welcome reception
Date: Fri, 26 Jul 2013 08:45:26 +0100
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p6P8jY054450139800; tid=p6P8jY0544501398sW; 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: r6Q7jTbU024140
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: John C Klensin <john-ietf@jck.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jul 2013 07:45:39 -0000

On 26 Jul 2013, at 07:36, Abdussalam Baryun <abdussalambaryun@gmail.com> wro=
te:

> On 7/24/13, John C Klensin <john-ietf@jck.com> wrote:
>>=20
>> --On Wednesday, July 24, 2013 09:22 +0300 IETF Chair
>> <chair@ietf.org> wrote:
>>=20
>>> I wanted to let you know about an experiment we are trying out
>>> in Berlin.
>>> ...
>>> But we want as many people as possible to become involved in
>>> these efforts, or at least provide their feedback during the
>>> week. So we have given an opportunity for the BOFs to display
>>> a poster in the Welcome Reception (Sunday 5pm to 7pm). If you
>>> are attending the reception, take a look at the posters and
>>> look for topics that interest you.
>=20
> What about each poster state which WG/RFCs it is mostly
> depending-on/related (if applicable), this can make an easier way to
> know if I am interested or should be interested.

The poster deadline passed some time ago. The easiest way to decide if you'r=
e interested though is to read the poster, assuming it is well-written :)

The conference-style poster idea came up quite late this year. It's a good i=
dea, and is hopefully something that can be improved for IETF88 and beyond. =
 I suspect the idea arose from IETF87 having an unusually high number of BOFs=
.

Tim

From leaf.yeh.sdo@gmail.com  Fri Jul 26 00:57:54 2013
Return-Path: <leaf.yeh.sdo@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D49221F84E3 for <ietf@ietfa.amsl.com>; Fri, 26 Jul 2013 00:57:54 -0700 (PDT)
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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AfS8RAgN6kcZ for <ietf@ietfa.amsl.com>; Fri, 26 Jul 2013 00:57:53 -0700 (PDT)
Received: from mail-pa0-x230.google.com (mail-pa0-x230.google.com [IPv6:2607:f8b0:400e:c03::230]) by ietfa.amsl.com (Postfix) with ESMTP id DA55821F84B6 for <ietf@ietf.org>; Fri, 26 Jul 2013 00:57:53 -0700 (PDT)
Received: by mail-pa0-f48.google.com with SMTP id kp13so1748554pab.35 for <ietf@ietf.org>; Fri, 26 Jul 2013 00:57:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-type:content-transfer-encoding:x-mailer:thread-index :content-language; bh=MpS/nnJ4Uwm528eRxMqYIEKVoWqzys4LByKrk/rgvpY=; b=ss7x+tTxafZjqn+8DGf64eqrrN8VXmo8kCna89+54KpBd0rVtFZXRKHfsc0nC5ayXp 0oDBYPbUxbOWfSNYOgLGb7LF29z0uxbUZx3WBnW8rKVWkuCt8x9II0D1tKKTIpfugT+n tBLwYHhKsOC/bmT4Tu5qdpFHToC6Ly/dvZFzBQwGRlLqkLtDDvlAwIcEKOQ8zPNFAuhs cRDGK6Q4yQvKsgCJQcxInL14lGVIQgFmk/oeFkBbQUduxd9QKlDbG3x5U+DgbKzT9y8e 82PQI6S4CSkfpqdpkdILWPixS+g1ujM9/xGxv8H4xobO1eaK4DAzYhGZ9tQoPic1kNq1 yPhg==
X-Received: by 10.66.154.195 with SMTP id vq3mr25990808pab.69.1374825473641; Fri, 26 Jul 2013 00:57:53 -0700 (PDT)
Received: from PC ([114.248.234.99]) by mx.google.com with ESMTPSA id dg3sm58612989pbc.24.2013.07.26.00.57.51 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Fri, 26 Jul 2013 00:57:53 -0700 (PDT)
From: "Leaf Yeh" <leaf.yeh.sdo@gmail.com>
To: "'Simon Perreault'" <simon.perreault@viagenie.ca>, <ietf@ietf.org>
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com> <51DEB9F2.9040405@viagenie.ca>
In-Reply-To: <51DEB9F2.9040405@viagenie.ca>
Subject: RE: Regarding call Chinese names
Date: Fri, 26 Jul 2013 15:57:48 +0800
Message-ID: <51f22c01.83b3440a.7496.2d61@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac5+PrWXKVU5rlN2T6OPa2ssNm2C4ALloPiw
Content-Language: zh-cn
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jul 2013 07:57:54 -0000

Simon - I have a question: I think I've seen Chinese names written in =
both
orders. That is, sometimes "Hui Deng" will be written "Deng Hui". Am I
right? Does this happen often? What is the most common order?

To me, as a native Chinese, "Hui Deng" is written in English, while =
"Deng
Hui" is written in Pinyin (Chinese phonetic alphabet) .


Best Regards,
Leaf



-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
Simon Perreault
Sent: Thursday, July 11, 2013 9:58 PM
To: ietf@ietf.org
Subject: Re: Regarding call Chinese names

Le 2013-07-11 02:04, Hui Deng a =E9crit :
> We submitted two drafts to help people here to correctly call chinese=20
> people names:
>=20
> http://tools.ietf.org/html/draft-deng-call-chinese-names-00=20
>    http://tools.ietf.org/html/draft-zcao-chinese-pronounce-00

Very cool! Thanks for writing this!

I have a question: I think I've seen Chinese names written in both =
orders.
That is, sometimes "Hui Deng" will be written "Deng Hui". Am I right? =
Does
this happen often? What is the most common order? Is there a way to =
guess
what order a name is written in? Sometimes it's not easy for =
non-Sinophones
to know which part is the given name and which part is the family name.

Thanks,
Simon


From leaf.yeh.sdo@gmail.com  Fri Jul 26 00:58:31 2013
Return-Path: <leaf.yeh.sdo@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CCE321F8934 for <ietf@ietfa.amsl.com>; Fri, 26 Jul 2013 00:58:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.374
X-Spam-Level: 
X-Spam-Status: No, score=-1.374 tagged_above=-999 required=5 tests=[AWL=-1.225, BAYES_00=-2.599, MIME_CHARSET_FARAWAY=2.45]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zA988uEAmwrx for <ietf@ietfa.amsl.com>; Fri, 26 Jul 2013 00:58:29 -0700 (PDT)
Received: from mail-pa0-x22b.google.com (mail-pa0-x22b.google.com [IPv6:2607:f8b0:400e:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 9B9B221F87B7 for <ietf@ietf.org>; Fri, 26 Jul 2013 00:58:24 -0700 (PDT)
Received: by mail-pa0-f43.google.com with SMTP id hz10so1993544pad.16 for <ietf@ietf.org>; Fri, 26 Jul 2013 00:58:24 -0700 (PDT)
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:x-mailer :thread-index:content-language; bh=tHwBVzSUXuLVfAMexA0EpVPD3LkubC2Wld2Qv94QJXE=; b=QEzvrVxoGbzm5gy07V4lOIAHFkaMkQ5nDZntirCniyf6icomi17CBBDryKKnOMq3xs D+UYcaxWllMoyRcbXQETbvEsmPpxfRCbtdV5uryXST6iGHxh2Ov0ZFIbI+qaHsfZ+AgD mLSBQUtTq7oX3akuczXoUw2BL/9wL2eEn5T0OIqKSOHnd0rrEcwRi2xZ3cM+ucNt72HM qRQ0QmeEYJKYeOBm46dPnPO3dH6w10H/mQAOcOThjpxjR/mLCiQQZqryWcwgytr96wzL ibdcAqiGi9D2ha09ttUrxZRsRAsLgDC2eeMrfx/9keiI9tSaqSiMPxS8I7jtwuwB5pKC 7Aog==
X-Received: by 10.68.107.226 with SMTP id hf2mr52734761pbb.28.1374825504370; Fri, 26 Jul 2013 00:58:24 -0700 (PDT)
Received: from PC ([114.248.234.99]) by mx.google.com with ESMTPSA id aj3sm2150261pad.8.2013.07.26.00.58.21 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Fri, 26 Jul 2013 00:58:23 -0700 (PDT)
From: "Leaf Yeh" <leaf.yeh.sdo@gmail.com>
To: "'Cao,Zhen'" <zehn.cao@gmail.com>, "'Ted Hardie'" <ted.ietf@gmail.com>
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com>	<CA+9kkMDZoX0Eq4TcbpP=+YMPmq-F3CAGB1dSogYJa6V2F-irbQ@mail.gmail.com>	<CANF0JMCA+HQ7=xEXjDkgxLt2iqUj3Wdq_+2+KFsPg34a0m+nxQ@mail.gmail.com>	<CA+9kkMCqRL5R8v5RivjRkNHQtMFiKs3Rhva+X5NogMB6_qMaSQ@mail.gmail.com> <CAProHASRwM8-Nnd6rPsXtXk85Vb9gNeBshppFjUQxpnLTJsjDg@mail.gmail.com>
In-Reply-To: <CAProHASRwM8-Nnd6rPsXtXk85Vb9gNeBshppFjUQxpnLTJsjDg@mail.gmail.com>
Subject: RE: Regarding call Chinese names
Date: Fri, 26 Jul 2013 15:58:17 +0800
Message-ID: <51f22c1f.a3fe420a.6639.ffff8235@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac6B/2kVKk38BZIPRgCMuFBeoI154QHzZ48A
Content-Language: zh-cn
Cc: 'IETF Discussion' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jul 2013 07:58:31 -0000

a. I suppose Mr. Leung and Mr. Tung used Wade-Giles Romanization (or =
system)
for their name's spelling, which looks very popular outside China =
mainland
including Hong Kong, and inside China mainland before the year of 1958 =
when
Pinyin (Chinese phonetic alphabet) was published.=20

b. I believe Taiwanese has adopted Pinyin system for Chinese Character =
now,
but they used Wade-Giles system before.

c. Pinyin has been employed on the passport of China Mainland, but I =
don't
think they are friendly enough for people speaking English to pronounce. =
To
me, some Pinyin of Chinese character are just for spelling in English, =
and
are not feasible for the correct pronunciation.

d. Pinyin uses roman (or roughly English) characters to denote the =
sounds of
Chinese Character, but in the Chinese style, which always causes =
confusion
in pronunciation. Though the beginning lessons on Chinese language in =
the
preliminary school is on the Pinyin (or Phonetic alphabet of Chinese
Character), but the foreigner seldom gets chance to learn it. :-(


Best Regards,
Leaf



-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of =
Cao,
Zhen
Sent: Tuesday, July 16, 2013 4:35 PM
To: Ted Hardie
Cc: IETF Discussion
Subject: Re: Regarding call Chinese names

On Tue, Jul 16, 2013 at 12:04 AM, Ted Hardie <ted.ietf@gmail.com> wrote:
> On Sun, Jul 14, 2013 at 5:26 PM, Hui Deng <denghui02@gmail.com> wrote:
>>
>> Hi Ted,
>>
>> I did explain them in the 1st paragraph about minorities (not=20
>> mentioned that they could have two kids in mainland) anyway, I will=20
>> revise the title by adding "Chinese "Han" people", hope that will be=20
>> ok
>>
>> -Hui
>>
>>
>
> While it is always valuable to note national minorities, I believe you =

> missed the point.  In some territories, there are dialects of Chinese=20
> other than Mandarin and romanizations other than pinyin which are=20
> common and normatively correct.  For those Chinese people, your=20
> document does not apply.  As an example, the current chief executive=20
> of Hong Kong is properly called Leung Chun Ying (=C1=BA=D5=F1=D3=A2); =
his
> predecessor  in that role was Tung Chee Hwa (=B6=AD=BD=A8=C8A).   =
Similar situations
> arise in Taiwan and in many territories where Chinese people are=20
> themselves national minorities.

That's not Pinyin system. I have a question for you, do you think these
spellings are self pronounciable?

>
> Clarifying that your document is specific to the pinyin romanization=20
> is likely enough (since that romanization is based on Mandarin).

We actually clarify that in pinyin draft,
http://tools.ietf.org/id/draft-zcao-chinese-pronounce-01

Thanks,
caozhen


From housley@vigilsec.com  Fri Jul 26 01:32:57 2013
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8575721F84E3; Fri, 26 Jul 2013 01:32:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5M6rWRBqOUit; Fri, 26 Jul 2013 01:32:52 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 4E76721F84B6; Fri, 26 Jul 2013 01:32:52 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 36F0DF240BA; Fri, 26 Jul 2013 04:33:12 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id D9Qp7BNORf2b; Fri, 26 Jul 2013 04:32:38 -0400 (EDT)
Received: from dhcp-5419.meeting.ietf.org (dhcp-5419.meeting.ietf.org [130.129.84.25]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id F2B35F2407E; Fri, 26 Jul 2013 04:33:09 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Gen-ART Telechat review of draft-nandakumar-rtcweb-stun-uri-05
Date: Fri, 26 Jul 2013 04:32:47 -0400
Message-Id: <20C00550-72F4-41F4-979C-ECFBD7B9D789@vigilsec.com>
To: draft-nandakumar-rtcweb-stun-uri.all@tools.ietf.org
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
Cc: gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jul 2013 08:32:57 -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-nandakumar-rtcweb-stun-uri-05
Reviewer: Russ Housley
Review Date: 26-July-2013
IETF LC End Date: 16-Auguest-2013
IESG Telechat date: Unknown

Summary: This draft is basically ready for publication as a Standards Track
RFC, but a few questions should be answered.

This document is the specification of the syntax and semantics of the
Uniform Resource Identifier (URI) scheme for the Session Traversal
Utilities for NAT (STUN) protocol.

Major issues:

None.

Minor issues:

This document defines ABNF for IPv4 and IPv6 addresses.  It seems better
to do these by reference.  


From nkukich@verilan.com  Fri Jul 26 03:00:46 2013
Return-Path: <nkukich@verilan.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AFC621F8C9D for <ietf@ietfa.amsl.com>; Fri, 26 Jul 2013 03:00:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.598
X-Spam-Level: 
X-Spam-Status: No, score=-103.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kCfSleQrSew7 for <ietf@ietfa.amsl.com>; Fri, 26 Jul 2013 03:00:42 -0700 (PDT)
Received: from mail-pb0-f41.google.com (mail-pb0-f41.google.com [209.85.160.41]) by ietfa.amsl.com (Postfix) with ESMTP id 3AB4621F9011 for <ietf@ietf.org>; Fri, 26 Jul 2013 03:00:34 -0700 (PDT)
Received: by mail-pb0-f41.google.com with SMTP id rp16so1862673pbb.14 for <ietf@ietf.org>; Fri, 26 Jul 2013 03:00:34 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=from:content-type:subject:message-id:date:to:mime-version:x-mailer :x-gm-message-state; bh=oewwnPFR6YI5OSjIe15GVjOvtfxJkbwj310WihmyjsY=; b=KkP2L3sfWAo3OaTLPx06ywIQcVzreISwKLypKHNB5w88nxQXDq3pxkSEpVZAi/Trm1 NB1fpHdsOnngACZbgLjNZFeR5gLdyENVoCOyJUoDyBgN3qmrOnTj53C7dTFhwbyRFJsm yTjyYgnhpk8kMQ8gcyuAtbqoiMKr6VDzOCzNGf07qO++QMM41YJqXbuzG4psU8OHkk7z YBFrZUMYr1db9i771qH4yop/6YuIC8vZ+ZSSLDHQlpaNpcnGeH7eXdqf1HDXpKTzw7R3 Dhf8wQnmjaNQeZiq4GBmSkkhjOkBslVazxm1vf3otDcKuV+UB/TT3rowa4PpX/jGHN37 T1xw==
X-Received: by 10.68.129.39 with SMTP id nt7mr7472026pbb.178.1374832834632; Fri, 26 Jul 2013 03:00:34 -0700 (PDT)
Received: from ?IPv6:2001:df8::16:d8f2:da38:a0a1:bac2? ([2001:df8:0:16:d8f2:da38:a0a1:bac2]) by mx.google.com with ESMTPSA id iu7sm12487683pbc.8.2013.07.26.03.00.32 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 26 Jul 2013 03:00:33 -0700 (PDT)
From: Nick Kukich <nkukich@verilan.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_4AC528E4-63EE-474F-B50D-598CA181E5CD"
Subject: IETF87 Audio Streaming Info
Message-Id: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com>
Date: Fri, 26 Jul 2013 12:00:30 +0200
To: "ietf@ietf.org" <ietf@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
X-Gm-Message-State: ALoCoQnqT26FVPb4pMDS+pG7rG+pSHKBnCWdN0HnBAFCf9fS5k4Qk7Pop/51pXiQ/VUY43coRI3G
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jul 2013 10:00:46 -0000

--Apple-Mail=_4AC528E4-63EE-474F-B50D-598CA181E5CD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Greetings,

For those interested in monitoring sessions or participating remotely =
the
following information may prove useful.

For general remote participation including Meetecho support see:

http://www.ietf.org/meeting/87/remote-participation.html

-Audio Streaming-

All 8 parallel tracks at the IETF 87 meeting will be broadcast starting
with the commencement of working group sessions on Monday, July 29, 2013
at 0900 CEST (UTC+2) and continue until the close of sessions on Friday,
August 2nd.

Because we have been asked several times in the past, note that if you
wish to use the rooms that are being recorded for impromptu meeting
during unscheduled sessions or lunch breaks that you can invite remote
participants to tune in to the appropriate stream. Recording cannot be
guaranteed for unscheduled sessions. Conversely, it should never be
assumed that recording or observation is not occurring on open
microphones, they are after all connected to the Internet.

The links for streaming sources and the schedule are best retrieved from
the IETF tools agenda, which as per standard operating procedure will be
located here:

http://tools.ietf.org/agenda/87/=20
-Jabber/XMPP-

For information on IETF Jabber participation see:

http://www.ietf.org/jabber/index.html

or click on the Jabber links in the tools team agenda once you have a
properly configured jabber/xmpp messaging client.

-Webex-

Webex screen sharing participation is possible for a limited number of
sessions. Consult with your working-group chair or the secretariat for
more information.

-Ticketing-

For prompt access to the meeting trouble desk, the email address is:

mtd@ietf.org

For streaming related issues please send email to =
ietf-streaming@verilan.com  with info including the current time and =
affected streaming channel.

Nick Kukich
Senior Network Engineer
Verilan, Inc.
503.710.5115




--Apple-Mail=_4AC528E4-63EE-474F-B50D-598CA181E5CD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div>Greetings,</div><div><br></div><div>For those interested in =
monitoring sessions or participating remotely the</div><div>following =
information may prove useful.</div><div><br></div><div>For general =
remote participation including Meetecho support =
see:</div><div><br></div><div><a =
href=3D"http://www.ietf.org/meeting/87/remote-participation.html">http://w=
ww.ietf.org/meeting/87/remote-participation.html</a></div><div><br></div><=
div>-Audio Streaming-</div><div><br></div><div>All 8 parallel tracks at =
the IETF 87 meeting will be broadcast starting</div><div>with the =
commencement of working group sessions on Monday, July 29, =
2013</div><div>at 0900 CEST (UTC+2) and continue until the close of =
sessions on Friday,</div><div>August =
2nd.</div><div><br></div><div>Because we have been asked several times =
in the past, note that if you</div><div>wish to use the rooms that are =
being recorded for impromptu meeting</div><div>during unscheduled =
sessions or lunch breaks that you can invite =
remote</div><div>participants to tune in to the appropriate stream. =
Recording cannot be</div><div>guaranteed for unscheduled sessions. =
Conversely, it should never be</div><div>assumed that recording or =
observation is not occurring on open</div><div>microphones, they are =
after all connected to the Internet.</div><div><br></div><div>The links =
for streaming sources and the schedule are best retrieved =
from</div><div>the IETF tools agenda, which as per standard operating =
procedure will be</div><div>located here:</div><div><br></div><div><a =
href=3D"http://tools.ietf.org/agenda/87/">http://tools.ietf.org/agenda/87/=
</a>&nbsp;</div><div>-Jabber/XMPP-</div><div><br></div><div>For =
information on IETF Jabber participation =
see:</div><div><br></div><div><a =
href=3D"http://www.ietf.org/jabber/index.html">http://www.ietf.org/jabber/=
index.html</a></div><div><br></div><div>or click on the Jabber links in =
the tools team agenda once you have a</div><div>properly configured =
jabber/xmpp messaging =
client.</div><div><br></div><div>-Webex-</div><div><br></div><div>Webex =
screen sharing participation is possible for a limited number =
of</div><div>sessions. Consult with your working-group chair or the =
secretariat for</div><div>more =
information.</div><div><br></div><div>-Ticketing-</div><div><br></div><div=
>For prompt access to the meeting trouble desk, the email address =
is:</div><div><br></div><div><a =
href=3D"mailto:mtd@ietf.org">mtd@ietf.org</a></div><div><br></div><div>For=
 streaming related issues please send email to&nbsp;<a =
href=3D"mailto:ietf-streaming@verilan.com">ietf-streaming@verilan.com</a>&=
nbsp;&nbsp;with info including the current time and affected streaming =
channel.</div><div><br></div><div apple-content-edited=3D"true"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: =
normal; widows: 2; word-spacing: 0px; border-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; border-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; border-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; border-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; border-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; border-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><b>Nick =
Kukich</b></span></div><div style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; border-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><b>Senior =
Network Engineer</b></span></div><div style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; border-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">Verilan, =
Inc.</span></div><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; "><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: =
normal; widows: 2; word-spacing: 0px; border-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; =
">503.710.5115</span></div><div style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><br></div></span></div></span></div></span></div></span></div></span=
>
</div>
<br></body></html>=

--Apple-Mail=_4AC528E4-63EE-474F-B50D-598CA181E5CD--

From davearonson@gmail.com  Fri Jul 26 04:56:25 2013
Return-Path: <davearonson@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73C4921F93C4 for <ietf@ietfa.amsl.com>; Fri, 26 Jul 2013 04:56:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.252
X-Spam-Level: 
X-Spam-Status: No, score=0.252 tagged_above=-999 required=5 tests=[AWL=0.370,  BAYES_20=-0.74, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U53+l6I+YlsV for <ietf@ietfa.amsl.com>; Fri, 26 Jul 2013 04:56:24 -0700 (PDT)
Received: from mail-pa0-x22b.google.com (mail-pa0-x22b.google.com [IPv6:2607:f8b0:400e:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id A619D21F9346 for <ietf@ietf.org>; Fri, 26 Jul 2013 04:56:21 -0700 (PDT)
Received: by mail-pa0-f43.google.com with SMTP id hz10so2188653pad.16 for <ietf@ietf.org>; Fri, 26 Jul 2013 04:56:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type; bh=mZsQPnJ4BG/Eh6SmQLNX9I4H1Cqi8OhCR1Ath8dzAkw=; b=Fcbw1SKU2K+GkjzvHM3U48CpR+LuoTnulz62bIi9s8xgiUzMU1R9j6LCh6ZdInKjVH zizQafr4ZXyNOzi3zuqJ6Psftm2oa+LCoPH6gOj/eVfc3Czbnr8DGnMQZa6es8no0DZ7 /OdoGE86xAzLaBPiGCfNvCaFj11GW2eXMb/vIRTTZrMqHakfVEmqyHzIAG4syLib9Dn1 Uz0Bpu9hQRwAf0VQkc1uNtH+PIqnIwkK1E4iobzXoTWspflP5AB5MeGTK5kkIrCSqSKr 43583vql7a6zFmjEBSZefwFB/6ddXkaM+RxAxlnOMePJyBRWNIUaIlGp0o0S2V1azpNi nVLg==
X-Received: by 10.66.122.41 with SMTP id lp9mr54955126pab.6.1374839781159; Fri, 26 Jul 2013 04:56:21 -0700 (PDT)
MIME-Version: 1.0
Sender: davearonson@gmail.com
Received: by 10.68.29.135 with HTTP; Fri, 26 Jul 2013 04:55:40 -0700 (PDT)
In-Reply-To: <CADnDZ89ZnoL0eW=dZBBYLCVRSEvx3fz4hVXvhU4os88Cgh8vvw@mail.gmail.com>
References: <A6B9C627-A141-416B-AB39-469FDA86A875@ietf.org> <2129CC69EEF207CADC2421AC@JcK-HP8200.jck.com> <CADnDZ89ZnoL0eW=dZBBYLCVRSEvx3fz4hVXvhU4os88Cgh8vvw@mail.gmail.com>
From: Dave Aronson <ietf2dave@davearonson.com>
Date: Fri, 26 Jul 2013 07:55:40 -0400
X-Google-Sender-Auth: Hp_RdQaOx9yuzyGhu49YsuTvJuM
Message-ID: <CAHxKQih_iJwKot2ARepws0=OQMHVbkt5JQ9=jGXN-8qjgwqp8w@mail.gmail.com>
Subject: Re: BOF posters in the welcome reception
To: IETF Discussion <ietf@ietf.org>
Content-Type: text/plain; charset=UTF-8
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jul 2013 11:56:25 -0000

On Fri, Jul 26, 2013 at 2:36 AM, Abdussalam Baryun
<abdussalambaryun@gmail.com> wrote:

> How can I access the live discuss while remote?

Sheldon Cooper had a good idea:

  http://www.youtube.com/watch?v=S5LKXO9aCTc

that is becoming more real every day:

  http://www.forbes.com/sites/parmyolson/2013/06/27/rise-of-the-telepresence-robots/

;-)

-Dave

-- 
Dave Aronson, the T. Rex of Codosaurus LLC,
secret-cleared freelance software developer
taking contracts in or near NoVa or remote.
See information at http://www.Codosaur.us/.

From john-ietf@jck.com  Fri Jul 26 08:32:30 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 360A621F9A25; Fri, 26 Jul 2013 08:32:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yzy7i2VxbFjW; Fri, 26 Jul 2013 08:32:24 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 48BF221F9A17; Fri, 26 Jul 2013 08:32:24 -0700 (PDT)
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 1V2k0E-0009db-HW; Fri, 26 Jul 2013 11:32:22 -0400
Date: Fri, 26 Jul 2013 11:32:17 -0400
From: John C Klensin <john-ietf@jck.com>
To: ietf@ietf.org
Subject: Remote participants, newcomers, and tutorials (was: IETF87 Audio Streaming Info)
Message-ID: <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com>
In-Reply-To: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.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: edu-team@ietf.org, iesg@ietf.org, rfc-editor@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jul 2013 15:32:30 -0000

Hi.

For a newcomer or someone expecting to write I-Ds, some of the
most important sessions at the IETF are the various Sunday
afternoon tutorials and introductions.  Many of them are (or
should be) of as much interest to remote participants as to f2f
attendees.   Until and unless a newcomer's tutorial can be
prepared that is focused on remote participants, even that
session should be of interest.

For this particular meeting all of the following seem relevant
to at least some remote participants:

	Newcomers' Orientation       
	Tools for Creating I-Ds and RFCs         
	IAOC Overview Session     
	Multipath TCP         
	Applying IP Flow Information Export (IPFIX) to Network
Measurement and Management

So...

(1) The note below strongly implies that none of those sessions
are being audiocast.    Why not and can that be fixed?

(2) There is no hint on the agenda or tools agenda about
availability of presentation and related materials (slides,
etc.) for those sessions.  Do those materials not exist?  I
know, but a newcomer or remote participant might not, that I can
find some tutorials by going to the IETF main page and going to
"Tutorial" under "Resources", but I have no idea which of those
links actually reflects what will be presented on Sunday.
Assuming the presentation materials do exist for at least
several of the sessions, finding them is much like the situation
with subscribing to the 87all list.  It should no involve a
treasure hunt at which only very experienced IETF participants
can be expected to succeed.  

Specific suggestions:

(i) Let's get these open Sunday sessions audiocast and/or
available over Meetecho or WebEx.  If that is impossible for
IETF 87, it should be a priority for IETF 88 and later.

(ii) If there are presentation materials available, links from
the tools agenda and an announcement to IETF-Announce as to
where to find them would be desirable.

(iii) If presentation materials are not available, why not?
And, more important, can this be made a requirement for IETF 88
and beyond?

thanks,
    john



--On Friday, July 26, 2013 12:00 +0200 Nick Kukich
<nkukich@verilan.com> wrote:

> Greetings,
> 
> For those interested in monitoring sessions or participating
> remotely the following information may prove useful.
>...
> All 8 parallel tracks at the IETF 87 meeting will be broadcast
> starting with the commencement of working group sessions on
> Monday, July 29, 2013 at 0900 CEST (UTC+2) and continue until
> the close of sessions on Friday, August 2nd.
>...


From gsalguei@cisco.com  Fri Jul 26 08:59:53 2013
Return-Path: <gsalguei@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6B6D21F9A59 for <ietf@ietfa.amsl.com>; Fri, 26 Jul 2013 08:59:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X6WFCu48yZRH for <ietf@ietfa.amsl.com>; Fri, 26 Jul 2013 08:59:49 -0700 (PDT)
Received: from av-tac-rtp.cisco.com (av-tac-rtp.cisco.com [64.102.19.209]) by ietfa.amsl.com (Postfix) with ESMTP id 7A5B821F9993 for <ietf@ietf.org>; Fri, 26 Jul 2013 08:59:49 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from chook.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r6QFxkjq004209 for <ietf@ietf.org>; Fri, 26 Jul 2013 11:59:46 -0400 (EDT)
Received: from rtp-gsalguei-8915.cisco.com (rtp-gsalguei-8915.cisco.com [10.116.132.54]) by chook.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r6QFxjRt026992; Fri, 26 Jul 2013 11:59:45 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Gen-ART Telechat review of draft-nandakumar-rtcweb-stun-uri-05
From: Gonzalo Salgueiro <gsalguei@cisco.com>
In-Reply-To: <20C00550-72F4-41F4-979C-ECFBD7B9D789@vigilsec.com>
Date: Fri, 26 Jul 2013 11:59:45 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <DA49ECB6-0F50-4C15-9EAB-A5019B00DD1C@cisco.com>
References: <20C00550-72F4-41F4-979C-ECFBD7B9D789@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.1508)
Cc: gen-art@ietf.org, ietf@ietf.org, draft-nandakumar-rtcweb-stun-uri.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jul 2013 15:59:53 -0000

Hi Russ -=20

Thanks for the review.  My response is inline to your only review =
comment...

On Jul 26, 2013, at 4:32 AM, Russ Housley <housley@vigilsec.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
>=20
> Please resolve these comments along with any other Last Call comments =
you
> may receive.
>=20
> Document: draft-nandakumar-rtcweb-stun-uri-05
> Reviewer: Russ Housley
> Review Date: 26-July-2013
> IETF LC End Date: 16-Auguest-2013
> IESG Telechat date: Unknown
>=20
> Summary: This draft is basically ready for publication as a Standards =
Track
> RFC, but a few questions should be answered.
>=20
> This document is the specification of the syntax and semantics of the
> Uniform Resource Identifier (URI) scheme for the Session Traversal
> Utilities for NAT (STUN) protocol.
>=20
> Major issues:
>=20
> None.
>=20
> Minor issues:
>=20
> This document defines ABNF for IPv4 and IPv6 addresses.  It seems =
better
> to do these by reference. =20

This document and draft-petithuguenin-behave-turn-uris are being =
progressed in parallel and share common elements. Duplicating the =
<IPv6address> and <IPv4address> ABNF production rules from RFC3986 is =
one of those common elements.  To provide you with a bit of background, =
this duplication was done intentionally and was done as a result of =
comments during uri-review of the original TURN URI draft back in 2009.  =
Here is the reference to the response to the relevant thread where this =
was decided:

https://www.ietf.org/mail-archive/web/behave/current/msg07380.html

Doing this knowingly spurred the addition of the Design Note you see =
here in the TURN URI draft:

=
http://tools.ietf.org/html/draft-petithuguenin-behave-turn-uris-05#appendi=
x-B

It was an oversight not to add that same Design Note to the STUN URI =
draft as well.  The next version will include an updated version of that =
Design Note with specific reference to the duplicated ABNF production =
rules (i.e., <IPv6address>, <IPv4address>, etc.).

Would that satisfactorily address your comment?

Cheers,

Gonzalo








From bclaise@cisco.com  Fri Jul 26 09:10:57 2013
Return-Path: <bclaise@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABCA911E80F4 for <ietf@ietfa.amsl.com>; Fri, 26 Jul 2013 09:10:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.455
X-Spam-Level: 
X-Spam-Status: No, score=-10.455 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NgzOqZWGwk4K for <ietf@ietfa.amsl.com>; Fri, 26 Jul 2013 09:10:53 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 263E421F9477 for <ietf@ietf.org>; Fri, 26 Jul 2013 09:10:48 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r6QGAm0A000865; Fri, 26 Jul 2013 18:10:48 +0200 (CEST)
Received: from [10.61.111.237] (dhcp-10-61-111-237.cisco.com [10.61.111.237]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r6QGAHsl017168; Fri, 26 Jul 2013 18:10:37 +0200 (CEST)
Message-ID: <51F25148.8050107@cisco.com>
Date: Fri, 26 Jul 2013 12:36:56 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: BOF posters in the welcome reception
References: <A6B9C627-A141-416B-AB39-469FDA86A875@ietf.org> <2129CC69EEF207CADC2421AC@JcK-HP8200.jck.com>
In-Reply-To: <2129CC69EEF207CADC2421AC@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jul 2013 16:10:57 -0000

John,
>
> --On Wednesday, July 24, 2013 09:22 +0300 IETF Chair
> <chair@ietf.org> wrote:
>
>> I wanted to let you know about an experiment we are trying out
>> in Berlin.
>> ...
>> But we want as many people as possible to become involved in
>> these efforts, or at least provide their feedback during the
>> week. So we have given an opportunity for the BOFs to display
>> a poster in the Welcome Reception (Sunday 5pm to 7pm). If you
>> are attending the reception, take a look at the posters and
>> look for topics that interest you. Someone running the BOF is
>> also likely standing by, so you can also get directly involved
>> in discussions, sign up to help, etc. We hope that this helps
>> you all network with others even more :-)
> In the interest of encouraging remote participation and
> involvement in those BOFs, could these posters be made available
> online before the reception?
I'm not sure that those posters will/should contain more information 
than what http://trac.tools.ietf.org/bof/trac/wiki contains.
So I'm questioning whether making those posters available online before 
the meeting, or even in the meeting minutes (to answer your next 
question) is that useful.

Let me explain what the targeted audience is for those posters.
It's not intended for the people who know about a specific BoF and plan 
on participating.
It's intended for people who have not prepared for a specific BoF, but 
just come to listen to it, and in the end, go to mic. to provide some 
useful feedback: "pay attention to this!", "similar work was done ...", 
"don't forget that ...", "don't forget OPS" ;-)

Talking about my experience now, it's only now that I'm an IESG member 
that I know what the BoFs are about before the IETF week. In the past, I 
would look at the agenda early in the week, and based on the BoF 
name/acronym (yes, nothing more), I would decide to attend a specific 
BoF. However, if I would discuss the BoF topic for just a minute or two, 
I could quickly decide whether I'm interested and whether I could add 
some value to a BoF. This discussion generally took place at the welcome 
reception. This is "this minute or two discussion" that posters at the 
welcome reception should facilitate, thanks to the person standing next 
to the poster.

Sure, everything is on the web, or sent to a mailing list, but we have 
way too many emails already.

Regards, Benoit
> Will they eventually be
> incorporated into the minutes?
>
> And, incidentally, is there a way for remote participants to
> sign up for one or both meeting-related mailing lists without
> registering (or using a "remote participation registration"
> mechanism, which would be my preference for other reasons)?
>
> thanks,
>     john
>
>
>
>


From amorris@amsl.com  Fri Jul 26 10:26:42 2013
Return-Path: <amorris@amsl.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F11821F9B3F for <ietf@ietfa.amsl.com>; Fri, 26 Jul 2013 10:26:42 -0700 (PDT)
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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ttDOsT0UDfUc for <ietf@ietfa.amsl.com>; Fri, 26 Jul 2013 10:26:38 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.21]) by ietfa.amsl.com (Postfix) with ESMTP id 433BF21F9B0D for <ietf@ietf.org>; Fri, 26 Jul 2013 10:26:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id 18F8F9FB82; Fri, 26 Jul 2013 10:25:16 -0700 (PDT)
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 Qmq81o84XfdK; Fri, 26 Jul 2013 10:25:16 -0700 (PDT)
Received: from [10.32.164.34] (unknown [31.221.87.87]) by c9a.amsl.com (Postfix) with ESMTPSA id 32CE19FB80; Fri, 26 Jul 2013 10:25:15 -0700 (PDT)
Subject: Re: BOF posters in the welcome reception
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Alexa Morris <amorris@amsl.com>
In-Reply-To: <51F25148.8050107@cisco.com>
Date: Fri, 26 Jul 2013 10:26:35 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <4EDB8AE2-218D-43EA-86D1-5E98791CB8A6@amsl.com>
References: <A6B9C627-A141-416B-AB39-469FDA86A875@ietf.org> <2129CC69EEF207CADC2421AC@JcK-HP8200.jck.com> <51F25148.8050107@cisco.com>
To: John C Klensin <john-ietf@jck.com>, IETF-Discussion list <ietf@ietf.org>
X-Mailer: Apple Mail (2.1085)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jul 2013 17:26:42 -0000

PDFs of all received BoF posters have been uploaded to the Meeting =
Materials page for those who are interested: =
https://datatracker.ietf.org/meeting/87/materials.html.

Regards,
Alexa

On Jul 26, 2013, at 3:36 AM, Benoit Claise wrote:

> John,
>>=20
>> --On Wednesday, July 24, 2013 09:22 +0300 IETF Chair
>> <chair@ietf.org> wrote:
>>=20
>>> I wanted to let you know about an experiment we are trying out
>>> in Berlin.
>>> ...
>>> But we want as many people as possible to become involved in
>>> these efforts, or at least provide their feedback during the
>>> week. So we have given an opportunity for the BOFs to display
>>> a poster in the Welcome Reception (Sunday 5pm to 7pm). If you
>>> are attending the reception, take a look at the posters and
>>> look for topics that interest you. Someone running the BOF is
>>> also likely standing by, so you can also get directly involved
>>> in discussions, sign up to help, etc. We hope that this helps
>>> you all network with others even more :-)
>> In the interest of encouraging remote participation and
>> involvement in those BOFs, could these posters be made available
>> online before the reception?
> I'm not sure that those posters will/should contain more information =
than what http://trac.tools.ietf.org/bof/trac/wiki contains.
> So I'm questioning whether making those posters available online =
before the meeting, or even in the meeting minutes (to answer your next =
question) is that useful.
>=20
> Let me explain what the targeted audience is for those posters.
> It's not intended for the people who know about a specific BoF and =
plan on participating.
> It's intended for people who have not prepared for a specific BoF, but =
just come to listen to it, and in the end, go to mic. to provide some =
useful feedback: "pay attention to this!", "similar work was done ...", =
"don't forget that ...", "don't forget OPS" ;-)
>=20
> Talking about my experience now, it's only now that I'm an IESG member =
that I know what the BoFs are about before the IETF week. In the past, I =
would look at the agenda early in the week, and based on the BoF =
name/acronym (yes, nothing more), I would decide to attend a specific =
BoF. However, if I would discuss the BoF topic for just a minute or two, =
I could quickly decide whether I'm interested and whether I could add =
some value to a BoF. This discussion generally took place at the welcome =
reception. This is "this minute or two discussion" that posters at the =
welcome reception should facilitate, thanks to the person standing next =
to the poster.
>=20
> Sure, everything is on the web, or sent to a mailing list, but we have =
way too many emails already.
>=20
> Regards, Benoit
>> Will they eventually be
>> incorporated into the minutes?
>>=20
>> And, incidentally, is there a way for remote participants to
>> sign up for one or both meeting-related mailing lists without
>> registering (or using a "remote participation registration"
>> mechanism, which would be my preference for other reasons)?
>>=20
>> thanks,
>>    john
>>=20
>>=20
>>=20
>>=20
>=20

----------
Alexa Morris / Executive Director / IETF
48377 Fremont Blvd., Suite 117, Fremont, CA  94538
Phone: +1.510.492.4089 / Fax: +1.510.492.4001
Email: amorris@amsl.com

Managed by Association Management Solutions (AMS)
Forum Management, Meeting and Event Planning
www.amsl.com <http://www.amsl.com/>


From ted.ietf@gmail.com  Fri Jul 26 10:50:59 2013
Return-Path: <ted.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 113EB11E8126 for <ietf@ietfa.amsl.com>; Fri, 26 Jul 2013 10:50:59 -0700 (PDT)
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=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xRhXFRE44PTC for <ietf@ietfa.amsl.com>; Fri, 26 Jul 2013 10:50:58 -0700 (PDT)
Received: from mail-ob0-x230.google.com (mail-ob0-x230.google.com [IPv6:2607:f8b0:4003:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id ED22011E8125 for <ietf@ietf.org>; Fri, 26 Jul 2013 10:50:57 -0700 (PDT)
Received: by mail-ob0-f176.google.com with SMTP id v19so4768866obq.7 for <ietf@ietf.org>; Fri, 26 Jul 2013 10:50:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=OOMKid49shYnimPIJ70DKYvj1NXAcU3bk4Gc6KtGuhE=; b=vJVTedVvg1YBgYx1tDuvcw+Vixfx6dLCmE1eIy+Y8cUt3c0SYj1dWBzDryjd7bbi6r ZuBshtst4nK3TaWu8V+cxAGqvfdzGkq0cZK9uiWb+OmPhnxaRdZsm2uRopNJonWptnXW n5K/cpxZqoFcBnDur3iJagCSpE6Jo+dTrUW09LcOrLNGRnu+sGgolANZ+xEx3zsYn+6e mqgRWyjrIpZbmqCRDqzbLGGCyaT+e7Uk2bBQjJ4ZxAQjGK5yzS2A64ptq3s48MInVUoY MtqRGl1o+zqt68Qv9jseS+/Pwmk++1oIu5EhxK1Spn0zsmj5T25/XrM5aVt9XWNfGm9Y eYjQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=OOMKid49shYnimPIJ70DKYvj1NXAcU3bk4Gc6KtGuhE=; b=d37D6zegrZwN+26dbUo+EVNkz83dGojoV8wmE+rIUrf5d5qwxPkHQglc+7nRiGPQ5r 88imBKvIUd1kcUXJBF5raNQTkdoAXgKi/NLx5+UQHRkKYSSJcL8A2lIvti/ruBi9gwGj O2nKUtmr17VSnQW19BLsf6/IAdzwzUZBAul6htkEOBHc0Zld4A+EkfAM6QydYYwqrjaN SHGEhthRQbO0yJ4ITNtYVuzDn2NaneCjXlxeeWpa26EMvXZx6KvI1J5bwQM9DBYHVM3r hnxoYtAnZG/ptmzVefDuOQXQGHEwHNA8CcYJ4akSXubW+kjNLYUfJXXf8KsVzsGtcaVH boFg==
MIME-Version: 1.0
X-Received: by 10.50.153.49 with SMTP id vd17mr1198112igb.22.1374861057361; Fri, 26 Jul 2013 10:50:57 -0700 (PDT)
Received: by 10.42.29.202 with HTTP; Fri, 26 Jul 2013 10:50:57 -0700 (PDT)
In-Reply-To: <51f22c1f.a3fe420a.6639.ffff8235@mx.google.com>
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com> <CA+9kkMDZoX0Eq4TcbpP=+YMPmq-F3CAGB1dSogYJa6V2F-irbQ@mail.gmail.com> <CANF0JMCA+HQ7=xEXjDkgxLt2iqUj3Wdq_+2+KFsPg34a0m+nxQ@mail.gmail.com> <CA+9kkMCqRL5R8v5RivjRkNHQtMFiKs3Rhva+X5NogMB6_qMaSQ@mail.gmail.com> <CAProHASRwM8-Nnd6rPsXtXk85Vb9gNeBshppFjUQxpnLTJsjDg@mail.gmail.com> <51f22c1f.a3fe420a.6639.ffff8235@mx.google.com>
Date: Fri, 26 Jul 2013 10:50:57 -0700
Message-ID: <CA+9kkMC1fGLmLnVVE9o+p26syJSmc-hfaVQhvu4oRz+9QzWnkw@mail.gmail.com>
Subject: Re: Regarding call Chinese names
From: Ted Hardie <ted.ietf@gmail.com>
To: Leaf Yeh <leaf.yeh.sdo@gmail.com>
Content-Type: multipart/alternative; boundary=089e014954bef0918c04e26dc867
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jul 2013 17:50:59 -0000

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

On Fri, Jul 26, 2013 at 12:58 AM, Leaf Yeh <leaf.yeh.sdo@gmail.com> wrote:

> a. I suppose Mr. Leung and Mr. Tung used Wade-Giles Romanization (or
> system)
> for their name's spelling, which looks very popular outside China mainlan=
d
> including Hong Kong, and inside China mainland before the year of 1958 wh=
en
> Pinyin (Chinese phonetic alphabet) was published.
>
>
Wade-Giles is a romanization system for Mandarin, not Cantonese.  The Yale
romanization for Cantonese developed by Parker Po-fei Huang and the
jyutping  (=E7=B2=B5=E6=8B=BC) are more likely sources for Cantonese names =
which use a
codified romanization system (jyutping being more recent).  Many names use
folk romanizations, rather than following a specific system.

regards,

Ted Hardie

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

On Fri, Jul 26, 2013 at 12:58 AM, Leaf Yeh <span dir=3D"ltr">&lt;<a href=3D=
"mailto:leaf.yeh.sdo@gmail.com" target=3D"_blank">leaf.yeh.sdo@gmail.com</a=
>&gt;</span> wrote:<br><div class=3D"gmail_quote"><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex">
a. I suppose Mr. Leung and Mr. Tung used Wade-Giles Romanization (or system=
)<br>
for their name&#39;s spelling, which looks very popular outside China mainl=
and<br>
including Hong Kong, and inside China mainland before the year of 1958 when=
<br>
Pinyin (Chinese phonetic alphabet) was published.<br>
<br></blockquote><div><br>Wade-Giles is a romanization system for Mandarin,=
 not Cantonese.=C2=A0 The Yale romanization for Cantonese developed by Park=
er Po-fei Huang and the jyutping=C2=A0 (<span lang=3D"zh-Hant">=E7=B2=B5=E6=
=8B=BC) are more likely sources for Cantonese names which use a codified ro=
manization system (jyutping being more recent).=C2=A0 Many names use folk r=
omanizations, rather than following a specific system.<br>
<br>regards,<br><br>Ted Hardie<br></span>=C2=A0<br></div></div>

--089e014954bef0918c04e26dc867--

From sm@resistor.net  Fri Jul 26 11:38:19 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A85BC11E8129; Fri, 26 Jul 2013 11:38:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.436
X-Spam-Level: 
X-Spam-Status: No, score=-102.436 tagged_above=-999 required=5 tests=[AWL=0.163, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mckkMcuchaMx; Fri, 26 Jul 2013 11:38:19 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 101A311E80FB; Fri, 26 Jul 2013 11:38:19 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r6QIcAlv028907; Fri, 26 Jul 2013 11:38:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1374863897; bh=2mz60fi0NX0a2JFdK8gWFKdN2f82dNtR7SHSaI0h4qI=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=dBPrzu2ovyf6KkEc2qCge3mypI6tgeaXFiSIP6acoCawrvN2d3TfrsIC+czc0kUfR dDM4xbbE9KCITNmErY0X8C6b9ZVUkGzrp3KQGYZuBBPd5G+QkB+jKmy5OdiNXmVyJK vgvp6tTI414J7ojQOlpcz11oJ1/wRlYFuGBEOaCM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1374863897; i=@resistor.net; bh=2mz60fi0NX0a2JFdK8gWFKdN2f82dNtR7SHSaI0h4qI=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=3A8/CRd4S6ohdepPWUkXs7BZdKZsyDjgJrGgTGR8LhVcaW5aPWkJwNBWEb1UDWbZD LSesB1MgYIHh6uJsDVhNDip3zzlKcyxn15QY9eNArgTCP3F4G+kfET+ghgaPN0rUUw QWp1djlG2HkiI6MbBoBxHsAaj9qHcuFs6cQQWKYQ=
Message-Id: <6.2.5.6.2.20130726101746.0c8db480@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 26 Jul 2013 11:29:07 -0700
To: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Remote participants, newcomers, and tutorials (was: IETF87 Audio Streaming Info)
In-Reply-To: <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: edu-team@ietf.org, iesg@ietf.org, rfc-editor@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jul 2013 18:38:19 -0000

Hello,
At 08:32 26-07-2013, John C Klensin wrote:
>For this particular meeting all of the following seem relevant
>to at least some remote participants:

[snip]

>with subscribing to the 87all list.  It should no involve a
>treasure hunt at which only very experienced IETF participants
>can be expected to succeed.

It would be helpful to new people if everything in the IETF was not a 
treasure hunt or required an email broadcast for a person to find information.

The consensus of the IETF is that:

   "newcomers who attend Working Group meetings are encouraged to
    observe and absorb whatever material they can, but should not
    interfere with the ongoing process of the group"

It was also mentioned that:

  "Working group meetings are not intended for the education of
   individuals"

The first quote might discourage newcomers from participating.  I 
suggest discussing about the two quotes during the orientation as 
they could be misunderstood.

>Specific suggestions:
>
>(i) Let's get these open Sunday sessions audiocast and/or
>available over Meetecho or WebEx.  If that is impossible for
>IETF 87, it should be a priority for IETF 88 and later.

Yes.

POSH has not published a session agenda.  However, the BoF is listed 
on the meeting agenda.  Is the BoF cancelled or will this be one of 
those willful violations of IETF Best Current Practices?

Regards,
-sm 


From brian.e.carpenter@gmail.com  Fri Jul 26 13:33:43 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E91AF11E8167; Fri, 26 Jul 2013 13:33:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.584
X-Spam-Level: 
X-Spam-Status: No, score=-102.584 tagged_above=-999 required=5 tests=[AWL=0.015, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P-Hxh-IlUC6U; Fri, 26 Jul 2013 13:33:43 -0700 (PDT)
Received: from mail-pd0-x235.google.com (mail-pd0-x235.google.com [IPv6:2607:f8b0:400e:c02::235]) by ietfa.amsl.com (Postfix) with ESMTP id 43EEB11E8114; Fri, 26 Jul 2013 13:33:43 -0700 (PDT)
Received: by mail-pd0-f181.google.com with SMTP id g12so2812904pdj.12 for <multiple recipients>; Fri, 26 Jul 2013 13:33:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=SHflEHRevJyaIwVFOqYgXzV767dwxX7HrKIYpfi15N0=; b=sMpIkHgIzyY8vH0inL4epBqdp0Qq0rbqZzZ/+hKBB4i6RWpDAcOD5fKivWoYiK5beK FeuHFMDjbs6tmzGzpeGdegS8iupYEavE5Y/0AaJiLPmXw+iKaWS5fqQo5Vdd7V9NjPG0 XNNf8JVYoI8/hyjcpREt01o4s5yIPuU6SX5R2pjk8w3qxFMNNM9rtTuMbSl6yda4+C4z C4mRwc2NeNST8QJNx70cJ1hhpIf9jAKmz1+8ZtmdIwKBjiCEHH+47rRrM2PQko1uwhLX UIXHz2TaRsChgxTH2ZpjnH4nU9Sy9aw+l2zp2fnMvhuBtrgzp5oQBxZG6dGUwoimZAuI kiGg==
X-Received: by 10.66.122.167 with SMTP id lt7mr27787921pab.190.1374870820999;  Fri, 26 Jul 2013 13:33:40 -0700 (PDT)
Received: from [192.168.178.23] (202.192.69.111.dynamic.snap.net.nz. [111.69.192.202]) by mx.google.com with ESMTPSA id pv5sm5423535pac.14.2013.07.26.13.33.37 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 26 Jul 2013 13:33:40 -0700 (PDT)
Message-ID: <51F2DD2A.7040700@gmail.com>
Date: Sat, 27 Jul 2013 08:33:46 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Remote participants, newcomers, and tutorials
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com>
In-Reply-To: <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: edu-team@ietf.org, ietf@ietf.org, rfc-editor@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jul 2013 20:33:44 -0000

On 27/07/2013 03:32, John C Klensin wrote:
> Hi.
> 
> For a newcomer or someone expecting to write I-Ds, some of the
> most important sessions at the IETF are the various Sunday
> afternoon tutorials and introductions.  Many of them are (or
> should be) of as much interest to remote participants as to f2f
> attendees.   Until and unless a newcomer's tutorial can be
> prepared that is focused on remote participants, even that
> session should be of interest.
> 
> For this particular meeting all of the following seem relevant
> to at least some remote participants:
> 
> 	Newcomers' Orientation       
> 	Tools for Creating I-Ds and RFCs         
> 	IAOC Overview Session     
> 	Multipath TCP         
> 	Applying IP Flow Information Export (IPFIX) to Network
> Measurement and Management
> 
> So...
> 
> (1) The note below strongly implies that none of those sessions
> are being audiocast.    Why not and can that be fixed?

I think that would mean that the crew (partly volunteers) would
need to mobilise 24 hours earlier. Not impossible, I suppose,
but not free of costs either.

> 
> (2) There is no hint on the agenda or tools agenda about
> availability of presentation and related materials (slides,
> etc.) for those sessions.  Do those materials not exist? 

At the moment the various EDU tutorials usually get posted after
the event, and I agree that isn't ideal.

It would be useful for all these ancillary sessions to be included
in the "meeting materials" page and all agenda tools (official and
volunteer). Again, not impossible, in fact very desirable IMHO,
but not free.

    Brian
> I
> know, but a newcomer or remote participant might not, that I can
> find some tutorials by going to the IETF main page and going to
> "Tutorial" under "Resources", but I have no idea which of those
> links actually reflects what will be presented on Sunday.
> Assuming the presentation materials do exist for at least
> several of the sessions, finding them is much like the situation
> with subscribing to the 87all list.  It should no involve a
> treasure hunt at which only very experienced IETF participants
> can be expected to succeed.  
> 
> Specific suggestions:
> 
> (i) Let's get these open Sunday sessions audiocast and/or
> available over Meetecho or WebEx.  If that is impossible for
> IETF 87, it should be a priority for IETF 88 and later.
> 
> (ii) If there are presentation materials available, links from
> the tools agenda and an announcement to IETF-Announce as to
> where to find them would be desirable.
> 
> (iii) If presentation materials are not available, why not?
> And, more important, can this be made a requirement for IETF 88
> and beyond?
> 
> thanks,
>     john
> 
> 
> 
> --On Friday, July 26, 2013 12:00 +0200 Nick Kukich
> <nkukich@verilan.com> wrote:
> 
>> Greetings,
>>
>> For those interested in monitoring sessions or participating
>> remotely the following information may prove useful.
>> ...
>> All 8 parallel tracks at the IETF 87 meeting will be broadcast
>> starting with the commencement of working group sessions on
>> Monday, July 29, 2013 at 0900 CEST (UTC+2) and continue until
>> the close of sessions on Friday, August 2nd.
>> ...
> 
> 

From brian.e.carpenter@gmail.com  Fri Jul 26 13:38:52 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9988B11E8156; Fri, 26 Jul 2013 13:38:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.585
X-Spam-Level: 
X-Spam-Status: No, score=-102.585 tagged_above=-999 required=5 tests=[AWL=0.014, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 50y+qWnj477y; Fri, 26 Jul 2013 13:38:52 -0700 (PDT)
Received: from mail-pd0-x234.google.com (mail-pd0-x234.google.com [IPv6:2607:f8b0:400e:c02::234]) by ietfa.amsl.com (Postfix) with ESMTP id AEC5011E814F; Fri, 26 Jul 2013 13:38:46 -0700 (PDT)
Received: by mail-pd0-f180.google.com with SMTP id 10so3267369pdi.39 for <multiple recipients>; Fri, 26 Jul 2013 13:38:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Nk5UW2w9oz9WiGejMAdduAkwKKYG8SxwAqXWJ7CRmxc=; b=aomW08lNSYpdlK1tLlUkEfJ9w6GsR+0ZAwcL2g0G+a3ktKKlh+tuOezOw3CzPUbrSy bMnrhMTkvf4jLthj8SRd2nSI2XfzUbKhWZqt4w44PrbDgHGMkmjTTK28bd1IHOHSmBNf DwNC2WqAZwwGZIIWbyHG0Qj0qyV/8916uRS5OIjDwffCJbQgY5weJfEClscTdSd2GNuP uqrayowSvy5/OG8Tfo+A60mxRi/FqpdBLcYwGX35YYeLiaywTbL8yHzOiTVhUuYjXQU1 L1DwlZBJrojjHpjAIT63FPOY4q39NLYs8qnj1xsuRDouCaAIgcWA6mc6zCAsvPmFOgzR 8IGg==
X-Received: by 10.68.59.73 with SMTP id x9mr55883930pbq.131.1374871126425; Fri, 26 Jul 2013 13:38:46 -0700 (PDT)
Received: from [192.168.178.23] (202.192.69.111.dynamic.snap.net.nz. [111.69.192.202]) by mx.google.com with ESMTPSA id e7sm48743153pbc.11.2013.07.26.13.38.43 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 26 Jul 2013 13:38:45 -0700 (PDT)
Message-ID: <51F2DE5F.1010708@gmail.com>
Date: Sat, 27 Jul 2013 08:38:55 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Oh look! [Re: Remote participants, newcomers, and tutorials]
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <51F2DD2A.7040700@gmail.com>
In-Reply-To: <51F2DD2A.7040700@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: edu-team@ietf.org, ietf@ietf.org, rfc-editor@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jul 2013 20:38:52 -0000

And there is a "Training" section in the meeting materials page.
It's empty... but thanks to somebody for putting it there.
All we need to do is figure out how to pre-load it.

Regards
   Brian

On 27/07/2013 08:33, Brian E Carpenter wrote:
> On 27/07/2013 03:32, John C Klensin wrote:
>> Hi.
>>
>> For a newcomer or someone expecting to write I-Ds, some of the
>> most important sessions at the IETF are the various Sunday
>> afternoon tutorials and introductions.  Many of them are (or
>> should be) of as much interest to remote participants as to f2f
>> attendees.   Until and unless a newcomer's tutorial can be
>> prepared that is focused on remote participants, even that
>> session should be of interest.
>>
>> For this particular meeting all of the following seem relevant
>> to at least some remote participants:
>>
>> 	Newcomers' Orientation       
>> 	Tools for Creating I-Ds and RFCs         
>> 	IAOC Overview Session     
>> 	Multipath TCP         
>> 	Applying IP Flow Information Export (IPFIX) to Network
>> Measurement and Management
>>
>> So...
>>
>> (1) The note below strongly implies that none of those sessions
>> are being audiocast.    Why not and can that be fixed?
> 
> I think that would mean that the crew (partly volunteers) would
> need to mobilise 24 hours earlier. Not impossible, I suppose,
> but not free of costs either.
> 
>> (2) There is no hint on the agenda or tools agenda about
>> availability of presentation and related materials (slides,
>> etc.) for those sessions.  Do those materials not exist? 
> 
> At the moment the various EDU tutorials usually get posted after
> the event, and I agree that isn't ideal.
> 
> It would be useful for all these ancillary sessions to be included
> in the "meeting materials" page and all agenda tools (official and
> volunteer). Again, not impossible, in fact very desirable IMHO,
> but not free.
> 
>     Brian
>> I
>> know, but a newcomer or remote participant might not, that I can
>> find some tutorials by going to the IETF main page and going to
>> "Tutorial" under "Resources", but I have no idea which of those
>> links actually reflects what will be presented on Sunday.
>> Assuming the presentation materials do exist for at least
>> several of the sessions, finding them is much like the situation
>> with subscribing to the 87all list.  It should no involve a
>> treasure hunt at which only very experienced IETF participants
>> can be expected to succeed.  
>>
>> Specific suggestions:
>>
>> (i) Let's get these open Sunday sessions audiocast and/or
>> available over Meetecho or WebEx.  If that is impossible for
>> IETF 87, it should be a priority for IETF 88 and later.
>>
>> (ii) If there are presentation materials available, links from
>> the tools agenda and an announcement to IETF-Announce as to
>> where to find them would be desirable.
>>
>> (iii) If presentation materials are not available, why not?
>> And, more important, can this be made a requirement for IETF 88
>> and beyond?
>>
>> thanks,
>>     john
>>
>>
>>
>> --On Friday, July 26, 2013 12:00 +0200 Nick Kukich
>> <nkukich@verilan.com> wrote:
>>
>>> Greetings,
>>>
>>> For those interested in monitoring sessions or participating
>>> remotely the following information may prove useful.
>>> ...
>>> All 8 parallel tracks at the IETF 87 meeting will be broadcast
>>> starting with the commencement of working group sessions on
>>> Monday, July 29, 2013 at 0900 CEST (UTC+2) and continue until
>>> the close of sessions on Friday, August 2nd.
>>> ...
>>
> 

From john-ietf@jck.com  Fri Jul 26 13:48:50 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C822811E8142; Fri, 26 Jul 2013 13:48:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id foyaGaIFuxcr; Fri, 26 Jul 2013 13:48:46 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 17CEC11E8140; Fri, 26 Jul 2013 13:48:45 -0700 (PDT)
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 1V2owO-000A0i-Qf; Fri, 26 Jul 2013 16:48:44 -0400
Date: Fri, 26 Jul 2013 16:48:39 -0400
From: John C Klensin <john-ietf@jck.com>
To: SM <sm@resistor.net>, ietf@ietf.org
Subject: dnssdext BOF (was: Re: Remote participants, newcomers, and tutorials (was: IETF87  Audio Streaming Info))
Message-ID: <B0968F4989FF5E2FC4949CDC@JcK-HP8200.jck.com>
In-Reply-To: <6.2.5.6.2.20130726101746.0c8db480@resistor.net>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.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: iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jul 2013 20:48:50 -0000

--On Friday, July 26, 2013 11:29 -0700 SM <sm@resistor.net>
wrote:

> POSH has not published a session agenda.  However, the BoF is
> listed on the meeting agenda.  Is the BoF cancelled or will
> this be one of those willful violations of IETF Best Current
> Practices?

On a similar note, according to its agenda, the core of the 
DNS-SD Extensions BOF (dnssdext) is apparently
draft-lynn-sadnssd-requirements-01.  The link from the agenda
page [1] yields a 404 error and attempts to look up either
"draft-lynn-sadnssd-requirements" or the author name "lynn" in
the I-D search engine yield nothing.

If one thinks to go to the I-D search engine and enter just
"draft-lynn", draft-lynn-mdnsext-requirements-02 shows up which
I'm guessing is the relevant draft.  

FWIW, I also note that the posted agenda is heavily dependent on
the Chairs and mentions an "agreed charter".   The Chairs are
not identified, preventing interested participants from
contacting them for information (and others from contacting them
about errors like the one above) and there is no link or other
pointer to the proposed "agreed charter".  So I am wondering why
this BOF was approved, which AD is watching the BOF agenda, and
why it is still on the meeting agenda? 

I am mentioning this on the IETF list only because it is another
example of the point that I (and probably SM and others) are
trying to make:  If we are interested in newcomers, remote
participants without years of IETF experience, and/or increased
diversity, we should not allow these kinds of issues to become
requirements for "treasure hunts" or other sorts of obstacles in
people's paths.

And, IMO, we should be especially careful about BOFs because
they provide newcomers (present at the meeting or remote) good
opportunities to get in at the beginning of new work items.

   john


[1] http://tools.ietf.org/agenda/87/agenda-87-dnssdext.html



From tjc@ecs.soton.ac.uk  Fri Jul 26 14:49:35 2013
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 639DC11E8177; Fri, 26 Jul 2013 14:49:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.424
X-Spam-Level: 
X-Spam-Status: No, score=-2.424 tagged_above=-999 required=5 tests=[AWL=0.174,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xO8cq05UmaEM; Fri, 26 Jul 2013 14:49:34 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 2850311E8150; Fri, 26 Jul 2013 14:49:33 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost.ecs.soton.ac.uk [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r6QLnTep014303; Fri, 26 Jul 2013 22:49:29 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r6QLnTep014303
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1374875370; bh=REW5I2njYL4Ilf0cQRGAI3Gz72Y=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=FXol+p7OrK2E9sbT/UgMmZjl4ilAXtAjJOmK9Woqcu87gUEtX5117G8NYSuhjUnbe tHp+e9Jidvyu8kQMljFmf8JKAzvsx+JNZzadAV1MHGX9n9CyXJVhU1o+V1XBeTT0Uy G+BShQMYzIGZ0yp2tyXCedO8HhZjwDGrOIkVVj10=
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 p6PMnY0544510135GP ret-id none; Fri, 26 Jul 2013 22:49:30 +0100
Received: from [192.168.1.110] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r6QLm8LP031648 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 26 Jul 2013 22:48:08 +0100
Content-Type: multipart/alternative; boundary="Apple-Mail=_F2940B61-5161-4EF6-A49B-9760E977013C"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: dnssdext BOF (was: Re: Remote participants, newcomers, and tutorials (was: IETF87  Audio Streaming Info))
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <B0968F4989FF5E2FC4949CDC@JcK-HP8200.jck.com>
Date: Fri, 26 Jul 2013 22:48:07 +0100
Message-ID: <EMEW3|7d3cba230c8c24cd4f09676cdd63913dp6PMnY03tjc|ecs.soton.ac.uk|8115DE14-2262-430F-A78F-8DD66E9DF5F6@ecs.soton.ac.uk>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net> <B0968F4989FF5E2FC4949CDC@JcK-HP8200.jck.com> <8115DE14-2262-430F-A78F-8DD66E9DF5F6@ecs.soton.ac.uk>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1508)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p6PMnY054451013500; tid=p6PMnY0544510135GP; client=relay,ipv6; mail=; rcpt=; nrcpt=4:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r6QLnTep014303
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: SM <sm@resistor.net>, ietf@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jul 2013 21:49:35 -0000

--Apple-Mail=_F2940B61-5161-4EF6-A49B-9760E977013C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On 26 Jul 2013, at 21:48, John C Klensin <john-ietf@jck.com> wrote:

>=20
>=20
> --On Friday, July 26, 2013 11:29 -0700 SM <sm@resistor.net>
> wrote:
>=20
>> POSH has not published a session agenda.  However, the BoF is
>> listed on the meeting agenda.  Is the BoF cancelled or will
>> this be one of those willful violations of IETF Best Current
>> Practices?
>=20
> On a similar note, according to its agenda, the core of the=20
> DNS-SD Extensions BOF (dnssdext) is apparently
> draft-lynn-sadnssd-requirements-01.  The link from the agenda
> page [1] yields a 404 error and attempts to look up either
> "draft-lynn-sadnssd-requirements" or the author name "lynn" in
> the I-D search engine yield nothing.

Hi John,

Apologies for this. The correct draft name, and the BoF chair contacts, =
are now in the agenda file at: =
https://datatracker.ietf.org/meeting/87/agenda/dnssdext/

> FWIW, I also note that the posted agenda is heavily dependent on
> the Chairs and mentions an "agreed charter".  =20

That means the charter agreed from the bashing of the draft charter in =
the previous 40 minutes, not that a charter is already agreed.

> I am mentioning this on the IETF list only because it is another
> example of the point that I (and probably SM and others) are
> trying to make:  If we are interested in newcomers, remote
> participants without years of IETF experience, and/or increased
> diversity, we should not allow these kinds of issues to become
> requirements for "treasure hunts" or other sorts of obstacles in
> people's paths.

True. Though the chair names are on the posters linked in the materials =
page, which I assume is well-advertised to newcomers as access to slides =
is rather important.  And also on the BoF wiki, which you should know =
about.  The names were just missing from the agenda file itself.

Tim=

--Apple-Mail=_F2940B61-5161-4EF6-A49B-9760E977013C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On 26 Jul 2013, at 21:48, John C Klensin &lt;<a =
href=3D"mailto:john-ietf@jck.com">john-ietf@jck.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><br><br>--On Friday, July 26, 2013 11:29 -0700 SM &lt;<a =
href=3D"mailto:sm@resistor.net">sm@resistor.net</a>&gt;<br>wrote:<br><br><=
blockquote type=3D"cite">POSH has not published a session agenda. =
&nbsp;However, the BoF is<br>listed on the meeting agenda. &nbsp;Is the =
BoF cancelled or will<br>this be one of those willful violations of IETF =
Best Current<br>Practices?<br></blockquote><br>On a similar note, =
according to its agenda, the core of the <br>DNS-SD Extensions BOF =
(dnssdext) is apparently<br>draft-lynn-sadnssd-requirements-01. =
&nbsp;The link from the agenda<br>page [1] yields a 404 error and =
attempts to look up either<br>"draft-lynn-sadnssd-requirements" or the =
author name "lynn" in<br>the I-D search engine yield =
nothing.<br></blockquote><div><br></div>Hi =
John,</div><div><br></div><div>Apologies for this.&nbsp;The correct =
draft name, and the BoF chair contacts, are now in the agenda file =
at:&nbsp;<a =
href=3D"https://datatracker.ietf.org/meeting/87/agenda/dnssdext/">https://=
datatracker.ietf.org/meeting/87/agenda/dnssdext/</a></div><div><br></div><=
div><blockquote type=3D"cite">FWIW, I also note that the posted agenda =
is heavily dependent on<br>the Chairs and mentions an "agreed charter". =
&nbsp;&nbsp;</blockquote><div><br></div>That means the charter agreed =
from the bashing of the draft charter in the previous 40 minutes, not =
that a charter is already agreed.<br><div><br></div><blockquote =
type=3D"cite">I am mentioning this on the IETF list only because it is =
another<br>example of the point that I (and probably SM and others) =
are<br>trying to make: &nbsp;If we are interested in newcomers, =
remote<br>participants without years of IETF experience, and/or =
increased<br>diversity, we should not allow these kinds of issues to =
become<br>requirements for "treasure hunts" or other sorts of obstacles =
in<br>people's paths.<br></blockquote><div><br></div>True. Though the =
chair names are on the posters linked in the materials page, which I =
assume is well-advertised to newcomers as access to slides is rather =
important. &nbsp;And also on the BoF wiki, which you should know about. =
&nbsp;The names were just missing from the agenda file =
itself.</div><div><br></div><div>Tim</div></body></html>=

--Apple-Mail=_F2940B61-5161-4EF6-A49B-9760E977013C--

From john-ietf@jck.com  Fri Jul 26 15:10:45 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B8CE21F9A30; Fri, 26 Jul 2013 15:10:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SPzC1vKr56AR; Fri, 26 Jul 2013 15:10:39 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id D01E511E8179; Fri, 26 Jul 2013 15:10:38 -0700 (PDT)
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 1V2qDd-000AQV-HT; Fri, 26 Jul 2013 18:10:37 -0400
Date: Fri, 26 Jul 2013 18:10:32 -0400
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Oh look! [Re: Remote participants, newcomers, and tutorials]
Message-ID: <B2856A2101451CF971914EFA@JcK-HP8200.jck.com>
In-Reply-To: <51F2DE5F.1010708@gmail.com>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <51F2DD2A.7040700@gmail.com> <51F2DE5F.1010708@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: edu-team@ietf.org, ietf@ietf.org, rfc-editor@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jul 2013 22:10:45 -0000

--On Saturday, July 27, 2013 08:38 +1200 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

> And there is a "Training" section in the meeting materials
> page. It's empty... but thanks to somebody for putting it
> there. All we need to do is figure out how to pre-load it.

And to remember that link appears on  the main meeting page
because it isn't on either of the agenda pages.  I suggest again
that these little treasure hunts work better for very
experienced participants and regular participants who are very
patient about searching for information, but much less well for
newcomers, remote-only participants, and the diverse and curious
potential participants we'd supposedly like to encourage.

I still believe that the agenda pages should be one-step
shopping for these types of meeting program-specific bits of
information, whether it be remote participation bits (or at lest
a pointer to whether they can be found) and meeting material
pages (ditto).  It is slightly extraneous information but I note
that we have had a list of Areas and ADs on the agenda pages
ever since I can remember.  That information is much more easily
located than most of the things I've been commenting on and, if
one locates it (IETF Home Page -> IESG -> Members) one even gets
contact information as a bonus.  And the listing of AD names is
pretty useless without contact info.


More inline.

>...
>>> (1) The note below strongly implies that none of those
>>> sessions are being audiocast.    Why not and can that be
>>> fixed?
>> 
>> I think that would mean that the crew (partly volunteers)
>> would need to mobilise 24 hours earlier. Not impossible, I
>> suppose, but not free of costs either.

Brian, there are two reasons I'm pushing on this set of issues.
One is that there are folks like you and me (and, since he
dropping into a different part of the thread, SM) who are
reasonably experienced participants but who are not likely to
attend most or all f2f meetings in the future.  To the extent to
which it is in the IETF's interest to keep us active --and I
hope that it is-- then a lot of this stuff ought to work (even
though  we will know about and, given enough patience, be able
to find meeting materials lists, mechanisms to subscribe to
slightly-hidden mailing lists, the actual names and locations of
incorrect links to drafts, names of BOF Chairs and responsible
ADs, etc.  If we are desperately concerned about hearing a
particular tutorial, I imagine that, with a little planning,
either of us could find someone to sit in the room and do a
Skype or equivalent if there was a functional network or get
someone to sit in the room with a voice recorder and make
something that could be converted into an MP3 file for
transmission after the network comes up.

I assume that, were the question posed, there would be general
IETF consensus that I run out of patience a lot faster than you
do.  I'm willing to concede that and agree that anything that
doesn't irritate you too is my problem and I should live with
it.  I certainly would have a lot of difficulty arguing for
folks going to a lot of extra trouble or expense on my account
(or even on yours).

However, the IETF has been having a lot of discussions about
newcomers, diversity, and attracting new folks to participate
and get work done.  I think those populations will be better
served if it is possible for people a lot less experienced than
the two of us can participate actively and constructively
without attending every meeting.  I also think that, especially
for many people from developing countries, universities, small
companies, and far-away places, we will be far more successful
in recruiting if we can encourage remote participation as a
starting point with the expectation of getting people physically
to meetings only after the value to them and their organizations
of doing so has been demonstrated.  I'd personally even favor
making remote participation at a could of meeting be a
prerequisite for most applications for ISOC's IETF Fellows
program.

But the above picture isn't going to happen unless we are
serious and treat that seriousness as an integral part of our
strategies about newcomers and diversity.  Seriousness to me
says that we get more careful about how experienced one has to
be to find critical information, that we make sure remote
participation works, and that we make any session that would be
relevant to remote participants accessible to them (and with
materials available as much as possible in advance and from
easy-to-find places).  Seriousness implies that, if there are
extra costs, we figure out how to cover them (or how to cut
somewhere else).  

Or, if we are not serious, it would probably be to the benefit
of the community for us to face that and stop wasting energy and
resources on outreach efforts that are expensive in one or the
other (or both).

best,
   john



From john-ietf@jck.com  Fri Jul 26 15:31:46 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07F8311E8162; Fri, 26 Jul 2013 15:31:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X7paqXT5yrB3; Fri, 26 Jul 2013 15:31:41 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 3BB6D11E8181; Fri, 26 Jul 2013 15:31:40 -0700 (PDT)
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 1V2qXp-000ATF-9A; Fri, 26 Jul 2013 18:31:29 -0400
Date: Fri, 26 Jul 2013 18:31:24 -0400
From: John C Klensin <john-ietf@jck.com>
To: Tim Chown <tjc@ecs.soton.ac.uk>
Subject: Re: dnssdext BOF (was: Re: Remote participants, newcomers, and tutorials (was: IETF87  Audio Streaming Info))
Message-ID: <445D37B5E1C5893CE249C62C@JcK-HP8200.jck.com>
In-Reply-To: <EMEW3|7d3cba230c8c24cd4f09676cdd63913dp6PMnY03tjc|ecs.soton.ac.uk|8115DE14-2262-430F-A78F-8DD66E9DF5F6@ecs.soton.ac.uk>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net> <B0968F4989FF5E2FC4949CDC@JcK-HP8200.jck.com> <8115DE14-2262-430F-A78F-8DD66E9DF5F6@ecs.soton.ac.uk> <EMEW3|7d3cba230c8c24cd4f09676cdd63913dp6PMnY03tjc|ecs.soton.ac.uk|8115DE14-2262-430F-A78F-8DD66E9DF5F6@ecs.soton.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
Cc: SM <sm@resistor.net>, ietf@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jul 2013 22:31:46 -0000

--On Friday, July 26, 2013 22:48 +0100 Tim Chown
<tjc@ecs.soton.ac.uk> wrote:

>...
>> On a similar note, according to its agenda, the core of the 
>> DNS-SD Extensions BOF (dnssdext) is apparently
>> draft-lynn-sadnssd-requirements-01.  The link from the agenda
>> page [1] yields a 404 error and attempts to look up either
>> "draft-lynn-sadnssd-requirements" or the author name "lynn" in
>> the I-D search engine yield nothing.
> 
> Hi John,
> 
> Apologies for this. The correct draft name, and the BoF chair
> contacts, are now in the agenda file at:
> https://datatracker.ietf.org/meeting/87/agenda/dnssdext/

Tim,

Many thanks.  Let me stress that I didn't set out to attack you
or your BOF.  You just lucked out and became the first example
that came in handy.  See below.

>> FWIW, I also note that the posted agenda is heavily dependent
>> on the Chairs and mentions an "agreed charter".   
> 
> That means the charter agreed from the bashing of the draft
> charter in the previous 40 minutes, not that a charter is
> already agreed.

If there is something to be bashed for those 40 minutes, I'd
expect a link to at least a skeleton first draft. I note that
draft charter does have a link from the meeting materials page,
just not from the agenda.   But, modulo the comment below, that
is a matter of taste to be working out between you, Ralph, and
the IESG.

>> I am mentioning this on the IETF list only because it is
>> another example of the point that I (and probably SM and
>> others) are trying to make:  If we are interested in
>> newcomers, remote participants without years of IETF
>> experience, and/or increased diversity, we should not allow
>> these kinds of issues to become requirements for "treasure
>> hunts" or other sorts of obstacles in people's paths.

> True. Though the chair names are on the posters linked in the
> materials page, which I assume is well-advertised to newcomers
> as access to slides is rather important.

As far as I know, the only "advertisement" is the link from the
"Agendas and Meeting Materials" section of the main meeting page
and the similar links from the Meetings entry on the IETF home
page.  Now I'd personally like to see the "New Attendees"
category on the main meeting page changed to "New Attendees and
Participantes" and then including a link to a page that would
give hints about where these things are and how to navigate
around them.  But that fairly clearly won't happen before Sunday
and YMMD. 

>  And also on the BoF wiki, which you should know about.  

Yep.  I know about it and where to find it.  But, as I explained
in my note to Brian, I'm a lot more concerned about newcomers
and remote participants without years or experience than I am
about what I can find if I remember all of the reasonable places
where I might look.

>...

Best wishes for a successful BOF.

   john


From tjc@ecs.soton.ac.uk  Fri Jul 26 16:39:29 2013
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4217621E8054; Fri, 26 Jul 2013 16:39:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.482
X-Spam-Level: 
X-Spam-Status: No, score=-2.482 tagged_above=-999 required=5 tests=[AWL=0.116,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QuVSeYKqlR+a; Fri, 26 Jul 2013 16:39:28 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id C4F7011E8183; Fri, 26 Jul 2013 16:39:26 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost.ecs.soton.ac.uk [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r6QNdLrP001389; Sat, 27 Jul 2013 00:39:21 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r6QNdLrP001389
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1374881962; bh=V0p0K+V42udDSXnTZfJQtfV2/b0=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=QeD1+didJdqW7pQDayE7z/Ys78X6d1881mJwrFVJdjL99lV3aOZoRytnQqhom8kZ4 8QZSH8h91FXI2+ZJxWRCMnmU3fZkJot5jIh5pZc04PoohFsWM73LdJaI0pJFebB/XZ Ui988mcspmsbZ9/eWcuZq7Gn8nSjVudqGaoZM9NQ=
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 p6Q0dL0544510644ZO ret-id none; Sat, 27 Jul 2013 00:39:22 +0100
Received: from [192.168.1.110] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r6QNbtb7020694 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 27 Jul 2013 00:37:58 +0100
Content-Type: multipart/alternative; boundary="Apple-Mail=_053DCE4A-0F65-4A4A-875F-BCCE0624D9F3"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: dnssdext BOF (was: Re: Remote participants, newcomers, and tutorials (was: IETF87  Audio Streaming Info))
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <445D37B5E1C5893CE249C62C@JcK-HP8200.jck.com>
Date: Sat, 27 Jul 2013 00:37:53 +0100
Message-ID: <EMEW3|6371582239049b5739a44172e8e53bdep6Q0dL03tjc|ecs.soton.ac.uk|6FA0237E-C766-485D-8179-0355A70ACD47@ecs.soton.ac.uk>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net> <B0968F4989FF5E2FC4949CDC@JcK-HP8200.jck.com> <8115DE14-2262-430F-A78F-8DD66E9DF5F6@ecs.soton.ac.uk> <EMEW3|7d3cba230c8c24cd4f09676cdd63913dp6PMnY03tjc|ecs.soton.ac.uk|8115DE14-2262-430F-A78F-8DD66E9DF5F6@ecs.soton.ac.uk> <445D37B5E1C5893CE249C62C@JcK-HP8200.jck.com> <6FA0237E-C766-485D-8179-0355A70ACD47@ecs.soton.ac.uk>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1508)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p6Q0dL054451064400; tid=p6Q0dL0544510644ZO; client=relay,ipv6; mail=; rcpt=; nrcpt=4:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r6QNdLrP001389
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: SM <sm@resistor.net>, ietf@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jul 2013 23:39:29 -0000

--Apple-Mail=_053DCE4A-0F65-4A4A-875F-BCCE0624D9F3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On 26 Jul 2013, at 23:31, John C Klensin <john-ietf@jck.com> wrote:

> --On Friday, July 26, 2013 22:48 +0100 Tim Chown
> <tjc@ecs.soton.ac.uk> wrote:
>>=20
>> That means the charter agreed from the bashing of the draft
>> charter in the previous 40 minutes, not that a charter is
>> already agreed.
>=20
> If there is something to be bashed for those 40 minutes, I'd
> expect a link to at least a skeleton first draft. I note that
> draft charter does have a link from the meeting materials page,
> just not from the agenda.   But, modulo the comment below, that
> is a matter of taste to be working out between you, Ralph, and
> the IESG.

The draft charter was placed where they usually are, on the BoF wiki.  =
But I added a link to a specific draft charter file when I updated the =
agenda, see https://datatracker.ietf.org/meeting/87/agenda/dnssdext/.

The other "problem" for mdnsext is that the second BoF has been given a =
different name, for various reasons, but that does make it a bit harder =
to locate the mail list and draft.=20

>> True. Though the chair names are on the posters linked in the
>> materials page, which I assume is well-advertised to newcomers
>> as access to slides is rather important.
>=20
> As far as I know, the only "advertisement" is the link from the
> "Agendas and Meeting Materials" section of the main meeting page
> and the similar links from the Meetings entry on the IETF home
> page.  Now I'd personally like to see the "New Attendees"
> category on the main meeting page changed to "New Attendees and
> Participantes" and then including a link to a page that would
> give hints about where these things are and how to navigate
> around them.  But that fairly clearly won't happen before Sunday
> and YMMD.=20

Well, I would certainly agree that the meeting materials page/area needs =
to be well advertised, if it isn't already, but I don't know what =
additional information newcomers are pointed at, not being one.

>> And also on the BoF wiki, which you should know about. =20
>=20
> Yep.  I know about it and where to find it.  But, as I explained
> in my note to Brian, I'm a lot more concerned about newcomers
> and remote participants without years or experience than I am
> about what I can find if I remember all of the reasonable places
> where I might look.


While we/you can try to guess what the problems are, it may be better to =
surveymonkey those who registered as newcomers in a couple of weeks and =
ask them about their experience, whether they were aware of certain =
things, and what could be done better.

Tim=

--Apple-Mail=_053DCE4A-0F65-4A4A-875F-BCCE0624D9F3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On 26 Jul 2013, at 23:31, John C Klensin &lt;<a =
href=3D"mailto:john-ietf@jck.com">john-ietf@jck.com</a>&gt; =
wrote:</div><br><blockquote type=3D"cite">--On Friday, July 26, 2013 =
22:48 +0100 Tim Chown<br>&lt;<a =
href=3D"mailto:tjc@ecs.soton.ac.uk">tjc@ecs.soton.ac.uk</a>&gt; =
wrote:<br><blockquote type=3D"cite"><br>That means the charter agreed =
from the bashing of the draft<br>charter in the previous 40 minutes, not =
that a charter is<br>already agreed.<br></blockquote><br>If there is =
something to be bashed for those 40 minutes, I'd<br>expect a link to at =
least a skeleton first draft. I note that<br>draft charter does have a =
link from the meeting materials page,<br>just not from the agenda. =
&nbsp;&nbsp;But, modulo the comment below, that<br>is a matter of taste =
to be working out between you, Ralph, and<br>the =
IESG.<br></blockquote><div><br></div>The draft charter was placed where =
they usually are, on the BoF wiki. &nbsp;But I added a link to a =
specific draft charter file when I updated the agenda, see&nbsp;<a =
href=3D"https://datatracker.ietf.org/meeting/87/agenda/dnssdext/">https://=
datatracker.ietf.org/meeting/87/agenda/dnssdext/</a>.</div><div><br></div>=
<div>The other "problem" for mdnsext is that the second BoF has been =
given a different name, for various reasons, but that does make it a bit =
harder to locate the mail list and =
draft.&nbsp;</div><div><br></div><div><blockquote =
type=3D"cite"><blockquote type=3D"cite">True. Though the chair names are =
on the posters linked in the<br>materials page, which I assume is =
well-advertised to newcomers<br>as access to slides is rather =
important.<br></blockquote><br>As far as I know, the only =
"advertisement" is the link from the<br>"Agendas and Meeting Materials" =
section of the main meeting page<br>and the similar links from the =
Meetings entry on the IETF home<br>page. &nbsp;Now I'd personally like =
to see the "New Attendees"<br>category on the main meeting page changed =
to "New Attendees and<br>Participantes" and then including a link to a =
page that would<br>give hints about where these things are and how to =
navigate<br>around them. &nbsp;But that fairly clearly won't happen =
before Sunday<br>and YMMD. <br></blockquote><div><br></div>Well, I would =
certainly agree that the meeting materials page/area needs to be well =
advertised, if it isn't already, but I don't know what additional =
information newcomers are pointed at, not being =
one.</div><div><br></div><div><blockquote type=3D"cite"><blockquote =
type=3D"cite"> And also on the BoF wiki, which you should know about. =
&nbsp;<br></blockquote><br>Yep. &nbsp;I know about it and where to find =
it. &nbsp;But, as I explained<br>in my note to Brian, I'm a lot more =
concerned about newcomers<br>and remote participants without years or =
experience than I am<br>about what I can find if I remember all of the =
reasonable places<br>where I might =
look.<br></blockquote></div><div><br></div><div>While we/you can try to =
guess what the problems are, it may be better to surveymonkey those who =
registered as newcomers in a couple of weeks and ask them about their =
experience, whether they were aware of certain things, and what could be =
done =
better.</div><div><br></div><div><div><div>Tim</div></div></div></body></h=
tml>=

--Apple-Mail=_053DCE4A-0F65-4A4A-875F-BCCE0624D9F3--

From john-ietf@jck.com  Fri Jul 26 17:55:30 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C97911E81A7; Fri, 26 Jul 2013 17:55:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qLxOmJAnScqq; Fri, 26 Jul 2013 17:55:24 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id B698F11E81A0; Fri, 26 Jul 2013 17:55:18 -0700 (PDT)
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 1V2smn-000Abo-PP; Fri, 26 Jul 2013 20:55:05 -0400
Date: Fri, 26 Jul 2013 20:55:00 -0400
From: John C Klensin <john-ietf@jck.com>
To: Tim Chown <tjc@ecs.soton.ac.uk>
Subject: Re: dnssdext BOF (was: Re: Remote participants, newcomers, and tutorials (was: IETF87  Audio Streaming Info))
Message-ID: <4750873F39F8835141851CEB@JcK-HP8200.jck.com>
In-Reply-To: <EMEW3|6371582239049b5739a44172e8e53bdep6Q0dL03tjc|ecs.soton.ac.uk|6FA0237E-C766-485D-8179-0355A70ACD47@ecs.soton.ac.uk>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net> <B0968F4989FF5E2FC4949CDC@JcK-HP8200.jck.com> <8115DE14-2262-430F-A78F-8DD66E9DF5F6@ecs.soton.ac.uk> <EMEW3|7d3cba230c8c24cd4f09676cdd63913dp6PMnY03tjc|ecs.soton.ac.uk|8115DE14-2262-430F-A78F-8DD66E9DF5F6@ecs.soton.ac.uk> <445D37B5E1C5893CE249C62C@JcK-HP8200.jck.com> <6FA0237E-C766-485D-8179-0355A70ACD47@ecs.soton.ac.uk> <EMEW3|6371582239049b5739a44172e8e53bdep6Q0dL03tjc|ecs.soton.ac.uk|6FA0237E-C766-485D-8179-0355A70ACD47@ecs.soton.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
Cc: SM <sm@resistor.net>, ietf@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Jul 2013 00:55:30 -0000

--On Saturday, July 27, 2013 00:37 +0100 Tim Chown
<tjc@ecs.soton.ac.uk> wrote:

>...
> While we/you can try to guess what the problems are, it may be
> better to surveymonkey those who registered as newcomers in a
> couple of weeks and ask them about their experience, whether
> they were aware of certain things, and what could be done
> better.

I hope that the mentoring program and assorted "ask me" dots
will take care of any of these issues for anyone who is in
Berlin.  If those newcomers have problems finding these things,
I hope they will bug someone.  If they do and can't get answers
or don't bother asking, those I'm slightly different problems.

So, right now, I'm personally more concerned about people who
are trying to participate remotely (or understand the IETF
remotely) for the first several times.  Given that, in general,
we have no idea who those people are, surveying them would be a
little difficult.  If a side-effect of these discussions is that
we change things enough that we do know who they are (at least
those who are willing to tell us in exchange for a bit more
support, sympathy, and the ability to take
remote-participant-specific surveys if those are offered), I'd
personally consider that a good thing.

best,
   john




From hallam@gmail.com  Fri Jul 26 18:20:24 2013
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 400D121F9644; Fri, 26 Jul 2013 18:20:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.183
X-Spam-Level: 
X-Spam-Status: No, score=-2.183 tagged_above=-999 required=5 tests=[AWL=0.417,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M-c3AF6+wHz9; Fri, 26 Jul 2013 18:20:23 -0700 (PDT)
Received: from mail-wg0-x229.google.com (mail-wg0-x229.google.com [IPv6:2a00:1450:400c:c00::229]) by ietfa.amsl.com (Postfix) with ESMTP id 60AFA21F9635; Fri, 26 Jul 2013 18:20:22 -0700 (PDT)
Received: by mail-wg0-f41.google.com with SMTP id n11so1294938wgh.4 for <multiple recipients>; Fri, 26 Jul 2013 18:20:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=2/YSbCrccZ7vCacBGaTCE+YmVJI+plC3Gl0Nac7qqDs=; b=SQi1PvDtCA/OkLLtpfY/93XdTCi3epyzzQCE7+v4pUJQ1M54na1RWMmf8GOlkaEfQc UBMrYXWolDE/e3yfB7DZCTqo6YGOlRMPq0aXiEc15X53d7S0qk95evEipJp3I2wACdno ezclc7Df1H2zOjIUPWysXgP9eYslF9Etuuqx6COTqgSx6xucE5ggu3pIDpblIQXbaNBq 4xpa+ruCF3ARUSig08ePcRYh/ZWwmIWJ7ycBIAPw1V2FScYbdCk5tD9QS6BiHwyp9sVm spT6fuYmhFUOfpn1UFex4Ban44RJyqy9SdLpKV82qol6ZVyZvbZ9NNXsyVlaGMzn1kdq Ytrw==
MIME-Version: 1.0
X-Received: by 10.180.183.40 with SMTP id ej8mr718552wic.37.1374888021423; Fri, 26 Jul 2013 18:20:21 -0700 (PDT)
Received: by 10.194.6.65 with HTTP; Fri, 26 Jul 2013 18:20:21 -0700 (PDT)
In-Reply-To: <EMEW3|6371582239049b5739a44172e8e53bdep6Q0dL03tjc|ecs.soton.ac.uk|6FA0237E-C766-485D-8179-0355A70ACD47@ecs.soton.ac.uk>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net> <B0968F4989FF5E2FC4949CDC@JcK-HP8200.jck.com> <8115DE14-2262-430F-A78F-8DD66E9DF5F6@ecs.soton.ac.uk> <EMEW3|7d3cba230c8c24cd4f09676cdd63913dp6PMnY03tjc|ecs.soton.ac.uk|8115DE14-2262-430F-A78F-8DD66E9DF5F6@ecs.soton.ac.uk> <6FA0237E-C766-485D-8179-0355A70ACD47@ecs.soton.ac.uk> <445D37B5E1C5893CE249C62C@JcK-HP8200.jck.com> <EMEW3|6371582239049b5739a44172e8e53bdep6Q0dL03tjc|ecs.soton.ac.uk|6FA0237E-C766-485D-8179-0355A70ACD47@ecs.soton.ac.uk>
Date: Fri, 26 Jul 2013 21:20:21 -0400
Message-ID: <CAMm+Lwhyt2Ery_TNOfaocmLxqD10pqvVYeqo16pBTp8f-=tnEg@mail.gmail.com>
Subject: Re: dnssdext BOF (was: Re: Remote participants, newcomers, and tutorials (was: IETF87 Audio Streaming Info))
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: multipart/alternative; boundary=001a11c2297a1f7d1004e2741075
Cc: John C Klensin <john-ietf@jck.com>, SM <sm@resistor.net>, IETF Discussion Mailing List <ietf@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Jul 2013 01:20:24 -0000

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

If I had known this was taking place I might have made the trip to Berlin.

I am very interested in the problem this tries to solve. I think it is the
wrong way to go about it but I am interested in the problem.

The case for having some sort of local name discovery mechanism is clear in
both the enterprise and the home network. The case for that discovery
mechanism responding to DNS queries in the local namespace is equally clear.

Thinking of this problem as how to clients configure their DNS entries is
completely the wrong way to go about it. Setting up a new network service
requires more than poking the DNS with a stick.



On Fri, Jul 26, 2013 at 7:37 PM, Tim Chown <tjc@ecs.soton.ac.uk> wrote:

> On 26 Jul 2013, at 23:31, John C Klensin <john-ietf@jck.com> wrote:
>
> --On Friday, July 26, 2013 22:48 +0100 Tim Chown
> <tjc@ecs.soton.ac.uk> wrote:
>
>
> That means the charter agreed from the bashing of the draft
> charter in the previous 40 minutes, not that a charter is
> already agreed.
>
>
> If there is something to be bashed for those 40 minutes, I'd
> expect a link to at least a skeleton first draft. I note that
> draft charter does have a link from the meeting materials page,
> just not from the agenda.   But, modulo the comment below, that
> is a matter of taste to be working out between you, Ralph, and
> the IESG.
>
>
> The draft charter was placed where they usually are, on the BoF wiki.  But
> I added a link to a specific draft charter file when I updated the agenda,
> see https://datatracker.ietf.org/meeting/87/agenda/dnssdext/.
>
> The other "problem" for mdnsext is that the second BoF has been given a
> different name, for various reasons, but that does make it a bit harder to
> locate the mail list and draft.
>
> True. Though the chair names are on the posters linked in the
> materials page, which I assume is well-advertised to newcomers
> as access to slides is rather important.
>
>
> As far as I know, the only "advertisement" is the link from the
> "Agendas and Meeting Materials" section of the main meeting page
> and the similar links from the Meetings entry on the IETF home
> page.  Now I'd personally like to see the "New Attendees"
> category on the main meeting page changed to "New Attendees and
> Participantes" and then including a link to a page that would
> give hints about where these things are and how to navigate
> around them.  But that fairly clearly won't happen before Sunday
> and YMMD.
>
>
> Well, I would certainly agree that the meeting materials page/area needs
> to be well advertised, if it isn't already, but I don't know what
> additional information newcomers are pointed at, not being one.
>
> And also on the BoF wiki, which you should know about.
>
>
> Yep.  I know about it and where to find it.  But, as I explained
> in my note to Brian, I'm a lot more concerned about newcomers
> and remote participants without years or experience than I am
> about what I can find if I remember all of the reasonable places
> where I might look.
>
>
> While we/you can try to guess what the problems are, it may be better to
> surveymonkey those who registered as newcomers in a couple of weeks and ask
> them about their experience, whether they were aware of certain things, and
> what could be done better.
>
> Tim
>



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

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

<div dir=3D"ltr">If I had known this was taking place I might have made the=
 trip to Berlin.<div><br></div><div>I am very interested in the problem thi=
s tries to solve. I think it is the wrong way to go about it but I am inter=
ested in the problem.</div>
<div><br></div><div>The case for having some sort of local name discovery m=
echanism is clear in both the enterprise and the home network. The case for=
 that discovery mechanism responding to DNS queries in the local namespace =
is equally clear.</div>
<div><br></div><div>Thinking of this problem as how to clients configure th=
eir DNS entries is completely the wrong way to go about it. Setting up a ne=
w network service requires more than poking the DNS with a stick.</div>
<div><br></div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Fri, Jul 26, 2013 at 7:37 PM, Tim Chown <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:tjc@ecs.soton.ac.uk" target=3D"_blank">tjc@ecs.soton.ac.uk<=
/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"><div><di=
v class=3D"im"><div>On 26 Jul 2013, at 23:31, John C Klensin &lt;<a href=3D=
"mailto:john-ietf@jck.com" target=3D"_blank">john-ietf@jck.com</a>&gt; wrot=
e:</div>
<br></div><blockquote type=3D"cite"><div class=3D"im">--On Friday, July 26,=
 2013 22:48 +0100 Tim Chown<br>&lt;<a href=3D"mailto:tjc@ecs.soton.ac.uk" t=
arget=3D"_blank">tjc@ecs.soton.ac.uk</a>&gt; wrote:<br></div><div class=3D"=
im"><blockquote type=3D"cite">
<br>That means the charter agreed from the bashing of the draft<br>charter =
in the previous 40 minutes, not that a charter is<br>already agreed.<br></b=
lockquote><br>If there is something to be bashed for those 40 minutes, I&#3=
9;d<br>
expect a link to at least a skeleton first draft. I note that<br>draft char=
ter does have a link from the meeting materials page,<br>just not from the =
agenda. =A0=A0But, modulo the comment below, that<br>is a matter of taste t=
o be working out between you, Ralph, and<br>
the IESG.<br></div></blockquote><div><br></div>The draft charter was placed=
 where they usually are, on the BoF wiki. =A0But I added a link to a specif=
ic draft charter file when I updated the agenda, see=A0<a href=3D"https://d=
atatracker.ietf.org/meeting/87/agenda/dnssdext/" target=3D"_blank">https://=
datatracker.ietf.org/meeting/87/agenda/dnssdext/</a>.</div>
<div><br></div><div>The other &quot;problem&quot; for mdnsext is that the s=
econd BoF has been given a different name, for various reasons, but that do=
es make it a bit harder to locate the mail list and draft.=A0</div><div><br=
>
</div><div><div class=3D"im"><blockquote type=3D"cite"><blockquote type=3D"=
cite">True. Though the chair names are on the posters linked in the<br>mate=
rials page, which I assume is well-advertised to newcomers<br>as access to =
slides is rather important.<br>
</blockquote><br>As far as I know, the only &quot;advertisement&quot; is th=
e link from the<br>&quot;Agendas and Meeting Materials&quot; section of the=
 main meeting page<br>and the similar links from the Meetings entry on the =
IETF home<br>
page. =A0Now I&#39;d personally like to see the &quot;New Attendees&quot;<b=
r>category on the main meeting page changed to &quot;New Attendees and<br>P=
articipantes&quot; and then including a link to a page that would<br>give h=
ints about where these things are and how to navigate<br>
around them. =A0But that fairly clearly won&#39;t happen before Sunday<br>a=
nd YMMD. <br></blockquote><div><br></div></div>Well, I would certainly agre=
e that the meeting materials page/area needs to be well advertised, if it i=
sn&#39;t already, but I don&#39;t know what additional information newcomer=
s are pointed at, not being one.</div>
<div class=3D"im"><div><br></div><div><blockquote type=3D"cite"><blockquote=
 type=3D"cite"> And also on the BoF wiki, which you should know about. =A0<=
br></blockquote><br>Yep. =A0I know about it and where to find it. =A0But, a=
s I explained<br>
in my note to Brian, I&#39;m a lot more concerned about newcomers<br>and re=
mote participants without years or experience than I am<br>about what I can=
 find if I remember all of the reasonable places<br>where I might look.<br>
</blockquote></div><div><br></div></div><div>While we/you can try to guess =
what the problems are, it may be better to surveymonkey those who registere=
d as newcomers in a couple of weeks and ask them about their experience, wh=
ether they were aware of certain things, and what could be done better.</di=
v>
<span class=3D"HOEnZb"><font color=3D"#888888"><div><br></div><div><div><di=
v>Tim</div></div></div></font></span></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>

--001a11c2297a1f7d1004e2741075--

From alejandroacostaalamo@gmail.com  Fri Jul 26 20:12:00 2013
Return-Path: <alejandroacostaalamo@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 381D611E81BF; Fri, 26 Jul 2013 20:12:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FOKY+1M6PUkY; Fri, 26 Jul 2013 20:11:59 -0700 (PDT)
Received: from mail-wg0-x231.google.com (mail-wg0-x231.google.com [IPv6:2a00:1450:400c:c00::231]) by ietfa.amsl.com (Postfix) with ESMTP id EAF6C11E81BB; Fri, 26 Jul 2013 20:11:58 -0700 (PDT)
Received: by mail-wg0-f49.google.com with SMTP id y10so2693518wgg.28 for <multiple recipients>; Fri, 26 Jul 2013 20:11:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ncIkbtxJomlzFpAepgmUAkCgBQmFt9WMdGOQuKTmpqA=; b=ilbTxYqWD0NOj+a0CAJMlUqcZzwnTMCEGH0vKCsD53LvqUj0R6R3ts3lYBoEZn8mek CA18HCk21UT09g8gGWBgxjO9rZKyVE/vNlv4Ot0tgKbeozDdyWVr9xHtu45iwue7UReN zlKKxIEhUHSeyv+NOqa1gCDnKU0F8oC8yF6c7lwXL/Ray++NpS1zErQ+CB5vukgeWPay 3abJmTEYUezJM2c68NWkti0PB6OMy7/bLJkJyym1NK81kJVMuZFrY7Fxi2rsjHkfmJKz OO8q1pb5si8n62I17kpGmzBLJfMIA3MoiAD6QhrwIUQV0GY30COP9xQnCGSrnLjJRFpk x1BA==
MIME-Version: 1.0
X-Received: by 10.194.9.101 with SMTP id y5mr36502792wja.86.1374894718086; Fri, 26 Jul 2013 20:11:58 -0700 (PDT)
Received: by 10.217.143.196 with HTTP; Fri, 26 Jul 2013 20:11:58 -0700 (PDT)
In-Reply-To: <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com>
Date: Fri, 26 Jul 2013 22:41:58 -0430
Message-ID: <CAOmxzdy6YPmgxw+7DVEjbKKu5djwbvp=dVo0+YH3nmg0jNn7GA@mail.gmail.com>
Subject: Re: Remote participants, newcomers, and tutorials (was: IETF87 Audio Streaming Info)
From: Alejandro Acosta <alejandroacostaalamo@gmail.com>
To: John C Klensin <john-ietf@jck.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: edu-team@ietf.org, ietf@ietf.org, rfc-editor@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Jul 2013 03:12:00 -0000

On 7/26/13, John C Klensin <john-ietf@jck.com> wrote:
> Hi.
>
> For a newcomer or someone expecting to write I-Ds, some of the
> most important sessions at the IETF are the various Sunday
> afternoon tutorials and introductions.  Many of them are (or
> should be) of as much interest to remote participants as to f2f
> attendees.   Until and unless a newcomer's tutorial can be
> prepared that is focused on remote participants, even that
> session should be of interest.
>
> For this particular meeting all of the following seem relevant
> to at least some remote participants:
>
> 	Newcomers' Orientation
> 	Tools for Creating I-Ds and RFCs
> 	IAOC Overview Session
> 	Multipath TCP
> 	Applying IP Flow Information Export (IPFIX) to Network
> Measurement and Management
>
> So...
>
> (1) The note below strongly implies that none of those sessions
> are being audiocast.    Why not and can that be fixed?
>
> (2) There is no hint on the agenda or tools agenda about
> availability of presentation and related materials (slides,
> etc.) for those sessions.  Do those materials not exist?  I
> know, but a newcomer or remote participant might not, that I can
> find some tutorials by going to the IETF main page and going to
> "Tutorial" under "Resources", but I have no idea which of those
> links actually reflects what will be presented on Sunday.
> Assuming the presentation materials do exist for at least
> several of the sessions, finding them is much like the situation
> with subscribing to the 87all list.  It should no involve a
> treasure hunt at which only very experienced IETF participants
> can be expected to succeed.
>
> Specific suggestions:
>
> (i) Let's get these open Sunday sessions audiocast and/or
> available over Meetecho or WebEx.  If that is impossible for
> IETF 87, it should be a priority for IETF 88 and later.

+1

>
> (ii) If there are presentation materials available, links from
> the tools agenda and an announcement to IETF-Announce as to
> where to find them would be desirable.
>
> (iii) If presentation materials are not available, why not?
> And, more important, can this be made a requirement for IETF 88
> and beyond?
>
> thanks,
>     john
>
>

From abdussalambaryun@gmail.com  Fri Jul 26 21:02:55 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E95121F9BAB; Fri, 26 Jul 2013 21:02:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UBSO4o6Idqxa; Fri, 26 Jul 2013 21:02:55 -0700 (PDT)
Received: from mail-pd0-x235.google.com (mail-pd0-x235.google.com [IPv6:2607:f8b0:400e:c02::235]) by ietfa.amsl.com (Postfix) with ESMTP id E85C521F9BA6; Fri, 26 Jul 2013 21:02:54 -0700 (PDT)
Received: by mail-pd0-f181.google.com with SMTP id g12so3038526pdj.40 for <multiple recipients>; Fri, 26 Jul 2013 21:02:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=5+6Au6+H4enxAsKp8DuFwXnkQzdAueFKS702W3wvxcE=; b=KESJ6RkAXbdL08DZr0hbEdrw+W74o5SDqoHD9KP6IOrpzqSsu7YN7MuxbUpQVkfati I8VD2zo6olj53MeP6ZBexj9hXXiEAirfjHqLy2AhPs4ThtfmU7aSrbCx752rqoBFw5w3 vrsmhKBUMUQFOcwa4dNVopkPdpoc9QVw3e+88Hq2ev3C1b0Dsp45QN58pJ2crcrnEl9T H7CFT7osx5UvEYISty8iEs0cyaHFeHcxPFakw3Zrdiz6RzGOxa5bOLV2HgQ6AM6FpbTD 9gAaHlv25yHQIF+uR9sv13ihDfvFMqfU70FEoMiZG8bXcFhP06B0XN3TVkw1sxY7hgdg dZfQ==
MIME-Version: 1.0
X-Received: by 10.67.22.69 with SMTP id hq5mr36124343pad.174.1374897774558; Fri, 26 Jul 2013 21:02:54 -0700 (PDT)
Received: by 10.68.250.133 with HTTP; Fri, 26 Jul 2013 21:02:54 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20130726101746.0c8db480@resistor.net>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net>
Date: Sat, 27 Jul 2013 06:02:54 +0200
Message-ID: <CADnDZ88vHLpNdJaKCHO=BPm4G_-rYxC0N8XCKHXokvXgzUK+9w@mail.gmail.com>
Subject: Re: Remote participants, newcomers, and tutorials (was: IETF87 Audio Streaming Info)
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: SM <sm@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: John C Klensin <john-ietf@jck.com>, edu-team@ietf.org, ietf@ietf.org, rfc-editor@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Jul 2013 04:03:17 -0000

On 7/26/13, SM <sm@resistor.net> wrote:
>
> The consensus of the IETF is that:
>
>    "newcomers who attend Working Group meetings are encouraged to
>     observe and absorb whatever material they can, but should not
>     interfere with the ongoing process of the group"

This is bad for IETF, why no interfer from new experience, does IETF
want to only be guided by longer-working people?

>
> It was also mentioned that:
>
>   "Working group meetings are not intended for the education of
>    individuals"

I think few ietf-WGs need to be educated or need mentoring, so
newcomers are recommended to help. I will add that it will be nice to
know the newcomers opinion about such consensus, and make an IETF
newcomer-WG consensus. The problem is that our IETF General Area (GA)
is still not covering all important issues and left to the IESG to
control thoes issues not the community. I requested before and still
want to do now, to suggest WGs in the GA, therefore, we avoid
discouraging reactions/decisions.

>
> The first quote might discourage newcomers from participating.  I
> suggest discussing about the two quotes during the orientation as
> they could be misunderstood.

Yes it does for me. I support your suggestion, because I don't think I
misunderstood, they seem clear to exclude newcomers and only include
groupings not individuals.

AB

From abdussalambaryun@gmail.com  Fri Jul 26 21:27:38 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD72221F9A74; Fri, 26 Jul 2013 21:27:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VlI0RRV4qy0V; Fri, 26 Jul 2013 21:27:38 -0700 (PDT)
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 287C621F9A65; Fri, 26 Jul 2013 21:27:38 -0700 (PDT)
Received: by mail-pd0-f177.google.com with SMTP id u11so3552168pdi.8 for <multiple recipients>; Fri, 26 Jul 2013 21:27:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=y4q9TcM0JM+vzuYxAgPyieA6joYwMDe22l6vU1jtI8E=; b=lnOMbBIJlSjw0usZyPr26uzXeGstXxjd4NtQlDnGIvSrxx8NLFZ19BbGb95G8CMg7P nLN3on6DtRYD+GBErz2QUvBe1nMnhcxr53wqSeuyUkf+rwwfsj/7LZskcbaRLvsUDXFJ KtanSJp90AkINosyZbmlmk+6KliEmnqOW8THJKycgtov5JtcMK9n0NoDuK4xyplg2Be2 6j6cKAyG5Z9+ojtWUs5/4zgSpCA2Ex9XMzISQyMFG7Po1/7+BFRITnqmQ0sSXUdURxkq SuVGshFny7nd7W4c1OfsSgvDi4mpfzRTxXls2JNYYVt/OuylZqB6dfh/1sgXjFwMrJaw 2eVw==
MIME-Version: 1.0
X-Received: by 10.68.228.201 with SMTP id sk9mr57143856pbc.4.1374899257750; Fri, 26 Jul 2013 21:27:37 -0700 (PDT)
Received: by 10.68.250.133 with HTTP; Fri, 26 Jul 2013 21:27:37 -0700 (PDT)
In-Reply-To: <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com>
Date: Sat, 27 Jul 2013 06:27:37 +0200
Message-ID: <CADnDZ88go41RThsfL1dO1J+Wn3N_2F7rAUJ-uPrvQ1GQ0AS1MQ@mail.gmail.com>
Subject: Re: Remote participants, newcomers, and tutorials (was: IETF87 Audio Streaming Info)
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: John C Klensin <john-ietf@jck.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "diversity@ietf.org" <diversity@ietf.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Jul 2013 04:27:39 -0000

Thanks, I agree with your points/suggestions. I want to add;

a) Work/Participation in IETF is remotely to run its daily business.

b) Newcomers (how many we have per meeting); are always welcomed, no
one in IETF have been participating for longer than 30 years, so some
how could we say participants are mostly all new (remotely+newBody).
It will be nice to have a presenter (one year ietf participant) in
session related to new comers so he/she can present their live
experience. IMHO, the IETF is always new not old, so we need newcomers
(let them speak and present in their session) to make IETF newer,
otherwise IETF will become old-oriented :-)

I define a new comer as one that have been participating for less than
5 years or never attended more than 2 meetings. It will be nice if all
newcomers with this definition gather together and discuss interested
issues.

c) Overall, all IETF participants including IESG members are mostly
serving IETF as Remote participants (new and old comers), but at
meeting days some are present at the venues and not remote. We need
both participation methods, and it is better to encourage both at all
times with equal access for diversity purposes.

AB

On 7/26/13, John C Klensin <john-ietf@jck.com> wrote:
> Hi.
>
> For a newcomer or someone expecting to write I-Ds, some of the
> most important sessions at the IETF are the various Sunday
> afternoon tutorials and introductions.  Many of them are (or
> should be) of as much interest to remote participants as to f2f
> attendees.   Until and unless a newcomer's tutorial can be
> prepared that is focused on remote participants, even that
> session should be of interest.
>
> For this particular meeting all of the following seem relevant
> to at least some remote participants:
>
> 	Newcomers' Orientation
> 	Tools for Creating I-Ds and RFCs
> 	IAOC Overview Session
> 	Multipath TCP
> 	Applying IP Flow Information Export (IPFIX) to Network
> Measurement and Management
>
> So...
>
> (1) The note below strongly implies that none of those sessions
> are being audiocast.    Why not and can that be fixed?
>
> (2) There is no hint on the agenda or tools agenda about
> availability of presentation and related materials (slides,
> etc.) for those sessions.  Do those materials not exist?  I
> know, but a newcomer or remote participant might not, that I can
> find some tutorials by going to the IETF main page and going to
> "Tutorial" under "Resources", but I have no idea which of those
> links actually reflects what will be presented on Sunday.
> Assuming the presentation materials do exist for at least
> several of the sessions, finding them is much like the situation
> with subscribing to the 87all list.  It should no involve a
> treasure hunt at which only very experienced IETF participants
> can be expected to succeed.
>
> Specific suggestions:
>
> (i) Let's get these open Sunday sessions audiocast and/or
> available over Meetecho or WebEx.  If that is impossible for
> IETF 87, it should be a priority for IETF 88 and later.
>
> (ii) If there are presentation materials available, links from
> the tools agenda and an announcement to IETF-Announce as to
> where to find them would be desirable.
>
> (iii) If presentation materials are not available, why not?
> And, more important, can this be made a requirement for IETF 88
> and beyond?
>
> thanks,
>     john
>
>
>
> --On Friday, July 26, 2013 12:00 +0200 Nick Kukich
> <nkukich@verilan.com> wrote:
>
>> Greetings,
>>
>> For those interested in monitoring sessions or participating
>> remotely the following information may prove useful.
>>...
>> All 8 parallel tracks at the IETF 87 meeting will be broadcast
>> starting with the commencement of working group sessions on
>> Monday, July 29, 2013 at 0900 CEST (UTC+2) and continue until
>> the close of sessions on Friday, August 2nd.
>>...
>
>

From jari.arkko@piuha.net  Fri Jul 26 23:17:23 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1963C11E81C4; Fri, 26 Jul 2013 23:17:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.573
X-Spam-Level: 
X-Spam-Status: No, score=-102.573 tagged_above=-999 required=5 tests=[AWL=0.026, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rXQV9-DCpBpo; Fri, 26 Jul 2013 23:17:19 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 9C80E11E80AD; Fri, 26 Jul 2013 23:17:18 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id BB0D92CC54; Sat, 27 Jul 2013 09:17:17 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H5fwHadcNBIZ; Sat, 27 Jul 2013 09:17:17 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id D7C202CC48; Sat, 27 Jul 2013 09:17:16 +0300 (EEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Remote participants, newcomers, and tutorials (was: IETF87 Audio Streaming Info)
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <6.2.5.6.2.20130726101746.0c8db480@resistor.net>
Date: Sat, 27 Jul 2013 09:17:16 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net>
To: SM <sm@resistor.net>, John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1508)
Cc: edu-team@ietf.org, "ietf@ietf.org list" <ietf@ietf.org>, rfc-editor@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Jul 2013 06:17:23 -0000

I agree with John that audio and other things would be useful, but Brian =
is also correct that they do involve some work. Let us see what we can =
do on audio for IETF-88. Past recordings of the tutorials are available =
at http://www.ietf.org/edu/process-oriented-tutorials.html#newcomers.

The meeting materials page does now have a training section now - added =
a couple of hours ago, thanks Alexa! - and some of the materials are =
there. We're working on putting the rest there.=20

(The newcomer's orientation file would already be there too but we're =
struggling with some bug in the system in the upload.)=20

As for:

> The consensus of the IETF is that:
>=20
>  "newcomers who attend Working Group meetings are encouraged to
>   observe and absorb whatever material they can, but should not
>   interfere with the ongoing process of the group"
>=20
> It was also mentioned that:
>=20
> "Working group meetings are not intended for the education of
>  individuals"
>=20
> The first quote might discourage newcomers from participating.  I =
suggest discussing about the two quotes during the orientation as they =
could be misunderstood.

The second quote is valid in most cases, though we've had some sessions =
at times that were designed more as education than discussion. For =
instance, the IAB WCIT BOF last time.

But the first one is just plain wrong. Is this from RFC 3184? Many of =
the first time IETFers are here for a reason, are well-versed in the =
technology in question, and very much able to provide suggestions to the =
WG. Maybe RFC 3184 is in the need of an update. (It also says other =
things that may not be up to date, like that locating mailing list =
archives is hard. I don=A8t think it has been hard ever since =
tools.ietf.org/wg/foo came about.)

Thanks for the feedback!

Jari

>=20
>> Specific suggestions:
>>=20
>> (i) Let's get these open Sunday sessions audiocast and/or
>> available over Meetecho or WebEx.  If that is impossible for
>> IETF 87, it should be a priority for IETF 88 and later.
>=20
> Yes.
>=20
> POSH has not published a session agenda.  However, the BoF is listed =
on the meeting agenda.  Is the BoF cancelled or will this be one of =
those willful violations of IETF Best Current Practices?
>=20
> Regards,
> -sm=20


From tjc@ecs.soton.ac.uk  Sat Jul 27 00:21:57 2013
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9EE521F9A1F; Sat, 27 Jul 2013 00:21:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level: 
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6Z3RPT8xKzS5; Sat, 27 Jul 2013 00:21:57 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id AFA3E21F9A1E; Sat, 27 Jul 2013 00:21:55 -0700 (PDT)
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 r6R7Lng2025218;  Sat, 27 Jul 2013 08:21:49 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r6R7Lng2025218
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1374909710; bh=wseA0CDurSO8oWOLs9KtWe3vYfQ=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=TXHKnbONuRNsDz3NDCOMauYXD7LyyB7lDZ8eDva1px51PmS9bujY7Ky8SysvxTjEf XHn6V+1qxf2PSaXF7nIW8l+3+tfEtrRqVTU4+3Hnoa0sgP0sT4BD9OFBOV21Y0kPAN BsH1z9421zSA/gFvwuhjN+OpKa5MqVZ8+Ub/MEqo=
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 p6Q8Ln0544512908Mc ret-id none; Sat, 27 Jul 2013 08:21:50 +0100
Received: from [192.168.1.110] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r6R7Le86017930 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 27 Jul 2013 08:21:40 +0100
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: dnssdext BOF (was: Re: Remote participants, newcomers, and tutorials (was: IETF87 Audio Streaming Info))
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <CAMm+Lwhyt2Ery_TNOfaocmLxqD10pqvVYeqo16pBTp8f-=tnEg@mail.gmail.com>
Date: Sat, 27 Jul 2013 08:21:40 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|787a3b9213e01352a01cc3f1333a2434p6Q8Ln03tjc|ecs.soton.ac.uk|64889D4C-8B17-4079-92DD-5948A8827243@ecs.soton.ac.uk>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net> <B0968F4989FF5E2FC4949CDC@JcK-HP8200.jck.com> <8115DE14-2262-430F-A78F-8DD66E9DF5F6@ecs.soton.ac.uk> <EMEW3|7d3cba230c8c24cd4f09676cdd63913dp6PMnY03tjc|ecs.soton.ac.uk|8115DE14-2262-430F-A78F-8DD66E9DF5F6@ecs.soton.ac.uk> <6FA0237E-C766-485D-8179-0355A70ACD47@ecs.soton.ac.uk> <445D37B5E1C5893CE249C62C@JcK-HP8200.jck.com> <EMEW3|6371582239049b5739a44172e8e53bdep6Q0dL03tjc|ecs.soton.ac.uk|6FA0237E-C766-485D-8179-0355A70ACD47@ecs.soton.ac.uk> <CAMm+Lwhyt2Ery_TNOfaocmLxqD10pqvVYeqo16pBTp8f-=tnEg@mail.gmail.com> <64889D4C-8B17-4079-92DD-5948A8827243@ecs.soton.ac.uk>
To: Phillip Hallam-Baker <hallam@gmail.com>
X-Mailer: Apple Mail (2.1508)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p6Q8Ln054451290800; tid=p6Q8Ln0544512908Mc; client=relay,ipv6; mail=; rcpt=; nrcpt=5:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r6R7Lng2025218
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: John C Klensin <john-ietf@jck.com>, SM <sm@resistor.net>, IETF Discussion Mailing List <ietf@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Jul 2013 07:21:57 -0000

On 27 Jul 2013, at 02:20, Phillip Hallam-Baker <hallam@gmail.com> wrote:

> If I had known this was taking place I might have made the trip to =
Berlin.
>=20
> I am very interested in the problem this tries to solve. I think it is =
the wrong way to go about it but I am interested in the problem.
>=20
> The case for having some sort of local name discovery mechanism is =
clear in both the enterprise and the home network. The case for that =
discovery mechanism responding to DNS queries in the local namespace is =
equally clear.
>=20
> Thinking of this problem as how to clients configure their DNS entries =
is completely the wrong way to go about it. Setting up a new network =
service requires more than poking the DNS with a stick.

Phil, comments on draft-lynn-mdnsext-requirements are very welcome.

There should be a jabber realy who can forward remote comments to the =
mic.

Tim


From sm@resistor.net  Sat Jul 27 01:50:40 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF84221F9DF1; Sat, 27 Jul 2013 01:50:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.463
X-Spam-Level: 
X-Spam-Status: No, score=-102.463 tagged_above=-999 required=5 tests=[AWL=0.136, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qe3FTRtF2taV; Sat, 27 Jul 2013 01:50:39 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 58ADD21F9DF0; Sat, 27 Jul 2013 01:50:39 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r6R8oOKq027759; Sat, 27 Jul 2013 01:50:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1374915032; bh=82A5irKcXvZEywYlE+uw1nwnJUzjkj1oTyQPYofUOIY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=YLy0hTbTcMh3DEodaWnuZRJQFt0VyLx/SJnOyVMWvkrP1BAoqAzdcIfg+vk2C3Gbo yRXqDxUreiAdlm0oRcqBAc2ydc+4IgtVRCUUef+9nfBRuhwBlrI0cogyM/xmZ3XFtU THb7xBX8b7QXkdyNyNNssNhmGZZNMNdVxkhafiC8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1374915032; i=@resistor.net; bh=82A5irKcXvZEywYlE+uw1nwnJUzjkj1oTyQPYofUOIY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=XZE4AL9ObDMxFu6CgbH8f2P2qtWnWlIECKSNjV3is5wX4tssfv4jGmEM8YG7ixrH7 kAU9jmnQ2HP8AX51nqP2mZPlzniz+15yo+ylFQ4w6QP7/vvmzBUiyw7mSAQeiFoV0j OguhLE1FF4xMrai+tmCIhaSDVZU/lwNJ3lBrHHBU=
Message-Id: <6.2.5.6.2.20130726223413.0b86d7e0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 27 Jul 2013 00:43:59 -0700
To: John C Klensin <john-ietf@jck.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: Oh look! [Re: Remote participants, newcomers, and tutorials]
In-Reply-To: <B2856A2101451CF971914EFA@JcK-HP8200.jck.com>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <51F2DD2A.7040700@gmail.com> <51F2DE5F.1010708@gmail.com> <B2856A2101451CF971914EFA@JcK-HP8200.jck.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: edu-team@ietf.org, ietf@ietf.org, rfc-editor@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Jul 2013 08:50:41 -0000

At 15:10 26-07-2013, John C Klensin wrote:
>However, the IETF has been having a lot of discussions about
>newcomers, diversity, and attracting new folks to participate
>and get work done.  I think those populations will be better
>served if it is possible for people a lot less experienced than
>the two of us can participate actively and constructively
>without attending every meeting.  I also think that, especially
>for many people from developing countries, universities, small
>companies, and far-away places, we will be far more successful
>in recruiting if we can encourage remote participation as a
>starting point with the expectation of getting people physically
>to meetings only after the value to them and their organizations
>of doing so has been demonstrated.  I'd personally even favor
>making remote participation at a could of meeting be a
>prerequisite for most applications for ISOC's IETF Fellows
>program.

Discussions that do not translation into actions are, well, 
discussions.  What is the easiest to enable the person from the 
university participate in the IETF meeting; what is the easiest way 
to enable the person from the small company to participate in the 
IETF meeting?  It is:

   (a) an audio stream

   (b) a jabber service

   (c) a jabber scribe

(a) and (b) are already available.  (c) is doable.  Will there be any 
results from that?  No.  Why should the IETF do that then?  Because 
it is simple, it is cheap, and if it works, who knows, there may be results.

>But the above picture isn't going to happen unless we are
>serious and treat that seriousness as an integral part of our
>strategies about newcomers and diversity.  Seriousness to me
>says that we get more careful about how experienced one has to
>be to find critical information, that we make sure remote
>participation works, and that we make any session that would be
>relevant to remote participants accessible to them (and with
>materials available as much as possible in advance and from
>easy-to-find places).  Seriousness implies that, if there are
>extra costs, we figure out how to cover them (or how to cut
>somewhere else).

Making information available is a first-step in getting things to 
work.  Please note that I do not see that as publishing some random 
web page.  I see that as making the information readily available to 
the target audience.

I'll quote part of a message from Benoit Claise:

   'Let me explain what the targeted audience is for those posters.

    It's not intended for the people who know about a specific BoF and plan on
    participating. It's intended for people who have not prepared for 
a specific
    BoF, but just come to listen to it, and in the end, go to mic. to provide
    some useful feedback: "pay attention to this!", "similar work was 
done ...",
    "don't forget that ...", "don't forget OPS" ;-)'

It is a down-to-earth explanation about how to get people interested 
in a specific BoF.

Two years ago (minus one day) Brian Carpenter objected to the fact 
that the regular
audio streaming is not available for the plenaries.  The link for the 
technical plenary audio stream is not available in the (tools) agenda.

>Or, if we are not serious, it would probably be to the benefit
>of the community for us to face that and stop wasting energy and
>resources on outreach efforts that are expensive in one or the
>other (or both).

It is a waste of energy and money to pursue outreach efforts if the 
IETF is not serious about how to lower the barriers for newcomers and 
its strategy about diversity.

Regards,
-sm 


From leaf.yeh.sdo@gmail.com  Sat Jul 27 01:53:52 2013
Return-Path: <leaf.yeh.sdo@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5DA521F9DAF for <ietf@ietfa.amsl.com>; Sat, 27 Jul 2013 01:53:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.293
X-Spam-Level: 
X-Spam-Status: No, score=-2.293 tagged_above=-999 required=5 tests=[AWL=0.305,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1w+z5Pinkbvk for <ietf@ietfa.amsl.com>; Sat, 27 Jul 2013 01:53:51 -0700 (PDT)
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 6056C21F99A8 for <ietf@ietf.org>; Sat, 27 Jul 2013 01:53:51 -0700 (PDT)
Received: by mail-pd0-f178.google.com with SMTP id w10so869076pde.37 for <ietf@ietf.org>; Sat, 27 Jul 2013 01:53:51 -0700 (PDT)
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:x-mailer:thread-index:content-language; bh=xjk1IUnQbXgeGSg3942aguwqeJikhN1aYPJG8kcVOaA=; b=BBFF7Uytc25lyZaZ+M/gENOM5QRcmxya3stkLYmzI73r9lNFzdJxaQT0mt4GILqJy8 xPTT8p/AQTyj6mcqVQcjcUs7Ifm6DdaUf0ezNHjEIIaIZr10oDxGXRY8XZsPNSsog3e9 ElFOyojmH6ltnWgLlD2D0GZn7pxoc5YHn26ShgyISmq6WqVEV2qmVlj4waOwzlwapSpW l0vkN/na0PP9g53wwRZQ9sx4G7fVzvyTvRrhT61BQxOT9GkFcExk8i2ytbf4WA7D+l+u Wciz/E5fcz8K1eQ3+JsZ5kaPeoEQsqV/zmc1iXG+98SUqtX0dRDtf0yCy+g9aeKDn3wi HUOg==
X-Received: by 10.68.224.161 with SMTP id rd1mr58070601pbc.121.1374915231047;  Sat, 27 Jul 2013 01:53:51 -0700 (PDT)
Received: from PC ([114.248.234.99]) by mx.google.com with ESMTPSA id om2sm7230093pbc.30.2013.07.27.01.53.45 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Sat, 27 Jul 2013 01:53:50 -0700 (PDT)
From: "Leaf Yeh" <leaf.yeh.sdo@gmail.com>
To: "'Ted Hardie'" <ted.ietf@gmail.com>
References: <CANF0JMBtNf9+=+CXo0xydfQ8AtQWaVYVKLBHmq8jBR-s2AuC7A@mail.gmail.com>	<CA+9kkMDZoX0Eq4TcbpP=+YMPmq-F3CAGB1dSogYJa6V2F-irbQ@mail.gmail.com>	<CANF0JMCA+HQ7=xEXjDkgxLt2iqUj3Wdq_+2+KFsPg34a0m+nxQ@mail.gmail.com>	<CA+9kkMCqRL5R8v5RivjRkNHQtMFiKs3Rhva+X5NogMB6_qMaSQ@mail.gmail.com>	<CAProHASRwM8-Nnd6rPsXtXk85Vb9gNeBshppFjUQxpnLTJsjDg@mail.gmail.com>	<51f22c1f.a3fe420a.6639.ffff8235@mx.google.com> <CA+9kkMC1fGLmLnVVE9o+p26syJSmc-hfaVQhvu4oRz+9QzWnkw@mail.gmail.com>
In-Reply-To: <CA+9kkMC1fGLmLnVVE9o+p26syJSmc-hfaVQhvu4oRz+9QzWnkw@mail.gmail.com>
Subject: RE: Regarding call Chinese names
Date: Sat, 27 Jul 2013 16:53:40 +0800
Message-ID: <51f38a9e.02d8440a.3ca6.ffff8f08@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00B1_01CE8AE9.DB060160"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac6KKK5s3PPOs4NPSYusr8G/glrrUAAbaPdA
Content-Language: zh-cn
Cc: 'IETF Discussion' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Jul 2013 08:53:52 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_00B1_01CE8AE9.DB060160
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

I have not learned  Yale romanization for Cantonese and jyutping (you =
mentioned) before. The following are my homework of today for you: -)

=20

a.       Per the Wikipidia @ =
http://en.wikipedia.org/wiki/Yale_Romanization=20

=20

Mandarin Yale was developed in 1943 by the Yale sinologist  =
<http://en.wikipedia.org/wiki/George_A._Kennedy_(sinologist)> George =
Kennedy to help prepare American soldiers to communicate with their =
Chinese allies on the battlefield. Rather than try to teach recruits to =
interpret the standard romanization of the time, the  =
<http://en.wikipedia.org/wiki/Wade%E2%80%93Giles> Wade=E2=80=93Giles =
system, a new system was invented that utilized the decoding skills that =
recruits would already know from having learned to read English, i.e. it =
used English spelling conventions to represent Chinese sounds.

=E2=80=A6

=20

Unlike the Mandarin Yale romanization, Cantonese Yale is still widely =
used in books and dictionaries for  =
<http://en.wikipedia.org/wiki/Standard_Cantonese> Cantonese, especially =
for foreign learners.  Developed by  =
<http://en.wikipedia.org/w/index.php?title=3DParker_Po-fei_Huang&action=3D=
edit&redlink=3D1> Parker Po-fei Huang and  =
<http://en.wikipedia.org/w/index.php?title=3DGerald_P._Kok&action=3Dedit&=
redlink=3D1> Gerald P. Kok and published in 1970,=E2=80=A6

=20

=E2=80=A6, Yale romanization is usually held to be easy for  =
<http://en.wikipedia.org/wiki/American_English> American English =
speakers to pronounce without much training. In  =
<http://en.wikipedia.org/wiki/Hong_Kong> Hong Kong, more people use  =
<http://en.wikipedia.org/wiki/Cantonese_Pinyin> Cantonese Pinyin and  =
<http://en.wikipedia.org/wiki/Jyutping> Jyutping, as these systems are =
more localized to Hong Kong people. Foreign students of Cantonese who =
attend Hong Kong University use Sidney Lau's spelling of Cantonese from =
his three-volume textbooks. Foreign students of Cantonese who attend =
Chinese University of Hong Kong's New-Asia Yale-in-China Chinese =
Language Center are taught to use the Yale spelling of Cantonese and =
eventually learn to read those traditional English voiced consonants in =
a new unvoiced Cantonese way subconsciously, without realizing they are =
doing so or without usually being aware of the linguistic difference.

=20

b.       Per the Wikipidia @ =
http://en.wikipedia.org/wiki/Cantonese_Pinyin=20

=20

Cantonese Pinyin ( =
<http://en.wikipedia.org/wiki/Traditional_Chinese_characters> Chinese: =
=E5=B8=B8=E7=94=A8=E5=AD=97=E5=BB=A3=E5=B7=9E=E8=A9=B1=E8=AE=80=E9=9F=B3=E8=
=A1=A8:=E6=8B=BC=E9=9F=B3=E6=96=B9=E6=A1=88, also known as =
=E6=95=99=E9=99=A2=E5=BC=8F=E6=8B=BC=E9=9F=B3=E6=96=B9=E6=A1=88) is a  =
<http://en.wikipedia.org/wiki/Romanization> romanization system for  =
<http://en.wikipedia.org/wiki/Standard_Cantonese> Cantonese developed by =
Yu Bingzhao (=E4=BD=99=E7=A7=89=E6=98=AD) in 1971, and subsequently =
modified by the Education Department (merged into the  =
<http://en.wikipedia.org/wiki/Education_and_Manpower_Bureau> Education =
and Manpower Bureau since 2003) of Hong Kong and  =
<http://en.wikipedia.org/w/index.php?title=3DZhan_Bohui&action=3Dedit&red=
link=3D1> Zhan Bohui (=E8=A9=B9=E4=BC=AF=E6=85=A7). It was used by =
Tongyin zihui (=E5=90=8C=E9=9F=B3=E5=AD=97=E5=BD=99), Cantonese =
Pronunciation list of Chinese Characters in Common Use =
(=E5=B8=B8=E7=94=A8=E5=AD=97=E5=BB=A3=E5=B7=9E=E8=A9=B1=E8=AE=80=E9=9F=B3=
=E8=A1=A8), Dictionary of Standard Cantonese Pronunciation =
(=E5=BB=A3=E5=B7=9E=E8=A9=B1=E6=AD=A3=E9=9F=B3=E5=AD=97=E5=85=B8), and =
List of Chinese Characters in Common Use for Primary education =
(=E5=B0=8F=E5=AD=B8=E4=B8=AD=E6=96=87=E7=A7=91=E5=B8=B8=E7=94=A8=E5=AD=97=
=E8=A1=A8). It is the only romanization system accepted by  =
<http://en.wikipedia.org/wiki/Education_and_Manpower_Bureau> Education =
and Manpower Bureau of Hong Kong and  =
<http://en.wikipedia.org/wiki/Hong_Kong_Examinations_and_Assessment_Autho=
rity> Hong Kong Examinations and Assessment Authority.

=20

c.       Per the Wikipidia @ http://en.wikipedia.org/wiki/Jyutping=20

=20

Jyutping =EF=BC=88Jyutping=EF=BC=9A =
<http://www.forvo.com/download/mp3/%E7%B2%A4%E6%8B%BC/yue/2248626> jyut6 =
ping3=EF=BC=89(Cantonese pronunciation:  =
<http://en.wikipedia.org/wiki/Help:IPA_for_Cantonese> =
[jy=CB=90t=CC=9A=CB=A8 p=CA=B0=C9=AA=C5=8B=CB=A7]), sometimes spelled =
Jyutpin) is a  <http://en.wikipedia.org/wiki/Romanization> romanization =
system for  <http://en.wikipedia.org/wiki/Standard_Cantonese> =
Cantonesedeveloped by the  =
<http://en.wikipedia.org/wiki/Linguistic_Society_of_Hong_Kong> =
Linguistic Society of Hong Kong (LSHK) in 1993. Its formal name is The =
Linguistic Society of Hong Kong Cantonese Romanization Scheme. The LSHK =
promotes the use of this romanization system.

=20

=20

Mr. Leung (http://en.wikipedia.org/wiki/Leung_Chun_Ying ) and Mr. Tung =
(http://en.wikipedia.org/wiki/Tung_Chee_Hwa) were born before 1970,  so =
I believe they had no chance to adopt Yale romanization for Cantonese =
and jyutping for their name=E2=80=99s spelling.=20

=20

=20

Best Regards,

Leaf

=20

=20

=20

From: Ted Hardie [mailto:ted.ietf@gmail.com]=20
Sent: Saturday, July 27, 2013 1:51 AM
To: Leaf Yeh
Cc: Cao,Zhen; IETF Discussion
Subject: Re: Regarding call Chinese names

=20

On Fri, Jul 26, 2013 at 12:58 AM, Leaf Yeh <leaf.yeh.sdo@gmail.com> =
wrote:

a. I suppose Mr. Leung and Mr. Tung used Wade-Giles Romanization (or =
system)
for their name's spelling, which looks very popular outside China =
mainland
including Hong Kong, and inside China mainland before the year of 1958 =
when
Pinyin (Chinese phonetic alphabet) was published.


Wade-Giles is a romanization system for Mandarin, not Cantonese.  The =
Yale romanization for Cantonese developed by Parker Po-fei Huang and the =
jyutping  (=E7=B2=B5=E6=8B=BC) are more likely sources for Cantonese =
names which use a codified romanization system (jyutping being more =
recent).  Many names use folk romanizations, rather than following a =
specific system.

regards,

Ted Hardie
=20


------=_NextPart_000_00B1_01CE8AE9.DB060160
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta =
name=3DGenerator content=3D"Microsoft Word 12 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:=E5=AE=8B=E4=BD=93;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@=E5=AE=8B=E4=BD=93";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:=E5=AE=8B=E4=BD=93;}
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.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin:0cm;
	margin-bottom:.0001pt;
	text-indent:21.0pt;
	font-size:12.0pt;
	font-family:=E5=AE=8B=E4=BD=93;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.apple-converted-space
	{mso-style-name:apple-converted-space;}
span.ipa
	{mso-style-name:ipa;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:2017075041;
	mso-list-type:hybrid;
	mso-list-template-ids:-479674464 93081116 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:18.0pt;
	text-indent:-18.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></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=3DZH-CN link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I have not learned =C2=A0Yale romanization for Cantonese and jyutping =
(you mentioned) before. The following are my homework of today for you: =
-)<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoListParagraph =
style=3D'margin-left:18.0pt;text-indent:-18.0pt;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span style=3D'mso-list:Ignore'>a.<span style=3D'font:7.0pt "Times =
New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Per the Wikipidia @ <a =
href=3D"http://en.wikipedia.org/wiki/Yale_Romanization">http://en.wikiped=
ia.org/wiki/Yale_Romanization</a> <o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><b><span =
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>Mandarin Yale</span></b><span =
class=3Dapple-converted-space><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>&nbsp;</span></span><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>was developed in 1943 by the Yale sinologist =
</span><span lang=3DEN-US><a =
href=3D"http://en.wikipedia.org/wiki/George_A._Kennedy_(sinologist)" =
title=3D"George A. Kennedy (sinologist)"><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#0B0080;=
background:white'>George Kennedy</span></a></span><span =
class=3Dapple-converted-space><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>&nbsp;</span></span><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>to help prepare American soldiers to communicate with =
their Chinese allies on the battlefield. Rather than try to teach =
recruits to interpret the standard romanization of the time, the<span =
class=3Dapple-converted-space>&nbsp;</span></span><span lang=3DEN-US><a =
href=3D"http://en.wikipedia.org/wiki/Wade%E2%80%93Giles" =
title=3D"Wade=E2=80=93Giles"><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#0B0080;=
background:white'>Wade=E2=80=93Giles</span></a></span><span =
class=3Dapple-converted-space><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>&nbsp;</span></span><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>system, a new system was invented that utilized the =
decoding skills that recruits would already know from having learned to =
read English, i.e. it used English spelling conventions to represent =
Chinese sounds.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>=E2=80=A6</span><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>Unlike the Mandarin Yale romanization,<span =
class=3Dapple-converted-space>&nbsp;</span><b>Cantonese Yale</b><span =
class=3Dapple-converted-space>&nbsp;</span>is still widely used in books =
and dictionaries for<span =
class=3Dapple-converted-space>&nbsp;</span></span><span lang=3DEN-US><a =
href=3D"http://en.wikipedia.org/wiki/Standard_Cantonese" =
title=3D"Standard Cantonese"><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#0B0080;=
background:white'>Cantonese</span></a></span><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>, especially for foreign learners. <span =
class=3Dapple-converted-space>&nbsp;</span>Developed by<span =
class=3Dapple-converted-space>&nbsp;</span></span><span lang=3DEN-US><a =
href=3D"http://en.wikipedia.org/w/index.php?title=3DParker_Po-fei_Huang&a=
mp;action=3Dedit&amp;redlink=3D1" title=3D"Parker Po-fei Huang (page =
does not exist)"><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#A55858;=
background:white'>Parker Po-fei Huang</span></a></span><span =
class=3Dapple-converted-space><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>&nbsp;</span></span><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>and<span =
class=3Dapple-converted-space>&nbsp;</span></span><span lang=3DEN-US><a =
href=3D"http://en.wikipedia.org/w/index.php?title=3DGerald_P._Kok&amp;act=
ion=3Dedit&amp;redlink=3D1" title=3D"Gerald P. Kok (page does not =
exist)"><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#A55858;=
background:white'>Gerald P. Kok</span></a></span><span =
class=3Dapple-converted-space><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>&nbsp;</span></span><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>and published in 1970,=E2=80=A6<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>=E2=80=A6, Yale romanization is usually held to be easy =
for<span class=3Dapple-converted-space>&nbsp;</span></span><span =
lang=3DEN-US><a href=3D"http://en.wikipedia.org/wiki/American_English" =
title=3D"American English"><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#0B0080;=
background:white'>American English</span></a></span><span =
class=3Dapple-converted-space><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>&nbsp;</span></span><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>speakers to pronounce without much training. In<span =
class=3Dapple-converted-space>&nbsp;</span></span><span lang=3DEN-US><a =
href=3D"http://en.wikipedia.org/wiki/Hong_Kong" title=3D"Hong =
Kong"><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#0B0080;=
background:white'>Hong Kong</span></a></span><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>, more people use<span =
class=3Dapple-converted-space>&nbsp;</span></span><span lang=3DEN-US><a =
href=3D"http://en.wikipedia.org/wiki/Cantonese_Pinyin" =
title=3D"Cantonese Pinyin"><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#0B0080;=
background:white'>Cantonese Pinyin</span></a></span><span =
class=3Dapple-converted-space><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>&nbsp;</span></span><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>and<span =
class=3Dapple-converted-space>&nbsp;</span></span><span lang=3DEN-US><a =
href=3D"http://en.wikipedia.org/wiki/Jyutping" title=3DJyutping><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#0B0080;=
background:white'>Jyutping</span></a></span><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>, as these systems are more localized to Hong Kong =
people. Foreign students of Cantonese who attend Hong Kong University =
use Sidney Lau's spelling of Cantonese from his three-volume textbooks. =
Foreign students of Cantonese who attend Chinese University of Hong =
Kong's New-Asia Yale-in-China Chinese Language Center are taught to use =
the Yale spelling of Cantonese and eventually learn to read those =
traditional English voiced consonants in a new unvoiced Cantonese way =
subconsciously, without realizing they are doing so or without usually =
being aware of the linguistic difference.</span><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoListParagraph =
style=3D'margin-left:18.0pt;text-indent:-18.0pt;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span style=3D'mso-list:Ignore'>b.<span style=3D'font:7.0pt "Times =
New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Per the Wikipidia @ <a =
href=3D"http://en.wikipedia.org/wiki/Cantonese_Pinyin">http://en.wikipedi=
a.org/wiki/Cantonese_Pinyin</a> <o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><b><span =
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>Cantonese Pinyin</span></b><span =
class=3Dapple-converted-space><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>&nbsp;</span></span><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>(</span><span lang=3DEN-US><a =
href=3D"http://en.wikipedia.org/wiki/Traditional_Chinese_characters" =
title=3D"Traditional Chinese characters"><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#0B0080;=
background:white'>Chinese</span></a></span><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>:<span =
class=3Dapple-converted-space>&nbsp;</span></span><span =
style=3D'font-size:10.0pt;color:black;background:white'>=E5=B8=B8=E7=94=A8=
=E5=AD=97=E5=BB=A3=E5=B7=9E=E8=A9=B1=E8=AE=80=E9=9F=B3=E8=A1=A8</span><sp=
an lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>:</span><span =
style=3D'font-size:10.0pt;color:black;background:white'>=E6=8B=BC=E9=9F=B3=
=E6=96=B9=E6=A1=88</span><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>, also known as<span =
class=3Dapple-converted-space>&nbsp;</span></span><span lang=3DZH =
style=3D'font-size:10.0pt;color:black;background:white'>=E6=95=99=E9=99=A2=
=E5=BC=8F=E6=8B=BC=E9=9F=B3=E6=96=B9=E6=A1=88</span><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>) is a<span =
class=3Dapple-converted-space>&nbsp;</span></span><span lang=3DEN-US><a =
href=3D"http://en.wikipedia.org/wiki/Romanization" =
title=3DRomanization><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#0B0080;=
background:white'>romanization</span></a></span><span =
class=3Dapple-converted-space><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>&nbsp;</span></span><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>system for<span =
class=3Dapple-converted-space>&nbsp;</span></span><span lang=3DEN-US><a =
href=3D"http://en.wikipedia.org/wiki/Standard_Cantonese" =
title=3D"Standard Cantonese"><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#0B0080;=
background:white'>Cantonese</span></a> </span><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>developed by Yu Bingzhao (</span><span =
style=3D'font-size:10.0pt;color:black;background:white'>=E4=BD=99=E7=A7=89=
=E6=98=AD</span><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>) in 1971, and subsequently modified by the Education =
Department (merged into the<span =
class=3Dapple-converted-space>&nbsp;</span></span><span lang=3DEN-US><a =
href=3D"http://en.wikipedia.org/wiki/Education_and_Manpower_Bureau" =
title=3D"Education and Manpower Bureau"><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#0B0080;=
background:white'>Education and Manpower Bureau</span></a></span><span =
class=3Dapple-converted-space><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>&nbsp;</span></span><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>since 2003) of Hong Kong and<span =
class=3Dapple-converted-space>&nbsp;</span></span><span lang=3DEN-US><a =
href=3D"http://en.wikipedia.org/w/index.php?title=3DZhan_Bohui&amp;action=
=3Dedit&amp;redlink=3D1" title=3D"Zhan Bohui (page does not =
exist)"><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#A55858;=
background:white'>Zhan Bohui</span></a></span><span =
class=3Dapple-converted-space><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>&nbsp;</span></span><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>(</span><span =
style=3D'font-size:10.0pt;color:black;background:white'>=E8=A9=B9=E4=BC=AF=
=E6=85=A7</span><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>). It was used by<span =
class=3Dapple-converted-space>&nbsp;</span><i>Tongyin zihui</i><span =
class=3Dapple-converted-space>&nbsp;</span>(</span><span =
style=3D'font-size:10.0pt;color:black;background:white'>=E5=90=8C=E9=9F=B3=
=E5=AD=97=E5=BD=99</span><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>),<span =
class=3Dapple-converted-space>&nbsp;</span><i>Cantonese Pronunciation =
list of Chinese Characters in Common Use</i><span =
class=3Dapple-converted-space>&nbsp;</span>(</span><span =
style=3D'font-size:10.0pt;color:black;background:white'>=E5=B8=B8=E7=94=A8=
=E5=AD=97=E5=BB=A3=E5=B7=9E=E8=A9=B1=E8=AE=80=E9=9F=B3=E8=A1=A8</span><sp=
an lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>),<span =
class=3Dapple-converted-space>&nbsp;</span><i>Dictionary of Standard =
Cantonese Pronunciation</i><span =
class=3Dapple-converted-space>&nbsp;</span>(</span><span =
style=3D'font-size:10.0pt;color:black;background:white'>=E5=BB=A3=E5=B7=9E=
=E8=A9=B1=E6=AD=A3=E9=9F=B3=E5=AD=97=E5=85=B8</span><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>), and<span =
class=3Dapple-converted-space>&nbsp;</span><i>List of Chinese Characters =
in Common Use for Primary education</i><span =
class=3Dapple-converted-space>&nbsp;</span>(</span><span =
style=3D'font-size:10.0pt;color:black;background:white'>=E5=B0=8F=E5=AD=B8=
=E4=B8=AD=E6=96=87=E7=A7=91=E5=B8=B8=E7=94=A8=E5=AD=97=E8=A1=A8</span><sp=
an lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>). It is the only romanization system accepted by<span =
class=3Dapple-converted-space>&nbsp;</span></span><span lang=3DEN-US><a =
href=3D"http://en.wikipedia.org/wiki/Education_and_Manpower_Bureau" =
title=3D"Education and Manpower Bureau"><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#0B0080;=
background:white'>Education and Manpower Bureau</span></a></span><span =
class=3Dapple-converted-space><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>&nbsp;</span></span><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>of Hong Kong and<span =
class=3Dapple-converted-space>&nbsp;</span></span><span lang=3DEN-US><a =
href=3D"http://en.wikipedia.org/wiki/Hong_Kong_Examinations_and_Assessmen=
t_Authority" title=3D"Hong Kong Examinations and Assessment =
Authority"><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#0B0080;=
background:white'>Hong Kong Examinations and Assessment =
Authority</span></a></span><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>.</span><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoListParagraph =
style=3D'margin-left:18.0pt;text-indent:-18.0pt;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span style=3D'mso-list:Ignore'>c.<span style=3D'font:7.0pt "Times =
New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Per the Wikipidia @ <a =
href=3D"http://en.wikipedia.org/wiki/Jyutping">http://en.wikipedia.org/wi=
ki/Jyutping</a> <o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><b><span =
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>Jyutping</span></b><span =
class=3Dapple-converted-space><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>&nbsp;</span></span><span =
style=3D'font-size:10.0pt;color:black;background:white'>=EF=BC=88</span><=
span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>Jyutping</span><span =
style=3D'font-size:10.0pt;color:black;background:white'>=EF=BC=9A</span><=
span lang=3DEN-US><a =
href=3D"http://www.forvo.com/download/mp3/%E7%B2%A4%E6%8B%BC/yue/2248626"=
><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#663366;=
background:white'>jyut6 ping3</span></a></span><span =
style=3D'font-size:10.0pt;color:black;background:white'>=EF=BC=89</span><=
span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>(Cantonese pronunciation:&nbsp;<span class=3Dipa><a =
href=3D"http://en.wikipedia.org/wiki/Help:IPA_for_Cantonese" =
title=3D"Help:IPA for Cantonese"><span =
style=3D'color:#0B0080'>[jy=CB=90t=CC=9A=CB=A8 p=CA=B0</span><span =
style=3D'color:#0B0080'>=C9=AA</span><span =
style=3D'color:#0B0080'>=C5=8B=CB=A7]</span></a></span>), sometimes =
spelled<span class=3Dapple-converted-space>&nbsp;</span><b>Jyutpin</b>) =
is a<span class=3Dapple-converted-space>&nbsp;</span></span><span =
lang=3DEN-US><a href=3D"http://en.wikipedia.org/wiki/Romanization" =
title=3DRomanization><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#0B0080;=
background:white'>romanization</span></a></span><span =
class=3Dapple-converted-space><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>&nbsp;</span></span><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>system for<span =
class=3Dapple-converted-space>&nbsp;</span></span><span lang=3DEN-US><a =
href=3D"http://en.wikipedia.org/wiki/Standard_Cantonese" =
title=3D"Standard Cantonese"><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#0B0080;=
background:white'>Cantonese</span></a></span><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>developed by the<span =
class=3Dapple-converted-space>&nbsp;</span></span><span lang=3DEN-US><a =
href=3D"http://en.wikipedia.org/wiki/Linguistic_Society_of_Hong_Kong" =
title=3D"Linguistic Society of Hong Kong"><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#0B0080;=
background:white'>Linguistic Society of Hong Kong</span></a></span><span =
class=3Dapple-converted-space><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>&nbsp;</span></span><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white'>(LSHK) in 1993. Its formal name is<span =
class=3Dapple-converted-space>&nbsp;</span><b><i>The Linguistic Society =
of Hong Kong Cantonese Romanization Scheme</i></b>. The LSHK promotes =
the use of this romanization system.</span><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Mr. Leung (<a =
href=3D"http://en.wikipedia.org/wiki/Leung_Chun_Ying">http://en.wikipedia=
.org/wiki/Leung_Chun_Ying</a> ) and Mr. Tung (<a =
href=3D"http://en.wikipedia.org/wiki/Tung_Chee_Hwa">http://en.wikipedia.o=
rg/wiki/Tung_Chee_Hwa</a>) were born before 1970, =C2=A0so I believe =
they had no chance to adopt Yale romanization for Cantonese and jyutping =
for their name=E2=80=99s spelling. <o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'text-align:justify;text-justify:inter-ideograph'><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Best Regards,<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-align:justify;text-justify:inter-ideograph'><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Leaf<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-align:justify;text-justify:inter-ideograph'><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'text-align:justify;text-justify:inter-ideograph'><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'><p class=3DMsoNormal><b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Ted Hardie =
[mailto:ted.ietf@gmail.com] <br><b>Sent:</b> Saturday, July 27, 2013 =
1:51 AM<br><b>To:</b> Leaf Yeh<br><b>Cc:</b> Cao,Zhen; IETF =
Discussion<br><b>Subject:</b> Re: Regarding call Chinese =
names<o:p></o:p></span></p></div><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>On Fri, Jul 26, 2013 at 12:58 AM, Leaf Yeh &lt;<a =
href=3D"mailto:leaf.yeh.sdo@gmail.com" =
target=3D"_blank">leaf.yeh.sdo@gmail.com</a>&gt; =
wrote:<o:p></o:p></span></p><div><blockquote =
style=3D'border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm =
6.0pt;margin-left:4.8pt;margin-right:0cm'><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><span lang=3DEN-US>a. I suppose Mr. Leung =
and Mr. Tung used Wade-Giles Romanization (or system)<br>for their =
name's spelling, which looks very popular outside China =
mainland<br>including Hong Kong, and inside China mainland before the =
year of 1958 when<br>Pinyin (Chinese phonetic alphabet) was =
published.<o:p></o:p></span></p></blockquote><div><p =
class=3DMsoNormal><span lang=3DEN-US><br>Wade-Giles is a romanization =
system for Mandarin, not Cantonese.&nbsp; The Yale romanization for =
Cantonese developed by Parker Po-fei Huang and the jyutping&nbsp; =
(</span>=E7=B2=B5=E6=8B=BC<span lang=3DEN-US>) are more likely sources =
for Cantonese names which use a codified romanization system (jyutping =
being more recent).&nbsp; Many names use folk romanizations, rather than =
following a specific system.<br><br>regards,<br><br>Ted =
Hardie<br>&nbsp;<o:p></o:p></span></p></div></div></div></body></html>
------=_NextPart_000_00B1_01CE8AE9.DB060160--


From amorris@amsl.com  Sat Jul 27 03:25:26 2013
Return-Path: <amorris@amsl.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 906B921F9E24 for <ietf@ietfa.amsl.com>; Sat, 27 Jul 2013 03:25:26 -0700 (PDT)
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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xeFLKMFFtbfH for <ietf@ietfa.amsl.com>; Sat, 27 Jul 2013 03:25:22 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.21]) by ietfa.amsl.com (Postfix) with ESMTP id 4B61121F9E0B for <ietf@ietf.org>; Sat, 27 Jul 2013 03:25:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id 3577A9FBB9; Sat, 27 Jul 2013 03:23:57 -0700 (PDT)
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 Ko5ivF05nXqu; Sat, 27 Jul 2013 03:23:57 -0700 (PDT)
Received: from dhcp-6496.meeting.ietf.org (dhcp-6496.meeting.ietf.org [130.129.100.150]) by c9a.amsl.com (Postfix) with ESMTPSA id 669989FBB7; Sat, 27 Jul 2013 03:23:56 -0700 (PDT)
Subject: Re: Remote participants access to Meeting Mailing Lists was Re: BOF posters in the welcome reception
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Alexa Morris <amorris@amsl.com>
In-Reply-To: <A267B1B422B975D55F9160D5@JcK-HP8200.jck.com>
Date: Sat, 27 Jul 2013 03:25:19 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <592301EC-0A5A-48CD-83A9-A12481D1BB54@amsl.com>
References: <A6B9C627-A141-416B-AB39-469FDA86A875@ietf.org> <2129CC69EEF207CADC2421AC@JcK-HP8200.jck.com> <CC160C56-5D74-4309-AD3D-FB88FEB60B01@piuha.net> <96F611AF0497CDC862CF30D4@JcK-HP8200.jck.com> <OF68BD4951.D37EA2D7-ON85257BB2.004EEDF0-85257BB2.004F4E5A@csc.com> <94EA01D5-C6BE-40B3-84C1-C707522627AB@piuha.net> <F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk> <EMEW3|07b43bbc00e6dd8decb147cb113c10dfp6NHk603tjc|ecs.soton.ac.uk|F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk> <4402A8BCBCF8C54CF188B4AA@JcK-HP8200.jck.com> <CAC4RtVCyN4QCzCepdw2fqwwGFOsve9Zdy+K-a7UPtYvetZhVSw@mail.gmail.com> <A267B1B422B975D55F9160D5@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1085)
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Jul 2013 10:25:26 -0000

>=20
> (3) While it is almost certainly too late to populate it before
> Berlin, I think the meeting page template could use a "Remote
> Participants" main section with pointers to hints and other
> relevant materials, including which mailing lists one should
> watch and that the web version of the meeting agenda should be
> refreshed at least daily.  Wouldn't hurt to repeat the
> instructions about what to do if the feeds go bad there either.
>=20


We have created a small section called Remote Participation on the lower =
right side of the 87 meeting page here: =
http://www.ietf.org/meeting/87/index.html. It can and will be improved =
over time, but it's a start.

-Alexa

----------
Alexa Morris / Executive Director / IETF
48377 Fremont Blvd., Suite 117, Fremont, CA  94538
Phone: +1.510.492.4089 / Fax: +1.510.492.4001
Email: amorris@amsl.com

Managed by Association Management Solutions (AMS)
Forum Management, Meeting and Event Planning
www.amsl.com <http://www.amsl.com/>


From yding@cs.helsinki.fi  Sat Jul 27 03:35:35 2013
Return-Path: <yding@cs.helsinki.fi>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90E0C21F9D38 for <ietf@ietfa.amsl.com>; Sat, 27 Jul 2013 03:35:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.499
X-Spam-Level: 
X-Spam-Status: No, score=-6.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OWUxInAZO3Ax for <ietf@ietfa.amsl.com>; Sat, 27 Jul 2013 03:35:31 -0700 (PDT)
Received: from courier.cs.helsinki.fi (courier.cs.helsinki.fi [128.214.9.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DED421F9D46 for <ietf@ietf.org>; Sat, 27 Jul 2013 03:35:31 -0700 (PDT)
X-DKIM: Courier DKIM Filter v0.50+pk-2013-06-17 courier.cs.helsinki.fi Sat Jul 27 13:34:11 2013
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cs.helsinki.fi; h=message-id:date:from:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; s= dkim20130528; bh=fCHG/LozwOkctfG7rn9sjP/4+GbP0VxD0J62QqSBjhU=; b= Daoplh9rIQGapBg1QFg446DXQ45c2TAV1QixhBj/v37PgWTOA678bGhcSKYJquxf 9DEYruopWzmoMZc1lcXLgG4OS1/GdKz+lMwT8ti9/DcylO7d56HrcIJKdCkaWExO P0Kc2Ut+S3Qy6AXiBrriKcwxpBRP57iskn5eiTGBpUY=
Received: from [131.111.218.40] (s218i40.wolfson.cam.ac.uk [131.111.218.40]) (AUTH: PLAIN yding, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by mail.cs.helsinki.fi with esmtp; Sat, 27 Jul 2013 13:34:10 +0300 id 00068AA1.51F3A222.000077BE
Message-ID: <51F3A21D.5080208@cs.helsinki.fi>
Date: Sat, 27 Jul 2013 11:34:05 +0100
From: Aaron Yi DING <yding@cs.helsinki.fi>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: Alexa Morris <amorris@amsl.com>
Subject: Re: Remote participants access to Meeting Mailing Lists was Re: BOF posters in the welcome reception
References: <A6B9C627-A141-416B-AB39-469FDA86A875@ietf.org> <2129CC69EEF207CADC2421AC@JcK-HP8200.jck.com> <CC160C56-5D74-4309-AD3D-FB88FEB60B01@piuha.net> <96F611AF0497CDC862CF30D4@JcK-HP8200.jck.com> <OF68BD4951.D37EA2D7-ON85257BB2.004EEDF0-85257BB2.004F4E5A@csc.com> <94EA01D5-C6BE-40B3-84C1-C707522627AB@piuha.net> <F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk> <EMEW3|07b43bbc00e6dd8decb147cb113c10dfp6NHk603tjc|ecs.soton.ac.uk|F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk> <4402A8BCBCF8C54CF188B4AA@JcK-HP8200.jck.com> <CAC4RtVCyN4QCzCepdw2fqwwGFOsve9Zdy+K-a7UPtYvetZhVSw@mail.gmail.com> <A267B1B422B975D55F9160D5@JcK-HP8200.jck.com> <592301EC-0A5A-48CD-83A9-A12481D1BB54@amsl.com>
In-Reply-To: <592301EC-0A5A-48CD-83A9-A12481D1BB54@amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Jul 2013 10:35:35 -0000

On 27/07/13 11:25, Alexa Morris wrote:
>
> We have created a small section called Remote Participation on the lower right side of the 87 meeting page here: http://www.ietf.org/meeting/87/index.html. It can and will be improved over time, but it's a start.


+1. The key parts are there now.

Thanks,
Aaron


> -Alexa
>
> ----------
> Alexa Morris / Executive Director / IETF
> 48377 Fremont Blvd., Suite 117, Fremont, CA  94538
> Phone: +1.510.492.4089 / Fax: +1.510.492.4001
> Email: amorris@amsl.com
>
> Managed by Association Management Solutions (AMS)
> Forum Management, Meeting and Event Planning
> www.amsl.com <http://www.amsl.com/>
>


From sm@resistor.net  Sat Jul 27 05:04:57 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6631A21F9D22; Sat, 27 Jul 2013 05:04:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.482
X-Spam-Level: 
X-Spam-Status: No, score=-102.482 tagged_above=-999 required=5 tests=[AWL=0.117, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HlhqiKTWMFDr; Sat, 27 Jul 2013 05:04:56 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id B9E8A21F9CD7; Sat, 27 Jul 2013 05:04:55 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r6RC4lQr024817; Sat, 27 Jul 2013 05:04:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1374926695; bh=rSDqYWgTwHI5rGdi9MhbKk7VetcgCEVtkwCB84782c4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=p2m4jIJXdbk1SVDEzqS2Zc51DjaF4JFP254KRiedDE/7k71hvEDsv9zZFUHUcCSYg pJrPaBMfaxU7oAi3MkApVQz9JlwWtM3C8q3mxrzMi9zzpi5ZuThg9YUI+reKpwLrFD 8EPCr224xzSyECO5s66LZd9ybHc+S9PfhBx3TQFs=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1374926695; i=@resistor.net; bh=rSDqYWgTwHI5rGdi9MhbKk7VetcgCEVtkwCB84782c4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=dCtBTcC9VL437ekSSAC5hZKqcvFhFZ6xANO36v/KWqIDyL+JDUm2hOCGepC9iM8g8 d6pPVvORhcsWkEyb0Z9Qwc3m/Xsyu6oSPQUIUsuiHGyHoGRTf4czdSA7ZWDremxZmB DfNRux6FRLlP+oI11Kz2le1O6QtgYiZDe/aATpMk=
Message-Id: <6.2.5.6.2.20130727021130.0bb54718@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 27 Jul 2013 03:02:32 -0700
To: Jari Arkko <jari.arkko@piuha.net>, John C Klensin <john-ietf@jck.com>
From: SM <sm@resistor.net>
Subject: Re: Remote participants, newcomers, and tutorials (was: IETF87 Audio Streaming Info)
In-Reply-To: <2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net> <2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: edu-team@ietf.org, "ietf@ietf.org list" <ietf@ietf.org>, rfc-editor@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Jul 2013 12:04:57 -0000

At 23:17 26-07-2013, Jari Arkko wrote:
>The second quote is valid in most cases, though we've had some 
>sessions at times that were designed more as education than 
>discussion. For instance, the IAB WCIT BOF last time.

The following will be discussed in the DMARC BoF:

   "a mechanism for protecting the <display-name> portion of the 
RFC5322.From field"

My guess is that it might be educational. :-)

I read the second quote as meaning that a WG session is not a how-to 
or a tutorial.  It might be help people understand if it is explained 
during the orientation session.

>But the first one is just plain wrong. Is this from RFC 3184? Many 
>of the first time IETFers are

Yes.

Regards,
-sm 


From dhc@dcrocker.net  Sat Jul 27 05:23:55 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1A9621E8056; Sat, 27 Jul 2013 05:23:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.449
X-Spam-Level: 
X-Spam-Status: No, score=-6.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C4bne0GVs3-O; Sat, 27 Jul 2013 05:23:44 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 90CC221F8436; Sat, 27 Jul 2013 05:23:44 -0700 (PDT)
Received: from [10.101.1.114] ([176.12.107.140]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r6RCNLBQ015213 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 27 Jul 2013 05:23:41 -0700
Message-ID: <51F3BBB6.5030406@dcrocker.net>
Date: Sat, 27 Jul 2013 13:23:18 +0100
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: edu-team@ietf.org
Subject: Re: Remote participants, newcomers, and tutorials
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net> <2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net>
In-Reply-To: <2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@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, 27 Jul 2013 05:23:44 -0700 (PDT)
Cc: "ietf@ietf.org list" <ietf@ietf.org>, rfc-editor@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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, 27 Jul 2013 12:23:56 -0000

On 7/27/2013 7:17 AM, Jari Arkko wrote:
>>> "newcomers who attend Working Group meetings are encouraged to
>>> observe and absorb whatever material they can, but should not
>>> interfere with the ongoing process of the group"
...
>>> The first quote might discourage newcomers from participating.  I
>>> suggest discussing about the two quotes during the orientation as
>>> they could be misunderstood.
...
> But the first one is just plain wrong. Is this from RFC 3184? Many of
> the first time IETFers are here for a reason, are well-versed in the
> technology in question, and very much able to provide suggestions to
> the WG.


It's not wrong.

It's badly worded, possibly bordering on rudeness.  It certainly lacks 
context.  And it probably doesn't apply to BOFs.  But it's not wrong.

WG face-to-face meetings are for resolving open issues.  Given 1-3 
hours, three times a year, these face to face meetings are not 
reasonable for any other purpose.  That's why doing the foundational 
work on the mailing list is essential.

We need to be /far/ more helpful to new folk who show up (on the mailing 
list or at the f2f) but having them take f2f time for education is 
simply not appropriate.  The time is too valuable.

If there really is an organizational shift towards making f2f wg 
meetings target education of new folk, then the meetings will cease to 
have /any/ utility for getting actual work done.  Really.

d/

ps. Small disclaimer: for ongoing work, it is often useful/necessary to 
start a status summary of the current situation.  Done well enough, 
these can look asymptotically similar to a tutorial.  But really, they 
are for the entire group, not (just) for new folk...


pps. and...
On 7/27/2013 11:02 AM, SM wrote:> At 23:17 26-07-2013, Jari Arkko wrote:
 > The following will be discussed in the DMARC BoF:
 >
 >    "a mechanism for protecting the <display-name> portion of the
 > RFC5322.From field"
 >
 > My guess is that it might be educational. :-)

    I'm involved with the DMARC effort.  I'm almost positive it won't be...


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From jnc@mercury.lcs.mit.edu  Sat Jul 27 06:07:22 2013
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5C4621F9B0A for <ietf@ietfa.amsl.com>; Sat, 27 Jul 2013 06:07:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.403
X-Spam-Level: 
X-Spam-Status: No, score=-6.403 tagged_above=-999 required=5 tests=[AWL=0.196,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R4U87htg8XWv for <ietf@ietfa.amsl.com>; Sat, 27 Jul 2013 06:07:10 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 48CE921F9A29 for <ietf@ietf.org>; Sat, 27 Jul 2013 06:07:05 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 1334518C12D; Sat, 27 Jul 2013 09:07:02 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: Remote participants, newcomers, and tutorials (was: IETF87 Audio Streaming Info)
Message-Id: <20130727130702.1334518C12D@mercury.lcs.mit.edu>
Date: Sat, 27 Jul 2013 09:07:02 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Jul 2013 13:07:23 -0000

    > From: Abdussalam Baryun <abdussalambaryun@gmail.com>

    > no one in IETF have been participating for longer than 30 years

The IETF was a renaming of things that existed before the formal first IETF
(in January, 1986). It's a direct descendant of the first 'TCP Working Group'
meeting, held in Washington DC on March 12, 1977.

And yes, one person who was at that meeting is _still_ participating (he
sent a message to the IETF list on 21 May, 2013; and had an RFC published
this month - RFC 6975).

(And if you consider the Internet work to be connected to the ARPANET - which
in some ways it is, because the RFC series shades slowly from NCP documents to
TCP documents - he goes back a lot further than that: to RFC 1!  Thereby
setting a 'first RFC to last RFC' record that's going to be very hard to beat!
But I digress...)

	Noel

From spromano@unina.it  Sat Jul 27 07:16:02 2013
Return-Path: <spromano@unina.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 016A421F9958; Sat, 27 Jul 2013 07:16:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.758
X-Spam-Level: 
X-Spam-Status: No, score=-98.758 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, HTML_MESSAGE=0.001, RCVD_IN_BL_SPAMCOP_NET=1.96, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HTReeOvKvIGD; Sat, 27 Jul 2013 07:15:57 -0700 (PDT)
Received: from smtp1.unina.it (smtp1.unina.it [192.132.34.61]) by ietfa.amsl.com (Postfix) with ESMTP id 8EE8121F961F; Sat, 27 Jul 2013 07:15:56 -0700 (PDT)
Received: from [10.54.235.147] ([88.128.80.7]) (authenticated bits=0) by smtp1.unina.it (8.14.4/8.14.4) with ESMTP id r6REFobq001698 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 27 Jul 2013 16:15:51 +0200
Subject: Re: Remote participants, newcomers, and tutorials (was: IETF87 Audio Streaming Info)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: multipart/alternative; boundary="Apple-Mail=_3B64630D-5C6E-42EE-96A6-D7BAE6FCB82E"
From: Simon Pietro Romano <spromano@unina.it>
In-Reply-To: <2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net>
Date: Sat, 27 Jul 2013 16:15:53 +0200
Message-Id: <5EB533DC-E6EF-40E3-A225-F8F1E39A46DC@unina.it>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net> <2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net>
To: Jari Arkko <jari.arkko@piuha.net>
X-Mailer: Apple Mail (2.1283)
Cc: "ietf@ietf.org list" <ietf@ietf.org>, iesg@ietf.org, rfc-editor@ietf.org, John C Klensin <john-ietf@jck.com>, SM <sm@resistor.net>, edu-team@ietf.org, team@meetecho.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Jul 2013 14:16:02 -0000

--Apple-Mail=_3B64630D-5C6E-42EE-96A6-D7BAE6FCB82E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Hello Jary and all,

for your information, the Meetecho team is going to record five =
tutorials on Sunday:

http://www.ietf.org/meeting/87/remote-participation.html#meetecho

We have already provided a URL for those who want to remotely attend the =
IAOC Overview Session. If you think this might be of interest, we can =
allow remotes to have access to the other tutorials as well. Just let us =
know, so we can advertise access URLs on the mentioned web page. As =
usual, we can provide a real-time, synchronized view of the sessions, =
involving audio, video and presentation slides.

Cheers,

Simon


Il giorno 27/lug/2013, alle ore 08:17, Jari Arkko ha scritto:

> I agree with John that audio and other things would be useful, but =
Brian is also correct that they do involve some work. Let us see what we =
can do on audio for IETF-88. Past recordings of the tutorials are =
available at =
http://www.ietf.org/edu/process-oriented-tutorials.html#newcomers.
>=20
> The meeting materials page does now have a training section now - =
added a couple of hours ago, thanks Alexa! - and some of the materials =
are there. We're working on putting the rest there.=20
>=20
> (The newcomer's orientation file would already be there too but we're =
struggling with some bug in the system in the upload.)=20
>=20
> As for:
>=20
>> The consensus of the IETF is that:
>>=20
>> "newcomers who attend Working Group meetings are encouraged to
>>  observe and absorb whatever material they can, but should not
>>  interfere with the ongoing process of the group"
>>=20
>> It was also mentioned that:
>>=20
>> "Working group meetings are not intended for the education of
>> individuals"
>>=20
>> The first quote might discourage newcomers from participating.  I =
suggest discussing about the two quotes during the orientation as they =
could be misunderstood.
>=20
> The second quote is valid in most cases, though we've had some =
sessions at times that were designed more as education than discussion. =
For instance, the IAB WCIT BOF last time.
>=20
> But the first one is just plain wrong. Is this from RFC 3184? Many of =
the first time IETFers are here for a reason, are well-versed in the =
technology in question, and very much able to provide suggestions to the =
WG. Maybe RFC 3184 is in the need of an update. (It also says other =
things that may not be up to date, like that locating mailing list =
archives is hard. I don=A8t think it has been hard ever since =
tools.ietf.org/wg/foo came about.)
>=20
> Thanks for the feedback!
>=20
> Jari
>=20
>>=20
>>> Specific suggestions:
>>>=20
>>> (i) Let's get these open Sunday sessions audiocast and/or
>>> available over Meetecho or WebEx.  If that is impossible for
>>> IETF 87, it should be a priority for IETF 88 and later.
>>=20
>> Yes.
>>=20
>> POSH has not published a session agenda.  However, the BoF is listed =
on the meeting agenda.  Is the BoF cancelled or will this be one of =
those willful violations of IETF Best Current Practices?
>>=20
>> Regards,
>> -sm=20
>=20
>=20

                     					       _\\|//_
                           				      ( O-O )
   ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
                    				Simon Pietro Romano
             				 Universita' di Napoli Federico =
II
                		     Computer Engineering Department=20
	             Phone: +39 081 7683823 -- Fax: +39 081 7683816
                                           e-mail: spromano@unina.it

		    <<Molti mi dicono che lo scoraggiamento =CB l'alibi =
degli=20
		    idioti. Ci rifletto un istante; e mi scoraggio>>. =
Magritte.
               			                     oooO
  ~~~~~~~~~~~~~~~~~~~~~~~(   )~~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
					                 \ (            =
(   )
			                                  \_)          ) =
/
                                                                       =
(_/






--Apple-Mail=_3B64630D-5C6E-42EE-96A6-D7BAE6FCB82E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div>Hello Jary and all,</div><div><br></div><div>for your =
information, the Meetecho team is going to record five tutorials on =
Sunday:</div><div><br></div><div><a =
href=3D"http://www.ietf.org/meeting/87/remote-participation.html#meetecho"=
>http://www.ietf.org/meeting/87/remote-participation.html#meetecho</a></di=
v><div><br></div><div>We have already provided a URL for those who want =
to remotely attend the IAOC Overview Session. If you think this might be =
of interest, we can allow remotes to have access to the other tutorials =
as well. Just let us know, so we can advertise access URLs on the =
mentioned web page. As usual, we can provide a real-time, synchronized =
view of the sessions, involving audio, video and presentation =
slides.</div><div><br></div><div>Cheers,</div><div><br></div><div>Simon</d=
iv><div><br></div><br><div><div>Il giorno 27/lug/2013, alle ore 08:17, =
Jari Arkko ha scritto:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div>I =
agree with John that audio and other things would be useful, but Brian =
is also correct that they do involve some work. Let us see what we can =
do on audio for IETF-88. Past recordings of the tutorials are available =
at <a =
href=3D"http://www.ietf.org/edu/process-oriented-tutorials.html#newcomers"=
>http://www.ietf.org/edu/process-oriented-tutorials.html#newcomers</a>.<br=
><br>The meeting materials page does now have a training section now - =
added a couple of hours ago, thanks Alexa! - and some of the materials =
are there. We're working on putting the rest there. <br><br>(The =
newcomer's orientation file would already be there too but we're =
struggling with some bug in the system in the upload.) <br><br>As =
for:<br><br><blockquote type=3D"cite">The consensus of the IETF is =
that:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite"> "newcomers who =
attend Working Group meetings are encouraged =
to<br></blockquote><blockquote type=3D"cite"> &nbsp;observe and absorb =
whatever material they can, but should not<br></blockquote><blockquote =
type=3D"cite"> &nbsp;interfere with the ongoing process of the =
group"<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">It was also =
mentioned that:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">"Working group =
meetings are not intended for the education =
of<br></blockquote><blockquote type=3D"cite"> =
individuals"<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">The first quote =
might discourage newcomers from participating. &nbsp;I suggest =
discussing about the two quotes during the orientation as they could be =
misunderstood.<br></blockquote><br>The second quote is valid in most =
cases, though we've had some sessions at times that were designed more =
as education than discussion. For instance, the IAB WCIT BOF last =
time.<br><br>But the first one is just plain wrong. Is this from RFC =
3184? Many of the first time IETFers are here for a reason, are =
well-versed in the technology in question, and very much able to provide =
suggestions to the WG. Maybe RFC 3184 is in the need of an update. (It =
also says other things that may not be up to date, like that locating =
mailing list archives is hard. I don=A8t think it has been hard ever =
since <a href=3D"http://tools.ietf.org/wg/foo">tools.ietf.org/wg/foo</a> =
came about.)<br><br>Thanks for the =
feedback!<br><br>Jari<br><br><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">Specific =
suggestions:<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">(i) Let's get these open Sunday =
sessions audiocast and/or<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">available over Meetecho or =
WebEx. &nbsp;If that is impossible =
for<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">IETF 87, it should be a priority for IETF 88 and =
later.<br></blockquote></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">Yes.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">POSH has not =
published a session agenda. &nbsp;However, the BoF is listed on the =
meeting agenda. &nbsp;Is the BoF cancelled or will this be one of those =
willful violations of IETF Best Current =
Practices?<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">Regards,<br></blockquote><blockquote type=3D"cite">-sm =
<br></blockquote><br><br></div></blockquote></div><br><div =
apple-content-edited=3D"true">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-align: -webkit-auto; text-indent: 0px; text-transform: none; =
white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div>&nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
	</span><span class=3D"Apple-converted-space">&nbsp;</span>&nbsp; =
&nbsp; &nbsp; _\\|//_</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
</span>&nbsp; &nbsp; &nbsp;&nbsp;( O-O )</div><div>&nbsp; =
&nbsp;~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~</div><di=
v>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;<span class=3D"Apple-converted-space">&nbsp;</span><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
</span>Simon Pietro Romano</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;<span class=3D"Apple-tab-span" style=3D"white-space: pre; =
">				</span><span =
class=3D"Apple-converted-space">&nbsp;</span>Universita' di Napoli =
Federico II</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;&nbsp;<span class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
	</span>&nbsp; &nbsp; &nbsp;Computer Engineering =
Department&nbsp;</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	</span>&nbsp; &nbsp; &nbsp;&nbsp; &nbsp; =
&nbsp; &nbsp; Phone: +39 081 7683823 -- Fax: +39 081 =
7683816</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;e-mail: <a =
href=3D"mailto:spromano@unina.it">spromano@unina.it</a></div><div><br></di=
v><div><span class=3D"Apple-tab-span" style=3D"white-space: pre; ">		=
</span>&nbsp; &nbsp; &lt;&lt;Molti mi dicono che lo scoraggiamento =CB =
l'alibi degli&nbsp;</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">		</span>&nbsp;&nbsp; =
&nbsp;idioti. Ci rifletto un istante; e mi scoraggio&gt;&gt;. =
Magritte.</div><div>&nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; =
&nbsp;<span class=3D"Apple-converted-space">&nbsp;</span><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">			=
</span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;oooO</div><div>&nbsp; ~~~~~~~~~~~~~~~~~~~~~~~( &nbsp; =
)~~~&nbsp;Oooo~~~~~~~~~~~~~~~~~~~~~~~~~</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
	</span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;\ ( &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;( &nbsp; =
)</div><div><span class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
		</span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
\_) &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;) /</div><div>&nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp;(_/</div></div><div><br></div></div></span><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<br></body></html>=

--Apple-Mail=_3B64630D-5C6E-42EE-96A6-D7BAE6FCB82E--

From jari.arkko@piuha.net  Sat Jul 27 07:43:48 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF7C021F9993; Sat, 27 Jul 2013 07:43:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.576
X-Spam-Level: 
X-Spam-Status: No, score=-102.576 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8FdJqqVKVZAU; Sat, 27 Jul 2013 07:43:44 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 6149021F89EB; Sat, 27 Jul 2013 07:43:44 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id BDB1C2CC54; Sat, 27 Jul 2013 17:43:42 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RYYNundP8NNE; Sat, 27 Jul 2013 17:43:40 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 73D082CC48; Sat, 27 Jul 2013 17:43:40 +0300 (EEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Remote participants, newcomers, and tutorials (was: IETF87 Audio Streaming Info)
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <5EB533DC-E6EF-40E3-A225-F8F1E39A46DC@unina.it>
Date: Sat, 27 Jul 2013 16:43:40 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <18690A2F-5439-4CCC-91F1-58CF67D8D704@piuha.net>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net> <2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net> <5EB533DC-E6EF-40E3-A225-F8F1E39A46DC@unina.it>
To: Simon Pietro Romano <spromano@unina.it>
X-Mailer: Apple Mail (2.1508)
Cc: "ietf@ietf.org list" <ietf@ietf.org>, iesg@ietf.org, rfc-editor@ietf.org, John C Klensin <john-ietf@jck.com>, SM <sm@resistor.net>, edu-team@ietf.org, team@meetecho.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Jul 2013 14:43:49 -0000

Simon,

> for your information, the Meetecho team is going to record five =
tutorials on Sunday:
>=20
> http://www.ietf.org/meeting/87/remote-participation.html#meetecho
>=20
> We have already provided a URL for those who want to remotely attend =
the IAOC Overview Session. If you think this might be of interest, we =
can allow remotes to have access to the other tutorials as well. Just =
let us know, so we can advertise access URLs on the mentioned web page. =
As usual, we can provide a real-time, synchronized view of the sessions, =
involving audio, video and presentation slides.

I think it would be useful. Thank you.

Jari


From john-ietf@jck.com  Sat Jul 27 07:44:50 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FA2521F99DD for <ietf@ietfa.amsl.com>; Sat, 27 Jul 2013 07:44:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GzTHDM+vpu12 for <ietf@ietfa.amsl.com>; Sat, 27 Jul 2013 07:44:45 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 7328321F99C3 for <ietf@ietf.org>; Sat, 27 Jul 2013 07:44:45 -0700 (PDT)
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 1V35jg-000CAr-St; Sat, 27 Jul 2013 10:44:44 -0400
Date: Sat, 27 Jul 2013 10:44:39 -0400
From: John C Klensin <john-ietf@jck.com>
To: Alexa Morris <amorris@amsl.com>
Subject: Re: Remote participants access to Meeting Mailing Lists was Re: BOF posters in the welcome reception
Message-ID: <EB2F8D9DD8C6C3AC13049535@JcK-HP8200.jck.com>
In-Reply-To: <592301EC-0A5A-48CD-83A9-A12481D1BB54@amsl.com>
References: <A6B9C627-A141-416B-AB39-469FDA86A875@ietf.org> <2129CC69EEF207CADC2421AC@JcK-HP8200.jck.com> <CC160C56-5D74-4309-AD3D-FB88FEB60B01@piuha.net> <96F611AF0497CDC862CF30D4@JcK-HP8200.jck.com> <OF68BD4951.D37EA2D7-ON85257BB2.004EEDF0-85257BB2.004F4E5A@csc.com> <94EA01D5-C6BE-40B3-84C1-C707522627AB@piuha.net> <F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk> <EMEW3|07b43bbc00e6dd8decb147cb113c10dfp6NHk603tjc|ecs.soton.ac.uk|F0D6FF7A-FD10-4540-BEAF-85CC31E6E46D@ecs.soton.ac.uk> <4402A8BCBCF8C54CF188B4AA@JcK-HP8200.jck.com> <CAC4RtVCyN4QCzCepdw2fqwwGFOsve9Zdy+K-a7UPtYvetZhVSw@mail.gmail.com> <A267B1B422B975D55F9160D5@JcK-HP8200.jck.com> <592301EC-0A5A-48CD-83A9-A12481D1BB54@amsl.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Jul 2013 14:44:50 -0000

--On Saturday, July 27, 2013 03:25 -0700 Alexa Morris
<amorris@amsl.com> wrote:

>> (3) While it is almost certainly too late to populate it
>> before Berlin, I think the meeting page template could use a
>> "Remote Participants" main section with pointers to hints and
>> other relevant materials, including which mailing lists one
>> should watch and that the web version of the meeting agenda
>> should be refreshed at least daily.  Wouldn't hurt to repeat
>> the instructions about what to do if the feeds go bad there
>> either.
>> 
> We have created a small section called Remote Participation on
> the lower right side of the 87 meeting page here:
> http://www.ietf.org/meeting/87/index.html. It can and will be
> improved over time, but it's a start.

This is a wonderful step forward.  Thanks.
   john






From steve@shinkuro.com  Sat Jul 27 08:19:27 2013
Return-Path: <steve@shinkuro.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 152A121F9B03 for <ietf@ietfa.amsl.com>; Sat, 27 Jul 2013 08:19:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.073
X-Spam-Level: 
X-Spam-Status: No, score=-0.073 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DSL=1.129, MIME_QP_LONG_LINE=1.396, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZUQQOZTPppS4 for <ietf@ietfa.amsl.com>; Sat, 27 Jul 2013 08:19:21 -0700 (PDT)
Received: from execdsl.com (remote.shinkuro.com [50.56.68.178]) by ietfa.amsl.com (Postfix) with ESMTP id AC3B321F9A74 for <ietf@ietf.org>; Sat, 27 Jul 2013 08:19:21 -0700 (PDT)
Received: from dummy.name; Sat, 27 Jul 2013 15:19:20 +0000
References: <20130727130702.1334518C12D@mercury.lcs.mit.edu>
In-Reply-To: <20130727130702.1334518C12D@mercury.lcs.mit.edu>
Mime-Version: 1.0 (1.0)
Content-Type: text/plain; charset=us-ascii
Message-Id: <BE8EB0B8-A661-40C6-A794-0A940E4CCE5C@shinkuro.com>
Content-Transfer-Encoding: quoted-printable
X-Mailer: iPhone Mail (9B206)
From: Steve Crocker <steve@shinkuro.com>
Subject: Re: Remote participants, newcomers, and tutorials (was: IETF87 Audio Streaming Info)
Date: Sat, 27 Jul 2013 11:19:24 -0400
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Cc: "ietf@ietf.org" <ietf@ietf.org>, "jnc@mercury.lcs.mit.edu" <jnc@mercury.lcs.mit.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Jul 2013 15:19:27 -0000

Well, actually, the IETF is a continuation of the Network Working Group, whi=
ch formed organically in late 1968.  We're a few days short of the 45 year m=
ark.  The NWG had open meetings, developed the layered architecture and publ=
ished RFCs.

Steve

Sent from my iPhone

On Jul 27, 2013, at 9:07 AM, jnc@mercury.lcs.mit.edu (Noel Chiappa) wrote:

>> From: Abdussalam Baryun <abdussalambaryun@gmail.com>
>=20
>> no one in IETF have been participating for longer than 30 years
>=20
> The IETF was a renaming of things that existed before the formal first IET=
F
> (in January, 1986). It's a direct descendant of the first 'TCP Working Gro=
up'
> meeting, held in Washington DC on March 12, 1977.
>=20
> And yes, one person who was at that meeting is _still_ participating (he
> sent a message to the IETF list on 21 May, 2013; and had an RFC published
> this month - RFC 6975).
>=20
> (And if you consider the Internet work to be connected to the ARPANET - wh=
ich
> in some ways it is, because the RFC series shades slowly from NCP document=
s to
> TCP documents - he goes back a lot further than that: to RFC 1!  Thereby
> setting a 'first RFC to last RFC' record that's going to be very hard to b=
eat!
> But I digress...)
>=20
>    Noel

From abdussalambaryun@gmail.com  Sat Jul 27 12:14:28 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 394AC21F918C; Sat, 27 Jul 2013 12:14:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hDVa-1-bGcrk; Sat, 27 Jul 2013 12:14:27 -0700 (PDT)
Received: from mail-pd0-x234.google.com (mail-pd0-x234.google.com [IPv6:2607:f8b0:400e:c02::234]) by ietfa.amsl.com (Postfix) with ESMTP id 8CBA821F8EFE; Sat, 27 Jul 2013 12:14:21 -0700 (PDT)
Received: by mail-pd0-f180.google.com with SMTP id 10so4025698pdi.11 for <multiple recipients>; Sat, 27 Jul 2013 12:14:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=B2+EtnFsMJSJSLtz9BwYVjsrYeMGeCiiGzb413zT4SA=; b=rTnNUXWqYvSMieNIBIHSrRnOhtI45X4hl2hQMJ0DVHX00Rlbko2lLuoPcbOp35xwfk nONJd3HyobX/q2TlvyuNhQ2VkfKzFfWbHol+cu9FlsiYE6o8EH+NezfR1usgelpNwgXY Fyk94m9gGvZnrsBfsGfUe4bCBpupeveB+9pYLyjL1HnmBy4xyYUXYu8MtLi24KCcgbsY fw8V1NIvlt+4yyvKZLDlAQxaneX2VYW8SEwXmMDDQA33U4igxmO8Ij0VnD4Zrf7WdtyH L1Pt6w8QCTVAgk+fPsNgzwnd8JuCJP2xa+8QhXAXLXeqnuxOfGEpBKumtkltDUJrLKtH iijQ==
MIME-Version: 1.0
X-Received: by 10.66.148.41 with SMTP id tp9mr61858405pab.40.1374952461206; Sat, 27 Jul 2013 12:14:21 -0700 (PDT)
Received: by 10.68.250.133 with HTTP; Sat, 27 Jul 2013 12:14:21 -0700 (PDT)
In-Reply-To: <B2856A2101451CF971914EFA@JcK-HP8200.jck.com>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <51F2DD2A.7040700@gmail.com> <51F2DE5F.1010708@gmail.com> <B2856A2101451CF971914EFA@JcK-HP8200.jck.com>
Date: Sat, 27 Jul 2013 21:14:21 +0200
Message-ID: <CADnDZ8_+Kjew8ZOjHdc1mN-kcnhG9NMUjSay3gLooHUAZNwLAQ@mail.gmail.com>
Subject: Re: Oh look! [Re: Remote participants, newcomers, and tutorials]
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: John C Klensin <john-ietf@jck.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: iesg@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Jul 2013 19:14:28 -0000

On 7/27/13, John C Klensin <john-ietf@jck.com> wrote:
> one locates it (IETF Home Page -> IESG -> Members) one even gets
> contact information as a bonus.  And the listing of AD names is
> pretty useless without contact info.
>

As from my remote participant experience in IETF Routing Area (rtg), I
was very happy/encouraged to be able to speak directly (issue related
to MANET WG) to the AD of rtg at his open-office session at a previous
IETF meeting (even 2 minutes makes big differences). Giving a chance
to remote participants to speak to WG chairs or ADs is good to
encourage remote-participants/new-interested-people to start thinking
to join the meetings. I suggest that all ADs for other areas do the
same if available (I am not sure if they do that, but if they do, that
is great). Furthermore, if mentoring is available for remote
participants then the mentor may book a time if needed with WG chair
or AD, otherwise an agreed time communication can continue directly
between mentor and participant.

Booking a 2 minute remote speach at IETF-meetings from
remote-community to an IETF AD or WG-Chair can be a new opportunity
that IETF/IESG can think about to schedule in future.

AB

From brian.e.carpenter@gmail.com  Sat Jul 27 13:37:08 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE5D311E80F6; Sat, 27 Jul 2013 13:37:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.564
X-Spam-Level: 
X-Spam-Status: No, score=-102.564 tagged_above=-999 required=5 tests=[AWL=0.035, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Er2C1o+L5MIW; Sat, 27 Jul 2013 13:37:08 -0700 (PDT)
Received: from mail-pd0-x22c.google.com (mail-pd0-x22c.google.com [IPv6:2607:f8b0:400e:c02::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 4F39111E80F3; Sat, 27 Jul 2013 13:37:08 -0700 (PDT)
Received: by mail-pd0-f172.google.com with SMTP id z10so4067112pdj.31 for <multiple recipients>; Sat, 27 Jul 2013 13:37:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=8tFmn3N1xe6fn8Zu7yKsisZKR5Vs8ZyAzXz6HCiSKzU=; b=AIQ/AQio2ACO2pBHSbKiRyA9cJBjdSTsmTthZKS7ASWce70Y69YD0MU13t8XPNZY3R 9HVNdFwUlWOGuvvQxgpCm62XRzE5YvtGFxrYh4qX5hg/p+GPnsaFnfkj7sZ+KOrHCDzu xZ9UeHB/EaPrVKoSeo1sVNhRsT+/iBIjed3/EmHdVrXnTmnBucL5DN6y7EvFwqGB1Myy gfvczLlGLbkmvV76l44oj73ItO14a/EBKZMmCrVc0UxKebBbZx40Bfn23Af6S6IQFREv 1sC8tVG+Y8eCXCdHvXjoIX/lz72LolrQyd3hICcv14/tz/3H7xBWAuYcrWVt1So/AsC6 fPNw==
X-Received: by 10.66.228.72 with SMTP id sg8mr61150261pac.45.1374957428011; Sat, 27 Jul 2013 13:37:08 -0700 (PDT)
Received: from [192.168.178.23] (125.198.69.111.dynamic.snap.net.nz. [111.69.198.125]) by mx.google.com with ESMTPSA id ry2sm67543677pbc.41.2013.07.27.13.37.04 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 27 Jul 2013 13:37:06 -0700 (PDT)
Message-ID: <51F42F7B.2060706@gmail.com>
Date: Sun, 28 Jul 2013 08:37:15 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: Remote participants, newcomers, and tutorials
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com>	<E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com>	<6.2.5.6.2.20130726101746.0c8db480@resistor.net>	<2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net> <51F3BBB6.5030406@dcrocker.net>
In-Reply-To: <51F3BBB6.5030406@dcrocker.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: edu-team@ietf.org, "ietf@ietf.org list" <ietf@ietf.org>, rfc-editor@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Jul 2013 20:37:09 -0000

On 28/07/2013 00:23, Dave Crocker wrote:
> On 7/27/2013 7:17 AM, Jari Arkko wrote:
>>>> "newcomers who attend Working Group meetings are encouraged to
>>>> observe and absorb whatever material they can, but should not
>>>> interfere with the ongoing process of the group"
> ...
>>>> The first quote might discourage newcomers from participating.  I
>>>> suggest discussing about the two quotes during the orientation as
>>>> they could be misunderstood.
> ...
>> But the first one is just plain wrong. Is this from RFC 3184? Many of
>> the first time IETFers are here for a reason, are well-versed in the
>> technology in question, and very much able to provide suggestions to
>> the WG.
> 
> 
> It's not wrong.
> 
> It's badly worded, possibly bordering on rudeness.  It certainly lacks
> context.  And it probably doesn't apply to BOFs.  But it's not wrong.

It reads rudely when taken out of context. But try reading the whole
paragraph in RFC 3184:

      IETF participants who attend Working Group meetings read the
      relevant Internet-Drafts, RFCs, and e-mail archives beforehand, in
      order to familiarize themselves with the technology under
      discussion.  This may represent a challenge for newcomers, as e-
      mail archives can be difficult to locate and search, and it may
      not be easy to trace the history of longstanding Working Group
      debates.  With that in mind, newcomers who attend Working Group
      meetings are encouraged to observe and absorb whatever material
      they can, but should not interfere with the ongoing process of the
      group.  Working Group meetings run on a very limited time
      schedule, and are not intended for the education of individuals.
      The work of the group will continue on the mailing list, and many
      questions would be better expressed on the list in the months that
      follow.

Exactly. My experience back when I was a newcomer was that it was
easy enough to ask beginner's questions after the meeting, and obviously
wrong to do so during the session. This remains true years later, if I
drop into a WG that I'm not familiar with.

    Brian

From jari.arkko@piuha.net  Sat Jul 27 14:01:52 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB71F11E80FE for <ietf@ietfa.amsl.com>; Sat, 27 Jul 2013 14:01:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.577
X-Spam-Level: 
X-Spam-Status: No, score=-102.577 tagged_above=-999 required=5 tests=[AWL=0.022, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xDtSzaqMbXP4 for <ietf@ietfa.amsl.com>; Sat, 27 Jul 2013 14:01:46 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 6C60521F8F4D for <ietf@ietf.org>; Sat, 27 Jul 2013 14:01:46 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 5D4622CC54; Sun, 28 Jul 2013 00:01:45 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oXDLFhYQNo6n; Sun, 28 Jul 2013 00:01:44 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 91E752CC48; Sun, 28 Jul 2013 00:01:44 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Remote participants, newcomers, and tutorials
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <51F42F7B.2060706@gmail.com>
Date: Sat, 27 Jul 2013 23:01:44 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <E12475C2-B005-42A7-A662-F36F55BB953E@piuha.net>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com>	<E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com>	<6.2.5.6.2.20130726101746.0c8db480@resistor.net>	<2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net> <51F3BBB6.5030406@dcrocker.net> <51F42F7B.2060706@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1508)
Cc: dcrocker@bbiw.net, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Jul 2013 21:01:52 -0000

(Dropping a few lists from the distribution.)

Brian, Dave,

> It reads rudely when taken out of context. But try reading the whole
> paragraph in RFC 3184:
>=20
>      IETF participants who attend Working Group meetings read the
>      relevant Internet-Drafts, RFCs, and e-mail archives beforehand, =
in
>      order to familiarize themselves with the technology under
>      discussion.  This may represent a challenge for newcomers, as e-
>      mail archives can be difficult to locate and search, and it may
>      not be easy to trace the history of longstanding Working Group
>      debates.  With that in mind, newcomers who attend Working Group
>      meetings are encouraged to observe and absorb whatever material
>      they can, but should not interfere with the ongoing process of =
the
>      group.  Working Group meetings run on a very limited time
>      schedule, and are not intended for the education of individuals.
>      The work of the group will continue on the mailing list, and many
>      questions would be better expressed on the list in the months =
that
>      follow.
>=20
> Exactly. My experience back when I was a newcomer was that it was
> easy enough to ask beginner's questions after the meeting, and =
obviously
> wrong to do so during the session. This remains true years later, if I
> drop into a WG that I'm not familiar with.

Let me clarify why I thought it was wrong. I don't think I'm disagreeing =
with you, actually. I do agree that asking beginner questions in a =
working group meeting would be inappropriate. And I agree that the =
meetings are not a place for education. And I agree that we should not =
become an organisation where the f2f time gets the primary role.

However. Newcomers are not all alike. The student coming here to observe =
the IETF. The researcher who understands the field we are embarking on. =
The colleague that has been implementing The Protocol for the last two =
years in the office, but is now coming to the IETF for the first time. =
The guy who has something to say about the operational experience of our =
results. The team who brought their idea to the IETF to be standardised. =
And so on.

Jari (the guy who is preparing for the possibility - no matter how  =
remote - that the cool kids might actually teach us a trick or two) :-)


From kathleen.moriarty@emc.com  Sat Jul 27 14:39:06 2013
Return-Path: <kathleen.moriarty@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43A2B11E8111; Sat, 27 Jul 2013 14:39:06 -0700 (PDT)
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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6dgUBYyiDnKu; Sat, 27 Jul 2013 14:38:52 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id E74D311E810D; Sat, 27 Jul 2013 14:38:51 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r6RLcnvS006580 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 27 Jul 2013 17:38:49 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd02.lss.emc.com [10.254.221.253]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Sat, 27 Jul 2013 17:38:33 -0400
Received: from mxhub05.corp.emc.com (mxhub05.corp.emc.com [128.222.70.202]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r6RLcUV0003145; Sat, 27 Jul 2013 17:38:31 -0400
Received: from mx15a.corp.emc.com ([169.254.1.184]) by mxhub05.corp.emc.com ([128.222.70.202]) with mapi; Sat, 27 Jul 2013 17:38:30 -0400
From: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
To: Jari Arkko <jari.arkko@piuha.net>
Date: Sat, 27 Jul 2013 17:38:26 -0400
Subject: Re: Remote participants, newcomers,	and tutorials (was: IETF87 Audio Streaming Info)
Thread-Topic: Remote participants, newcomers,	and tutorials (was: IETF87 Audio Streaming Info)
Thread-Index: Ac6LEaHWVsF2jXZ3TDSFjZ4HGF91DQ==
Message-ID: <8BA59F96-A1DE-460F-9A22-F2CD4CE5F31C@emc.com>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net> <2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net> <5EB533DC-E6EF-40E3-A225-F8F1E39A46DC@unina.it> <18690A2F-5439-4CCC-91F1-58CF67D8D704@piuha.net>
In-Reply-To: <18690A2F-5439-4CCC-91F1-58CF67D8D704@piuha.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "ietf@ietf.org list" <ietf@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, "rfc-editor@ietf.org" <rfc-editor@ietf.org>, John C Klensin <john-ietf@jck.com>, SM <sm@resistor.net>, "edu-team@ietf.org" <edu-team@ietf.org>, "team@meetecho.com" <team@meetecho.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Jul 2013 21:39:06 -0000

I think it would be really helpful/useful if working groups could provide s=
hort video overviews to help people understand the work.  This includes new=
comers and also interested observers, who may include implementers.  Can th=
at be accommodated, maybe at a future meeting?  I am happy to help if I can=
.

Thank you!
Kathleen=20

Sent from my iPhone

On Jul 27, 2013, at 4:44 PM, "Jari Arkko" <jari.arkko@piuha.net> wrote:

> Simon,
>=20
>> for your information, the Meetecho team is going to record five tutorial=
s on Sunday:
>>=20
>> http://www.ietf.org/meeting/87/remote-participation.html#meetecho
>>=20
>> We have already provided a URL for those who want to remotely attend the=
 IAOC Overview Session. If you think this might be of interest, we can allo=
w remotes to have access to the other tutorials as well. Just let us know, =
so we can advertise access URLs on the mentioned web page. As usual, we can=
 provide a real-time, synchronized view of the sessions, involving audio, v=
ideo and presentation slides.
>=20
> I think it would be useful. Thank you.
>=20
> Jari
>=20
>=20

From johnl@iecc.com  Sat Jul 27 15:01:03 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDCCC21F94DC for <ietf@ietfa.amsl.com>; Sat, 27 Jul 2013 15:01:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.655
X-Spam-Level: 
X-Spam-Status: No, score=-110.655 tagged_above=-999 required=5 tests=[AWL=0.544, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id StflAuSW-FrT for <ietf@ietfa.amsl.com>; Sat, 27 Jul 2013 15:00:59 -0700 (PDT)
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 7708521F94FD for <ietf@ietf.org>; Sat, 27 Jul 2013 15:00:59 -0700 (PDT)
Received: (qmail 63177 invoked from network); 27 Jul 2013 22:00:58 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 27 Jul 2013 22:00:58 -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=51f4431a.xn--3zv.k1307; i=johnl@user.iecc.com; bh=QlxcUoatkSgPHiNjbZcJjRVdYVc1/PfMZv4HkHLf8Lw=; b=d8/7ZgrfbjphVmcYt/kEc/F5hMQ2OwtjLjeGI2gGFsYDls+0VyeW89gH+0aPcNuYECmXsWM81YYdDAfWvGvctA31USEcB2CVE71BGhMZFgyBCMKPzgKYBBj55w6osxGzt4aII2yiE602QBEPoADKyg9djem0bmmiyjox4R3FuYzZHhnF2D2+czKN1BcJaDPi/AvypqtZHp9lDERfGOrEjRZ+t+7YV0yKMBxkikPBFp5eqK59370/OpEdGpTESt6g
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=51f4431a.xn--3zv.k1307; olt=johnl@user.iecc.com; bh=QlxcUoatkSgPHiNjbZcJjRVdYVc1/PfMZv4HkHLf8Lw=; b=a386i1B2bZrdKSlWpvld3DSA4bDxa5+T6xJsBrGZovnSUSY1MgktO/GnEWZF2X6gL1Fge6bRQeeUnPTzFuGWIcD6evWXaEqVOsW/NkwIlGYgH9j8p96+DAKS0bPs9CUFIp0Ur/EtqoZWuyaJWN/o9NGDizKcWSnHRuJsk/+8WfiRbMsRIh9Nsje39OvD6vlbnZUVaRrRp7S2dYfGY2Drsn8WGVcUPtQm6SN7gBbZcewVHncXTtsu012g3zaKiQRq
Date: 27 Jul 2013 22:00:36 -0000
Message-ID: <20130727220036.3517.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Remote participants, newcomers, and tutorials (was: IETF87 Audio Streaming Info)
In-Reply-To: <8BA59F96-A1DE-460F-9A22-F2CD4CE5F31C@emc.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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Jul 2013 22:01:04 -0000

In article <8BA59F96-A1DE-460F-9A22-F2CD4CE5F31C@emc.com> you write:
>I think it would be really helpful/useful if working groups could provide short
>video overviews to help people understand the work.  This includes newcomers and
>also interested observers, who may include implementers.  Can that be
>accommodated, maybe at a future meeting?  I am happy to help if I can.

I gather you're active in the MILE group.  How about making a video
overview for it and let us know how it went?  If we make videos, we
can put it on the web and not take up time at WG meetings.

Having made my share of five minute videos, I've found that a PC with
a webcam and cheap video recording and editing software (to add a
title and splice together the pieces) is all you need technically, but
coming up with a script, getting the required people to agree that
it's OK, and recording it in a way that is watchable is a surprisingly
large amount of work.

R's,
John

From melinda.shore@gmail.com  Sat Jul 27 15:22:45 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D75111E811A for <ietf@ietfa.amsl.com>; Sat, 27 Jul 2013 15:22:45 -0700 (PDT)
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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EMb1s+L9Zltu for <ietf@ietfa.amsl.com>; Sat, 27 Jul 2013 15:22:45 -0700 (PDT)
Received: from mail-pd0-x230.google.com (mail-pd0-x230.google.com [IPv6:2607:f8b0:400e:c02::230]) by ietfa.amsl.com (Postfix) with ESMTP id 1A58311E8119 for <ietf@ietf.org>; Sat, 27 Jul 2013 15:22:45 -0700 (PDT)
Received: by mail-pd0-f176.google.com with SMTP id q10so976117pdj.35 for <ietf@ietf.org>; Sat, 27 Jul 2013 15:22:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=h+geGFOg0y1DXrimC5Jg4wkFE7Kxv59R8bI7KxUZhTA=; b=zFR54+Zz7mCWevSvMPH9FFpplGqWlTbpdU23155RKRAD0KGDAEriIgV0e+Yh0dF627 HnLSm2DF7BNPNnqoEJ+umi/BRmvC5s6CGeYLxDmg16x8slQswaEXDoKsGKtPMTDQW1Hp fquHVJcY1N3ATr6WVK0RZniD2BjjpctfxcbHAd8CCnVHMGRvlFhU4TgkydAXOBCyH8A8 HuPI/x8rd77xNLFIbbnWTQljEwIO4mI9R5E5wzHPpXvHtXr7dYic+lgiVoTULJEwZHFX uzMzZyxIsQwkUhKKqeXGL+q3Hf798IKUQTdHhN0enb0ZH1nbGjPXkqxpL3suACRxhV0V blTA==
X-Received: by 10.69.8.65 with SMTP id di1mr53264861pbd.32.1374963764813; Sat, 27 Jul 2013 15:22:44 -0700 (PDT)
Received: from spandex.local (66-230-85-245-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.85.245]) by mx.google.com with ESMTPSA id oj6sm11590145pab.9.2013.07.27.15.22.43 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 27 Jul 2013 15:22:43 -0700 (PDT)
Message-ID: <51F44831.2030300@gmail.com>
Date: Sat, 27 Jul 2013 14:22:41 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Remote participants, newcomers,	and tutorials
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net> <2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net> <5EB533DC-E6EF-40E3-A225-F8F1E39A46DC@unina.it> <18690A2F-5439-4CCC-91F1-58CF67D8D704@piuha.net> <8BA59F96-A1DE-460F-9A22-F2CD4CE5F31C@emc.com>
In-Reply-To: <8BA59F96-A1DE-460F-9A22-F2CD4CE5F31C@emc.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Jul 2013 22:22:45 -0000

On 7/27/13 1:38 PM, Moriarty, Kathleen wrote:
> I think it would be really helpful/useful if working groups could
> provide short video overviews to help people understand the work.
> This includes newcomers and also interested observers, who may
> include implementers.  Can that be accommodated, maybe at a future
> meeting?  I am happy to help if I can.

I'm sorry, but no, I am not comfortable with this.  If someone
wants to go off on their own and do something along these lines,
more power to them, but we have working group charters, we've
got framework documents, and presumably people can read.

I would be very sorry to see IETF *working* meetings turned into
something closer to conferences, or to dumbing things down to
accommodate newcomers who I gather from discussion so far don't have
anything particular in mind.

I've participated remotely quite a bit and I do think that having
the newcomers session available to remote participants would be a
big win (and there's something that I think it would be helpful
to record on video and make available on Youtube or some such).

It may be the case over the longer term that we've got so many
newer participants who won't adapt to the IETF's working style
that the IETF will need to become more like other standards bodies
to accommodate them, but I don't think we're there yet and I
would be sorry to see working meetings turned into conferences.
People who attend should be participants, not audience.

Melinda

From sm@resistor.net  Sat Jul 27 16:12:25 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90EB811E811B for <ietf@ietfa.amsl.com>; Sat, 27 Jul 2013 16:12:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.497
X-Spam-Level: 
X-Spam-Status: No, score=-102.497 tagged_above=-999 required=5 tests=[AWL=0.102, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aZJbpA8iANsq for <ietf@ietfa.amsl.com>; Sat, 27 Jul 2013 16:12:24 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id BDFD311E811A for <ietf@ietf.org>; Sat, 27 Jul 2013 16:12:23 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r6RNC7s2005218; Sat, 27 Jul 2013 16:12:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1374966733; bh=9JGyFkn5LRtE8bNi4Zc4KTlhu8tfdPttcRpcOwc0e/s=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=jDuvshHOU7KRkaomspzOG0e/2VyBypPSqFVAXI2OdgMtFm0Wh3Sq4SDrXVD0T1Esm JVQ0VqSnCjNQvBTMwm5UkO9kApNZKQhHYPBIwR1QH94ucBXIi7DOF2TMBC0jes84v5 8pHaUfnhy3sFwV1pq32jy26TZ592avjsR3ccapTk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1374966733; i=@resistor.net; bh=9JGyFkn5LRtE8bNi4Zc4KTlhu8tfdPttcRpcOwc0e/s=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=dMJRLLd6E0HuVZhIufuMotJJk85rIQwqZSVCR0ZLQXK+96J1RhREsX9kh8vZmadci Z2wW2GE6AZuh2ATlaX504PtELefVEokIBsdwtTUxKEEL7qvJkOvn8pL5wk3EjY5rzV dZPO8B9iddQiK6y4po54KseA5BuhbmTbyrTd89p0=
Message-Id: <6.2.5.6.2.20130727142410.0665a0f8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 27 Jul 2013 16:11:53 -0700
To: Jari Arkko <jari.arkko@piuha.net>, dcrocker@bbiw.net, Brian E Carpenter <brian.e.carpenter@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: Remote participants, newcomers, and tutorials
In-Reply-To: <E12475C2-B005-42A7-A662-F36F55BB953E@piuha.net>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net> <2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net> <51F3BBB6.5030406@dcrocker.net> <51F42F7B.2060706@gmail.com> <E12475C2-B005-42A7-A662-F36F55BB953E@piuha.net>
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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Jul 2013 23:12:25 -0000

At 14:01 27-07-2013, Jari Arkko wrote:
>Let me clarify why I thought it was wrong. I don't think I'm 
>disagreeing with you,

I'll reorder the end of the original message.

>Jari (the guy who is preparing for the possibility - no matter 
>how  remote - that the cool kids might actually teach us a trick or two) :-)

If there is a possibility, however remote, that someone, irrespective 
or age or any other attributes, can teach me something I believe that 
it is worthwhile to be open to that.  Yes, it may have been tried 
before.  And yes, there is a history of failure.

>However. Newcomers are not all alike. The student coming here to 
>observe the IETF. The researcher who understands the field we are 
>embarking on. The colleague that has been implementing The Protocol 
>for the last two years in the office, but is now coming to the IETF 
>for the first time. The guy who has something to say about the 
>operational experience of our results. The team who brought their 
>idea to the IETF to be standardised. And so on.

I do not equate new to the IETF with beginner.  The student may be 
someone writing code.  The person may know that for all its fancy 
words what's in the draft won't work as he or she tried that.  The 
operator knows that whatever the RFC says it is not possible to 
follow that due to operational constraints.

A guideline is not a good one if it will have a chilling effect 
(motivate people not to speak up).

Regards,
-sm 


From yding@cs.helsinki.fi  Sat Jul 27 16:53:26 2013
Return-Path: <yding@cs.helsinki.fi>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 227D421F8E97 for <ietf@ietfa.amsl.com>; Sat, 27 Jul 2013 16:53:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.219
X-Spam-Level: 
X-Spam-Status: No, score=-6.219 tagged_above=-999 required=5 tests=[AWL=0.380,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fhlP9AXpB7RV for <ietf@ietfa.amsl.com>; Sat, 27 Jul 2013 16:53:21 -0700 (PDT)
Received: from courier.cs.helsinki.fi (courier.cs.helsinki.fi [128.214.9.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8CD411E811D for <ietf@ietf.org>; Sat, 27 Jul 2013 16:53:15 -0700 (PDT)
X-DKIM: Courier DKIM Filter v0.50+pk-2013-06-17 courier.cs.helsinki.fi Sun Jul 28 02:52:59 2013
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cs.helsinki.fi; h=message-id:date:from:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; s= dkim20130528; bh=QlLcK+ba70fBMcon60Q29moj5ABw8KWrxeXwL8G6DsI=; b= IJQ9JRJ97r2Qupg4XsM+U59rAcH6PFhKgzie4fvfajP2OIBiZZ/LnPUB8Rqe1w2B bsnoMPZ1MNqjXj4Bmy9BDis2tYcoS9wxW8TYsh4D/53mrAnlWD65SC1jBCSr3GPy skJZCPtOr5r0HWVL+xp77B8ArF75DvdmuPGLOf97xBo=
Received: from [131.111.218.40] (s218i40.wolfson.cam.ac.uk [131.111.218.40]) (AUTH: PLAIN yding, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by mail.cs.helsinki.fi with esmtp; Sun, 28 Jul 2013 02:52:59 +0300 id 00068082.51F45D5B.00000B3C
Message-ID: <51F45D55.4040709@cs.helsinki.fi>
Date: Sun, 28 Jul 2013 00:52:53 +0100
From: Aaron Yi DING <yding@cs.helsinki.fi>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: Remote participants, newcomers,	and tutorials
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net> <2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net> <5EB533DC-E6EF-40E3-A225-F8F1E39A46DC@unina.it> <18690A2F-5439-4CCC-91F1-58CF67D8D704@piuha.net> <8BA59F96-A1DE-460F-9A22-F2CD4CE5F31C@emc.com> <51F44831.2030300@gmail.com>
In-Reply-To: <51F44831.2030300@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Jul 2013 23:53:26 -0000

On 27/07/13 23:22, Melinda Shore wrote:
> On 7/27/13 1:38 PM, Moriarty, Kathleen wrote:
>> I think it would be really helpful/useful if working groups could
>> provide short video overviews to help people understand the work.
>> This includes newcomers and also interested observers, who may
>> include implementers.  Can that be accommodated, maybe at a future
>> meeting?  I am happy to help if I can.
> I'm sorry, but no, I am not comfortable with this.  If someone
> wants to go off on their own and do something along these lines,
> more power to them, but we have working group charters, we've
> got framework documents, and presumably people can read.
>
> I would be very sorry to see IETF *working* meetings turned into
> something closer to conferences, or to dumbing things down to
> accommodate newcomers who I gather from discussion so far don't have
> anything particular in mind.
>
> I've participated remotely quite a bit and I do think that having
> the newcomers session available to remote participants would be a
> big win (and there's something that I think it would be helpful
> to record on video and make available on Youtube or some such).
>
> It may be the case over the longer term that we've got so many
> newer participants who won't adapt to the IETF's working style
> that the IETF will need to become more like other standards bodies
> to accommodate them, but I don't think we're there yet and I
> would be sorry to see working meetings turned into conferences.
> People who attend should be participants, not audience.


What do you mean by conference? too much information inferred in your 
term that may confuse others on the list.  Will appreciate, if you can 
share bit more on it, behind the single term "conference" that you 
particularly don't like.

I agree with you that changing the working culture in WG meetings can be 
bad, and we shall not go out of the ways to accommodate anything under 
the name of "diversity".

Aaron


PS: things evolve, over the long term. it does not matter we like it or 
not. that is how it is.



> Melinda


From melinda.shore@gmail.com  Sat Jul 27 17:27:20 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F03211E812B for <ietf@ietfa.amsl.com>; Sat, 27 Jul 2013 17:27:20 -0700 (PDT)
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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1isiIBc3dKYD for <ietf@ietfa.amsl.com>; Sat, 27 Jul 2013 17:27:19 -0700 (PDT)
Received: from mail-pd0-x235.google.com (mail-pd0-x235.google.com [IPv6:2607:f8b0:400e:c02::235]) by ietfa.amsl.com (Postfix) with ESMTP id 310CE11E811F for <ietf@ietf.org>; Sat, 27 Jul 2013 17:27:15 -0700 (PDT)
Received: by mail-pd0-f181.google.com with SMTP id g10so468690pdj.12 for <ietf@ietf.org>; Sat, 27 Jul 2013 17:27:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=RvEwTtYtvpgETtpKXm7uDjj79UVk9yFRWqK8Sadp4f4=; b=o1TQqQKAMz0j6M/qyjJisD6rgVZkkeTt9rY/maXeAVHY3zcXXvP3GksJ0aaRySgAtH bH7+sQpwc2wtR+vRro9JDIQArmtVsAyGgDNR0X0NCGprCu9Dxq0ESajvgqvRHTFOcPod 1MOjOk52gjDn3eiXsCJVma2exUQ2LtRiwKvIdq8j+8v9xQUtQ2EqlJKCV0IFN9XlD/J2 LmQdBdZheKM/B2lDxbvQ6QeurA17vf7IjXZ03Vcq2V6NQotMpg8q9/S72cGpRERw6MDJ Wu5LmTK6epp5p4iV9oYbtkunhaSEhthW2LIFVxtQ7vOT6ApGDdxB1emRQBIzPu4fWYr5 0lSA==
X-Received: by 10.68.58.97 with SMTP id p1mr61401121pbq.144.1374971234891; Sat, 27 Jul 2013 17:27:14 -0700 (PDT)
Received: from spandex.local (66-230-85-245-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.85.245]) by mx.google.com with ESMTPSA id lk9sm11985642pab.2.2013.07.27.17.27.13 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 27 Jul 2013 17:27:14 -0700 (PDT)
Message-ID: <51F4655F.3060108@gmail.com>
Date: Sat, 27 Jul 2013 16:27:11 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Aaron Yi DING <yding@cs.helsinki.fi>
Subject: Re: Remote participants, newcomers,	and tutorials
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net> <2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net> <5EB533DC-E6EF-40E3-A225-F8F1E39A46DC@unina.it> <18690A2F-5439-4CCC-91F1-58CF67D8D704@piuha.net> <8BA59F96-A1DE-460F-9A22-F2CD4CE5F31C@emc.com> <51F44831.2030300@gmail.com> <51F45D55.4040709@cs.helsinki.fi>
In-Reply-To: <51F45D55.4040709@cs.helsinki.fi>
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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jul 2013 00:27:20 -0000

On 7/27/13 3:52 PM, Aaron Yi DING wrote:
> What do you mean by conference? too much information inferred in your
> term that may confuse others on the list.  Will appreciate, if you can
> share bit more on it, behind the single term "conference" that you
> particularly don't like.

I love conferences but I'd hate to see IETF meetings turned into
them.  By "conference" I mean something in which people give papers
(or other talks) and most of the participants have an audience
role.  IETF meeting participation should be active.  It is almost
always the case, of course, that someone attending a meeting will
sit in on working groups in which they're not active, but it
should be unusual for someone who has no particular work in the
IETF and who's active in no working groups and active on no mailing
lists to come to a meeting.  IETF meetings are places to get work
done.

> I agree with you that changing the working culture in WG meetings can be
> bad, and we shall not go out of the ways to accommodate anything under
> the name of "diversity".

I actually do think we should go out of our way to accommodate
and encourage diversity, but again, that's in the interest of
getting work done (and getting our work correct).  But back to
the original question of how to bring newcomers in through
remote participation - I would start with the assumption that
they'd be participating, remotely or otherwise, because they
have some networking problem (and possibly solution) that needs
standardization.  I'd also assume that they've done a basic
literature search, etc.

I wonder if it would be worthwhile to put together some material
(video or otherwise) that would help people decide whether or not
their problem belongs in the IETF.

Melinda


From hallam@gmail.com  Sat Jul 27 18:28:43 2013
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0B2D21E8063 for <ietf@ietfa.amsl.com>; Sat, 27 Jul 2013 18:28:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.321
X-Spam-Level: 
X-Spam-Status: No, score=-2.321 tagged_above=-999 required=5 tests=[AWL=0.278,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X7k+QCbrGwBE for <ietf@ietfa.amsl.com>; Sat, 27 Jul 2013 18:28:43 -0700 (PDT)
Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) by ietfa.amsl.com (Postfix) with ESMTP id BDB5221E8054 for <ietf@ietf.org>; Sat, 27 Jul 2013 18:28:42 -0700 (PDT)
Received: by mail-wi0-f172.google.com with SMTP id c10so2006533wiw.5 for <ietf@ietf.org>; Sat, 27 Jul 2013 18:28:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=yC7IDFI/r5X23rKs6zHpBPNI4Wj4BhuNSRZqVhvIqJk=; b=ou9XVuB8DDUDjaE6SsAuiV2uXPQPZynWOh4G+wqvz8tlYgyBIaS+q9JqiclUhALM6+ Gd8Qapx5RR3Yh7OKSsNurR8xmU7HTyxMopscRgu3XI5BkeqmkXikasLC28jo46R2rgMs jdThwIrXW3QEEECFAhcoDtmc/z3/t7Xfmb6KUVEKOusTizMVE8qVIa9zqmLpTLoR1fHp PyxBD/FKDyk+jp46DkG4l0MK5NLZfNAgNAfWvGb/vcfzNxf0We4i2pnFwE/vIGCzUCwF IowghyipDetjdZUMKATFCbYC3QDoIgHS8J4Q+QsWOHrcc+errPHtXdIADhJBPmTezbrK k/Mg==
MIME-Version: 1.0
X-Received: by 10.194.219.233 with SMTP id pr9mr703102wjc.8.1374974921902; Sat, 27 Jul 2013 18:28:41 -0700 (PDT)
Received: by 10.194.6.65 with HTTP; Sat, 27 Jul 2013 18:28:41 -0700 (PDT)
In-Reply-To: <51F44831.2030300@gmail.com>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net> <2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net> <5EB533DC-E6EF-40E3-A225-F8F1E39A46DC@unina.it> <18690A2F-5439-4CCC-91F1-58CF67D8D704@piuha.net> <8BA59F96-A1DE-460F-9A22-F2CD4CE5F31C@emc.com> <51F44831.2030300@gmail.com>
Date: Sat, 27 Jul 2013 21:28:41 -0400
Message-ID: <CAMm+LwjzH4bVU_kBSnVtTbcHrkWuAFkTsn2CWm3osAA670aFjA@mail.gmail.com>
Subject: Re: Remote participants, newcomers, and tutorials
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c1b7e6cb920204e2884b69
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jul 2013 01:28:44 -0000

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

On Sat, Jul 27, 2013 at 6:22 PM, Melinda Shore <melinda.shore@gmail.com>wrote:

> On 7/27/13 1:38 PM, Moriarty, Kathleen wrote:
> > I think it would be really helpful/useful if working groups could
> > provide short video overviews to help people understand the work.
> > This includes newcomers and also interested observers, who may
> > include implementers.  Can that be accommodated, maybe at a future
> > meeting?  I am happy to help if I can.
>
> I'm sorry, but no, I am not comfortable with this.  If someone
> wants to go off on their own and do something along these lines,
> more power to them, but we have working group charters, we've
> got framework documents, and presumably people can read.
>
> I would be very sorry to see IETF *working* meetings turned into
> something closer to conferences, or to dumbing things down to
> accommodate newcomers who I gather from discussion so far don't have
> anything particular in mind.
>

IETF meetings are trying to do two different things

1) Do work on working group documents and specifications

2) Foster understanding of work in other parts of the IETF and encourage
cross-working group interactions.


These are different objectives that require totally different approaches.
The first is best met by small one or two day meetings of people who are
concentrating on just that one spec. The second is best met by plenaries
and session talks designed to explain work to people outside the group.



As for tutorial sessions on tools for writing IDs... Isn't the need for
such a session proof that the tools and/or the formats are broken?

I got fed up with the hosted version of XML2RFC and found it impossible to
get the code running on my machine (it requires very specific python
package versions that would require me to down-version). Plus I find the
XML2RFC format obnoxious. The original expectation in 1999 was that XML
editors would soon be ubiquitous and good. Instead there are rather and
they all suck.

So I wrote my own. You can now write your RFC in HTML and the tool will
convert it into IETF caveman format, formatted HTML and/or XML2RFC. I will
be adding XML2RFC format sometime next week.

The code has only been tested on Windows so far but it is in CLI and so the
executable can run on any platform with a runtime (all of them). I want to
test on other platforms and test submitting drafts before making a release.

http://sourceforge.net/projects/html2rfc/?source=directory


The reason for adding xml2rfc format is that some folk may want to use it
just for the ability to manage references. Instead of having to mess about
with sticking entities in the front and citations in the middle and
references in the running text, just add a reference in the text, [~RFC822]
for informative, [!RFC822] for normative and the tool will work it all out.


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

--001a11c1b7e6cb920204e2884b69
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, Jul 27, 2013 at 6:22 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: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 7/27/13 1:38 PM, Moriarty, Kathleen wrote:<br>
&gt; I think it would be really helpful/useful if working groups could<br>
&gt; provide short video overviews to help people understand the work.<br>
&gt; This includes newcomers and also interested observers, who may<br>
&gt; include implementers. =A0Can that be accommodated, maybe at a future<b=
r>
&gt; meeting? =A0I am happy to help if I can.<br>
<br>
I&#39;m sorry, but no, I am not comfortable with this. =A0If someone<br>
wants to go off on their own and do something along these lines,<br>
more power to them, but we have working group charters, we&#39;ve<br>
got framework documents, and presumably people can read.<br>
<br>
I would be very sorry to see IETF *working* meetings turned into<br>
something closer to conferences, or to dumbing things down to<br>
accommodate newcomers who I gather from discussion so far don&#39;t have<br=
>
anything particular in mind.<br></blockquote><div><br></div><div>IETF meeti=
ngs are trying to do two different things</div><div><br></div><div>1) Do wo=
rk on working group documents and specifications</div><div><br></div><div>
2) Foster understanding of work in other parts of the IETF and encourage cr=
oss-working group interactions.</div><div><br></div><div><br></div><div>The=
se are different objectives that require totally different approaches. The =
first is best met by small one or two day meetings of people who are concen=
trating on just that one spec. The second is best met by plenaries and sess=
ion talks designed to explain work to people outside the group.</div>
<div><br></div><div><br></div><div><br></div><div>As for tutorial sessions =
on tools for writing IDs... Isn&#39;t the need for such a session proof tha=
t the tools and/or the formats are broken?</div><div><br></div><div>I got f=
ed up with the hosted version of XML2RFC and found it impossible to get the=
 code running on my machine (it requires very specific python package versi=
ons that would require me to down-version). Plus I find the XML2RFC format =
obnoxious. The original expectation in 1999 was that XML editors would soon=
 be ubiquitous and good. Instead there are rather and they all suck.</div>
<div><br></div><div>So I wrote my own. You can now write your RFC in HTML a=
nd the tool will convert it into IETF caveman format, formatted HTML and/or=
 XML2RFC. I will be adding XML2RFC format sometime next week.=A0</div><div>
<br></div><div>The code has only been tested on Windows so far but it is in=
 CLI and so the executable can run on any platform with a runtime (all of t=
hem). I want to test on other platforms and test submitting drafts before m=
aking a release.</div>
<div><br></div><div><a href=3D"http://sourceforge.net/projects/html2rfc/?so=
urce=3Ddirectory">http://sourceforge.net/projects/html2rfc/?source=3Ddirect=
ory</a><br></div><div><br></div><div><br></div><div>The reason for adding x=
ml2rfc format is that some folk may want to use it just for the ability to =
manage references. Instead of having to mess about with sticking entities i=
n the front and citations in the middle and references in the running text,=
 just add a reference in the text, [~RFC822] for informative, [!RFC822] for=
 normative and the tool will work it all out.</div>
<div><br></div><div><br></div></div>-- <br>Website: <a href=3D"http://halla=
mbaker.com/">http://hallambaker.com/</a><br>
</div></div>

--001a11c1b7e6cb920204e2884b69--

From randy@psg.com  Sat Jul 27 21:11:17 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07A9911E8168 for <ietf@ietfa.amsl.com>; Sat, 27 Jul 2013 21:11:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.546
X-Spam-Level: 
X-Spam-Status: No, score=-2.546 tagged_above=-999 required=5 tests=[AWL=0.053,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XKeoEG4bF70S for <ietf@ietfa.amsl.com>; Sat, 27 Jul 2013 21:11:12 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [198.180.150.18]) by ietfa.amsl.com (Postfix) with ESMTP id E45C911E8166 for <ietf@ietf.org>; Sat, 27 Jul 2013 21:11:11 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1V3IJr-0006h1-37; Sun, 28 Jul 2013 04:11:09 +0000
Date: Sun, 28 Jul 2013 06:10:54 +0200
Message-ID: <m2iozvxr1t.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Kathleen Moriarty <kathleen.moriarty@emc.com>
Subject: Re: Remote participants, newcomers, and tutorials (was: IETF87	Audio Streaming Info)
In-Reply-To: <8BA59F96-A1DE-460F-9A22-F2CD4CE5F31C@emc.com>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net> <2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net> <5EB533DC-E6EF-40E3-A225-F8F1E39A46DC@unina.it> <18690A2F-5439-4CCC-91F1-58CF67D8D704@piuha.net> <8BA59F96-A1DE-460F-9A22-F2CD4CE5F31C@emc.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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jul 2013 04:11:17 -0000

> I think it would be really helpful/useful if working groups could
> provide short video overviews to help people understand the work.
> This includes newcomers and also interested observers, who may include
> implementers.

putting up yuotube/vimeo tutorials on the wg's technical space would be
a good thing for folk with spare time to do.  i am sure we could arrange
pointer space on the wg's web page.

> Can that be accommodated, maybe at a future meeting?

in meeting time?  great ghu, please no!

randy

From randy@psg.com  Sat Jul 27 21:13:08 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2825A21F8426 for <ietf@ietfa.amsl.com>; Sat, 27 Jul 2013 21:13:08 -0700 (PDT)
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=[AWL=0.050,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8qX6iUqVRNHI for <ietf@ietfa.amsl.com>; Sat, 27 Jul 2013 21:13:03 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [198.180.150.18]) by ietfa.amsl.com (Postfix) with ESMTP id 055B311E8160 for <ietf@ietf.org>; Sat, 27 Jul 2013 21:13:03 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1V3ILt-0006hN-QQ; Sun, 28 Jul 2013 04:13:02 +0000
Date: Sun, 28 Jul 2013 06:13:01 +0200
Message-ID: <m2haffxqya.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: Remote participants, newcomers,	and tutorials
In-Reply-To: <51F44831.2030300@gmail.com>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net> <2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net> <5EB533DC-E6EF-40E3-A225-F8F1E39A46DC@unina.it> <18690A2F-5439-4CCC-91F1-58CF67D8D704@piuha.net> <8BA59F96-A1DE-460F-9A22-F2CD4CE5F31C@emc.com> <51F44831.2030300@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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jul 2013 04:13:08 -0000

> I would be very sorry to see IETF *working* meetings turned into
> something closer to conferences, or to dumbing things down to
> accommodate newcomers who I gather from discussion so far don't have
> anything particular in mind.

yup.  i guess it is time for my quarterly suggestion to remove the
projectors and screens.

randy

From melinda.shore@gmail.com  Sat Jul 27 21:17:19 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8F0621F855F for <ietf@ietfa.amsl.com>; Sat, 27 Jul 2013 21:17:19 -0700 (PDT)
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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WoS1uTzTNddq for <ietf@ietfa.amsl.com>; Sat, 27 Jul 2013 21:17:19 -0700 (PDT)
Received: from mail-pb0-x230.google.com (mail-pb0-x230.google.com [IPv6:2607:f8b0:400e:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id 53F6E21F854E for <ietf@ietf.org>; Sat, 27 Jul 2013 21:17:19 -0700 (PDT)
Received: by mail-pb0-f48.google.com with SMTP id md4so3401798pbc.7 for <ietf@ietf.org>; Sat, 27 Jul 2013 21:17:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=s6gmZOrui8svLzznBHy71ewN2AEjCEkCT9F9y/sC26E=; b=I7ZyyhNKxhn4hj2/WzOgOJBeA4sbud8jRw6IiPI6Er//8GqAuTxDm7QnZSQ8I/qbRS RT6NVaSEOhSlRHsGHIwjPgbjAXPujvMvVfjxXs1hOwYLXOCBg0R3Gc1QYtNv/eMCTLqn VOEyXIjZuEtykV8m2HKnkQHYnRo6DekbiRic5LLt/iaQm4yRekeT0JldHXpk1L1TpJdT l+gdfiAwUJl2MlTNbCwUUisTB8s/vJG2RQ85w4O2EcI1El/B5aFChPcz4xqETdvFtn8j 1aciSEzZGGU769HG1MLx19bwqmVqyt9VUrG2e1XlUEWKzpfcz/bZ/PLc5m9da8Dvs2W8 mRqw==
X-Received: by 10.66.121.195 with SMTP id lm3mr62903330pab.116.1374985039072;  Sat, 27 Jul 2013 21:17:19 -0700 (PDT)
Received: from spandex.local (66-230-85-245-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.85.245]) by mx.google.com with ESMTPSA id ys4sm69080656pbb.9.2013.07.27.21.17.17 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 27 Jul 2013 21:17:18 -0700 (PDT)
Message-ID: <51F49B4A.7020609@gmail.com>
Date: Sat, 27 Jul 2013 20:17:14 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
Subject: Re: Remote participants, newcomers,	and tutorials
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net> <2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net> <5EB533DC-E6EF-40E3-A225-F8F1E39A46DC@unina.it> <18690A2F-5439-4CCC-91F1-58CF67D8D704@piuha.net> <8BA59F96-A1DE-460F-9A22-F2CD4CE5F31C@emc.com> <51F44831.2030300@gmail.com> <m2haffxqya.wl%randy@psg.com>
In-Reply-To: <m2haffxqya.wl%randy@psg.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jul 2013 04:17:19 -0000

On 7/27/13 8:13 PM, Randy Bush wrote:
> yup.  i guess it is time for my quarterly suggestion to remove the
> projectors and screens.

Then I guess it's time for my quarterly "I'd be good with that."

Melinda


From l.wood@surrey.ac.uk  Sat Jul 27 21:23:52 2013
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E310721F8F3C for <ietf@ietfa.amsl.com>; Sat, 27 Jul 2013 21:23:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S8URpCZ3mUGE for <ietf@ietfa.amsl.com>; Sat, 27 Jul 2013 21:23:48 -0700 (PDT)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.174]) by ietfa.amsl.com (Postfix) with ESMTP id C653521F935A for <ietf@ietf.org>; Sat, 27 Jul 2013 21:23:47 -0700 (PDT)
Received: from [195.245.230.131:22513] by server-14.bemta-3.messagelabs.com id 2D/74-12881-1DC94F15; Sun, 28 Jul 2013 04:23:45 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-12.tower-78.messagelabs.com!1374985424!29384428!1
X-Originating-IP: [131.227.200.35]
X-StarScan-Received: 
X-StarScan-Version: 6.9.11; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 17800 invoked from network); 28 Jul 2013 04:23:45 -0000
Received: from exht021p.surrey.ac.uk (HELO EXHT021P.surrey.ac.uk) (131.227.200.35) by server-12.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 28 Jul 2013 04:23:45 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT021P.surrey.ac.uk ([131.227.200.35]) with mapi; Sun, 28 Jul 2013 05:23:44 +0100
From: <l.wood@surrey.ac.uk>
To: <randy@psg.com>, <melinda.shore@gmail.com>
Date: Sun, 28 Jul 2013 05:23:21 +0100
Subject: RE: Remote participants, newcomers,	and tutorials
Thread-Topic: Remote participants, newcomers,	and tutorials
Thread-Index: Ac6LSN+h2eW5+JULRAKPNKByPvdmNwAAVHZQ
Message-ID: <290E20B455C66743BE178C5C84F1240822406074EA@EXMB01CMS.surrey.ac.uk>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net> <2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net> <5EB533DC-E6EF-40E3-A225-F8F1E39A46DC@unina.it> <18690A2F-5439-4CCC-91F1-58CF67D8D704@piuha.net> <8BA59F96-A1DE-460F-9A22-F2CD4CE5F31C@emc.com> <51F44831.2030300@gmail.com>,<m2haffxqya.wl%randy@psg.com>
In-Reply-To: <m2haffxqya.wl%randy@psg.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jul 2013 04:23:53 -0000

> I would be very sorry to see IETF *working* meetings turned into
> something closer to conferences,=20

with poster sessions!

Lloyd Wood
http://sat-net.com/L.Wood/


From melinda.shore@gmail.com  Sat Jul 27 21:26:38 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7848411E8155 for <ietf@ietfa.amsl.com>; Sat, 27 Jul 2013 21:26:38 -0700 (PDT)
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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KZFb-YENju5v for <ietf@ietfa.amsl.com>; Sat, 27 Jul 2013 21:26:38 -0700 (PDT)
Received: from mail-pa0-x22e.google.com (mail-pa0-x22e.google.com [IPv6:2607:f8b0:400e:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 7C2F411E8163 for <ietf@ietf.org>; Sat, 27 Jul 2013 21:26:27 -0700 (PDT)
Received: by mail-pa0-f46.google.com with SMTP id fa1so4693176pad.33 for <ietf@ietf.org>; Sat, 27 Jul 2013 21:26:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=SBoiP2NYAp4OoOaJBkoloNQAMpBXuxRD+c1xgiwRRFk=; b=SSr1vxNfPf7/DKTIIHNFno706W/oCxtKYUzw1/vAR7bzpCWzTuly1cKA4q7EA4ERqk 9AawdTPt2u+arjRrAH11Zop6+eirA4IEpROZa3I2e0OUvB+Ih6vhaGJxC1GjRsLw3OFK 5w9cvh18TO1ODYnwYukdR071SAW+Wru6KH99UyqiA+41xvdSXmiYVo/HDXppSDIs0FzE Yo9T3WzE2HnpoBvakrjVlQO6Lffc9njnqt7QuJGDuxiBMAhyuMD7dstpshwnXryPHHaP BiopHSsK6l38Do4bgN0NEI3SwnQmRDD/YhAlM1R/+itDFvyVrAGkt3CIT5n/wZrLjtXc krpA==
X-Received: by 10.68.137.8 with SMTP id qe8mr61920506pbb.100.1374985587224; Sat, 27 Jul 2013 21:26:27 -0700 (PDT)
Received: from spandex.local (66-230-85-245-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.85.245]) by mx.google.com with ESMTPSA id pv5sm12780807pac.14.2013.07.27.21.26.25 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 27 Jul 2013 21:26:26 -0700 (PDT)
Message-ID: <51F49D6F.4080304@gmail.com>
Date: Sat, 27 Jul 2013 20:26:23 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: l.wood@surrey.ac.uk
Subject: Re: Remote participants, newcomers,	and tutorials
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net> <2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net> <5EB533DC-E6EF-40E3-A225-F8F1E39A46DC@unina.it> <18690A2F-5439-4CCC-91F1-58CF67D8D704@piuha.net> <8BA59F96-A1DE-460F-9A22-F2CD4CE5F31C@emc.com> <51F44831.2030300@gmail.com>, <m2haffxqya.wl%randy@psg.com> <290E20B455C66743BE178C5C84F1240822406074EA@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F1240822406074EA@EXMB01CMS.surrey.ac.uk>
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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jul 2013 04:26:38 -0000

On 7/27/13 8:23 PM, l.wood@surrey.ac.uk wrote:
>> I would be very sorry to see IETF *working* meetings turned into
>> something closer to conferences, 
> with poster sessions!

Arrrr!

Melinda



From moore@network-heretics.com  Sat Jul 27 22:35:35 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A75E721F9BA2 for <ietf@ietfa.amsl.com>; Sat, 27 Jul 2013 22:35:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.98
X-Spam-Level: 
X-Spam-Status: No, score=-2.98 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P0vgmlHCLLnD for <ietf@ietfa.amsl.com>; Sat, 27 Jul 2013 22:35:30 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id 99C1321F937E for <ietf@ietf.org>; Sat, 27 Jul 2013 22:35:30 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 6165320CD5; Sun, 28 Jul 2013 01:35:29 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute6.internal (MEProxy); Sun, 28 Jul 2013 01:35:29 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id :references:to; s=smtpout; bh=9nJBSCb+3l5DDIdA+9sQI7Lntgw=; b=TC tTc1P6hWXYIU4oTpbALN2uFNJbWoIt06fyqqpCw7DkAua3F2W67mRu1hia4lvljG Ia8fODlDQD9DmtA/llGGt/hDO/OODbPE/NdM30QjzAlP6xFcTjq4FfwYKoIWHmBD K2Wob6iKfE29HSDau41heNX6QXvNQyRFzATvWWnbw=
X-Sasl-enc: slJ1HaBqMiW563ShFqQ0o8/5w1rSVWQg2Oe/PUFvO94g 1374989729
Received: from [172.18.100.145] (unknown [94.246.102.170]) by mail.messagingengine.com (Postfix) with ESMTPA id B4BD7680090; Sun, 28 Jul 2013 01:35:28 -0400 (EDT)
Subject: Re: Remote participants, newcomers,	and tutorials
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <51F49B4A.7020609@gmail.com>
Date: Sun, 28 Jul 2013 07:35:27 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <E375D2AA-6CF7-4913-A6B3-D481825BF7F9@network-heretics.com>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net> <2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net> <5EB533DC-E6EF-40E3-A225-F8F1E39A46DC@unina.it> <18690A2F-5439-4CCC-91F1-58CF67D8D704@piuha.net> <8BA59F96-A1DE-460F-9A22-F2CD4CE5F31C@emc.com> <51F44831.2030300@gmail.com> <m2haffxqya.wl%randy@psg.com> <51F49B4A.7020609@gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
X-Mailer: Apple Mail (2.1085)
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jul 2013 05:35:35 -0000

On Jul 28, 2013, at 6:17 AM, Melinda Shore wrote:

> On 7/27/13 8:13 PM, Randy Bush wrote:
>> yup.  i guess it is time for my quarterly suggestion to remove the
>> projectors and screens.
> 
> Then I guess it's time for my quarterly "I'd be good with that."

As would I.

Keith



From lorenzo@meetecho.com  Sat Jul 27 23:58:53 2013
Return-Path: <lorenzo@meetecho.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C17121F9CF2 for <ietf@ietfa.amsl.com>; Sat, 27 Jul 2013 23:58:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.719
X-Spam-Level: 
X-Spam-Status: No, score=-0.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RzcUi1M17wIM for <ietf@ietfa.amsl.com>; Sat, 27 Jul 2013 23:58:44 -0700 (PDT)
Received: from smtpdg2.aruba.it (smtpdg220.aruba.it [62.149.158.220]) by ietfa.amsl.com (Postfix) with ESMTP id 6D19F21F8F24 for <ietf@ietf.org>; Sat, 27 Jul 2013 23:58:42 -0700 (PDT)
Received: from lminiero ([130.129.17.12]) by smtpcmd01.ad.aruba.it with bizsmtp id 5iyd1m00V0FdNkJ01iyeRT; Sun, 28 Jul 2013 08:58:39 +0200
Date: Sun, 28 Jul 2013 08:58:36 +0200
From: Lorenzo Miniero <lorenzo@meetecho.com>
To: team@meetecho.com
Subject: Re: [Team] Re: Remote participants, newcomers, and tutorials (was: IETF87 Audio Streaming Info)
Message-ID: <20130728085836.786715ca@lminiero>
In-Reply-To: <18690A2F-5439-4CCC-91F1-58CF67D8D704@piuha.net>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net> <2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net> <5EB533DC-E6EF-40E3-A225-F8F1E39A46DC@unina.it> <18690A2F-5439-4CCC-91F1-58CF67D8D704@piuha.net>
Organization: Meetecho
X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.18; x86_64-redhat-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org list" <ietf@ietf.org>, iesg@ietf.org, rfc-editor@ietf.org, John C Klensin <john-ietf@jck.com>, SM <sm@resistor.net>, edu-team@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jul 2013 06:58:53 -0000

Il giorno Sat, 27 Jul 2013 16:43:40 +0200
Jari Arkko <jari.arkko@piuha.net> ha scritto:

> Simon,
> 
> > for your information, the Meetecho team is going to record five
> > tutorials on Sunday:
> > 
> > http://www.ietf.org/meeting/87/remote-participation.html#meetecho
> > 
> > We have already provided a URL for those who want to remotely
> > attend the IAOC Overview Session. If you think this might be of
> > interest, we can allow remotes to have access to the other
> > tutorials as well. Just let us know, so we can advertise access
> > URLs on the mentioned web page. As usual, we can provide a
> > real-time, synchronized view of the sessions, involving audio,
> > video and presentation slides.
> 
> I think it would be useful. Thank you.
> 
> Jari
> 

We just updated our agenda page to include links to attend the tutorial
sessions remotely:

	http://ietf87.conf.meetecho.com/

not all are there yet but we'll add more later. The IAB Privacy
Tutorial link is already available, though and will become active in a
couple of minutes, as the session is about to start.

Lorenzo

From ynir@checkpoint.com  Sun Jul 28 00:09:56 2013
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E4E921F9D5E for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 00:09:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.509
X-Spam-Level: 
X-Spam-Status: No, score=-10.509 tagged_above=-999 required=5 tests=[AWL=0.090, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 59FyM1kQvwue for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 00:09:23 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id A79ED21F9D67 for <ietf@ietf.org>; Sun, 28 Jul 2013 00:09:22 -0700 (PDT)
Received: from IL-EX10.ad.checkpoint.com ([194.29.34.147]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r6S79Els003828; Sun, 28 Jul 2013 10:09:14 +0300
X-CheckPoint: {51F4C39A-11-1B221DC2-1FFFF}
Received: from DAG-EX10.ad.checkpoint.com ([169.254.3.90]) by IL-EX10.ad.checkpoint.com ([169.254.2.105]) with mapi id 14.02.0342.003; Sun, 28 Jul 2013 10:09:14 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: "<l.wood@surrey.ac.uk> " <l.wood@surrey.ac.uk>
Subject: Re: Remote participants, newcomers,	and tutorials
Thread-Topic: Remote participants, newcomers,	and tutorials
Thread-Index: AQHOixfdPXU1KqTPEk6hOnTM7P7pUZl5SQWAgAAC44CAAC5WAA==
Date: Sun, 28 Jul 2013 07:09:13 +0000
Message-ID: <A23FA0FC-390A-4E2C-BDA3-57FC0F7502ED@checkpoint.com>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net> <2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net> <5EB533DC-E6EF-40E3-A225-F8F1E39A46DC@unina.it> <18690A2F-5439-4CCC-91F1-58CF67D8D704@piuha.net> <8BA59F96-A1DE-460F-9A22-F2CD4CE5F31C@emc.com> <51F44831.2030300@gmail.com>,<m2haffxqya.wl%randy@psg.com> <290E20B455C66743BE178C5C84F1240822406074EA@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F1240822406074EA@EXMB01CMS.surrey.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.21.103]
x-kse-antivirus-interceptor-info: protection disabled
x-cpdlp: 115109e166bad85261aa3e59e747fbc74e5e077087
Content-Type: text/plain; charset="us-ascii"
Content-ID: <39FC6930D55F3E4E95FBCA847FB9A8B9@ad.checkpoint.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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jul 2013 07:09:57 -0000

On Jul 28, 2013, at 6:23 AM, <l.wood@surrey.ac.uk>
 wrote:

>> I would be very sorry to see IETF *working* meetings turned into
>> something closer to conferences,=20
>=20
> with poster sessions!

And mandatory suit and tie (or women's equivalent business attire) for pres=
enters and chairs.=

From ynir@checkpoint.com  Sun Jul 28 00:11:05 2013
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61E9721F9D68 for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 00:11:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.524
X-Spam-Level: 
X-Spam-Status: No, score=-10.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aAoSG+AIS21s for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 00:10:59 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 2D42B21F8E79 for <ietf@ietf.org>; Sun, 28 Jul 2013 00:10:58 -0700 (PDT)
Received: from IL-EX10.ad.checkpoint.com ([194.29.34.147]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r6S7AtGf004346; Sun, 28 Jul 2013 10:10:56 +0300
X-CheckPoint: {51F4C3FF-2-1B221DC2-1FFFF}
Received: from DAG-EX10.ad.checkpoint.com ([169.254.3.90]) by IL-EX10.ad.checkpoint.com ([169.254.2.105]) with mapi id 14.02.0342.003; Sun, 28 Jul 2013 10:10:55 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Keith Moore <moore@network-heretics.com>
Subject: Re: Remote participants, newcomers,	and tutorials
Thread-Topic: Remote participants, newcomers,	and tutorials
Thread-Index: AQHOixfdPXU1KqTPEk6hOnTM7P7pUZl5SQWAgAABLQCAABXbgIAAGqsA
Date: Sun, 28 Jul 2013 07:10:55 +0000
Message-ID: <C48A3EE7-DB53-428A-9C5F-95802B0383F1@checkpoint.com>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net> <2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net> <5EB533DC-E6EF-40E3-A225-F8F1E39A46DC@unina.it> <18690A2F-5439-4CCC-91F1-58CF67D8D704@piuha.net> <8BA59F96-A1DE-460F-9A22-F2CD4CE5F31C@emc.com> <51F44831.2030300@gmail.com> <m2haffxqya.wl%randy@psg.com> <51F49B4A.7020609@gmail.com> <E375D2AA-6CF7-4913-A6B3-D481825BF7F9@network-heretics.com>
In-Reply-To: <E375D2AA-6CF7-4913-A6B3-D481825BF7F9@network-heretics.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.21.103]
x-kse-antivirus-interceptor-info: protection disabled
x-cpdlp: 1104ba4e58f2da803f2ef2d64aa8d635f02712c64a
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1157D904028D7945858CA70F7354913C@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jul 2013 07:11:05 -0000

On Jul 28, 2013, at 7:35 AM, Keith Moore <moore@network-heretics.com> wrote=
:

>=20
> On Jul 28, 2013, at 6:17 AM, Melinda Shore wrote:
>=20
>> On 7/27/13 8:13 PM, Randy Bush wrote:
>>> yup.  i guess it is time for my quarterly suggestion to remove the
>>> projectors and screens.
>>=20
>> Then I guess it's time for my quarterly "I'd be good with that."
>=20
> As would I.

Me too, as long as we get whiteboards or flip-charts in their stead.

But both the academic world and the business world have taught all of us to=
 communicate through presentations. So, lost cause.

Yoav=

From petithug@acm.org  Sun Jul 28 00:32:59 2013
Return-Path: <petithug@acm.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A9EF21F9D7A for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 00:32:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U64o3UqEWtYE for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 00:32:58 -0700 (PDT)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id EB4AC21F9D6B for <ietf@ietf.org>; Sun, 28 Jul 2013 00:32:57 -0700 (PDT)
Received: from [IPv6:2001:df8:0:64:ca0a:a9ff:fe2e:a4f6] (unknown [IPv6:2001:df8:0:64:ca0a:a9ff:fe2e:a4f6]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id F0A5520EF8; Sun, 28 Jul 2013 09:32:53 +0200 (CEST)
Message-ID: <51F4C92D.4070308@acm.org>
Date: Sun, 28 Jul 2013 09:33:01 +0200
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130630 Icedove/17.0.7
MIME-Version: 1.0
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: Remote participants, newcomers,	and tutorials
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net> <2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net> <5EB533DC-E6EF-40E3-A225-F8F1E39A46DC@unina.it> <18690A2F-5439-4CCC-91F1-58CF67D8D704@piuha.net> <8BA59F96-A1DE-460F-9A22-F2CD4CE5F31C@emc.com> <51F44831.2030300@gmail.com> <m2haffxqya.wl%randy@psg.com> <51F49B4A.7020609@gmail.com> <E375D2AA-6CF7-4913-A6B3-D481825BF7F9@network-heretics.com> <C48A3EE7-DB53-428A-9C5F-95802B0383F1@checkpoint.com>
In-Reply-To: <C48A3EE7-DB53-428A-9C5F-95802B0383F1@checkpoint.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Keith Moore <moore@network-heretics.com>, IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jul 2013 07:32:59 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 07/28/2013 09:10 AM, Yoav Nir wrote:
> 
> On Jul 28, 2013, at 7:35 AM, Keith Moore <moore@network-heretics.com>
> wrote:
> 
>> 
>> On Jul 28, 2013, at 6:17 AM, Melinda Shore wrote:
>> 
>>> On 7/27/13 8:13 PM, Randy Bush wrote:
>>>> yup.  i guess it is time for my quarterly suggestion to remove the 
>>>> projectors and screens.
>>> 
>>> Then I guess it's time for my quarterly "I'd be good with that."
>> 
>> As would I.
> 
> Me too, as long as we get whiteboards or flip-charts in their stead.

What about people at the back of the room who cannot see what you write on the
whiteboard or flip-charts? (at least slides can be downloaded on laptop/tablet
if too far from the projection screen)

What about people following remotely?

What about people who have difficulties understanding the speaker without some
sort of context?

What about being able to understand the problem that will be discussed before
the session, so to cut on the "thinking out loud" on the microphone?

Do you have a presentation during IETF 87? (I already checked that Randy,
Keith and Melinda do not).  I would be really interested to see how this could
work.

Thanks.

> 
> But both the academic world and the business world have taught all of us to
> communicate through presentations. So, lost cause.
> 
> Yoav
> 


- -- 
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: http://blog.marc.petit-huguenin.org
Profile: http://www.linkedin.com/in/petithug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJR9MkpAAoJECnERZXWan7E7msP+wcufr0/az88TuE8OAmF43+F
QsYS1+DZh/trQRgHx3doKIP0e8Iq5pn3TLHCmEevZhOusfh5JrNuAsZgNCectA97
mFFlZgarYTPPIo9PZ2NAgq8iiBiJFh5hS5U2GVZLdqT0JfK24bZuvqDBhSF/4UcF
IuLz2S3RlctPdr6j3mA2pr4yeSImSx5CTmRenyywzwmtrv6Df33Vucql1f5QLmdv
uDbymUhbaaca3usiKHhWts1tAt2K/1olUH65pZ0cPA3QhSTSTW9kt+VL7DQMHShC
DIELaqrATG86JPraRvF2RrjVpbE03X4xmvZ7VeUtYZ8g4I8kXU+lOilo/Z34SfV4
+OPD35xOvfY1nL53VlMqFFd79cQQn56hH+UdJ76ZSVNaDYnGMtaGKTeQlLdYhols
beNIY4ZZYeu2A9/ao52SwUW3fXugLE/doc4jDdORqvgimrXp9+KVxH7HnrlrcoOa
HHhxO/J9xVDef82V0TfEAsv3pzFX9dqM2iKmOgSoCVSX8B0XgcKBvatKQQ5aXq0u
0VvrFrVihydFuVQ+7coB17Wk1XQeHtTP9hoyHdDXTSHYsTnpLi5brYmD2GdCXTDV
vH/4FlWV+Y38Pht6coUbDttgur4rOsbBgU/3n5R59gwrWeqdgmkzzfsPksDhmmDN
f5mdhFZThi5xxPWKS0Ds
=+5lh
-----END PGP SIGNATURE-----

From ynir@checkpoint.com  Sun Jul 28 00:48:22 2013
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB4DD21F90CC for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 00:48:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.535
X-Spam-Level: 
X-Spam-Status: No, score=-10.535 tagged_above=-999 required=5 tests=[AWL=0.064, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3RjztIqaHvhi for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 00:48:11 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 9C74921F9048 for <ietf@ietf.org>; Sun, 28 Jul 2013 00:48:10 -0700 (PDT)
Received: from IL-EX10.ad.checkpoint.com ([194.29.34.147]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r6S7luwB017424; Sun, 28 Jul 2013 10:48:04 +0300
X-CheckPoint: {51F4CCAC-0-1B221DC2-1FFFF}
Received: from DAG-EX10.ad.checkpoint.com ([169.254.3.90]) by IL-EX10.ad.checkpoint.com ([169.254.2.105]) with mapi id 14.02.0342.003; Sun, 28 Jul 2013 10:47:59 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Marc Petit-Huguenin <petithug@acm.org>
Subject: Re: Remote participants, newcomers,	and tutorials
Thread-Topic: Remote participants, newcomers,	and tutorials
Thread-Index: AQHOixfdPXU1KqTPEk6hOnTM7P7pUZl5SQWAgAABLQCAABXbgIAAGqsAgAAGLoCAAAQtAA==
Date: Sun, 28 Jul 2013 07:47:59 +0000
Message-ID: <48579069-8214-4B78-969E-9C96BEF0367F@checkpoint.com>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net> <2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net> <5EB533DC-E6EF-40E3-A225-F8F1E39A46DC@unina.it> <18690A2F-5439-4CCC-91F1-58CF67D8D704@piuha.net> <8BA59F96-A1DE-460F-9A22-F2CD4CE5F31C@emc.com> <51F44831.2030300@gmail.com> <m2haffxqya.wl%randy@psg.com> <51F49B4A.7020609@gmail.com> <E375D2AA-6CF7-4913-A6B3-D481825BF7F9@network-heretics.com> <C48A3EE7-DB53-428A-9C5F-95802B0383F1@checkpoint.com> <51F4C92D.4070308@acm.org>
In-Reply-To: <51F4C92D.4070308@acm.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.21.103]
x-kse-antivirus-interceptor-info: protection disabled
x-cpdlp: 112d7320ec7e714db2f97a301de88ea3c134cbec46
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1D7ECCCD5EB4484F9C4F733893766B61@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Keith Moore <moore@network-heretics.com>, IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jul 2013 07:48:23 -0000

On Jul 28, 2013, at 9:33 AM, Marc Petit-Huguenin <petithug@acm.org> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>=20
> On 07/28/2013 09:10 AM, Yoav Nir wrote:
>>=20
>> On Jul 28, 2013, at 7:35 AM, Keith Moore <moore@network-heretics.com>
>> wrote:
>>=20
>>>=20
>>> On Jul 28, 2013, at 6:17 AM, Melinda Shore wrote:
>>>=20
>>>> On 7/27/13 8:13 PM, Randy Bush wrote:
>>>>> yup.  i guess it is time for my quarterly suggestion to remove the=20
>>>>> projectors and screens.
>>>>=20
>>>> Then I guess it's time for my quarterly "I'd be good with that."
>>>=20
>>> As would I.
>>=20
>> Me too, as long as we get whiteboards or flip-charts in their stead.
>=20
> What about people at the back of the room who cannot see what you write o=
n the
> whiteboard or flip-charts? (at least slides can be downloaded on laptop/t=
ablet
> if too far from the projection screen)
>=20
> What about people following remotely?

There are some technological solutions, like electronic whiteboards, or cam=
eras pointed at whiteboards/flipboards. Frame rate makes no difference.

Work is done through conversation. If we use a presentation, the conversati=
on is scripted. I, the presenter, say stuff. You, the audience, can only re=
ply. When we collaborate to develop something at work, we hardly ever do it=
 with a presentation. Presentations work best for tutorial and for showing =
proposals.

> What about people who have difficulties understanding the speaker without=
 some
> sort of context?

With some speakers, context doesn't help. Slides help bad enunciation. They=
 usually don't help missing context.

> What about being able to understand the problem that will be discussed be=
fore
> the session, so to cut on the "thinking out loud" on the microphone?

That's what drafts are for.

> Do you have a presentation during IETF 87? (I already checked that Randy,
> Keith and Melinda do not).  I would be really interested to see how this =
could
> work.

I have three. I don't get a flip-chart, so I do have slide-sets. There is o=
ne 5-minute thing that I'm going to do with hand-waving and no slides, but =
otherwise, I'm doing things the way that people expect them to be.

Yoav


From petithug@acm.org  Sun Jul 28 01:14:04 2013
Return-Path: <petithug@acm.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E99921F9D4A for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 01:14:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bjfmT9ynU9Ee for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 01:14:03 -0700 (PDT)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id 16BFF21F9DA0 for <ietf@ietf.org>; Sun, 28 Jul 2013 01:14:02 -0700 (PDT)
Received: from [IPv6:2001:df8:0:64:ca0a:a9ff:fe2e:a4f6] (unknown [IPv6:2001:df8:0:64:ca0a:a9ff:fe2e:a4f6]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id B9AF020EF8; Sun, 28 Jul 2013 10:13:58 +0200 (CEST)
Message-ID: <51F4D2D0.1050806@acm.org>
Date: Sun, 28 Jul 2013 10:14:08 +0200
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130630 Icedove/17.0.7
MIME-Version: 1.0
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: Remote participants, newcomers,	and tutorials
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net> <2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net> <5EB533DC-E6EF-40E3-A225-F8F1E39A46DC@unina.it> <18690A2F-5439-4CCC-91F1-58CF67D8D704@piuha.net> <8BA59F96-A1DE-460F-9A22-F2CD4CE5F31C@emc.com> <51F44831.2030300@gmail.com> <m2haffxqya.wl%randy@psg.com> <51F49B4A.7020609@gmail.com> <E375D2AA-6CF7-4913-A6B3-D481825BF7F9@network-heretics.com> <C48A3EE7-DB53-428A-9C5F-95802B0383F1@checkpoint.com> <51F4C92D.4070308@acm.org> <48579069-8214-4B78-969E-9C96BEF0367F@checkpoint.com>
In-Reply-To: <48579069-8214-4B78-969E-9C96BEF0367F@checkpoint.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Keith Moore <moore@network-heretics.com>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jul 2013 08:14:04 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 07/28/2013 09:47 AM, Yoav Nir wrote:
> 
> On Jul 28, 2013, at 9:33 AM, Marc Petit-Huguenin <petithug@acm.org> wrote:
> 
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
>> 
>> On 07/28/2013 09:10 AM, Yoav Nir wrote:
>>> 
>>> On Jul 28, 2013, at 7:35 AM, Keith Moore <moore@network-heretics.com> 
>>> wrote:
>>> 
>>>> 
>>>> On Jul 28, 2013, at 6:17 AM, Melinda Shore wrote:
>>>> 
>>>>> On 7/27/13 8:13 PM, Randy Bush wrote:
>>>>>> yup.  i guess it is time for my quarterly suggestion to remove
>>>>>> the projectors and screens.
>>>>> 
>>>>> Then I guess it's time for my quarterly "I'd be good with that."
>>>> 
>>>> As would I.
>>> 
>>> Me too, as long as we get whiteboards or flip-charts in their stead.
>> 
>> What about people at the back of the room who cannot see what you write
>> on the whiteboard or flip-charts? (at least slides can be downloaded on 
>> laptop/tablet if too far from the projection screen)
>> 
>> What about people following remotely?
> 
> There are some technological solutions, like electronic whiteboards, or 
> cameras pointed at whiteboards/flipboards. Frame rate makes no difference.
> 
> Work is done through conversation. If we use a presentation, the
> conversation is scripted. I, the presenter, say stuff. You, the audience,
> can only reply. When we collaborate to develop something at work, we hardly
> ever do it with a presentation. Presentations work best for tutorial and
> for showing proposals.
> 
>> What about people who have difficulties understanding the speaker
>> without some sort of context?
> 
> With some speakers, context doesn't help. Slides help bad enunciation.
> They usually don't help missing context.
> 
>> What about being able to understand the problem that will be discussed 
>> before the session, so to cut on the "thinking out loud" on the 
>> microphone?
> 
> That's what drafts are for.
> 
>> Do you have a presentation during IETF 87? (I already checked that Randy,
>>  Keith and Melinda do not).  I would be really interested to see how
>> this could work.
> 
> I have three. I don't get a flip-chart, so I do have slide-sets. There is
> one 5-minute thing that I'm going to do with hand-waving and no slides,
> but otherwise, I'm doing things the way that people expect them to be.

I can not find your presentations in the agendas.  Please tell me when they
are and I'll rent a flip-chart.

Thanks.

- -- 
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: http://blog.marc.petit-huguenin.org
Profile: http://www.linkedin.com/in/petithug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIbBAEBCAAGBQJR9NLNAAoJECnERZXWan7ELxgP+OsC2yZo717ZU0qQpP0FWl0e
W1/PsAgFO3vShPlHy5VXWASovdagJB2fSgRonY6HGYDdTlRy4KF5p+wYs9mopweJ
gDAO2q8DRe7CIQyhCgts6z93S3t3p1GWFU9wf5ajQWaOqK9PLwqnpcdILorP+zyt
pJ09wQNabV1vhDB8cLtBmkzbZMldqIqmYbY1HFJ2s79weggmVEqW9XFkN4Xhmkl6
P261QGXNgrFlc+ayWAjyal3qKGwTZX7VLZ6JUwIjRYq5Bk0kpf7WubAEMp5N+JBS
ocOwlPHG/zZeUUxsTDlZ0l3QnMWrc0ygc7n+I8T3DWlLbDJP8sofj39YXquifZG3
T4drnQlfuu0sTXUTsgx9HbGmj89u7g127vRx5mnjbhEpnsCjpSJH9G6Hnc7zFUTv
VGI6u2oi9Ym5M+KfxWQmjR8GltVCqcF/6EvxuIxAN/hEosK5vwFBvC1hKtYkOOkl
usZZKj4ICcRuSxM8KNZtjTX2X6lZATCSbjgCx4fjw+Zv79sgo7naRTU3A63xqHMl
6nnRGcjoEP69YGfYBR3lxRZM85QCpU42820FdhrMr4YY2MeOxsFKR2SFIEPeMpGl
Lwbirh7rOZthMXWW69AmdJ5Z2IlL5AY0kbZw5soV4glNrv4bWRHIn5D4am9u8FHc
EPL6kPP4WOUn5eAHkwE=
=lrvp
-----END PGP SIGNATURE-----

From Ted.Lemon@nominum.com  Sun Jul 28 01:25:31 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5090021F9D98 for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 01:25:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.299
X-Spam-Level: 
X-Spam-Status: No, score=-106.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_22=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9QYHaOA7Xxhq for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 01:25:13 -0700 (PDT)
Received: from exprod7og113.obsmtp.com (exprod7og113.obsmtp.com [64.18.2.179]) by ietfa.amsl.com (Postfix) with ESMTP id 4A31F21F9D67 for <ietf@ietf.org>; Sun, 28 Jul 2013 01:25:11 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob113.postini.com ([64.18.6.12]) with SMTP ID DSNKUfTVZnAWnuI3VVFWZL21mY/2PZ3Gqoms@postini.com; Sun, 28 Jul 2013 01:25:11 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 0467F1B825D for <ietf@ietf.org>; Sun, 28 Jul 2013 01:25:10 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id F25E119006B; Sun, 28 Jul 2013 01:25:09 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Sun, 28 Jul 2013 01:25:09 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Randy Bush <randy@psg.com>
Subject: Re: Remote participants, newcomers,	and tutorials (was: IETF87 Audio Streaming Info)
Thread-Topic: Remote participants, newcomers,	and tutorials (was: IETF87 Audio Streaming Info)
Thread-Index: AQHOixHEiTW24f+7jUSiO0ADTam/WJl58B0AgABHCYA=
Date: Sun, 28 Jul 2013 08:25:09 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775232119@mbx-01.win.nominum.com>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net> <2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net> <5EB533DC-E6EF-40E3-A225-F8F1E39A46DC@unina.it> <18690A2F-5439-4CCC-91F1-58CF67D8D704@piuha.net> <8BA59F96-A1DE-460F-9A22-F2CD4CE5F31C@emc.com> <m2iozvxr1t.wl%randy@psg.com>
In-Reply-To: <m2iozvxr1t.wl%randy@psg.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <344CF2129C7AC947AF59E7EA7847C0E5@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jul 2013 08:25:32 -0000

On Jul 28, 2013, at 6:10 AM, Randy Bush <randy@psg.com> wrote:
> putting up yuotube/vimeo tutorials on the wg's technical space would be
> a good thing for folk with spare time to do.  i am sure we could arrange
> pointer space on the wg's web page.

Effective video presentations are _hard_.   Otherwise they're TL;DW.   So I=
'd definitely be in favor of tight, effective video presentations on a yout=
ube stream or something, but would discourage random posting of videos that=
 aren't going to be carefully refined for effectiveness.   My concern is th=
at we may see many more of the latter than the former if we go down this pa=
th.


From ynir@checkpoint.com  Sun Jul 28 01:26:35 2013
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6413921F9DD5 for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 01:26:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.543
X-Spam-Level: 
X-Spam-Status: No, score=-10.543 tagged_above=-999 required=5 tests=[AWL=0.056, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ovJLQK0arkhL for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 01:26:21 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 3CAB521F9DB2 for <ietf@ietf.org>; Sun, 28 Jul 2013 01:25:48 -0700 (PDT)
Received: from IL-EX10.ad.checkpoint.com ([194.29.34.147]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r6S8PhTl031538; Sun, 28 Jul 2013 11:25:43 +0300
X-CheckPoint: {51F4D587-2-1B221DC2-1FFFF}
Received: from DAG-EX10.ad.checkpoint.com ([169.254.3.90]) by IL-EX10.ad.checkpoint.com ([169.254.2.105]) with mapi id 14.02.0342.003; Sun, 28 Jul 2013 11:25:43 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Marc Petit-Huguenin <petithug@acm.org>
Subject: Re: Remote participants, newcomers,	and tutorials
Thread-Topic: Remote participants, newcomers,	and tutorials
Thread-Index: AQHOixfdPXU1KqTPEk6hOnTM7P7pUZl5SQWAgAABLQCAABXbgIAAGqsAgAAGLoCAAAQtAIAAB1AAgAADOoA=
Date: Sun, 28 Jul 2013 08:25:42 +0000
Message-ID: <8E3123B6-3FE2-4642-97F9-0435E52D6EEE@checkpoint.com>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net> <2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net> <5EB533DC-E6EF-40E3-A225-F8F1E39A46DC@unina.it> <18690A2F-5439-4CCC-91F1-58CF67D8D704@piuha.net> <8BA59F96-A1DE-460F-9A22-F2CD4CE5F31C@emc.com> <51F44831.2030300@gmail.com> <m2haffxqya.wl%randy@psg.com> <51F49B4A.7020609@gmail.com> <E375D2AA-6CF7-4913-A6B3-D481825BF7F9@network-heretics.com> <C48A3EE7-DB53-428A-9C5F-95802B0383F1@checkpoint.com> <51F4C92D.4070308@acm.org> <48579069-8214-4B78-969E-9C96BEF0367F@checkpoint.com> <51F4D2D0.1050806@acm.org>
In-Reply-To: <51F4D2D0.1050806@acm.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.21.103]
x-kse-antivirus-interceptor-info: protection disabled
x-cpdlp: 11706454e4d2dd41b9c9ba59c8981d4dcc512ecb1c
Content-Type: text/plain; charset="us-ascii"
Content-ID: <9EB93264B6C9734F867E8168BE85B559@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: ietf Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jul 2013 08:26:37 -0000

On Jul 28, 2013, at 10:14 AM, Marc Petit-Huguenin <petithug@acm.org> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>=20
> On 07/28/2013 09:47 AM, Yoav Nir wrote:
>>=20
>> On Jul 28, 2013, at 9:33 AM, Marc Petit-Huguenin <petithug@acm.org> wrot=
e:
>>=20
>>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
>>>=20
>>> On 07/28/2013 09:10 AM, Yoav Nir wrote:
>>>>=20
>>>> On Jul 28, 2013, at 7:35 AM, Keith Moore <moore@network-heretics.com>=
=20
>>>> wrote:
>>>>=20
>>>>>=20
>>>>> On Jul 28, 2013, at 6:17 AM, Melinda Shore wrote:
>>>>>=20
>>>>>> On 7/27/13 8:13 PM, Randy Bush wrote:
>>>>>>> yup.  i guess it is time for my quarterly suggestion to remove
>>>>>>> the projectors and screens.
>>>>>>=20
>>>>>> Then I guess it's time for my quarterly "I'd be good with that."
>>>>>=20
>>>>> As would I.
>>>>=20
>>>> Me too, as long as we get whiteboards or flip-charts in their stead.
>>>=20
>>> What about people at the back of the room who cannot see what you write
>>> on the whiteboard or flip-charts? (at least slides can be downloaded on=
=20
>>> laptop/tablet if too far from the projection screen)
>>>=20
>>> What about people following remotely?
>>=20
>> There are some technological solutions, like electronic whiteboards, or=
=20
>> cameras pointed at whiteboards/flipboards. Frame rate makes no differenc=
e.
>>=20
>> Work is done through conversation. If we use a presentation, the
>> conversation is scripted. I, the presenter, say stuff. You, the audience=
,
>> can only reply. When we collaborate to develop something at work, we har=
dly
>> ever do it with a presentation. Presentations work best for tutorial and
>> for showing proposals.
>>=20
>>> What about people who have difficulties understanding the speaker
>>> without some sort of context?
>>=20
>> With some speakers, context doesn't help. Slides help bad enunciation.
>> They usually don't help missing context.
>>=20
>>> What about being able to understand the problem that will be discussed=
=20
>>> before the session, so to cut on the "thinking out loud" on the=20
>>> microphone?
>>=20
>> That's what drafts are for.
>>=20
>>> Do you have a presentation during IETF 87? (I already checked that Rand=
y,
>>> Keith and Melinda do not).  I would be really interested to see how
>>> this could work.
>>=20
>> I have three. I don't get a flip-chart, so I do have slide-sets. There i=
s
>> one 5-minute thing that I'm going to do with hand-waving and no slides,
>> but otherwise, I'm doing things the way that people expect them to be.
>=20
> I can not find your presentations in the agendas.  Please tell me when th=
ey
> are and I'll rent a flip-chart.

There's one in IPsec.

The other two are chairs slides in httpauth and websec. The former are not =
yet up.


From sm@resistor.net  Sun Jul 28 01:31:19 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAF0C21F9D93 for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 01:31:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.508
X-Spam-Level: 
X-Spam-Status: No, score=-102.508 tagged_above=-999 required=5 tests=[AWL=0.091, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zjgs0fgRwMm5 for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 01:31:15 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id AB7FE21F9684 for <ietf@ietf.org>; Sun, 28 Jul 2013 01:31:12 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r6S8Uxlt004050; Sun, 28 Jul 2013 01:31:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1375000266; bh=YNVkt1fFBevvNdsLnRL1CamXS67j9RZApjxqpwd6wGQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=c02Z5DDhryjxfaosCqKW0CijbbOnaG37WeeEjTTYBXsvtzI7e4MbBcYR+EFkV72w1 JJYRppYeO987G/GDcw7oLclUPerg9KwwuyKUE3ax29O/MtcSS+BDjcJxAIgEX7136r uQyyWdLYb1p75kGJ2NBploe6n9xe/SAR1Ay8+5do=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1375000266; i=@resistor.net; bh=YNVkt1fFBevvNdsLnRL1CamXS67j9RZApjxqpwd6wGQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=4zhURvaEHcvoU5TeByyk/yVkoGO7tkxQ2xZjvsLawWFNTsDguA40b5IQ9qhz18hqS /Exm6qaTnV8BLvCpl/kQG+qkHzuOEeU6/kLbKLhP2Pa5uiW0PQrkdTrBGDhhWxHjBw Fsc/ZnS6NTiONUMELtApUGLekDt+4Nz6I0hBRtGM=
Message-Id: <6.2.5.6.2.20130727232312.0b9c81d8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 28 Jul 2013 01:17:50 -0700
To: Aaron Yi DING <yding@cs.helsinki.fi>, Marc Petit-Huguenin <petithug@acm.org>
From: SM <sm@resistor.net>
Subject: Re: Remote participants, newcomers,	and tutorials
In-Reply-To: <51F45D55.4040709@cs.helsinki.fi>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net> <2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net> <5EB533DC-E6EF-40E3-A225-F8F1E39A46DC@unina.it> <18690A2F-5439-4CCC-91F1-58CF67D8D704@piuha.net> <8BA59F96-A1DE-460F-9A22-F2CD4CE5F31C@emc.com> <51F44831.2030300@gmail.com> <51F45D55.4040709@cs.helsinki.fi>
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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jul 2013 08:31:19 -0000

As an off-topic note, thanks to Alexa, Alexey, Jari, Lorenzo and the 
Meetecho team.

At 16:52 27-07-2013, Aaron Yi DING wrote:
>What do you mean by conference? too much information inferred in 
>your term that may confuse others on the list.  Will appreciate, if 
>you can share bit more on it, behind the single term "conference" 
>that you particularly don't like.

I took a quick look at some session agendas.  The common format is:

    - Name of draft

    - Presenter

That looks like a conference to me.  There will be the usual 
Powerpoint presentations.  People can object to that on this mailing 
list but the fact is that these presentations will happen.

>PS: things evolve, over the long term. it does not matter we like it 
>or not. that is how it is.

Yes.

At 00:33 28-07-2013, Marc Petit-Huguenin wrote:
>What about people who have difficulties understanding the speaker without some
>sort of context?

It helps to provide some context before discussing the issue.  I 
would not expect cross-area input if I do not provide 
context.  Sometimes it is difficult to understand the speaker.  The 
written form, for example slides, can help.

>What about being able to understand the problem that will be discussed before
>the session, so to cut on the "thinking out loud" on the microphone?

That is where the agenda can help.  The name of the draft does not 
tell me about the issues that will be discussed.

Regards,
-sm 


From d3e3e3@gmail.com  Sun Jul 28 01:38:35 2013
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40CE021F9D02 for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 01:38:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9T6v9dOQBw3O for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 01:38:34 -0700 (PDT)
Received: from mail-ob0-x22e.google.com (mail-ob0-x22e.google.com [IPv6:2607:f8b0:4003:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 56F8621F8C93 for <ietf@ietf.org>; Sun, 28 Jul 2013 01:38:27 -0700 (PDT)
Received: by mail-ob0-f174.google.com with SMTP id wd6so4057520obb.19 for <ietf@ietf.org>; Sun, 28 Jul 2013 01:38:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=5oshj4iod8Wv9r18j9KQEkqY/w3zstaEdpeF4OE0G+4=; b=g2aHSZb6ODBGkd4djFYW2hTxH6zYje745ZflkAtjitkYA24Zfsp8s37+mNOxVaaArt ZLEuc2DMOtJQFwPUSTvUR88L+Fj3Bvb6YNmfgiYc0oBhk0xdK54eYgVFH4ipbS558UKk cQgpelV6SSxJRslBAhZHA6vc+rKEWbRS+JHEYEz7ADW6sZlb4xjyXgOgkrsSvHJ+ljeL 8SHQ6vqSLwj6X60uLInQGcnExuGkoFd4LsLDcY5Jm4wHtrWIw8q7AoyduVfd0pqtM0xR U11hgbu2Qt+9fHJTRMIsHX/ZUvo53hnyuySnTYLqGXbT/cv5+lqW+2WtVlnaV9M+LMPT mg3g==
X-Received: by 10.182.72.137 with SMTP id d9mr47524281obv.99.1375000706906; Sun, 28 Jul 2013 01:38:26 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.131.7 with HTTP; Sun, 28 Jul 2013 01:38:05 -0700 (PDT)
In-Reply-To: <CAMm+LwjzH4bVU_kBSnVtTbcHrkWuAFkTsn2CWm3osAA670aFjA@mail.gmail.com>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net> <2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net> <5EB533DC-E6EF-40E3-A225-F8F1E39A46DC@unina.it> <18690A2F-5439-4CCC-91F1-58CF67D8D704@piuha.net> <8BA59F96-A1DE-460F-9A22-F2CD4CE5F31C@emc.com> <51F44831.2030300@gmail.com> <CAMm+LwjzH4bVU_kBSnVtTbcHrkWuAFkTsn2CWm3osAA670aFjA@mail.gmail.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Sun, 28 Jul 2013 04:38:05 -0400
Message-ID: <CAF4+nEGBpDkTF0F_LkLte_p8Y+Vig_X1-_e7_69XAC6wxRr5ZA@mail.gmail.com>
Subject: Re: Remote participants, newcomers, and tutorials
To: Phillip Hallam-Baker <hallam@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jul 2013 08:38:35 -0000

nroff still works fine for me. It's already there in Mac OS X.

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


On Sat, Jul 27, 2013 at 9:28 PM, Phillip Hallam-Baker <hallam@gmail.com> wrote:
>
>
>
> On Sat, Jul 27, 2013 at 6:22 PM, Melinda Shore <melinda.shore@gmail.com>
> wrote:
>>
>> On 7/27/13 1:38 PM, Moriarty, Kathleen wrote:
>> > I think it would be really helpful/useful if working groups could
>> > provide short video overviews to help people understand the work.
>> > This includes newcomers and also interested observers, who may
>> > include implementers.  Can that be accommodated, maybe at a future
>> > meeting?  I am happy to help if I can.
>>
>> I'm sorry, but no, I am not comfortable with this.  If someone
>> wants to go off on their own and do something along these lines,
>> more power to them, but we have working group charters, we've
>> got framework documents, and presumably people can read.
>>
>> I would be very sorry to see IETF *working* meetings turned into
>> something closer to conferences, or to dumbing things down to
>> accommodate newcomers who I gather from discussion so far don't have
>> anything particular in mind.
>
>
> IETF meetings are trying to do two different things
>
> 1) Do work on working group documents and specifications
>
> 2) Foster understanding of work in other parts of the IETF and encourage
> cross-working group interactions.
>
>
> These are different objectives that require totally different approaches.
> The first is best met by small one or two day meetings of people who are
> concentrating on just that one spec. The second is best met by plenaries and
> session talks designed to explain work to people outside the group.
>
>
>
> As for tutorial sessions on tools for writing IDs... Isn't the need for such
> a session proof that the tools and/or the formats are broken?
>
> I got fed up with the hosted version of XML2RFC and found it impossible to
> get the code running on my machine (it requires very specific python package
> versions that would require me to down-version). Plus I find the XML2RFC
> format obnoxious. The original expectation in 1999 was that XML editors
> would soon be ubiquitous and good. Instead there are rather and they all
> suck.
>
> So I wrote my own. You can now write your RFC in HTML and the tool will
> convert it into IETF caveman format, formatted HTML and/or XML2RFC. I will
> be adding XML2RFC format sometime next week.
>
> The code has only been tested on Windows so far but it is in CLI and so the
> executable can run on any platform with a runtime (all of them). I want to
> test on other platforms and test submitting drafts before making a release.
>
> http://sourceforge.net/projects/html2rfc/?source=directory
>
>
> The reason for adding xml2rfc format is that some folk may want to use it
> just for the ability to manage references. Instead of having to mess about
> with sticking entities in the front and citations in the middle and
> references in the running text, just add a reference in the text, [~RFC822]
> for informative, [!RFC822] for normative and the tool will work it all out.
>
>
> --
> Website: http://hallambaker.com/

From fluffy@cisco.com  Sun Jul 28 01:43:41 2013
Return-Path: <fluffy@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFF1421F9C6E; Sun, 28 Jul 2013 01:43:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.249
X-Spam-Level: 
X-Spam-Status: No, score=-110.249 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wmM6MHzhBWOk; Sun, 28 Jul 2013 01:43:37 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id C74C321F9C6C; Sun, 28 Jul 2013 01:43:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1713; q=dns/txt; s=iport; t=1375001017; x=1376210617; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=8dO/6ph5SJm18PIqDuaYPOAulOn9nuB6mZhzHTec+t4=; b=XO5PkN1Ay9cNNXsVBzPeZxlPE1zkx0Wg2yfcmU9/5BAma7SsbefcGXi8 K/zQZvj6DWtT5ikbImKkLgpoHHQMdnIqYhSpJEHJnIle3E3zrvkX/eeA1 Gd35s1L428FCgju0OBQQXTJRq0AJK3utmfN6/o2Df0iIzNaqF0/Nt+BrA 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhcFAFfZ9FGtJXG8/2dsb2JhbABagwY1UL1SgRcWdIIkAQEBAwEBAQE3NAsFCwIBCBgKFAULJwslAgQOBQiIAgYMt10EjkmBAQIxB4MWbwOpK4FbgTmBaUE
X-IronPort-AV: E=Sophos;i="4.89,763,1367971200"; d="scan'208";a="240416385"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-2.cisco.com with ESMTP; 28 Jul 2013 08:43:36 +0000
Received: from xhc-aln-x05.cisco.com (xhc-aln-x05.cisco.com [173.36.12.79]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id r6S8haUY003905 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 28 Jul 2013 08:43:36 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.29]) by xhc-aln-x05.cisco.com ([173.36.12.79]) with mapi id 14.02.0318.004; Sun, 28 Jul 2013 03:43:36 -0500
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: "Timothy B. Terriberry" <tterribe@xiph.org>
Subject: Re: [payload] Last Call: <draft-ietf-payload-vp8-08.txt> (RTP Payload Format for	VP8 Video) to Proposed Standard
Thread-Topic: [payload] Last Call: <draft-ietf-payload-vp8-08.txt> (RTP Payload Format for	VP8 Video) to Proposed Standard
Thread-Index: AQHOi26MMJs9rmga5UWYQED6+9xbFw==
Date: Sun, 28 Jul 2013 08:43:35 +0000
Message-ID: <C5E08FE080ACFD4DAE31E4BDBF944EB113617E32@xmb-aln-x02.cisco.com>
References: <20130604222555.32402.16024.idtracker@ietfa.amsl.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1135E7A62@xmb-aln-x02.cisco.com> <51EFB31A.3010506@xiph.org>
In-Reply-To: <51EFB31A.3010506@xiph.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.61.97.124]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <99BA1A193C12AB47B2EAACB4F53C79BE@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>, "payload@ietf.org" <payload@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jul 2013 08:43:42 -0000

So do you expect your implementations on devices with hardware acceleration=
 to have any limits on resolution of images they can decode?  I can't imagi=
ne how I could implement the frame buffers in VP8 in VLSI without having an=
 upper limit on both the width and height of the image. How do you deal wit=
h that?

I don't know if you ever got the Google VHDL code for VP8 but I have never =
got it so I don't know what it does but if you do, that would be great.=20


On Jul 24, 2013, at 12:57 PM, Timothy B. Terriberry <tterribe@xiph.org> wro=
te:

> Cullen Jennings (fluffy) wrote:
>> There is one thing that as far as I can tell that all the implementors a=
gree on. None of the implications control the resolution using
>>=20
>>   m=3Dvideo 62537 RTP/SAVPF 96
>>   a=3Drtpmap:96 VP8/90000
>>   a=3Dfmtp:96 max-fr=3D30;max-fs=3D3600
>>=20
>> What resolution do you think "max-fs=3D3600" is? I have no idea. It is n=
ot possible to implement so it is not surprising no one is doing  it. Howev=
er, this draft-ietf-payload-vp8 draft says the resolution is specified usin=
g the max-fs and max-fr.
>=20
> I can't speak for other implementations, but here at Mozilla, our interpr=
etation of RFC 6236 was that the values specified in imageattr can be compl=
etely ignored by either side, if they so choose. That leaves max-fs and max=
-fr as the only mechanism to indicate a resource constraint that cannot be =
ignored, and we plan to use it as such.
>=20
> See <https://bugzilla.mozilla.org/show_bug.cgi?id=3D881935> for details.
> _______________________________________________
> payload mailing list
> payload@ietf.org
> https://www.ietf.org/mailman/listinfo/payload


From ad707@hermes.cam.ac.uk  Sun Jul 28 02:18:54 2013
Return-Path: <ad707@hermes.cam.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05EB821F9C6E for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 02:18:54 -0700 (PDT)
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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k6D6wwZONy0G for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 02:18:53 -0700 (PDT)
Received: from ppsw-33.csi.cam.ac.uk (ppsw-33.csi.cam.ac.uk [IPv6:2001:630:212:8::e:f33]) by ietfa.amsl.com (Postfix) with ESMTP id 534CE21F9D1E for <ietf@ietf.org>; Sun, 28 Jul 2013 02:18:52 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-2.csi.cam.ac.uk ([131.111.8.54]:56059) by ppsw-33.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:25) with esmtpa (EXTERNAL:ad707) id 1V3N7p-0007PB-gQ (Exim 4.80_167-5a66dd3) (return-path <ad707@hermes.cam.ac.uk>); Sun, 28 Jul 2013 10:18:49 +0100
Received: from prayer by hermes-2.csi.cam.ac.uk (hermes.cam.ac.uk) with local (PRAYER:ad707) id 1V3N7p-0001Ua-2P (Exim 4.72) (return-path <ad707@hermes.cam.ac.uk>); Sun, 28 Jul 2013 10:18:49 +0100
Received: from [131.111.218.40] by webmail.hermes.cam.ac.uk with HTTP (Prayer-1.3.5); 28 Jul 2013 10:18:49 +0100
Date: 28 Jul 2013 10:18:49 +0100
From: Aaron Yi DING <Aaron.Ding@cl.cam.ac.uk>
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: Remote participants, newcomers,	and tutorials
Message-ID: <Prayer.1.3.5.1307281018490.1884@hermes-2.csi.cam.ac.uk>
X-Mailer: Prayer v1.3.5
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset=ISO-8859-1
Sender: Aaron Yi DING <ad707@hermes.cam.ac.uk>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jul 2013 09:26:04 -0000

On 28/07/13 01:27, Melinda Shore wrote:
> On 7/27/13 3:52 PM, Aaron Yi DING wrote:
>> What do you mean by conference? too much information inferred in your
>> term that may confuse others on the list.  Will appreciate, if you can
>> share bit more on it, behind the single term "conference" that you
>> particularly don't like.
>
> I love conferences but I'd hate to see IETF meetings turned into
> them.  By "conference" I mean something in which people give papers
> (or other talks) and most of the participants have an audience
> role.  IETF meeting participation should be active.  It is almost
> always the case, of course, that someone attending a meeting will
> sit in on working groups in which they're not active, but it
> should be unusual for someone who has no particular work in the
> IETF and who's active in no working groups and active on no mailing
> lists to come to a meeting.  IETF meetings are places to get work
> done.
>
>> I agree with you that changing the working culture in WG meetings can be
>> bad, and we shall not go out of the ways to accommodate anything under
>> the name of "diversity".
>
> I actually do think we should go out of our way to accommodate
> and encourage diversity, but again, that's in the interest of
> getting work done (and getting our work correct).


+1. 

A recent observation is roughly half of attendants are active in WG 
meeting, while the other half is more or less audience since they are 
interested in the topics. of course the ratio can vary depending on the WG 
area.


> But back to
> the original question of how to bring newcomers in through
> remote participation - I would start with the assumption that
> they'd be participating, remotely or otherwise, because they
> have some networking problem (and possibly solution) that needs
> standardization.  I'd also assume that they've done a basic
> literature search, etc.
>
> I wonder if it would be worthwhile to put together some material
> (video or otherwise) that would help people decide whether or not
> their problem belongs in the IETF.
>


Defining a proper boundary is hard, but it is helpful.

Cheers,
Aaron


> Melinda
>

From hallam@gmail.com  Sun Jul 28 04:02:08 2013
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03C2421F9DC7 for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 04:02:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.391
X-Spam-Level: 
X-Spam-Status: No, score=-2.391 tagged_above=-999 required=5 tests=[AWL=0.208,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gCRJATXdoxLf for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 04:02:07 -0700 (PDT)
Received: from mail-wg0-x22a.google.com (mail-wg0-x22a.google.com [IPv6:2a00:1450:400c:c00::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 0A44821F9D7C for <ietf@ietf.org>; Sun, 28 Jul 2013 04:02:06 -0700 (PDT)
Received: by mail-wg0-f42.google.com with SMTP id j13so1983492wgh.5 for <ietf@ietf.org>; Sun, 28 Jul 2013 04:02:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=kmnlLVMh2uGIWlthXe2NgKH1hpW6At1l44IrK8G8ZzY=; b=hbpBr1UjQQbIPDlHYEBaYo6DRoAmZEGFFjrXmJ/udyMuPTWFzFJrx+Mldo9AaVVMHO fXrD9fNjvqeZD+tXOrsQ1xBvBwqnTbivA35qzEgzUfrULh5WQF+XjiBGQNxvpK0ZIZ/a ECnXKn+NshaRwoYLjXsH9Vk/kKSIY7mlJ73ZieDUu/MB5ZP8Gl08Kdn5i5Yea9gzGhsi z7Scj+nt8ubEK9WKGIgIf1IiSVznAWH+/I9OiZk/F31SfmzDbEeKBCYLtY3G4rnJHP41 v1dJnv6IVRPD1FzZsFPyfF5s/EASNC9Z3rKg8DQbWAU3a5RymUKg6QSmMKtZbU6SYo+p aXsw==
MIME-Version: 1.0
X-Received: by 10.180.183.40 with SMTP id ej8mr4048361wic.37.1375009326144; Sun, 28 Jul 2013 04:02:06 -0700 (PDT)
Received: by 10.194.6.65 with HTTP; Sun, 28 Jul 2013 04:02:05 -0700 (PDT)
In-Reply-To: <CAF4+nEGBpDkTF0F_LkLte_p8Y+Vig_X1-_e7_69XAC6wxRr5ZA@mail.gmail.com>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net> <2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net> <5EB533DC-E6EF-40E3-A225-F8F1E39A46DC@unina.it> <18690A2F-5439-4CCC-91F1-58CF67D8D704@piuha.net> <8BA59F96-A1DE-460F-9A22-F2CD4CE5F31C@emc.com> <51F44831.2030300@gmail.com> <CAMm+LwjzH4bVU_kBSnVtTbcHrkWuAFkTsn2CWm3osAA670aFjA@mail.gmail.com> <CAF4+nEGBpDkTF0F_LkLte_p8Y+Vig_X1-_e7_69XAC6wxRr5ZA@mail.gmail.com>
Date: Sun, 28 Jul 2013 07:02:05 -0400
Message-ID: <CAMm+LwjjsYQP86-jwd74ytakN9o=vPTHrSHLLny58aA+MAryrg@mail.gmail.com>
Subject: Re: Remote participants, newcomers, and tutorials
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c2297a72a33004e2904e7d
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jul 2013 11:02:08 -0000

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

On Sun, Jul 28, 2013 at 4:38 AM, Donald Eastlake <d3e3e3@gmail.com> wrote:

> nroff still works fine for me. It's already there in Mac OS X.
>
>
Only the topic of the conversation is how to get more people involved in
IETF, not how to make them run away screaming and crying.



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

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

<div dir=3D"ltr">On Sun, Jul 28, 2013 at 4:38 AM, Donald Eastlake <span dir=
=3D"ltr">&lt;<a href=3D"mailto:d3e3e3@gmail.com" target=3D"_blank">d3e3e3@g=
mail.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">nroff still works fine for me. It&#39;s alre=
ady there in Mac OS X.<br>
<br></blockquote><div><br></div><div>Only the topic of the conversation is =
how to get more people involved in IETF, not how to make them run away scre=
aming and crying.</div><div><br></div><div>=A0<br></div></div><div><br></di=
v>
-- <br>Website: <a href=3D"http://hallambaker.com/">http://hallambaker.com/=
</a><br>
</div></div>

--001a11c2297a72a33004e2904e7d--

From arturo.servin@gmail.com  Sun Jul 28 05:47:32 2013
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DEAE21F9D2F for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 05:47:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Eb+9d5+H9MQT for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 05:47:31 -0700 (PDT)
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 C085721F9D21 for <ietf@ietf.org>; Sun, 28 Jul 2013 05:47:31 -0700 (PDT)
Received: by mail-pb0-f51.google.com with SMTP id um15so3638402pbc.38 for <ietf@ietf.org>; Sun, 28 Jul 2013 05:47:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=U9xurs2MjRE80Q2UTz2W/k+n7nTqLkHDqHVHsfTJHW0=; b=T/wWQMelZJ0cOVkeTGK8CV7zjN2qi0GKn9f583dwGF96xQcQpoftAulMBwXkUeiI/q 33rk87sF+1HaEnUFzfvPZPch2bdPrWrVm1Bg15yJGb4+98ep0EvWdO5H6k6Twcbvp5fF lr8yuiTyzSLYNSj6vRUAyiFA+I5V3eaBJr+6v0PUgSFiXPglQLQHFmiYVu8FaLxWIM4r AApBVlaLTLd7lUjaETOKHiBzYbndWcjINRO/0x3fQUMrrA6BXjOr9r2t5nPdb5eNZSL3 uiYDp4GzER8db+UMOQgRzDum7ku7Lgit6ZGQV8oFqoYhSkggaCuZC48V/mBsrDKroz53 aU3A==
X-Received: by 10.68.203.137 with SMTP id kq9mr62410605pbc.190.1375015651493;  Sun, 28 Jul 2013 05:47:31 -0700 (PDT)
Received: from dhcp-4263.meeting.ietf.org ([2001:df8:0:64:f1a3:1f68:28ac:2139]) by mx.google.com with ESMTPSA id tr10sm71083064pbc.22.2013.07.28.05.47.28 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 28 Jul 2013 05:47:29 -0700 (PDT)
Message-ID: <51F512E3.7070801@gmail.com>
Date: Sun, 28 Jul 2013 14:47:31 +0200
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Remote participants, newcomers, and tutorials
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com>	<E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com>	<6.2.5.6.2.20130726101746.0c8db480@resistor.net>	<2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net> <51F3BBB6.5030406@dcrocker.net> <51F42F7B.2060706@gmail.com>
In-Reply-To: <51F42F7B.2060706@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jul 2013 12:47:32 -0000

	Even in context is rude. Even when doing it is because of practical
reasons and for the good use of the scarce meeting time, I think that is
one of the reasons why the IETF is so intimidating for newcomers.

Regards,
as

On 7/27/13 10:37 PM, Brian E Carpenter wrote:
>> > It's not wrong.
>> > 
>> > It's badly worded, possibly bordering on rudeness.  It certainly lacks
>> > context.  And it probably doesn't apply to BOFs.  But it's not wrong.
> It reads rudely when taken out of context. But try reading the whole
> paragraph in RFC 3184:
> 
>       IETF participants who attend Working Group meetings read the
>       relevant Internet-Drafts, RFCs, and e-mail archives beforehand, in
>       order to familiarize themselves with the technology under
>       discussion.  This may represent a challenge for newcomers, as e-
>       mail archives can be difficult to locate and search, and it may
>       not be easy to trace the history of longstanding Working Group
>       debates.  With that in mind, newcomers who attend Working Group
>       meetings are encouraged to observe and absorb whatever material
>       they can, but should not interfere with the ongoing process of the
>       group.  Working Group meetings run on a very limited time
>       schedule, and are not intended for the education of individuals.
>       The work of the group will continue on the mailing list, and many
>       questions would be better expressed on the list in the months that
>       follow.
> 
> Exactly. My experience back when I was a newcomer was that it was
> easy enough to ask beginner's questions after the meeting, and obviously
> wrong to do so during the session. This remains true years later, if I
> drop into a WG that I'm not familiar with.
> 
>     Brian

From arturo.servin@gmail.com  Sun Jul 28 05:56:37 2013
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB9B821F9CAD for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 05:56:37 -0700 (PDT)
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=[AWL=-0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 86FNCuohL9jk for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 05:56:36 -0700 (PDT)
Received: from mail-pa0-x233.google.com (mail-pa0-x233.google.com [IPv6:2607:f8b0:400e:c03::233]) by ietfa.amsl.com (Postfix) with ESMTP id 3F7BA21F9C4D for <ietf@ietf.org>; Sun, 28 Jul 2013 05:56:29 -0700 (PDT)
Received: by mail-pa0-f51.google.com with SMTP id lf11so4860609pab.38 for <ietf@ietf.org>; Sun, 28 Jul 2013 05:56:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=ZtLdoWFof6vv1FLxpGegEttv/QKXKDK35Wmakib5vg8=; b=m4RAkeGTD/guAzNX10bodLCyh6Mtdzdlg9If4ifirLuniXoe0Esgx67FZ002gaUciA tLnyuV8Ne4n4d9fTz4M0f8Znrt9BH6u11qMNAs1mnoaptrmQqMRw9GqXGSc2tUB1kyNJ l2T+cQIvDQBk++Kyfb36TP6EedniqMlXvDrMc8fXRqkHGu+N9AY5MKxn89PhWLSurNUk 6fUQxlr1nK4R5UhCRSAmE6a8MWpSYKQdXVj++5T56GOjQuO3HI5Doj2utTHl1WxEfwGL B/ynjoFEwTNZQEAcfMowCuEGwhSfDRC2grQqpI5fEwOLIR9UNXZjBi/9E5anSwXfL1Hu qmDg==
X-Received: by 10.68.58.97 with SMTP id p1mr63497769pbq.144.1375016188964; Sun, 28 Jul 2013 05:56:28 -0700 (PDT)
Received: from dhcp-4263.meeting.ietf.org (dhcp-4263.meeting.ietf.org. [130.129.66.99]) by mx.google.com with ESMTPSA id qv4sm71148525pbc.16.2013.07.28.05.56.26 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 28 Jul 2013 05:56:27 -0700 (PDT)
Message-ID: <51F514FE.8020700@gmail.com>
Date: Sun, 28 Jul 2013 14:56:30 +0200
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: IETF Disgust <ietf@ietf.org>
Subject: Re: Remote participants, newcomers,	and tutorials
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net> <2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net> <5EB533DC-E6EF-40E3-A225-F8F1E39A46DC@unina.it> <18690A2F-5439-4CCC-91F1-58CF67D8D704@piuha.net> <8BA59F96-A1DE-460F-9A22-F2CD4CE5F31C@emc.com> <51F44831.2030300@gmail.com> <m2haffxqya.wl%randy@psg.com>
In-Reply-To: <m2haffxqya.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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jul 2013 12:56:37 -0000

	I agree with Randy.

	Presentation material, documents, etc. should be available in advance
at least 1 or 2 weeks before the IETF (not 2 hours, not 2 days) and to
support the discussion (not to be presented). People in the meeting
should have read it (draft and slides) and be prepared to discuss the
draft, not to learn about it as we are doing now.

	F2F meetings should be about discussions, no presentations.

	We could try something like this:

A Simple Rule to Eliminate Useless Meetings

https://www.linkedin.com/today/post/article/20130701022638-22330283-a-simple-rule-to-eliminate-useless-meetings

	(I have never done it, but it seems interesting).

Regards,
as

On 7/28/13 6:13 AM, Randy Bush wrote:
>> I would be very sorry to see IETF *working* meetings turned into
>> something closer to conferences, or to dumbing things down to
>> accommodate newcomers who I gather from discussion so far don't have
>> anything particular in mind.
> 
> yup.  i guess it is time for my quarterly suggestion to remove the
> projectors and screens.
> 
> randy
> 

From hallam@gmail.com  Sun Jul 28 06:01:32 2013
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DE8E21F9C4C for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 06:01:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.432
X-Spam-Level: 
X-Spam-Status: No, score=-2.432 tagged_above=-999 required=5 tests=[AWL=0.167,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J6EhrQlYVDwC for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 06:01:31 -0700 (PDT)
Received: from mail-we0-x230.google.com (mail-we0-x230.google.com [IPv6:2a00:1450:400c:c03::230]) by ietfa.amsl.com (Postfix) with ESMTP id 3709821F9622 for <ietf@ietf.org>; Sun, 28 Jul 2013 06:01:30 -0700 (PDT)
Received: by mail-we0-f176.google.com with SMTP id q56so3106979wes.7 for <ietf@ietf.org>; Sun, 28 Jul 2013 06:01:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ytnBDgFyFB3Ghg6j8adp8NG3GB4+ZlUaU28yfpIQdD4=; b=ke63xsxMtRFixeTUn+iCveFWADV9CW+2bwjlxltFFC23uLYbqz35kqzP+Z4XL+mATo vBL1pWtpgTB55mAYLT6gPjA60VFoMXlTQkMBqR1Ycd0H7GEpAQM0jitmCYKjPZSFmemC BgMkFhFAlCgoDaPEM1JZTMJzwHhGDb4vgsMeDXVgz63+hDvDqX7bz23qBIdmBa9n5whg qvS+jPI/vYNQozl8fLDFk8Tf4oiSE596Fw7QZHZhIdzcRGjIbrTqT/xPANsOv37IO1sy xetmdHnkg5qbPYIo/FWnDqJm8/TgbPMhY+AOmUZe0+DmIv376AvtZXd2HzXaXRvGjnTJ fxnA==
MIME-Version: 1.0
X-Received: by 10.180.126.2 with SMTP id mu2mr4194371wib.63.1375016489363; Sun, 28 Jul 2013 06:01:29 -0700 (PDT)
Received: by 10.194.6.65 with HTTP; Sun, 28 Jul 2013 06:01:29 -0700 (PDT)
In-Reply-To: <51F514FE.8020700@gmail.com>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net> <2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net> <5EB533DC-E6EF-40E3-A225-F8F1E39A46DC@unina.it> <18690A2F-5439-4CCC-91F1-58CF67D8D704@piuha.net> <8BA59F96-A1DE-460F-9A22-F2CD4CE5F31C@emc.com> <51F44831.2030300@gmail.com> <m2haffxqya.wl%randy@psg.com> <51F514FE.8020700@gmail.com>
Date: Sun, 28 Jul 2013 09:01:29 -0400
Message-ID: <CAMm+Lwj2B_0+ViMzeWcoQ-vLQ5Cn=1h8sxGXSNpxgr2Usxzzeg@mail.gmail.com>
Subject: Re: Remote participants, newcomers, and tutorials
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Arturo Servin <arturo.servin@gmail.com>
Content-Type: multipart/alternative; boundary=e89a8f642dfc68aef904e291f961
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jul 2013 13:01:32 -0000

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

Why not put the presentations up on YouTube as podcasts. That way people
can watch them before starting off for the meeting.


On Sun, Jul 28, 2013 at 8:56 AM, Arturo Servin <arturo.servin@gmail.com>wrote:

>
>         I agree with Randy.
>
>         Presentation material, documents, etc. should be available in
> advance
> at least 1 or 2 weeks before the IETF (not 2 hours, not 2 days) and to
> support the discussion (not to be presented). People in the meeting
> should have read it (draft and slides) and be prepared to discuss the
> draft, not to learn about it as we are doing now.
>
>         F2F meetings should be about discussions, no presentations.
>
>         We could try something like this:
>
> A Simple Rule to Eliminate Useless Meetings
>
>
> https://www.linkedin.com/today/post/article/20130701022638-22330283-a-simple-rule-to-eliminate-useless-meetings
>
>         (I have never done it, but it seems interesting).
>
> Regards,
> as
>
> On 7/28/13 6:13 AM, Randy Bush wrote:
> >> I would be very sorry to see IETF *working* meetings turned into
> >> something closer to conferences, or to dumbing things down to
> >> accommodate newcomers who I gather from discussion so far don't have
> >> anything particular in mind.
> >
> > yup.  i guess it is time for my quarterly suggestion to remove the
> > projectors and screens.
> >
> > randy
> >
>



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

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

<div dir=3D"ltr">Why not put the presentations up on YouTube as podcasts. T=
hat way people can watch them before starting off for the meeting.</div><di=
v class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Sun, Jul 28, =
2013 at 8:56 AM, Arturo Servin <span dir=3D"ltr">&lt;<a href=3D"mailto:artu=
ro.servin@gmail.com" target=3D"_blank">arturo.servin@gmail.com</a>&gt;</spa=
n> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><br>
=A0 =A0 =A0 =A0 I agree with Randy.<br>
<br>
=A0 =A0 =A0 =A0 Presentation material, documents, etc. should be available =
in advance<br>
at least 1 or 2 weeks before the IETF (not 2 hours, not 2 days) and to<br>
support the discussion (not to be presented). People in the meeting<br>
should have read it (draft and slides) and be prepared to discuss the<br>
draft, not to learn about it as we are doing now.<br>
<br>
=A0 =A0 =A0 =A0 F2F meetings should be about discussions, no presentations.=
<br>
<br>
=A0 =A0 =A0 =A0 We could try something like this:<br>
<br>
A Simple Rule to Eliminate Useless Meetings<br>
<br>
<a href=3D"https://www.linkedin.com/today/post/article/20130701022638-22330=
283-a-simple-rule-to-eliminate-useless-meetings" target=3D"_blank">https://=
www.linkedin.com/today/post/article/20130701022638-22330283-a-simple-rule-t=
o-eliminate-useless-meetings</a><br>

<br>
=A0 =A0 =A0 =A0 (I have never done it, but it seems interesting).<br>
<br>
Regards,<br>
as<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
On 7/28/13 6:13 AM, Randy Bush wrote:<br>
&gt;&gt; I would be very sorry to see IETF *working* meetings turned into<b=
r>
&gt;&gt; something closer to conferences, or to dumbing things down to<br>
&gt;&gt; accommodate newcomers who I gather from discussion so far don&#39;=
t have<br>
&gt;&gt; anything particular in mind.<br>
&gt;<br>
&gt; yup. =A0i guess it is time for my quarterly suggestion to remove the<b=
r>
&gt; projectors and screens.<br>
&gt;<br>
&gt; randy<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>

--e89a8f642dfc68aef904e291f961--

From arturo.servin@gmail.com  Sun Jul 28 06:02:16 2013
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCE0121F9622 for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 06:02:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MLQ8Jy1r7iw3 for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 06:02:16 -0700 (PDT)
Received: from mail-pd0-x229.google.com (mail-pd0-x229.google.com [IPv6:2607:f8b0:400e:c02::229]) by ietfa.amsl.com (Postfix) with ESMTP id 18BF221F9D96 for <ietf@ietf.org>; Sun, 28 Jul 2013 06:02:14 -0700 (PDT)
Received: by mail-pd0-f169.google.com with SMTP id y10so4521442pdj.14 for <ietf@ietf.org>; Sun, 28 Jul 2013 06:02:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=k4VNt3BN+sgd/VK77CUR/EMvyIWHizK3Qnrvmw/NukI=; b=h+NFCR2vug5vse92ICiAz8xGBB2MxZaKqvmcuzCtxmMfZL0Q0yyDOf/LDRl7JcK9ol POvUD+5yHo/lCLLCjP6vAQfZ4Rt8dIYwWDSm/LoUnL0vgTvlIasxEs1og4i4YMC7gRmc yi09+WB3+WHFTWv2ybLATYWqei/vXVOh2RGlt0oDEMk271szlaWy/bpG/3+tWG8F9/A1 A+GZdkk/TSd3FrKctYTBKzgj5Ul0uPn5pqxIbfaX/9u08t2ksZHBynqd+Kdq/Gl5el7k 0bOS51WdhDVHxFlsCwOOmldLSvZPei+Ni80HlZgylMUsJLd4WDjBSuWeeMkFfARWAv38 MyZQ==
X-Received: by 10.68.163.195 with SMTP id yk3mr61818104pbb.142.1375016534763;  Sun, 28 Jul 2013 06:02:14 -0700 (PDT)
Received: from dhcp-4263.meeting.ietf.org ([2001:df8:0:64:f1a3:1f68:28ac:2139]) by mx.google.com with ESMTPSA id 4sm71130443pbw.32.2013.07.28.06.02.12 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 28 Jul 2013 06:02:13 -0700 (PDT)
Message-ID: <51F51658.9060109@gmail.com>
Date: Sun, 28 Jul 2013 15:02:16 +0200
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Oh look! [Re: Remote participants, newcomers, and tutorials]
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <51F2DD2A.7040700@gmail.com> <51F2DE5F.1010708@gmail.com> <B2856A2101451CF971914EFA@JcK-HP8200.jck.com> <CADnDZ8_+Kjew8ZOjHdc1mN-kcnhG9NMUjSay3gLooHUAZNwLAQ@mail.gmail.com>
In-Reply-To: <CADnDZ8_+Kjew8ZOjHdc1mN-kcnhG9NMUjSay3gLooHUAZNwLAQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jul 2013 13:02:16 -0000

	Why during the F2F IETF meeting?

	It seems that is not a good way to use the time of an AD during the F2F
IETF meeting. I think is a good idea to provide people remote-access to
ADs, but doing it during the F2F IETF meeting does not look like a good
use of resources.

/as


On 7/27/13 9:14 PM, Abdussalam Baryun wrote:
> Booking a 2 minute remote speach at IETF-meetings from
> remote-community to an IETF AD or WG-Chair can be a new opportunity
> that IETF/IESG can think about to schedule in future.

From arturo.servin@gmail.com  Sun Jul 28 06:05:50 2013
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89F9221F9D12 for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 06:05:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DNvf2dUMuJl6 for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 06:05:50 -0700 (PDT)
Received: from mail-pa0-x236.google.com (mail-pa0-x236.google.com [IPv6:2607:f8b0:400e:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id 114F021F9D0E for <ietf@ietf.org>; Sun, 28 Jul 2013 06:05:50 -0700 (PDT)
Received: by mail-pa0-f54.google.com with SMTP id kx1so4614921pab.13 for <ietf@ietf.org>; Sun, 28 Jul 2013 06:05:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=oapFonedAjiwyH+zRgNG1FxCyLG9eJLoEmFYzaxMBwA=; b=cWGlnvhMndsiPahTFYjuxBS3+sB4PlyF7dv7qIfWiSYCzfHtaNjiuYNmKuR7Qy2P8E pdaUSSbEOzJGpDOU0LTT17ngbBlhIRhIdH1J9PZaJEQQWg8G3ybcKz618VmfdCnm8tFj d/Ok1hU+buPnS9R1IEUOlJTRtk2t0Ay2c0/mUsV70h1w2gLBiqtBuvcjwphCjr0UbjX/ HDmps096V5leXszWDjtWugXM9ZTgqOSKywdul4rXMbN+d1GkN08x4AeIIU4xx0MySOh9 QtnkioxiEPMCr6UswgPYVTqNqjKW7jaRaz+pD3gbAnCfjEhSfSCkK9/kJgK/au3prbAL 0EMQ==
X-Received: by 10.66.50.104 with SMTP id b8mr64687240pao.39.1375016749691; Sun, 28 Jul 2013 06:05:49 -0700 (PDT)
Received: from dhcp-4263.meeting.ietf.org ([2001:df8:0:64:f1a3:1f68:28ac:2139]) by mx.google.com with ESMTPSA id 7sm14884792paf.22.2013.07.28.06.05.47 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 28 Jul 2013 06:05:48 -0700 (PDT)
Message-ID: <51F5172E.9090307@gmail.com>
Date: Sun, 28 Jul 2013 15:05:50 +0200
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: Remote participants, newcomers, and tutorials
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net> <2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net> <5EB533DC-E6EF-40E3-A225-F8F1E39A46DC@unina.it> <18690A2F-5439-4CCC-91F1-58CF67D8D704@piuha.net> <8BA59F96-A1DE-460F-9A22-F2CD4CE5F31C@emc.com> <51F44831.2030300@gmail.com> <m2haffxqya.wl%randy@psg.com> <51F514FE.8020700@gmail.com> <CAMm+Lwj2B_0+ViMzeWcoQ-vLQ5Cn=1h8sxGXSNpxgr2Usxzzeg@mail.gmail.com>
In-Reply-To: <CAMm+Lwj2B_0+ViMzeWcoQ-vLQ5Cn=1h8sxGXSNpxgr2Usxzzeg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jul 2013 13:05:50 -0000

	That may work as well.

	It depends on the time that the presenters have to make the material
available.

	The important is to have discussion-material available in advance. It
could be a presentation or a video (I would personally prefer a
presentation because I can quickly scan it for important things)

Regards,
as

On 7/28/13 3:01 PM, Phillip Hallam-Baker wrote:
> Why not put the presentations up on YouTube as podcasts. That way people
> can watch them before starting off for the meeting.
> 
> 
> On Sun, Jul 28, 2013 at 8:56 AM, Arturo Servin <arturo.servin@gmail.com
> <mailto:arturo.servin@gmail.com>> wrote:
> 
> 
>             I agree with Randy.
> 
>             Presentation material, documents, etc. should be available
>     in advance
>     at least 1 or 2 weeks before the IETF (not 2 hours, not 2 days) and to
>     support the discussion (not to be presented). People in the meeting
>     should have read it (draft and slides) and be prepared to discuss the
>     draft, not to learn about it as we are doing now.
> 
>             F2F meetings should be about discussions, no presentations.
> 
>             We could try something like this:
> 
>     A Simple Rule to Eliminate Useless Meetings
> 
>     https://www.linkedin.com/today/post/article/20130701022638-22330283-a-simple-rule-to-eliminate-useless-meetings
> 
>             (I have never done it, but it seems interesting).
> 
>     Regards,
>     as
> 
>     On 7/28/13 6:13 AM, Randy Bush wrote:
>     >> I would be very sorry to see IETF *working* meetings turned into
>     >> something closer to conferences, or to dumbing things down to
>     >> accommodate newcomers who I gather from discussion so far don't have
>     >> anything particular in mind.
>     >
>     > yup.  i guess it is time for my quarterly suggestion to remove the
>     > projectors and screens.
>     >
>     > randy
>     >
> 
> 
> 
> 
> -- 
> Website: http://hallambaker.com/

From doug.mtview@gmail.com  Sun Jul 28 06:20:09 2013
Return-Path: <doug.mtview@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1977021F9CE3 for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 06:20:09 -0700 (PDT)
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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FQiU5dvj4sjw for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 06:20:07 -0700 (PDT)
Received: from mail-bk0-x231.google.com (mail-bk0-x231.google.com [IPv6:2a00:1450:4008:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id 9B09721F9C4E for <ietf@ietf.org>; Sun, 28 Jul 2013 06:20:07 -0700 (PDT)
Received: by mail-bk0-f49.google.com with SMTP id r7so1260308bkg.36 for <ietf@ietf.org>; Sun, 28 Jul 2013 06:20:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=FOV1AIzt2NpThK/ROyTdk4ap1k14KXJVyMBDwPI4it4=; b=xkzsuZAXSAmqgSqD+smPxMVAz+EB3gvHdFuCZrd5S3WXkq+WQClq8ARm6cVIlS2pO9 ghlP9xRPcQkp+UuFclIQwV/KTD4CNP07zzyZk0V2kPk/A15NQPRXV4d7SLc5cYO+e9Ta gkUNjLUpCoXdoqm96D3fP4ZghJaivfQGKQnVFrCurpN1/XWU9E/gkkU7BbhYPWNf7kdV JJZEdL+igfTtnQ8eC5X3M6a2pduI7GiDsY+p53TzoJNhh1KcaArWBtmITpWgqPlmeTng CEh4Z76rfW8Jlhzx90h04+SpKpnc7gUTfg9+QYbSW8qSVKnxVJg1U5iSsmdwwQq001Td GFPA==
X-Received: by 10.204.187.66 with SMTP id cv2mr3621729bkb.52.1375017606668; Sun, 28 Jul 2013 06:20:06 -0700 (PDT)
Received: from [10.54.243.138] ([88.128.80.7]) by mx.google.com with ESMTPSA id m6sm14518551bki.7.2013.07.28.06.20.05 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 28 Jul 2013 06:20:05 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Remote participants, newcomers, and tutorials
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <51F5172E.9090307@gmail.com>
Date: Sun, 28 Jul 2013 15:20:05 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <B6E1F079-777E-4BD1-BC43-9E1AF7C0B36B@gmail.com>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net> <2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net> <5EB533DC-E6EF-40E3-A225-F8F1E39A46DC@unina.it> <18690A2F-5439-4CCC-91F1-58CF67D8D704@piuha.net> <8BA59F96-A1DE-460F-9A22-F2CD4CE5F31C@emc.com> <51F44831.2030300@gmail.com> <m2haffxqya.wl%randy@psg.com> <51F514FE.8020700@gmail.com> <CAMm+Lwj2B_0+ViMzeWcoQ-vLQ5Cn=1h8sxGXSNpxgr2Usxzzeg@mail.gmail.com> <51F5172E.9090307@gmail.com>
To: Arturo Servin <arturo.servin@gmail.com>
X-Mailer: Apple Mail (2.1508)
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jul 2013 13:20:09 -0000

On Jul 28, 2013, at 3:05 PM, Arturo Servin <arturo.servin@gmail.com> =
wrote:

>=20
> 	That may work as well.
>=20
> 	It depends on the time that the presenters have to make the =
material
> available.
>=20
> 	The important is to have discussion-material available in =
advance. It
> could be a presentation or a video (I would personally prefer a
> presentation because I can quickly scan it for important things)

Dear Arturo,

Emphasis should be to ensure equal status for remote participants.  For =
reasonable remote participation, presentation material should be made =
available in advance. It seems reasonable to allow minor edits within a =
day or even hours before the meeting starts.

To do this, video and audio control should be centralized within the =
meeting room and virtualized in the cloud when necessary.  A dual core =
Atom processor should be all that is needed.  Rather than using an audio =
bridge with multiple simultaneous  audio and video feeds, a strategy =
should be developed that suits those in the meeting venue as as well as =
those who are remote.   For this, there should be a minor level of =
automation available to facilitate selection of individuals permitted to =
speak.  This control should not need to be done at the meeting venue, =
but in the cloud as well.

Regards,
Douglas Otis


From arturo.servin@gmail.com  Sun Jul 28 06:38:06 2013
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2BE021F8CB4 for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 06:38:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MS1+0a0PiIN6 for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 06:38:06 -0700 (PDT)
Received: from mail-pa0-x22e.google.com (mail-pa0-x22e.google.com [IPv6:2607:f8b0:400e:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 2D6E921F8B4E for <ietf@ietf.org>; Sun, 28 Jul 2013 06:38:06 -0700 (PDT)
Received: by mail-pa0-f46.google.com with SMTP id fa1so4914424pad.19 for <ietf@ietf.org>; Sun, 28 Jul 2013 06:38:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=X6bS+HIwCOHjhFCkQgK7ux1C4+Kw3nIns5/Vb3SPUio=; b=1D/ypB+rvDa/EBaoFLdWDmsKeCNWD2wxunequvAlmZGW+ZHZ6WZXkjzDIv3z9fGimR czS+VwJ/CJF9NhZ+MMmrMQGS5XbkQqU+YN0tYdHQGp3Zb0lbDPQgIXlBaDzyl7mW52Bh r2apPkF33o35AYdTB/EmjmmLNcfVyHlHWpmaL237dA5Mm/XLAjxXzC4FOA+Dhb88mefn r83DUUp5Awo/EdNTvjzRjM8wBak4QXZp2fU4mmrNiou4ZGMtfF9Hl11XShytk/qmKG6U yrrIKzY97Az6VoRN6xl6V1reyHjb49n6nRA6Q+FPAxKribBycNp2M1aBWunj4NITfMhk 3dug==
X-Received: by 10.68.76.34 with SMTP id h2mr63128240pbw.20.1375018685759; Sun, 28 Jul 2013 06:38:05 -0700 (PDT)
Received: from dhcp-4263.meeting.ietf.org ([2001:df8:0:64:f1a3:1f68:28ac:2139]) by mx.google.com with ESMTPSA id ss8sm15060710pab.6.2013.07.28.06.38.02 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 28 Jul 2013 06:38:04 -0700 (PDT)
Message-ID: <51F51EBF.4040905@gmail.com>
Date: Sun, 28 Jul 2013 15:38:07 +0200
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Douglas Otis <doug.mtview@gmail.com>
Subject: Re: Remote participants, newcomers, and tutorials
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net> <2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net> <5EB533DC-E6EF-40E3-A225-F8F1E39A46DC@unina.it> <18690A2F-5439-4CCC-91F1-58CF67D8D704@piuha.net> <8BA59F96-A1DE-460F-9A22-F2CD4CE5F31C@emc.com> <51F44831.2030300@gmail.com> <m2haffxqya.wl%randy@psg.com> <51F514FE.8020700@gmail.com> <CAMm+Lwj2B_0+ViMzeWcoQ-vLQ5Cn=1h8sxGXSNpxgr2Usxzzeg@mail.gmail.com> <51F5172E.9090307@gmail.com> <B6E1F079-777E-4BD1-BC43-9E1AF7C0B36B@gmail.com>
In-Reply-To: <B6E1F079-777E-4BD1-BC43-9E1AF7C0B36B@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jul 2013 13:38:06 -0000

Douglas,

    Totally agree that a requirement is that F2F and remote are equals.
I even believe that a presentation-less format (as the described) is
better for remote participants.

    About the minor changes, perhaps. Not very convinced but it could be.

    In the same line, what about to have the presentation-material
attached to the last htmlized version of the draft?

    In that way people going to a wg meeting (local or remote) knows
where to find the last version of the presentation and if this were
submited in the same way than drafts, then WG chairs would have less work.

Regards,
as


On 7/28/13 3:20 PM, Douglas Otis wrote:
> On Jul 28, 2013, at 3:05 PM, Arturo Servin <arturo.servin@gmail.com> wrote:
>
>> 	That may work as well.
>>
>> 	It depends on the time that the presenters have to make the material
>> available.
>>
>> 	The important is to have discussion-material available in advance. It
>> could be a presentation or a video (I would personally prefer a
>> presentation because I can quickly scan it for important things)
> Dear Arturo,
>
> Emphasis should be to ensure equal status for remote participants.  For reasonable remote participation, presentation material should be made available in advance. It seems reasonable to allow minor edits within a day or even hours before the meeting starts.
>
> To do this, video and audio control should be centralized within the meeting room and virtualized in the cloud when necessary.  A dual core Atom processor should be all that is needed.  Rather than using an audio bridge with multiple simultaneous  audio and video feeds, a strategy should be developed that suits those in the meeting venue as as well as those who are remote.   For this, there should be a minor level of automation available to facilitate selection of individuals permitted to speak.  This control should not need to be done at the meeting venue, but in the cloud as well.
>
> Regards,
> Douglas Otis
>


From Ted.Lemon@nominum.com  Sun Jul 28 07:10:47 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24B3E21F9C4A for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 07:10:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.576
X-Spam-Level: 
X-Spam-Status: No, score=-106.576 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IGdcAzDHP6Rg for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 07:10:36 -0700 (PDT)
Received: from exprod7og103.obsmtp.com (exprod7og103.obsmtp.com [64.18.2.159]) by ietfa.amsl.com (Postfix) with ESMTP id 156D021F9A94 for <ietf@ietf.org>; Sun, 28 Jul 2013 07:10:36 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob103.postini.com ([64.18.6.12]) with SMTP ID DSNKUfUmW7o2VXh35Unfp/RBgEiPyelbCopw@postini.com; Sun, 28 Jul 2013 07:10:36 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id BB2C01B8225 for <ietf@ietf.org>; Sun, 28 Jul 2013 07:10:35 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id B50F019006B; Sun, 28 Jul 2013 07:10:35 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Sun, 28 Jul 2013 07:10:35 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Arturo Servin <arturo.servin@gmail.com>
Subject: Re: Remote participants, newcomers, and tutorials
Thread-Topic: Remote participants, newcomers, and tutorials
Thread-Index: AQHOisQw/AXa1hutrUCOl9zEtf6zE5l5cfiAgAEPF4CAABc2gA==
Date: Sun, 28 Jul 2013 14:10:35 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775232B4B@mbx-01.win.nominum.com>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net> <2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net> <51F3BBB6.5030406@dcrocker.net> <51F42F7B.2060706@gmail.com> <51F512E3.7070801@gmail.com>
In-Reply-To: <51F512E3.7070801@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <77C092EC9004D645AB605D3A4F4B85F1@nominum.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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jul 2013 14:10:47 -0000

On Jul 28, 2013, at 2:47 PM, Arturo Servin <arturo.servin@gmail.com> wrote:
> 	Even in context is rude. Even when doing it is because of practical
> reasons and for the good use of the scarce meeting time, I think that is
> one of the reasons why the IETF is so intimidating for newcomers.

There's a careful line that has to be drawn between being welcoming and fai=
ling because we are spending too much time being welcoming.   No matter whe=
re it is drawn, someone will be unhappy.


From mir@ripe.net  Sun Jul 28 03:55:06 2013
Return-Path: <mir@ripe.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA39221F9DA1; Sun, 28 Jul 2013 03:55:05 -0700 (PDT)
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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 33owraLaRdk7; Sun, 28 Jul 2013 03:54:58 -0700 (PDT)
Received: from postgirl.ripe.net (postgirl.ipv6.ripe.net [IPv6:2001:67c:2e8:11::c100:1342]) by ietfa.amsl.com (Postfix) with ESMTP id BD8A121F9BC9; Sun, 28 Jul 2013 03:54:57 -0700 (PDT)
Received: from dodo.ripe.net ([193.0.23.4]) by postgirl.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <mir@ripe.net>) id 1V3Ocm-00041h-7H; Sun, 28 Jul 2013 12:54:54 +0200
Received: from tel-sslvpn-1.ripe.net ([193.0.20.232] helo=dhcp-43fb.meeting.ietf.org) by dodo.ripe.net with esmtp (Exim 4.72) (envelope-from <mir@ripe.net>) id 1V3Ocm-0008Lk-4H; Sun, 28 Jul 2013 12:54:52 +0200
Message-ID: <51F4F87B.8000709@ripe.net>
Date: Sun, 28 Jul 2013 12:54:51 +0200
From: Mirjam Kuehne <mir@ripe.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
Subject: Re: [edu-team] Remote participants, newcomers, and tutorials
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net> <2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net> <5EB533DC-E6EF-40E3-A225-F8F1E39A46DC@unina.it> <18690A2F-5439-4CCC-91F1-58CF67D8D704@piuha.net> <8BA59F96-A1DE-460F-9A22-F2CD4CE5F31C@emc.com>
In-Reply-To: <8BA59F96-A1DE-460F-9A22-F2CD4CE5F31C@emc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Anti-Virus: Kaspersky Anti-Virus for Linux Mail Server 5.6.48/RELEASE, bases: 20120425 #7816575, check: 20130728 clean
X-RIPE-Spam-Level: --
X-RIPE-Spam-Report: Spam Total Points:   -2.9 points pts rule name              description ---- ---------------------- ------------------------------------ -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -0.0 T_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: 7e0932718cf60c1d07d29cd25dae927466eaed389b226dcc3fab0ffdce2c1c15
X-Mailman-Approved-At: Sun, 28 Jul 2013 08:12:23 -0700
Cc: "ietf@ietf.org list" <ietf@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, "rfc-editor@ietf.org" <rfc-editor@ietf.org>, John C Klensin <john-ietf@jck.com>, SM <sm@resistor.net>, "edu-team@ietf.org" <edu-team@ietf.org>, "team@meetecho.com" <team@meetecho.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jul 2013 10:55:06 -0000

Hi Kathleen,

The Edu Team tried to achieve this by providing a high-level overview of 
all the IETF areas (including a short description of the various WGs, 
current discussions and hot topics etc.). The RAI people offered to do 
that for the first time in Orlando:

https://www.ietf.org/edu/process-oriented-tutorials.html#raiinfrastructure

and we're planning to repeat this session at the next meeting (it will 
then also be recorded).

Unfortunately we didn't get a lot of response from other areas. So, any 
help in that respect would be appreciated!

Kind regards,
Mirjam Kuehne
(Edu Team)

On 27/7/13 11:38 PM, Moriarty, Kathleen wrote:
> I think it would be really helpful/useful if working groups could provide short video overviews to help people understand the work.  This includes newcomers and also interested observers, who may include implementers.  Can that be accommodated, maybe at a future meeting?  I am happy to help if I can.
>
> Thank you!
> Kathleen
>
> Sent from my iPhone
>
> On Jul 27, 2013, at 4:44 PM, "Jari Arkko" <jari.arkko@piuha.net> wrote:
>
>> Simon,
>>
>>> for your information, the Meetecho team is going to record five tutorials on Sunday:
>>>
>>> http://www.ietf.org/meeting/87/remote-participation.html#meetecho
>>>
>>> We have already provided a URL for those who want to remotely attend the IAOC Overview Session. If you think this might be of interest, we can allow remotes to have access to the other tutorials as well. Just let us know, so we can advertise access URLs on the mentioned web page. As usual, we can provide a real-time, synchronized view of the sessions, involving audio, video and presentation slides.
>>
>> I think it would be useful. Thank you.
>>
>> Jari
>>
>>
> _______________________________________________
> edu-team mailing list
> edu-team@ietf.org
> https://www.ietf.org/mailman/listinfo/edu-team
>


From zach@sensinode.com  Sun Jul 28 07:30:33 2013
Return-Path: <zach@sensinode.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9B4621F9D9B for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 07:30:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YIcKJVHnre2h for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 07:30:29 -0700 (PDT)
Received: from auth-smtp.nebula.fi (auth-smtp.nebula.fi [217.30.180.105]) by ietfa.amsl.com (Postfix) with ESMTP id 8D1E421F9D96 for <ietf@ietf.org>; Sun, 28 Jul 2013 07:30:29 -0700 (PDT)
Received: from dhcp-414b.meeting.ietf.org (dhcp-414b.meeting.ietf.org [130.129.65.75]) (authenticated bits=0) by auth-smtp.nebula.fi (8.13.8/8.13.4) with ESMTP id r6SEUQNd025558 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Sun, 28 Jul 2013 17:30:27 +0300
X-Authenticated-User: sensinodecom
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
From: Zach Shelby <zach@sensinode.com>
In-Reply-To: <20130716195803.9658.64560.idtracker@ietfa.amsl.com>
Date: Sun, 28 Jul 2013 16:30:25 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <AA708E07-A58B-4759-89A9-D3EFD9F24524@sensinode.com>
References: <20130716195803.9658.64560.idtracker@ietfa.amsl.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1503)
X-Mailman-Approved-At: Sun, 28 Jul 2013 08:12:23 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jul 2013 14:30:33 -0000

I have reviewed this version of the CBOR draft, and am fully supportive =
of this as a proposed standard.=20

For IoT applications over CoAP and other protocols, there is a clear =
need for a standard binary object representation with a straightforward =
mapping to JSON that is suitable for constrained devices and networks. =
This is it. I have not yet implemented CBOR, but plan to do so for use =
with several commercial CoAP implementations. Furthermore, JSON based =
formats used in this field such as SenML, or standards from other SDOs =
like OMA Lightweight M2M that use JSON, will clearly benefit from =
standardising CBOR. =20

I found the document to be well written and concise.

Zach Shelby

On Jul 16, 2013, at 9:58 PM, The IESG <iesg-secretary@ietf.org> wrote:

>=20
> The IESG has received a request from an individual submitter to =
consider
> the following document:
> - 'Concise Binary Object Representation (CBOR)'
>  <draft-bormann-cbor-04.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 2013-08-13. 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
>   The Concise Binary Object Representation (CBOR) is a data format
>   whose design goals include the possibility of extremely small code
>   size, fairly small message size, and extensibility without the need
>   for version negotiation.  These design goals make it different from
>   earlier binary serializations such as ASN.1 and MessagePack.
>=20
>=20
>=20
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-bormann-cbor/
>=20
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-bormann-cbor/ballot/
>=20
>=20
> No IPR declarations have been submitted directly on this I-D.
>=20
>=20

--=20
Zach Shelby, Chief Nerd, Sensinode Ltd.
http://www.sensinode.com @SensinodeIoT
Mobile: +358 40 7796297
Twitter: @zach_shelby
LinkedIn: http://fi.linkedin.com/in/zachshelby
6LoWPAN Book: http://6lowpan.net





From andrewmcgr@google.com  Sun Jul 28 10:19:59 2013
Return-Path: <andrewmcgr@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EAF9F21F9C60 for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 10:19:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 502SCtMfXgy0 for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 10:19:59 -0700 (PDT)
Received: from mail-qa0-x235.google.com (mail-qa0-x235.google.com [IPv6:2607:f8b0:400d:c00::235]) by ietfa.amsl.com (Postfix) with ESMTP id BE0AC21F9C01 for <ietf@ietf.org>; Sun, 28 Jul 2013 10:19:58 -0700 (PDT)
Received: by mail-qa0-f53.google.com with SMTP id hu14so1264285qab.5 for <ietf@ietf.org>; Sun, 28 Jul 2013 10:19:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=4RkHaz0ei/Smj+UnsyvxEnmSofPbX3AtvfBzFH1td/o=; b=fJmF6XvnR2MFFK6uAQmNU1epOZhSQJsKLw2jpYjdbfqCtf171v8+PFRk39759gn4AB EGpuvOXS/sO4G+oGOdZxmg/74MGa6b2OAObpJsai7QtYHpbhVreZdGoruzsGM+gBWU5t oh4aJUbcj1eOYQYbUgOSQEPcUdK7sJjZcNyojXnY22iwFSKq2Hh7BsER/ugi2UBr4TQp qAMLw9h7+HHA0AfsDGNXg5DSnIjkPll8dFL9arBzpFGWjgOluAK7QvPOFuw4Czilhv0y ynvN+mWbxFPd5eHjxq4ml4W3idzFX8lLQrKS7XAabhKQPMUPs5sQn+Ti97NRxCLKNAlU 9B9Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=4RkHaz0ei/Smj+UnsyvxEnmSofPbX3AtvfBzFH1td/o=; b=A1JgJPQXJuo7ZZqYrITEce6nE6Au40plACvVDW8VBeftNPTp/uBXI9XCZ0dbSNCI4j rc2HrjKVnnUFZDV7XlGw0ul+UlIcgJuf/tqVBpP6F4uOjszO3S0CHzlKQOgx4ZAV/3gB 25P0FJrR7FvBLEiwGIW6TGQZ0cfgz+7G7Mw4bHm7xefW1Y2GGygpPDSlcFY4EsoVuo2R zdg/zXJ2zOtZasjCYFwc5llRC3zDfpFnfgsPWRwed5EfNAslhy34z6cVeoGLXKDaxg40 VkYzPcsVNrICmpFbAethsqxrdCNv7XTpyh0qqQEhTLk0HZ9jJsNAbgNVwiVxNgaZE14X eI9w==
MIME-Version: 1.0
X-Received: by 10.224.97.66 with SMTP id k2mr45306444qan.109.1375031996036; Sun, 28 Jul 2013 10:19:56 -0700 (PDT)
Received: by 10.224.137.196 with HTTP; Sun, 28 Jul 2013 10:19:55 -0700 (PDT)
In-Reply-To: <AA708E07-A58B-4759-89A9-D3EFD9F24524@sensinode.com>
References: <20130716195803.9658.64560.idtracker@ietfa.amsl.com> <AA708E07-A58B-4759-89A9-D3EFD9F24524@sensinode.com>
Date: Sun, 28 Jul 2013 10:19:55 -0700
Message-ID: <CAPRuP3mQdbmsDfC7fbkvGwS19LJ-uoYgZDf=Bxse4iQE1XnrbQ@mail.gmail.com>
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
From: Andrew Mcgregor <andrewmcgr@google.com>
To: Zach Shelby <zach@sensinode.com>
Content-Type: multipart/alternative; boundary=001a11c3ef46addd5204e295956f
X-Gm-Message-State: ALoCoQkA2mj9UWiyhJZlO8+gFrZ0Vjr5mXcr4N3XAVQa0wKjT837oehG1ZhF/YR0Pn/nYq9e2FLpr8pY9f/uE+zb/cHfB5LYQWssCnL5gcAN1B3yHBKRcqb4RvKWrSrsyPi8HmZcueRMseSQT+IS1s6pyccgY1NcqLgN+06YtM61b60/z9S6Te33vj6i3d4x8iJr2fCsdSt9
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jul 2013 17:20:00 -0000

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

I have reviewed the -03 version of this draft, and I support this as a
proposed standard.

As an exercise for review, I implemented a large part of the draft (in
plain Python) and found the description completely adequate to produce
working code that parsed the examples in the draft correctly, and could
generate many of them.



On 28 July 2013 07:30, Zach Shelby <zach@sensinode.com> wrote:

> I have reviewed this version of the CBOR draft, and am fully supportive of
> this as a proposed standard.
>
> For IoT applications over CoAP and other protocols, there is a clear need
> for a standard binary object representation with a straightforward mapping
> to JSON that is suitable for constrained devices and networks. This is it.
> I have not yet implemented CBOR, but plan to do so for use with several
> commercial CoAP implementations. Furthermore, JSON based formats used in
> this field such as SenML, or standards from other SDOs like OMA Lightweight
> M2M that use JSON, will clearly benefit from standardising CBOR.
>
> I found the document to be well written and concise.
>
> Zach Shelby
>
> On Jul 16, 2013, at 9:58 PM, The IESG <iesg-secretary@ietf.org> wrote:
>
> >
> > The IESG has received a request from an individual submitter to consider
> > the following document:
> > - 'Concise Binary Object Representation (CBOR)'
> >  <draft-bormann-cbor-04.txt> as Proposed Standard
> >
> > The IESG plans to make a decision in the next few weeks, and solicits
> > final comments on this action. Please send substantive comments to the
> > ietf@ietf.org mailing lists by 2013-08-13. 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
> >
> >
> >   The Concise Binary Object Representation (CBOR) is a data format
> >   whose design goals include the possibility of extremely small code
> >   size, fairly small message size, and extensibility without the need
> >   for version negotiation.  These design goals make it different from
> >   earlier binary serializations such as ASN.1 and MessagePack.
> >
> >
> >
> >
> > The file can be obtained via
> > http://datatracker.ietf.org/doc/draft-bormann-cbor/
> >
> > IESG discussion can be tracked via
> > http://datatracker.ietf.org/doc/draft-bormann-cbor/ballot/
> >
> >
> > No IPR declarations have been submitted directly on this I-D.
> >
> >
>
> --
> Zach Shelby, Chief Nerd, Sensinode Ltd.
> http://www.sensinode.com @SensinodeIoT
> Mobile: +358 40 7796297
> Twitter: @zach_shelby
> LinkedIn: http://fi.linkedin.com/in/zachshelby
> 6LoWPAN Book: http://6lowpan.net
>
>
>
>
>


-- 
Andrew McGregor | SRE | andrewmcgr@google.com | +61 4 8143 7128

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

<div dir=3D"ltr">I have reviewed the -03 version of this draft, and I suppo=
rt this as a proposed standard.<div><br></div><div>As an exercise for revie=
w, I implemented a large part of the draft (in plain Python) and found the =
description completely adequate to produce working code that parsed the exa=
mples in the draft correctly, and could generate many of them.</div>
<div><br></div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On 28 July 2013 07:30, Zach Shelby <span dir=3D"ltr">&lt;<a href=3D=
"mailto:zach@sensinode.com" target=3D"_blank">zach@sensinode.com</a>&gt;</s=
pan> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">I have reviewed this version of the CBOR dra=
ft, and am fully supportive of this as a proposed standard.<br>
<br>
For IoT applications over CoAP and other protocols, there is a clear need f=
or a standard binary object representation with a straightforward mapping t=
o JSON that is suitable for constrained devices and networks. This is it. I=
 have not yet implemented CBOR, but plan to do so for use with several comm=
ercial CoAP implementations. Furthermore, JSON based formats used in this f=
ield such as SenML, or standards from other SDOs like OMA Lightweight M2M t=
hat use JSON, will clearly benefit from standardising CBOR.<br>

<br>
I found the document to be well written and concise.<br>
<br>
Zach Shelby<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
On Jul 16, 2013, at 9:58 PM, The IESG &lt;<a href=3D"mailto:iesg-secretary@=
ietf.org">iesg-secretary@ietf.org</a>&gt; wrote:<br>
<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;Concise Binary Object Representation (CBOR)&#39;<br>
&gt; =A0&lt;draft-bormann-cbor-04.txt&gt; as Proposed Standard<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"mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by 20=
13-08-13. Exceptionally, comments may be<br>
&gt; sent to <a href=3D"mailto:iesg@ietf.org">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 The Concise Binary Object Representation (CBOR) is a data format<b=
r>
&gt; =A0 whose design goals include the possibility of extremely small code=
<br>
&gt; =A0 size, fairly small message size, and extensibility without the nee=
d<br>
&gt; =A0 for version negotiation. =A0These design goals make it different f=
rom<br>
&gt; =A0 earlier binary serializations such as ASN.1 and MessagePack.<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-bormann-cbor/" target=
=3D"_blank">http://datatracker.ietf.org/doc/draft-bormann-cbor/</a><br>
&gt;<br>
&gt; IESG discussion can be tracked via<br>
&gt; <a href=3D"http://datatracker.ietf.org/doc/draft-bormann-cbor/ballot/"=
 target=3D"_blank">http://datatracker.ietf.org/doc/draft-bormann-cbor/ballo=
t/</a><br>
&gt;<br>
&gt;<br>
&gt; No IPR declarations have been submitted directly on this I-D.<br>
&gt;<br>
&gt;<br>
<br>
</div></div><span class=3D"HOEnZb"><font color=3D"#888888">--<br>
Zach Shelby, Chief Nerd, Sensinode Ltd.<br>
<a href=3D"http://www.sensinode.com" target=3D"_blank">http://www.sensinode=
.com</a> @SensinodeIoT<br>
Mobile: <a href=3D"tel:%2B358%2040%207796297" value=3D"+358407796297">+358 =
40 7796297</a><br>
Twitter: @zach_shelby<br>
LinkedIn: <a href=3D"http://fi.linkedin.com/in/zachshelby" target=3D"_blank=
">http://fi.linkedin.com/in/zachshelby</a><br>
6LoWPAN Book: <a href=3D"http://6lowpan.net" target=3D"_blank">http://6lowp=
an.net</a><br>
<br>
<br>
<br>
<br>
</font></span></blockquote></div><br><br clear=3D"all"><div><br></div>-- <b=
r><div dir=3D"ltr"><span style=3D"color:rgb(85,85,85);font-family:sans-seri=
f;font-size:small;line-height:1.5em;border-width:2px 0px 0px;border-style:s=
olid;border-color:rgb(213,15,37);padding-top:2px;margin-top:2px">Andrew McG=
regor=A0|</span><span style=3D"color:rgb(85,85,85);font-family:sans-serif;f=
ont-size:small;line-height:1.5em;border-width:2px 0px 0px;border-style:soli=
d;border-color:rgb(51,105,232);padding-top:2px;margin-top:2px">=A0SRE=A0|</=
span><span style=3D"color:rgb(85,85,85);font-family:sans-serif;font-size:sm=
all;line-height:1.5em;border-width:2px 0px 0px;border-style:solid;border-co=
lor:rgb(0,153,57);padding-top:2px;margin-top:2px">=A0<a href=3D"mailto:andr=
ewmcgr@google.com" target=3D"_blank">andrewmcgr@google.com</a>=A0|</span><s=
pan style=3D"color:rgb(85,85,85);font-family:sans-serif;font-size:small;lin=
e-height:1.5em;border-width:2px 0px 0px;border-style:solid;border-color:rgb=
(238,178,17);padding-top:2px;margin-top:2px">=A0+61 4 8143 7128</span><br>
</div>
</div>

--001a11c3ef46addd5204e295956f--

From hallam@gmail.com  Sun Jul 28 19:54:39 2013
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 499CC21F96CA; Sun, 28 Jul 2013 19:54:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.46
X-Spam-Level: 
X-Spam-Status: No, score=-2.46 tagged_above=-999 required=5 tests=[AWL=0.139,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tadeh6iWHN4O; Sun, 28 Jul 2013 19:54:38 -0700 (PDT)
Received: from mail-we0-x231.google.com (mail-we0-x231.google.com [IPv6:2a00:1450:400c:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id D049521F92C2; Sun, 28 Jul 2013 19:54:37 -0700 (PDT)
Received: by mail-we0-f177.google.com with SMTP id m46so3355085wev.8 for <multiple recipients>; Sun, 28 Jul 2013 19:54:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=DG7TWkhzni6olk7agrWwZ5OW02b5YNoNdI/fEP84bXs=; b=fmHRHddxAQgWhIRsh7l7TKKHoYjlU962v7HIVQB7lOo8RDrk5fgGxnEThYZR5R//Wm b+rZaQxaImvrSuqiOAi1JQMwhUDgbfyNAjkK4nv9uciqUl4kJNqA/R8ZGNLVfLntU1q8 lkR96RiLdB4SuBHph/451HC/6IozedUPkUMfk+TW4lwY9lu1PxZES11ZvvfOHihNpoSl y3x6hmjW7CgASYNkYaCgL2Vl3F0SHI5GmqondU1/cwyKqR6Vz6RDeDzOMo0SsBKsqR2u xFSi6Rd4i3ufWTV+JuY4L0quMX5Cafk7orUXEfV9NXdEW0pXxhLRi4OvWfgyeN+ysiyv QkiA==
MIME-Version: 1.0
X-Received: by 10.180.182.229 with SMTP id eh5mr5562836wic.63.1375066476967; Sun, 28 Jul 2013 19:54:36 -0700 (PDT)
Received: by 10.194.6.65 with HTTP; Sun, 28 Jul 2013 19:54:36 -0700 (PDT)
In-Reply-To: <20130716195803.9658.64560.idtracker@ietfa.amsl.com>
References: <20130716195803.9658.64560.idtracker@ietfa.amsl.com>
Date: Sun, 28 Jul 2013 22:54:36 -0400
Message-ID: <CAMm+Lwh2N+WhwWL599xjtES_jQQaubL4vGRJBt=L-2Nq8jd0mg@mail.gmail.com>
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
From: Phillip Hallam-Baker <hallam@gmail.com>
To: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=089e0163491ee6fc7d04e29d9cc6
Cc: IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Jul 2013 02:54:39 -0000

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

The question I want an answer to is whether this is going to be the only
standard for a binary version of JSON allowed.

I have an alternative proposal which is designed to be compatible with JSON
so that existing encoder and decoder implementations can be used and so
that a single decoder can handle the binary features as a superset of the
existing JSON specification.

http://tools.ietf.org/html/draft-hallambaker-jsonbcd-00

What is the process here?

So far I have been led to believe that this is a personal submission that
is not going to be the last chance we get to discuss this in IETF. Now I
see it being a proposed standard. And I am pretty sure that people are
going to be telling other people that this is the agreed IETF standard that
we all have to use because it is what was decided.


There are existing specs that does what CBOR does just as well that have
actual users. There are requirements that the individuals proposing this
chose not to address.





On Tue, Jul 16, 2013 at 3:58 PM, The IESG <iesg-secretary@ietf.org> wrote:

>
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Concise Binary Object Representation (CBOR)'
>   <draft-bormann-cbor-04.txt> as Proposed Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-08-13. 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
>
>
>    The Concise Binary Object Representation (CBOR) is a data format
>    whose design goals include the possibility of extremely small code
>    size, fairly small message size, and extensibility without the need
>    for version negotiation.  These design goals make it different from
>    earlier binary serializations such as ASN.1 and MessagePack.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-bormann-cbor/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-bormann-cbor/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
>


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

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

<div dir=3D"ltr">The question I want an answer to is whether this is going =
to be the only standard for a binary version of JSON allowed.<div><br></div=
><div>I have an alternative proposal which is designed to be compatible wit=
h JSON so that existing encoder and decoder implementations can be used and=
 so that a single decoder can handle the binary features as a superset of t=
he existing JSON specification.</div>
<div><br></div><div><a href=3D"http://tools.ietf.org/html/draft-hallambaker=
-jsonbcd-00">http://tools.ietf.org/html/draft-hallambaker-jsonbcd-00</a><br=
></div><div><br></div><div>What is the process here?=A0</div><div><br></div=
>
<div>So far I have been led to believe that this is a personal submission t=
hat is not going to be the last chance we get to discuss this in IETF. Now =
I see it being a proposed standard. And I am pretty sure that people are go=
ing to be telling other people that this is the agreed IETF standard that w=
e all have to use because it is what was decided.</div>
<div><br></div><div><br></div><div>There are existing specs that does what =
CBOR does just as well that have actual users. There are requirements that =
the individuals proposing this chose not to address.</div><div><br></div>
<div><br></div><div><br></div></div><div class=3D"gmail_extra"><br><br><div=
 class=3D"gmail_quote">On Tue, Jul 16, 2013 at 3:58 PM, The IESG <span dir=
=3D"ltr">&lt;<a href=3D"mailto:iesg-secretary@ietf.org" target=3D"_blank">i=
esg-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"><br>
The IESG has received a request from an individual submitter to consider<br=
>
the following document:<br>
- &#39;Concise Binary Object Representation (CBOR)&#39;<br>
=A0 &lt;draft-bormann-cbor-04.txt&gt; as Proposed Standard<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 2013-08=
-13. 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>
<br>
=A0 =A0The Concise Binary Object Representation (CBOR) is a data format<br>
=A0 =A0whose design goals include the possibility of extremely small code<b=
r>
=A0 =A0size, fairly small message size, and extensibility without the need<=
br>
=A0 =A0for version negotiation. =A0These design goals make it different fro=
m<br>
=A0 =A0earlier binary serializations such as ASN.1 and MessagePack.<br>
<br>
<br>
<br>
<br>
The file can be obtained via<br>
<a href=3D"http://datatracker.ietf.org/doc/draft-bormann-cbor/" target=3D"_=
blank">http://datatracker.ietf.org/doc/draft-bormann-cbor/</a><br>
<br>
IESG discussion can be tracked via<br>
<a href=3D"http://datatracker.ietf.org/doc/draft-bormann-cbor/ballot/" targ=
et=3D"_blank">http://datatracker.ietf.org/doc/draft-bormann-cbor/ballot/</a=
><br>
<br>
<br>
No IPR declarations have been submitted directly on this I-D.<br>
<br>
<br>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>Website: <a =
href=3D"http://hallambaker.com/">http://hallambaker.com/</a><br>
</div>

--089e0163491ee6fc7d04e29d9cc6--

From moore@network-heretics.com  Sun Jul 28 21:50:24 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C898921F9F50 for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 21:50:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t3j9tFF-CzNn for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 21:50:11 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id 8232121F9F21 for <ietf@ietf.org>; Sun, 28 Jul 2013 21:50:08 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id E28B3204BD; Mon, 29 Jul 2013 00:50:06 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute3.internal (MEProxy); Mon, 29 Jul 2013 00:50:06 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id :references:to; s=smtpout; bh=pEEp8zm+NmDJc5RNIn+bqBVONJU=; b=Vx W131kqNyE67tNB7izGv7t9RGEcr7lw3wDfxdScawoweoiGW1TyO1okUxaRiw78ge BUdE3Vcvb8U/DLdVpFvwChAotZKOeyGuchZLf13k5Q/ps77pZfCUof1OCL42vq3K Kq5jQ8Ry0vjd8LRNOuDVXBUN3ZuTpB410yAYw9INU=
X-Sasl-enc: 7iFh1GMw7q3ZgcnahEasR6O6uAholnBk9P120QQE4yUY 1375073406
Received: from surfer-172-29-8-65-hotspot.internet-for-guests.com (unknown [87.193.195.90]) by mail.messagingengine.com (Postfix) with ESMTPA id EB599C00E82; Mon, 29 Jul 2013 00:50:05 -0400 (EDT)
Subject: Re: Remote participants, newcomers,	and tutorials
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <C48A3EE7-DB53-428A-9C5F-95802B0383F1@checkpoint.com>
Date: Mon, 29 Jul 2013 06:50:03 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <27880CAF-3982-40D7-87C4-444E79368602@network-heretics.com>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net> <2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net> <5EB533DC-E6EF-40E3-A225-F8F1E39A46DC@unina.it> <18690A2F-5439-4CCC-91F1-58CF67D8D704@piuha.net> <8BA59F96-A1DE-460F-9A22-F2CD4CE5F31C@emc.com> <51F44831.2030300@gmail.com> <m2haffxqya.wl%randy@psg.com> <51F49B4A.7020609@gmail.com> <E375D2AA-6CF7-4913-A6B3-D481825BF7F9@network-heretics.com> <C48A3EE7-DB53-428A-9C5F-95802B0383F1@checkpoint.com>
To: Yoav Nir <ynir@checkpoint.com>
X-Mailer: Apple Mail (2.1085)
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Jul 2013 04:50:24 -0000

On Jul 28, 2013, at 9:10 AM, Yoav Nir wrote:

>>>=20
>>>> yup.  i guess it is time for my quarterly suggestion to remove the
>>>> projectors and screens.
>>>=20
>>> Then I guess it's time for my quarterly "I'd be good with that."
>>=20
>> As would I.
>=20
> Me too, as long as we get whiteboards or flip-charts in their stead.
>=20
> But both the academic world and the business world have taught all of =
us to communicate through presentations. So, lost cause.

Regardless of what has been taught, people who can only communicate =
through presentations can't communicate effectively anyway.   Forcing =
effective communicators to filter their communications through =
presentations is a big part of the reason that IETF takes so long to get =
work done.

Keith


From dhc@dcrocker.net  Sun Jul 28 22:25:29 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6F3D21F9FA8 for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 22:25:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ptp1WG53FeG2 for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 22:25:25 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id B480721F9F98 for <ietf@ietf.org>; Sun, 28 Jul 2013 22:25:24 -0700 (PDT)
Received: from [192.168.1.203] (e179046222.adsl.alicedsl.de [85.179.46.222]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r6T5PEM8002688 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 28 Jul 2013 22:25:21 -0700
Message-ID: <51F5FCB6.6060006@dcrocker.net>
Date: Mon, 29 Jul 2013 07:25:10 +0200
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: Remote participants, newcomers, and tutorials
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com>	<E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com>	<6.2.5.6.2.20130726101746.0c8db480@resistor.net>	<2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net> <51F3BBB6.5030406@dcrocker.net> <51F42F7B.2060706@gmail.com> <E12475C2-B005-42A7-A662-F36F55BB953E@piuha.net>
In-Reply-To: <E12475C2-B005-42A7-A662-F36F55BB953E@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]); Sun, 28 Jul 2013 22:25:24 -0700 (PDT)
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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, 29 Jul 2013 05:25:30 -0000

On 7/27/2013 11:01 PM, Jari Arkko wrote:
>> It reads rudely when taken out of context. But try reading the whole
>> paragraph in RFC 3184:
...
>> Exactly. My experience back when I was a newcomer was that it was
>> easy enough to ask beginner's questions after the meeting, and obviously
>> wrong to do so during the session. This remains true years later, if I
>> drop into a WG that I'm not familiar with.
>
> Let me clarify why I thought it was wrong. I don't think I'm disagreeing with you, actually. I do agree that asking beginner questions in a working group meeting would be inappropriate. And I agree that the meetings are not a place for education. And I agree that we should not become an organisation where the f2f time gets the primary role.
>
> However. Newcomers are not all alike. The student coming here to observe the IETF. The researcher who understands the field we are embarking on. The colleague that has been implementing The Protocol for the last two years in the office, but is now coming to the IETF for the first time. The guy who has something to say about the operational experience of our results. The team who brought their idea to the IETF to be standardised. And so on.


Jari (et al)

I've been finding discussion and actions about newcomers far more 
interesting this year, than most previous ones.  So I think it's worth 
pressing on several fronts, to see how we can both accommodate such folk 
better, as well as be clear about when and where and how such 
accommodation is /and is not/ appropriate.

Your reply to me, above, lists different types of new folk -- and of 
course the list is reasonable and might be useful -- but I didn't see 
the actual clarification of what you felt was wrong in the target text 
or how you agreed with me an others.  So, now you've got me curious for 
that detail...


And while I've got the floor I'll offer a thought I had after a brief 
conversation with Jari at last night's reception:

      Warning:  This calls for working groups to do a little more work.

The working group home page and the working group wiki have become 
excellent tools for assembling relevant documents.  For someone trying 
to get started in the wg, these are incredibly helpful.

      My suggestion is for a 'status' page that gives a brief summary 
about the current state of the working group, ideally listing the 
current, near-term vector of the work -- what's the current focus of 
effort -- and major open issues.

      I'll suggest that it be updated after every meeting.

Arguably, this sort of status statement is good to have even without 
newcomers, since it forces working groups to face the question of what 
progress they are and are not making.

An exercise like this can be cast as onerous or helpful, depending upon 
the surrounding organizational 'tone' we use.  In a supportive 
environment, the exercise is helpful.  In a hostile one, not so much.

Basically, if a wg is being diligent and candid in summarizing its 
problems (as well as progress) the rest of us have an obligation to be 
helpful.


d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From brian@innovationslab.net  Sun Jul 28 22:37:16 2013
Return-Path: <brian@innovationslab.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2525221F9F59 for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 22:37:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ud7rpMUyjUTs for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 22:37:11 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 1724B21F9F80 for <ietf@ietf.org>; Sun, 28 Jul 2013 22:37:10 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id CA590880F0 for <ietf@ietf.org>; Sun, 28 Jul 2013 22:37:10 -0700 (PDT)
Received: from 10252091.rudm1.ra.johnshopkins.edu (addr16212925014.ippl.jhmi.edu [162.129.250.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 5F68B130003 for <ietf@ietf.org>; Sun, 28 Jul 2013 22:37:10 -0700 (PDT)
Message-ID: <51F5FF83.4080308@innovationslab.net>
Date: Mon, 29 Jul 2013 01:37:07 -0400
From: Brian Haberman <brian@innovationslab.net>
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: Remote participants, newcomers, and tutorials
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com>	<E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com>	<6.2.5.6.2.20130726101746.0c8db480@resistor.net>	<2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net> <51F3BBB6.5030406@dcrocker.net> <51F42F7B.2060706@gmail.com> <E12475C2-B005-42A7-A662-F36F55BB953E@piuha.net> <51F5FCB6.6060006@dcrocker.net>
In-Reply-To: <51F5FCB6.6060006@dcrocker.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Jul 2013 05:37:16 -0000

Hi Dave,
      I am not Jari, but I do have an opinion on your thoughts below...

On 7/29/13 1:25 AM, Dave Crocker wrote:
>
> I've been finding discussion and actions about newcomers far more
> interesting this year, than most previous ones.  So I think it's worth
> pressing on several fronts, to see how we can both accommodate such folk
> better, as well as be clear about when and where and how such
> accommodation is /and is not/ appropriate.
>
> Your reply to me, above, lists different types of new folk -- and of
> course the list is reasonable and might be useful -- but I didn't see
> the actual clarification of what you felt was wrong in the target text
> or how you agreed with me an others.  So, now you've got me curious for
> that detail...
>
>
> And while I've got the floor I'll offer a thought I had after a brief
> conversation with Jari at last night's reception:
>
>       Warning:  This calls for working groups to do a little more work.
>
> The working group home page and the working group wiki have become
> excellent tools for assembling relevant documents.  For someone trying
> to get started in the wg, these are incredibly helpful.
>
>       My suggestion is for a 'status' page that gives a brief summary
> about the current state of the working group, ideally listing the
> current, near-term vector of the work -- what's the current focus of
> effort -- and major open issues.
>
>       I'll suggest that it be updated after every meeting.
>
> Arguably, this sort of status statement is good to have even without
> newcomers, since it forces working groups to face the question of what
> progress they are and are not making.
>
> An exercise like this can be cast as onerous or helpful, depending upon
> the surrounding organizational 'tone' we use.  In a supportive
> environment, the exercise is helpful.  In a hostile one, not so much.
>
> Basically, if a wg is being diligent and candid in summarizing its
> problems (as well as progress) the rest of us have an obligation to be
> helpful.

One of the things that I ask the Internet Area chairs to do is send in a 
summary of their WG after each IETF meeting.  Those summaries generally 
give folks a good idea of the current state of each WG.  I post those 
summaries on the Internet Area wiki.  An alternative that would work as 
well is to have each WG post summaries to their own wikis.  Each WG has 
a wiki available via their Tools page (e.g., 
http://trac.tools.ietf.org/wg/6man/trac/wiki).

I like seeing the summaries from my chairs and I have gotten feedback 
from participants that they find them quite useful for keeping up with 
WGs that are tangential to their primary focus.  I would encourage every 
WG chair to periodically summarize the state of their WG/drafts.

Regards,
Brian



From joelja@bogus.com  Sun Jul 28 22:55:32 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E81121F9FF2 for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 22:55:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vHPTkyAXWXbo for <ietf@ietfa.amsl.com>; Sun, 28 Jul 2013 22:55:31 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 60C9611E80D3 for <ietf@ietf.org>; Sun, 28 Jul 2013 22:55:26 -0700 (PDT)
Received: from dhcp-603a.meeting.ietf.org (dhcp-603a.meeting.ietf.org [130.129.96.58]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r6T5tJkD045137 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Mon, 29 Jul 2013 05:55:21 GMT (envelope-from joelja@bogus.com)
Message-ID: <51F603C6.1070002@bogus.com>
Date: Mon, 29 Jul 2013 07:55:18 +0200
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:23.0) Gecko/20100101 Thunderbird/23.0
MIME-Version: 1.0
To: dcrocker@bbiw.net, Jari Arkko <jari.arkko@piuha.net>
Subject: Re: Remote participants, newcomers, and tutorials
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com>	<E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com>	<6.2.5.6.2.20130726101746.0c8db480@resistor.net>	<2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net>	<51F3BBB6.5030406@dcrocker.net> <51F42F7B.2060706@gmail.com>	<E12475C2-B005-42A7-A662-F36F55BB953E@piuha.net> <51F5FCB6.6060006@dcrocker.net>
In-Reply-To: <51F5FCB6.6060006@dcrocker.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Mon, 29 Jul 2013 05:55:22 +0000 (UTC)
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Jul 2013 05:55:32 -0000

On 7/29/13 7:25 AM, Dave Crocker wrote:
>
>      My suggestion is for a 'status' page that gives a brief summary
> about the current state of the working group, ideally listing the
> current, near-term vector of the work -- what's the current focus of
> effort -- and major open issues.
>
>      I'll suggest that it be updated after every meeting.
>
> Arguably, this sort of status statement is good to have even without
> newcomers, since it forces working groups to face the question of what
> progress they are and are not making.
>
> An exercise like this can be cast as onerous or helpful, depending
> upon the surrounding organizational 'tone' we use.  In a supportive
> environment, the exercise is helpful.  In a hostile one, not so much.
>
> Basically, if a wg is being diligent and candid in summarizing its
> problems (as well as progress) the rest of us have an obligation to be
> helpful.
http://trac.tools.ietf.org/area/ops/trac/wiki/IETF86summary

is the ops area's experiment with doing this.
>
>
> d/
>


From hartmans@mit.edu  Mon Jul 29 01:54:32 2013
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A09521E808A; Mon, 29 Jul 2013 01:54:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jat8880m0KUy; Mon, 29 Jul 2013 01:54:26 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id DFD0421F9E3F; Mon, 29 Jul 2013 01:54:24 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id AB26620202; Mon, 29 Jul 2013 04:53:50 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xxm_SuNIw_ti; Mon, 29 Jul 2013 04:53:49 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (dhcp-4332.meeting.ietf.org [130.129.67.50]) (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; Mon, 29 Jul 2013 04:53:49 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 31E3787FB4; Mon, 29 Jul 2013 04:54:20 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: ietf@ietf.org
Subject: Re: [karp] Last Call: <draft-ietf-karp-ops-model-07.txt> (Operations Model for	Router Keying) to Informational RFC
References: <20130729063557.22039.63212.idtracker@ietfa.amsl.com>
Date: Mon, 29 Jul 2013 04:54:20 -0400
In-Reply-To: <20130729063557.22039.63212.idtracker@ietfa.amsl.com> (The IESG's message of "Sun, 28 Jul 2013 23:35:57 -0700")
Message-ID: <tsltxjdwxtv.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
Cc: danny@tcb.net, karp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Jul 2013 08:54:32 -0000

Hi.

Yes I'm making a last call comment on a document I edit:-)

During discussion of another document
)(draft-ietf-karp-crypto-key-table), a routing directorate review
brought up the concern that we don't talk about time synchronization.
Without time synchronization, the wrong keys can be selected in certain
circumstances.
In some cases, time synchronization is required for replay detection,
although that is rare for routing protocols.

Those involved in the discussion of time synchronization and
draft-ietf-karp-crypto-key-table believed that draft-ietf-karp-ops-model
is a better place for a discussion of time synchronization than
draft-ietf-karp-crypto-key-table.

So, I'd like to propose the following text be added to security
considerations:

      <t>Close synchronization of time can impact the security of
      routing protocols in a number of ways.  Time is used to control
      when keys MAY bxegin being used and when they MUST NOT be used any
      longer as described in <xref
      target="i-d.ietf-karp-crypto-key-table"></xref>.  Routers need to
      have tight enough time synchronization that receivers permit a key
      to be used prior to the first use of that key or availability will
      be impacted.  If time synchronization is too loose, then a key can
      be used beyond its intended lifetime.  The Network Time Protocol
      (NTP) can be used to provide time synchronization.  For some
      protocols, time synchronization is also important for replay
      detection.

From chair@ietf.org  Mon Jul 29 02:07:24 2013
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 149CA21F9D68; Mon, 29 Jul 2013 02:07:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dbsjoYWxBiOD; Mon, 29 Jul 2013 02:07:13 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.21]) by ietfa.amsl.com (Postfix) with ESMTP id C976A21F9F77; Mon, 29 Jul 2013 02:07:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id A40439FB77; Mon, 29 Jul 2013 02:07:12 -0700 (PDT)
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 9QpL834t5kHJ; Mon, 29 Jul 2013 02:07:12 -0700 (PDT)
Received: from dhcp-14b8.meeting.ietf.org (dhcp-14b8.meeting.ietf.org [130.129.20.184]) by c9a.amsl.com (Postfix) with ESMTPSA id 0F1CF9FB7B; Mon, 29 Jul 2013 02:07:11 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Subject: moving more responsibility to working groups
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: IETF Chair <chair@ietf.org>
Date: Mon, 29 Jul 2013 11:07:09 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <A7CEFA3E-A71B-45A0-A50A-004BDCB6F685@ietf.org>
To: "ietf-announce@ietf.org" <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1508)
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "ietf@ietf.org 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: Mon, 29 Jul 2013 09:07:24 -0000

I would like to report an experiment that the IESG is starting. (There's =
also an associated blog article about this at =
http://www.ietf.org/blog/2013/07/the-role-of-working-groups/)

Internet Drafts sent for approval as RFCs are reviewed by individuals =
during the IETF Last Call, the Area Directors, IANA, as well as a number =
of volunteers from various directorates and review teams. The reviews =
from these teams has gained a significant role in ensuring that the IETF =
produces high-quality, understandable and implementable RFCs.

Yet, as discussed in =
http://www.ietf.org/blog/2013/05/balancing-the-process/ we have a =
general problem that quite a lot of the work around IETF documents =
happens at the end of the process. In particular, a number of the =
reviews during IETF last call point out issues that end up being raised =
by the IESG as comments. It is of course good that issues are caught, =
but raising them earlier would be better. And it would be better if the =
working groups - the intended focus point of work on a topic - would get =
to handle them, as opposed to raising these issues with the IESG. The =
has IESG discussed these issues and decided to experiment with three =
actions designed to move more work to the responsibility of the working =
groups:

(1) Perform some reviews that are now happening at IETF Last Call a bit =
earlier. This will put the working group in a bigger role in resolving =
cross-area and general issues.

(2) Invite document shepherds on IESG telechats when there's a document =
that is likely to require discussion. This will make it possible for the =
document shepherd to be directly involved in the discussions.=20

(3) When a document up for approval has a number of issues, hand over =
the process back to the working group, as opposed to the IESG tracking =
the issues. Among other things, this will ensure that changes are =
discussed in an open working group list and agreed through consensus.

We are at the beginning of the experiment. We've done (2) and (3) a few =
times and plan to use it more from now on. We are discussing with the =
review teams to plan how (1) comes into effect. Building quality and =
cross-area review to the process earlier is of course a big effort. We =
are making a small change to current directorate review procedures. If =
successful, this will enable working groups to deal with issues before =
IETF Last Call and IESG review and empower the working groups to be in =
charge of the documents throughout their life cycle. We are also hoping =
that document quality will improve and number of issues discussed in the =
IESG will be lower.

=46rom the point of view of the document authors and WG participants, =
all the above works through your working group chairs. They will be =
talking to you when documents come back to the working group. They or =
the document shepherds will be even more part of the IESG discussions =
and will keep the working groups updated on the progress of the =
documents. They will work with review teams to request earlier review. =
You will be seeing some reviews in the working group mailing lists. The =
current plan is to do these reviews after WGLC has completed, in =
parallel with ongoing reviews from your responsible ADs and chairs =
preparing the write-ups for the document to be submitted to the IETF =
Last Call.

While the number of reviews as such is not changed, some additional =
effort and care will however be required from the reviewers, directorate =
coordinators/secretaries, the working group chairs, and other =
participants. The experiment will show us whether this effort is =
reasonable and if there are any unexpected effects. The experiment is =
performed on a voluntary basis by each directorate, for a limited number =
of drafts at the beginning.

We will be collecting experiences so that in six months we can evaluate =
the experience. I would also like to thank the document shepherds, =
chairs, and review teams for participation in this effort!

Jari


From danny@tcb.net  Mon Jul 29 02:19:48 2013
Return-Path: <danny@tcb.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAEE121F9E46 for <ietf@ietfa.amsl.com>; Mon, 29 Jul 2013 02:19:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.437
X-Spam-Level: 
X-Spam-Status: No, score=-100.437 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611,  RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CidposAVkjbV for <ietf@ietfa.amsl.com>; Mon, 29 Jul 2013 02:19:42 -0700 (PDT)
Received: from mail.friendswithtools.org (unknown [64.78.239.70]) by ietfa.amsl.com (Postfix) with ESMTP id E305A21F9A71 for <ietf@ietf.org>; Mon, 29 Jul 2013 02:19:37 -0700 (PDT)
Received: from dspam (unknown [127.0.0.1]) by mail.friendswithtools.org (Postfix) with SMTP id 7B0EA30004D for <ietf@ietf.org>; Mon, 29 Jul 2013 09:19:37 +0000 (UTC)
Received: from [10.13.129.205] (unknown [81.92.22.186]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.friendswithtools.org (Postfix) with ESMTPSA id AB18830004A; Mon, 29 Jul 2013 03:19:36 -0600 (MDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [karp] Last Call: <draft-ietf-karp-ops-model-07.txt> (Operations Model for	Router Keying) to Informational RFC
From: Danny McPherson <danny@tcb.net>
In-Reply-To: <tsltxjdwxtv.fsf@mit.edu>
Date: Mon, 29 Jul 2013 05:19:36 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <DEEFC821-D9C4-4CAF-9A60-0BBE024DD30C@tcb.net>
References: <20130729063557.22039.63212.idtracker@ietfa.amsl.com> <tsltxjdwxtv.fsf@mit.edu>
To: Sam Hartman <hartmans-ietf@mit.edu>
X-Mailer: Apple Mail (2.1508)
X-DSPAM-Result: Innocent
X-DSPAM-Processed: Mon Jul 29 03:19:37 2013
X-DSPAM-Confidence: 1.0000
X-DSPAM-Improbability: 1 in 98689409 chance of being spam
X-DSPAM-Probability: 0.0023
X-DSPAM-Signature: 51f633a942071873926418
X-DSPAM-Factors: 27, 2013+at, 0.40000, detection+#+#+is, 0.40000, with+#+#+surprisingly, 0.40000, can+#+#+#+certain, 0.40000, Subject*Model+#+Router, 0.40000, that+#+#+for, 0.40000, I'd+like, 0.40000, Subject*Router+Keying, 0.40000, I'm+making, 0.40000, a+better, 0.40000, Subject*Model+for, 0.40000, to+#+the, 0.40000, rare+for, 0.40000, I+#+#+discussion, 0.40000, time+#+than, 0.40000, edit+#+#+of, 0.40000, I'd+#+to, 0.40000, that+#+#+#+about, 0.40000, hartmans+#+#+edu, 0.40000, last+#+#+#+a, 0.40000, this+#+#+#+bxegin, 0.40000, to+#+considerations, 0.40000, and+draft, 0.40000, AM+#+Hartman, 0.40000, draft+#+#+ops, 0.40000, edu+#+#+Yes, 0.40000, I+agree, 0.40000
Cc: ietf@ietf.org, karp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Jul 2013 09:19:48 -0000

On Jul 29, 2013, at 4:54 AM, Sam Hartman <hartmans-ietf@mit.edu> wrote:

> 
> Hi.
> 
> Yes I'm making a last call comment on a document I edit:-)
> 
> During discussion of another document
> )(draft-ietf-karp-crypto-key-table), a routing directorate review
> brought up the concern that we don't talk about time synchronization.
> Without time synchronization, the wrong keys can be selected in certain
> circumstances.
> In some cases, time synchronization is required for replay detection,
> although that is rare for routing protocols.
> 
> Those involved in the discussion of time synchronization and
> draft-ietf-karp-crypto-key-table believed that draft-ietf-karp-ops-model
> is a better place for a discussion of time synchronization than
> draft-ietf-karp-crypto-key-table.

I agree with this (not surprisingly :-)

> So, I'd like to propose the following text be added to security
> considerations:

I'm good with this, one nit:

s/bxegin/begin/

Thanks Sam, 

-danny


From hartmans@mit.edu  Mon Jul 29 02:36:15 2013
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 473EE21F9ACA; Mon, 29 Jul 2013 02:36:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yZIgj5aDLo0k; Mon, 29 Jul 2013 02:36:09 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id D717411E80DF; Mon, 29 Jul 2013 02:35:49 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 6A08E20118; Mon, 29 Jul 2013 05:35:00 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gMwaWuWU5wNp; Mon, 29 Jul 2013 05:35:00 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (dhcp-4332.meeting.ietf.org [130.129.67.50]) (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; Mon, 29 Jul 2013 05:35:00 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 59DDC87FB4; Mon, 29 Jul 2013 05:35:31 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Danny McPherson <danny@tcb.net>
Subject: Re: [karp] Last Call: <draft-ietf-karp-ops-model-07.txt> (Operations Model for	Router Keying) to Informational RFC
References: <20130729063557.22039.63212.idtracker@ietfa.amsl.com> <tsltxjdwxtv.fsf@mit.edu> <21DC453F-A434-463F-9F69-D036675507FB@tcb.net>
Date: Mon, 29 Jul 2013 05:35:31 -0400
In-Reply-To: <21DC453F-A434-463F-9F69-D036675507FB@tcb.net> (Danny McPherson's message of "Mon, 29 Jul 2013 05:31:00 -0400")
Message-ID: <tsltxjdvhcs.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
Cc: Sam Hartman <hartmans-ietf@mit.edu>, ietf@ietf.org, karp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Jul 2013 09:36:15 -0000

Danny sent me private text that he believes is better than what I
proposed.


I like your text below except that signing is the wrong word.
How about generation of integrity-protected messages?

These messages are almost never digitally signed.

Proposed text:

> Routers need to
>      have tight enough time synchronization that receivers permit a key
>      to be utilized for validation prior to the first use of that key for signing or
>      availability will be impacted.

From stpeter@stpeter.im  Mon Jul 29 03:06:31 2013
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDFDB21F9FFF for <ietf@ietfa.amsl.com>; Mon, 29 Jul 2013 03:06:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id siyKGvI92Mhs for <ietf@ietfa.amsl.com>; Mon, 29 Jul 2013 03:06:20 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id D10A521F9FCF for <ietf@ietf.org>; Mon, 29 Jul 2013 03:06:20 -0700 (PDT)
Received: from dhcp-10f3.meeting.ietf.org (unknown [130.129.16.243]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 5039040049; Mon, 29 Jul 2013 04:08:28 -0600 (MDT)
Message-ID: <51F63E9A.4000003@stpeter.im>
Date: Mon, 29 Jul 2013 12:06:18 +0200
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
References: <20130716195803.9658.64560.idtracker@ietfa.amsl.com> <CAMm+Lwh2N+WhwWL599xjtES_jQQaubL4vGRJBt=L-2Nq8jd0mg@mail.gmail.com>
In-Reply-To: <CAMm+Lwh2N+WhwWL599xjtES_jQQaubL4vGRJBt=L-2Nq8jd0mg@mail.gmail.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Jul 2013 10:06:31 -0000

On 7/29/13 4:54 AM, Phillip Hallam-Baker wrote:
> The question I want an answer to is whether this is going to be the only
> standard for a binary version of JSON allowed.

That is certainly not what I heard during the APPSAWG session this
morning: the intent is that this be one format among many.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From sm@resistor.net  Mon Jul 29 03:09:53 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F94A21E808C for <ietf@ietfa.amsl.com>; Mon, 29 Jul 2013 03:09:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.525
X-Spam-Level: 
X-Spam-Status: No, score=-102.525 tagged_above=-999 required=5 tests=[AWL=0.074, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aQXnSrOlJ-6a for <ietf@ietfa.amsl.com>; Mon, 29 Jul 2013 03:09:52 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5712221E8089 for <ietf@ietf.org>; Mon, 29 Jul 2013 03:09:51 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r6TA9glc001965; Mon, 29 Jul 2013 03:09:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1375092587; bh=4YdKRlp8gtwxOqYZ94yV/bCupduQPlXZ3J7atan3vvA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=mnpiFBTGqbOb6y6QnehpM5gkj3K+6C/0/gVDQTXwL6CdbZPwPOuuA3VDA5x/u8m6a BWKQgKnC7gQ/ea6HAIXbm+twaTB5Hdckd9r+9bz/kYCFgmi8viyFnVNKmJkPS3hLSX 05vkOuUFG7Zk5mEU/8aTnfiJmPoELOeoK3+FoILQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1375092587; i=@resistor.net; bh=4YdKRlp8gtwxOqYZ94yV/bCupduQPlXZ3J7atan3vvA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=mwYO6Bo0pgDXdScGu/hRdkCXsdG6FWEstrPplSi/uOaivf3oa0nYU9uD/8tAEz0vW IKxRFkTqDJ8yzhksN71iZbcQnhS7K3PYPIAEUwLHopfBSShKjq6/hc1PVObzMnNCKT 7GtrRD1ZRgFb+YqTeujaBh4gFi5ZST8zpQQJRW2g=
Message-Id: <6.2.5.6.2.20130729015035.06eb3500@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 29 Jul 2013 03:08:49 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Remote participants, newcomers, and tutorials
In-Reply-To: <51F5FCB6.6060006@dcrocker.net>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net> <2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net> <51F3BBB6.5030406@dcrocker.net> <51F42F7B.2060706@gmail.com> <E12475C2-B005-42A7-A662-F36F55BB953E@piuha.net> <51F5FCB6.6060006@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: dcrocker@bbiw.net
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Jul 2013 10:09:53 -0000

At 22:25 28-07-2013, Dave Crocker wrote:
>I've been finding discussion and actions about newcomers far more 
>interesting this year, than most previous ones.  So I think it's 
>worth pressing on several fronts, to see how we can both accommodate 
>such folk better, as well as be clear about when and where and how 
>such accommodation is /and is not/ appropriate.

The keyword in the above is "actions".  Some actions do not require 
the agreement of the entire IETF.  In other words, an action does not 
require consensus if it is not mandatory.

>Your reply to me, above, lists different types of new folk -- and of 
>course the list is reasonable and might be useful -- but I didn't 
>see the actual clarification of what you felt was wrong in the 
>target text or how you agreed with me an others.  So, now you've got 
>me curious for that detail...

A public discussion can be started with:

  (a) I will be listening to your comment.

  (b) You must have read X, Y, and Z before you comment.

  (c) Be sure that you are not wasting my time when you comment.

I'll argue that (b) and (c) are trying to stop problems before they 
happen.  (b) looks like the type of thing which ought to be explained 
during the orientation.  (b) is not a problem caused by remote 
participants as it is possible to provide an explanation through the 
Jabber room.  (c) is intimidating.  I would choose (a).

>      My suggestion is for a 'status' page that gives a brief 
> summary about the current state of the working group, ideally 
> listing the current, near-term vector of the work -- what's the 
> current focus of effort -- and major open issues.
>
>      I'll suggest that it be updated after every meeting.
>
>Arguably, this sort of status statement is good to have even without 
>newcomers, since it forces working groups to face the question of 
>what progress they are and are not making.

The simpler form might be to update the milestones so that anyone can 
read about the work the working group is planning to do and when it 
is planning to do it.  It also provides information about the work 
that the working group has completed.

On the topic of remote participation I'll mention that the current 
approach is to open a trouble ticket when there is a problem.  A 
status web page could provide some visibility about whether the 
services are running correctly, whether there is a known problem, 
etc.   Notifications could be sent to xmpp:hallway@jabber.ietf.org so 
that people do not hit the reload button repeatedly.

Regards,
-sm 


From jcurran@istaff.org  Mon Jul 29 04:03:13 2013
Return-Path: <jcurran@istaff.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28AE421F99F8 for <ietf@ietfa.amsl.com>; Mon, 29 Jul 2013 04:03:12 -0700 (PDT)
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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mYw2Qa5Ksv0q for <ietf@ietfa.amsl.com>; Mon, 29 Jul 2013 04:03:07 -0700 (PDT)
Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) by ietfa.amsl.com (Postfix) with ESMTP id BF26111E8174 for <ietf@ietf.org>; Mon, 29 Jul 2013 03:59:25 -0700 (PDT)
Received: from pool-71-191-247-90.washdc.fios.verizon.net ([71.191.247.90] helo=diamond.istaff.org) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.72) (envelope-from <jcurran@istaff.org>) id 1V3lAj-000LkZ-AR for ietf@ietf.org; Mon, 29 Jul 2013 10:59:25 +0000
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Originating-IP: 71.191.247.90
X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX1968I8JGzwGsMhdIhIdPCzQ
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: moving more responsibility to working groups
From: John Curran <jcurran@istaff.org>
In-Reply-To: <A7CEFA3E-A71B-45A0-A50A-004BDCB6F685@ietf.org>
Date: Mon, 29 Jul 2013 06:59:22 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <5E7D293A-077D-42C7-B7E6-42ABDA606669@istaff.org>
References: <A7CEFA3E-A71B-45A0-A50A-004BDCB6F685@ietf.org>
To: "ietf@ietf.org list" <ietf@ietf.org>
X-Mailer: Apple Mail (2.1508)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Jul 2013 11:03:14 -0000

Jari -=20
=20
  Thanks for the excellent writeup of the situation; the hypothesis
  regarding the problem and the experiment to address look to be a
  an appropriate response.

Thanks!
/John

On Jul 29, 2013, at 5:07 AM, IETF Chair <chair@ietf.org> wrote:

> I would like to report an experiment that the IESG is starting. =
(There's also an associated blog article about this at =
http://www.ietf.org/blog/2013/07/the-role-of-working-groups/)
>=20
> Internet Drafts sent for approval as RFCs are reviewed by individuals =
during the IETF Last Call, the Area Directors, IANA, as well as a number =
of volunteers from various directorates and review teams. The reviews =
from these teams has gained a significant role in ensuring that the IETF =
produces high-quality, understandable and implementable RFCs.
>=20
> Yet, as discussed in =
http://www.ietf.org/blog/2013/05/balancing-the-process/ we have a =
general problem that quite a lot of the work around IETF documents =
happens at the end of the process. In particular, a number of the =
reviews during IETF last call point out issues that end up being raised =
by the IESG as comments. It is of course good that issues are caught, =
but raising them earlier would be better. And it would be better if the =
working groups - the intended focus point of work on a topic - would get =
to handle them, as opposed to raising these issues with the IESG. The =
has IESG discussed these issues and decided to experiment with three =
actions designed to move more work to the responsibility of the working =
groups:
>=20
> (1) Perform some reviews that are now happening at IETF Last Call a =
bit earlier. This will put the working group in a bigger role in =
resolving cross-area and general issues.
>=20
> (2) Invite document shepherds on IESG telechats when there's a =
document that is likely to require discussion. This will make it =
possible for the document shepherd to be directly involved in the =
discussions.=20
>=20
> (3) When a document up for approval has a number of issues, hand over =
the process back to the working group, as opposed to the IESG tracking =
the issues. Among other things, this will ensure that changes are =
discussed in an open working group list and agreed through consensus.
>=20
> We are at the beginning of the experiment. We've done (2) and (3) a =
few times and plan to use it more from now on. We are discussing with =
the review teams to plan how (1) comes into effect. Building quality and =
cross-area review to the process earlier is of course a big effort. We =
are making a small change to current directorate review procedures. If =
successful, this will enable working groups to deal with issues before =
IETF Last Call and IESG review and empower the working groups to be in =
charge of the documents throughout their life cycle. We are also hoping =
that document quality will improve and number of issues discussed in the =
IESG will be lower.
>=20
> =46rom the point of view of the document authors and WG participants, =
all the above works through your working group chairs. They will be =
talking to you when documents come back to the working group. They or =
the document shepherds will be even more part of the IESG discussions =
and will keep the working groups updated on the progress of the =
documents. They will work with review teams to request earlier review. =
You will be seeing some reviews in the working group mailing lists. The =
current plan is to do these reviews after WGLC has completed, in =
parallel with ongoing reviews from your responsible ADs and chairs =
preparing the write-ups for the document to be submitted to the IETF =
Last Call.
>=20
> While the number of reviews as such is not changed, some additional =
effort and care will however be required from the reviewers, directorate =
coordinators/secretaries, the working group chairs, and other =
participants. The experiment will show us whether this effort is =
reasonable and if there are any unexpected effects. The experiment is =
performed on a voluntary basis by each directorate, for a limited number =
of drafts at the beginning.
>=20
> We will be collecting experiences so that in six months we can =
evaluate the experience. I would also like to thank the document =
shepherds, chairs, and review teams for participation in this effort!
>=20
> Jari
>=20


From jsalowey@cisco.com  Mon Jul 29 04:08:32 2013
Return-Path: <jsalowey@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3349A21F9655 for <ietf@ietfa.amsl.com>; Mon, 29 Jul 2013 04:08:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.299
X-Spam-Level: 
X-Spam-Status: No, score=-110.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_36=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YQkqzc5FZjkq for <ietf@ietfa.amsl.com>; Mon, 29 Jul 2013 04:08:27 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 5368311E8116 for <ietf@ietf.org>; Mon, 29 Jul 2013 04:03:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9150; q=dns/txt; s=iport; t=1375095821; x=1376305421; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=m9IuNAiPEa8jwxNSM+Hksao0qIZfXg2BwKWpwNIQFyw=; b=RqeIHfUSqnqkrAYHydtn100CqZpJA3m7YUirpCQ9tzMNeddwimSwRLW7 akNDO368hiYQf2ZTzwQE0N4xFWne0l/u0HfxZVDt+zFh1e0RCNC16sPdS K3GfYOtBljKUK1QMAvrMJDPDC6btz5fkfdF+lfaxtC55Jw3kIOQAswnpI k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgkFADxL9lGtJV2Z/2dsb2JhbABSCYMGgQW9V4EWFnSCJAEBAQMBDGYHBQsCAQgiGQsyJQIEDgUIDod0Brd8jkUJfAIxB4MYbwOIcosWlSOBW4E5gWoHFwYc
X-IronPort-AV: E=Sophos;i="4.89,768,1367971200"; d="scan'208";a="240767039"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-6.cisco.com with ESMTP; 29 Jul 2013 11:03:34 +0000
Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r6TB3YAu018978 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 29 Jul 2013 11:03:34 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.235]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.02.0318.004; Mon, 29 Jul 2013 06:03:33 -0500
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: Stefan Winter <stefan.winter@restena.lu>
Subject: Re: Last Call: <draft-ietf-emu-eap-tunnel-method-07.txt> (Tunnel EAP	Method (TEAP) Version 1) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-emu-eap-tunnel-method-07.txt> (Tunnel EAP	Method (TEAP) Version 1) to Proposed Standard
Thread-Index: AQHOhu8X+X5wOZU5LEmRElkL1BqFrJl73HoA
Date: Mon, 29 Jul 2013 11:03:33 +0000
Message-ID: <A95B4818FD85874D8F16607F1AC7C628D8EEF2@xmb-rcd-x09.cisco.com>
References: <51ED4DBC.5000409@restena.lu>
In-Reply-To: <51ED4DBC.5000409@restena.lu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.21.79.148]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <E4ACBD79AD685147AB2AEBBF1E90C101@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Jul 2013 11:08:32 -0000

On Jul 22, 2013, at 8:20 AM, Stefan Winter <stefan.winter@restena.lu> wrote=
:

> Hello,
>=20
> I didn't follow TEAP's creation process in enough detail, so may have
> missed some information. Apologies if what I write below is noise.
>=20
> I have two questions about TEAP Version 1 which I don't find
> satisfactorily answered in the draft. I wonder if they are worth a
> discussion.
>=20
> Q1: How to determine Server-ID /deterministically/ ?
> =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=3D=
=3D=3D=3D
> One crucial check for an EAP peer to execute is whether it is talking to
> the server it expects to; the primary means are:
> a) is the server certificate issued by a CA the EAP peer trusts for the
> purposes of EAP?
> b) is the name of the server the expected one?
>=20
> a) is pretty clear, RFC5280 section 6 provides for an algorithm to
> determine whether a given certificate was issued by a trusted anchor;
> and that RFC is referenced in the TEAP draft.
>=20
> b) is less clear. The TEAP draft in section 3.4 states
>  "the Server-Id is determined in a similar fashion as stated
>   above for the Peer-Id; e.g., the subject or subjectAltName field in
>   the server certificate defines the Server-Id."
>=20
> First of all, I think the "e.g." should be an "i.e." because these two
> fields are the only part of the certificate that yields server identity
> information.
>=20
> More important than that though is the deliberately indeterministic "or"
> in that sentence.
>=20
> Certificates may carry only a Subject DN, or only subjectAltNames, or
> both; if they carry both names, the CN part of the DN may be the same as
> one of the subjectAltName values, or it may not.
>=20
> With the sentence being an "or", EAP peer implementations which are
> configured to trust a sever name "aaa.foo.bar" can be presented the same
> certificate, but come to different conclusions whether this is the
> server they expect, depending on
> 1) the order in which they inspect the fields (first DN, or first sANs)
> 2) how they behave if their preferred field does not match or is not
> part of the certificate (bail out, or try the other field)
> 3) how they behave if they observe discrepancies between the two (e.g.
> CN matches, but there are sANs and none of them matches the CN).
>=20
> The draft could make this behaviour deterministic with a few simple rules=
.
>=20
> 1) prefer the set of subjectAltName:DNS fields over CN
> 2) fallback to CN if none of the subjectAltName fields matches
> 3) discrepancies between the two fields are not enforced
>=20
> Of course, some EAP peer might be configured for "strange" other sANs;
> maybe sAN:iPAddr. The validation rules above would then be analogous for
> these fields.
>=20

[Joe] In the case of multiple authentications multiple identities are expor=
ted so I would think that if there are multiple subject names in the certif=
icate then they should all be exported.  Something like replacing or with a=
nd

"When X.509 certificates are used for peer authentication, the Peer-Id is d=
etermined by the subject and subjectAltName fields in the peer certificate.=
 "

similar for server-ID



> Q2: Does the draft need text regarding i18n in EAP-Response/Identity?
> =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=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> In the recent discussion about ABFAB's eapapplicability document, we
> concluded that either EAP or all the EAP methods need patching up to
> prevent an encoding/normalisation mess. With TEAP being in IETF LC, I
> took a look at how it handles User-Name encoding, normalisation, and
> whether there is a nice place inside the TEAP spec to nail things.
>=20
> TEAP takes the (sensible) approach of not caring how its own context
> came to be. It states in its Protocol Overview:
>=20
>  "TEAP authentication occurs in two phases after the initial EAP
>   Identity request/response exchange."
>=20
> I.e. it simply assumes that EAP peer and EAP server "somehow" found each
> other and decided to use TEAP.
>=20
> It defines Peer ID's in its phase two; for basic auth it sanely mandates
> UTF-8 encoding for these (but no word about normalisation); section 4.2.1=
5.
>=20
> Where TEAPs inner method is EAP - there are no provisions regarding
> encoding or normalisation. That is the same situation that EAP (outside)
> has as well; TEAP basically becomes an EAP lower layer itself. I guess
> the draft expects that the inner method has some notion of a username,
> and the inner method will export it to the EAP-Response/Identity of
> TEAP's phase 2 EAP exchange.
>=20
> So in phase 2 of TEAP, there's either UTF-8, or an unknown encoding
> inherited from an inner EAP method.
> [As an aside: If the inner method if EAP-TLS, then the ambiguity from
> question 1 occurs again: the Peer-Id is the subject "or" a
> subjectAltName (if there's a set of subjectAltNames in the certificate
> *which* is considered the Peer-Id? That should be clarified in the draft)=
.]
>=20
> TEAP mentions that username privacy is optional. If username privacy is
> not used, then the common way of constructing EAP-Identity is by taking
> the string that is going to used during phase 2 and put that into the
> EAP-Response/Identity. In that case, the encoding being used for that
> EAP-Response/Identity is unknown with TEAP; because it may depend on an
> inner EAP method which is not known to TEAP, and where TEAP cannot
> mandate UTF-8.
>=20
> If username privacy is used, there is no relation to the phase 2
> identity and what's put into EAP-Response/Identity. In particular, the
> encoding is not fixed.
>=20
> TEAP mentions in its section on that topic that NAIs exist, and
> references RFC4282, which has known deficiencies in terms of i18n. I
> believe it would be better not to mention RFC4282.
>=20
> It is good that NAIs are not mentioned normatively in that section;
> after all Peer-Ids and also anonymous outer identities may or may not be
> NAI realms - they can also be simple strings with no particular
> structure. But since they can be just that - simple strings with no
> structure - there is also no encoding known for these incoming strings.
>=20
> I know, TEAP doesn't (and doesn't *have to*) care about the outer
> identities, because they happen outside of itself and are not of
> importance for neither its phase 1 or 2.
>=20
> And still, some spec needs to say something about the encoding! Or we'll
> never have clarity about what's coming in.
>=20
> After taking a step back, looking at where to properly fix things, I'm
> becoming more and more convinced that chasing individual EAP methods to
> include normative language about something that happens outside their
> own method-protocol; and in TEAP's case being at the whim that some
> other EAP method which happens to have been configured as TEAPs inner
> method has already done its homework to include provisions about
> exporting its inner IDs in a sane format for the TEAP exchange as a
> whole to become deterministically encoded is - impractical.
>=20
> The much more straightforward approach is to mandate EAP (core) to
> always force use of UTF-8 for EAP-Response/Identity.
>=20
> In summary (kudos for reading this far!)
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> IMHO, TEAP should fix the following points
>=20
> * Peer-Id and Server-Id should become deterministic.
> * When discussing NAIs, mentions of RFC4282 should be removed, or
> qualified so that readers of spec are urged to read (exclusively) its
> successor as soon as it becomes available.
>=20

[Joe]  I think the main issue is making the realm portion of the NAI consis=
tent with DNS name representation.   If we need to we can add something tha=
t says:

Ongoing work clarifying the usage of UTF-8 in the NAI in [draft-radext-nai]=
 will update or replace [RFC4282].

> Things that might be tackled in TEAP, but my personal preference would
> be to do that in EAP core:
>=20

[Joe] I do not think we should tackle these issues in TEAP. =20


> * Specify the encoding in which phase 2's Peer-Id is used during the EAP
> negotiation that precedes the TEAP exchange. If Peer-Ids are not used
> (i.e. identity privacy support is enabled), specify in which encoding
> the privacy-preserving identity hints are expected.
>=20
> Thanks for reading this :-)
>=20
> Note how I did not go into detail about normalization; similar
> principles apply here, but the mail is long enough.
>=20
> Greetings,
>=20
> Stefan Winter
>=20
> --=20
> Stefan WINTER
> Ingenieur de Recherche
> Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education National=
e et
> de la Recherche
> 6, rue Richard Coudenhove-Kalergi
> L-1359 Luxembourg
>=20
> Tel: +352 424409 1
> Fax: +352 422473
>=20


From adrian@olddog.co.uk  Mon Jul 29 04:26:16 2013
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9300921F9FE5; Mon, 29 Jul 2013 04:26:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.413
X-Spam-Level: 
X-Spam-Status: No, score=-2.413 tagged_above=-999 required=5 tests=[AWL=0.186,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gBCpFlH6JA3s; Mon, 29 Jul 2013 04:26:09 -0700 (PDT)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by ietfa.amsl.com (Postfix) with ESMTP id 44BF421F9E9C; Mon, 29 Jul 2013 04:26:08 -0700 (PDT)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id r6TBQ4Ht002429;  Mon, 29 Jul 2013 12:26:04 +0100
Received: from 950129200 (dhcp-45d9.meeting.ietf.org [130.129.69.217]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id r6TBQ3td002342 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 29 Jul 2013 12:26:04 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <ietf@ietf.org>, <87all@ietf.org>
References: <20130729111753.24528.44252.idtracker@ietfa.amsl.com>
In-Reply-To: <20130729111753.24528.44252.idtracker@ietfa.amsl.com>
Subject: RE: [87all] IETF 87 - InterContinental Lunch Options
Date: Mon, 29 Jul 2013 12:26:02 +0100
Message-ID: <052e01ce8c4e$6930b2e0$3b9218a0$@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: AQHgap53qWCpqjAtJ/+NOEr/E4zAD5lXxylg
Content-Language: en-gb
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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, 29 Jul 2013 11:26:17 -0000

> Clarifications on Lunch Options at the InterContinental:
> 
> Grab-N-Go is only available at the Marlene Bar. A limited variety of salads
and
> currywurst will be available.

And it was tasty.
But turned out to be "grab and wait for it to be prepared by a caring and
meticulous chef"

Adrian


From kathleen.moriarty@emc.com  Mon Jul 29 04:40:27 2013
Return-Path: <kathleen.moriarty@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89AA521F9C29 for <ietf@ietfa.amsl.com>; Mon, 29 Jul 2013 04:40:27 -0700 (PDT)
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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d2BlLcFA8zGQ for <ietf@ietfa.amsl.com>; Mon, 29 Jul 2013 04:40:22 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 12BCA21F9BC3 for <ietf@ietf.org>; Mon, 29 Jul 2013 04:40:20 -0700 (PDT)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r6TBeKhd008450 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 29 Jul 2013 07:40:20 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd04.lss.emc.com [10.254.222.226]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Mon, 29 Jul 2013 07:40:02 -0400
Received: from mxhub12.corp.emc.com (mxhub12.corp.emc.com [10.254.92.107]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r6TBe14T018401; Mon, 29 Jul 2013 07:40:01 -0400
Received: from mx15a.corp.emc.com ([169.254.1.184]) by mxhub12.corp.emc.com ([10.254.92.107]) with mapi; Mon, 29 Jul 2013 07:40:01 -0400
From: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
To: John Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
Date: Mon, 29 Jul 2013 07:39:03 -0400
Subject: RE: Remote participants, newcomers, and tutorials (was: IETF87 Audio Streaming Info)
Thread-Topic: Remote participants, newcomers, and tutorials (was: IETF87 Audio Streaming Info)
Thread-Index: Ac6LFQOaB/6rwH9aQjqmJl8sdSX9gABOzYB/
Message-ID: <F5063677821E3B4F81ACFB7905573F24DF0532EB@MX15A.corp.emc.com>
References: <8BA59F96-A1DE-460F-9A22-F2CD4CE5F31C@emc.com>, <20130727220036.3517.qmail@joyce.lan>
In-Reply-To: <20130727220036.3517.qmail@joyce.lan>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Jul 2013 11:40:27 -0000

I will see what I can do and will share back the results.  It may not be so=
mething that would be useful to all working groups, but I think it could he=
lp mine and some others.

Thanks,
Kathleen
________________________________________
From: John Levine [johnl@taugh.com]
Sent: Saturday, July 27, 2013 6:00 PM
To: ietf@ietf.org
Cc: Moriarty, Kathleen
Subject: Re: Remote participants, newcomers, and tutorials (was: IETF87 Aud=
io Streaming Info)

In article <8BA59F96-A1DE-460F-9A22-F2CD4CE5F31C@emc.com> you write:
>I think it would be really helpful/useful if working groups could provide =
short
>video overviews to help people understand the work.  This includes newcome=
rs and
>also interested observers, who may include implementers.  Can that be
>accommodated, maybe at a future meeting?  I am happy to help if I can.

I gather you're active in the MILE group.  How about making a video
overview for it and let us know how it went?  If we make videos, we
can put it on the web and not take up time at WG meetings.

Having made my share of five minute videos, I've found that a PC with
a webcam and cheap video recording and editing software (to add a
title and splice together the pieces) is all you need technically, but
coming up with a script, getting the required people to agree that
it's OK, and recording it in a way that is watchable is a surprisingly
large amount of work.

R's,
John

From spromano@unina.it  Mon Jul 29 05:11:14 2013
Return-Path: <spromano@unina.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D06D821F9DC7 for <ietf@ietfa.amsl.com>; Mon, 29 Jul 2013 05:11:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.718
X-Spam-Level: 
X-Spam-Status: No, score=-100.718 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GUkDKWblktDn for <ietf@ietfa.amsl.com>; Mon, 29 Jul 2013 05:11:09 -0700 (PDT)
Received: from smtp2.unina.it (smtp2.unina.it [192.132.34.62]) by ietfa.amsl.com (Postfix) with ESMTP id A4B7521F9E0B for <ietf@ietf.org>; Mon, 29 Jul 2013 05:11:08 -0700 (PDT)
Received: from dhcp-1483.meeting.ietf.org (dhcp-1483.meeting.ietf.org [130.129.20.131]) (authenticated bits=0) by smtp2.unina.it (8.14.4/8.14.4) with ESMTP id r6TCB2QJ002458 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 29 Jul 2013 14:11:05 +0200
From: Simon Pietro Romano <spromano@unina.it>
Content-Type: multipart/alternative; boundary="Apple-Mail=_AF918D20-DB6B-42E2-BA45-5EEC3A4CE462"
Subject: Opus experiment via WebRTC at today's plenary
Date: Mon, 29 Jul 2013 14:11:01 +0200
Message-Id: <4D750009-6E45-4959-B725-8680C45FDB3E@unina.it>
To: "ietf@ietf.org list" <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1283)
X-Mailer: Apple Mail (2.1283)
Cc: team@meetecho.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Jul 2013 12:11:14 -0000

--Apple-Mail=_AF918D20-DB6B-42E2-BA45-5EEC3A4CE462
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Dear all,

in view of today's plenary, we set up a short tutorial page on the =
WebRTC interface you can use to interact with the room if you are =
remote. You can find this stuff at the following URL:

http://ietf87.conf.meetecho.com/index.php/WebRTC_Interface

Hope this helps,

Simon

                     					       _\\|//_
                           				      ( O-O )
   ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
                    				Simon Pietro Romano
             				 Universita' di Napoli Federico =
II
                		     Computer Engineering Department=20
	             Phone: +39 081 7683823 -- Fax: +39 081 7683816
                                           e-mail: spromano@unina.it

		    <<Molti mi dicono che lo scoraggiamento =CB l'alibi =
degli=20
		    idioti. Ci rifletto un istante; e mi scoraggio>>. =
Magritte.
               			                     oooO
  ~~~~~~~~~~~~~~~~~~~~~~~(   )~~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
					                 \ (            =
(   )
			                                  \_)          ) =
/
                                                                       =
(_/






--Apple-Mail=_AF918D20-DB6B-42E2-BA45-5EEC3A4CE462
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Dear =
all,<div><br></div><div>in view of today's plenary, we set up a short =
tutorial page on the WebRTC interface you can use to interact with the =
room if you are remote. You can find this stuff at the following =
URL:</div><div><br></div><div><a =
href=3D"http://ietf87.conf.meetecho.com/index.php/WebRTC_Interface">http:/=
/ietf87.conf.meetecho.com/index.php/WebRTC_Interface</a></div><div><br></d=
iv><div>Hope this =
helps,</div><div><br></div><div>Simon</div><div><br><div =
apple-content-edited=3D"true">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-align: -webkit-auto; text-indent: 0px; text-transform: none; =
white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div>&nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
	</span><span class=3D"Apple-converted-space">&nbsp;</span>&nbsp; =
&nbsp; &nbsp; _\\|//_</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
</span>&nbsp; &nbsp; &nbsp;&nbsp;( O-O )</div><div>&nbsp; =
&nbsp;~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~</div><di=
v>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;<span class=3D"Apple-converted-space">&nbsp;</span><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
</span>Simon Pietro Romano</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;<span class=3D"Apple-tab-span" style=3D"white-space: pre; =
">				</span><span =
class=3D"Apple-converted-space">&nbsp;</span>Universita' di Napoli =
Federico II</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;&nbsp;<span class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
	</span>&nbsp; &nbsp; &nbsp;Computer Engineering =
Department&nbsp;</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	</span>&nbsp; &nbsp; &nbsp;&nbsp; &nbsp; =
&nbsp; &nbsp; Phone: +39 081 7683823 -- Fax: +39 081 =
7683816</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;e-mail: <a =
href=3D"mailto:spromano@unina.it">spromano@unina.it</a></div><div><br></di=
v><div><span class=3D"Apple-tab-span" style=3D"white-space: pre; ">		=
</span>&nbsp; &nbsp; &lt;&lt;Molti mi dicono che lo scoraggiamento =CB =
l'alibi degli&nbsp;</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">		</span>&nbsp;&nbsp; =
&nbsp;idioti. Ci rifletto un istante; e mi scoraggio&gt;&gt;. =
Magritte.</div><div>&nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; =
&nbsp;<span class=3D"Apple-converted-space">&nbsp;</span><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">			=
</span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;oooO</div><div>&nbsp; ~~~~~~~~~~~~~~~~~~~~~~~( &nbsp; =
)~~~&nbsp;Oooo~~~~~~~~~~~~~~~~~~~~~~~~~</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
	</span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;\ ( &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;( &nbsp; =
)</div><div><span class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
		</span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
\_) &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;) /</div><div>&nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp;(_/</div></div><div><br></div></div></span><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<br></div></body></html>=

--Apple-Mail=_AF918D20-DB6B-42E2-BA45-5EEC3A4CE462--

From mary.h.barnes@gmail.com  Mon Jul 29 05:38:35 2013
Return-Path: <mary.h.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34A7121F8425 for <ietf@ietfa.amsl.com>; Mon, 29 Jul 2013 05:38:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lk8mjrnVt-rA for <ietf@ietfa.amsl.com>; Mon, 29 Jul 2013 05:38:32 -0700 (PDT)
Received: from mail-vb0-x22a.google.com (mail-vb0-x22a.google.com [IPv6:2607:f8b0:400c:c02::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 62AC821F9D0F for <ietf@ietf.org>; Mon, 29 Jul 2013 05:38:24 -0700 (PDT)
Received: by mail-vb0-f42.google.com with SMTP id e12so656950vbg.15 for <ietf@ietf.org>; Mon, 29 Jul 2013 05:38:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Jn9dMRGflJAjxdNVzWfyf6ia3xF/lc9lL5yklxjAPVw=; b=c71U6kt6PZ1qB1cs95uJUzL13h1yzSIcDeytZWKKlCKk2u/VKL2KTrVXmQmDsgYuKw X/PU6z7jFhfBTtA34lPaZRTBbJFVl/P1XwZO82LjTuojjKDJJLAMttxfPeKW6repE18J oZacKgj4cCtO1QqdvFcoHS1lJ55SpEnQdEXOPr4JpQ6ebVvgnDbTMbNcL2xRURr4fiqX 1keMDc4FFA/vI9mUcj9zB0bH6+WdC5qlSSFlorW5Yf71dqlSwiaR9GpF6LoXl5TDukHn oAyrR1zqt26EM60FZkY6BmWIqpLag0OVfX5MoJ8nqHLUUZu5g3KBbRsYZ1SNe/DraaAR zyeg==
MIME-Version: 1.0
X-Received: by 10.220.183.10 with SMTP id ce10mr8233751vcb.41.1375101503637; Mon, 29 Jul 2013 05:38:23 -0700 (PDT)
Received: by 10.58.74.97 with HTTP; Mon, 29 Jul 2013 05:38:23 -0700 (PDT)
In-Reply-To: <F5063677821E3B4F81ACFB7905573F24DF0532EB@MX15A.corp.emc.com>
References: <8BA59F96-A1DE-460F-9A22-F2CD4CE5F31C@emc.com> <20130727220036.3517.qmail@joyce.lan> <F5063677821E3B4F81ACFB7905573F24DF0532EB@MX15A.corp.emc.com>
Date: Mon, 29 Jul 2013 07:38:23 -0500
Message-ID: <CABmDk8=w4L42PZUt2t3s-yieQHwGvXY=MrWDpgyRWH7y2TGGxA@mail.gmail.com>
Subject: Re: Remote participants, newcomers, and tutorials (was: IETF87 Audio Streaming Info)
From: Mary Barnes <mary.h.barnes@gmail.com>
To: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
Content-Type: multipart/alternative; boundary=089e01536dc4a7930604e2a5c44a
Cc: John Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Jul 2013 12:38:35 -0000

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

We did a lunchtime tutorial for the CLUE WG in Vancouver.  We had the
Meetecho guys record it:
http://ietf84.conf.meetecho.com/index.php/Recorded_Sessions#IETF84_CLUE_TUTORIAL

It worked quite well I think.  I believe these sorts of tutorials would be
extremely helpful for a number of WGs.  Having it during the f2f sessions
provides an opportunity to ask questions, but then it's available
afterwards for those that can't attend.   We put the link in the minutes in
the proceedings, but I'm realizing that it would be very useful to have
that on the WG wiki (which I've now done).

Mary.


On Mon, Jul 29, 2013 at 6:39 AM, Moriarty, Kathleen <
kathleen.moriarty@emc.com> wrote:

> I will see what I can do and will share back the results.  It may not be
> something that would be useful to all working groups, but I think it could
> help mine and some others.
>
> Thanks,
> Kathleen
> ________________________________________
> From: John Levine [johnl@taugh.com]
> Sent: Saturday, July 27, 2013 6:00 PM
> To: ietf@ietf.org
> Cc: Moriarty, Kathleen
> Subject: Re: Remote participants, newcomers, and tutorials (was: IETF87
> Audio Streaming Info)
>
> In article <8BA59F96-A1DE-460F-9A22-F2CD4CE5F31C@emc.com> you write:
> >I think it would be really helpful/useful if working groups could provide
> short
> >video overviews to help people understand the work.  This includes
> newcomers and
> >also interested observers, who may include implementers.  Can that be
> >accommodated, maybe at a future meeting?  I am happy to help if I can.
>
> I gather you're active in the MILE group.  How about making a video
> overview for it and let us know how it went?  If we make videos, we
> can put it on the web and not take up time at WG meetings.
>
> Having made my share of five minute videos, I've found that a PC with
> a webcam and cheap video recording and editing software (to add a
> title and splice together the pieces) is all you need technically, but
> coming up with a script, getting the required people to agree that
> it's OK, and recording it in a way that is watchable is a surprisingly
> large amount of work.
>
> R's,
> John
>

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

<div dir=3D"ltr">We did a lunchtime tutorial for the CLUE WG in Vancouver. =
=A0We had the Meetecho guys record it:<div><a href=3D"http://ietf84.conf.me=
etecho.com/index.php/Recorded_Sessions#IETF84_CLUE_TUTORIAL">http://ietf84.=
conf.meetecho.com/index.php/Recorded_Sessions#IETF84_CLUE_TUTORIAL</a></div=
>
<div><br><div>It worked quite well I think. =A0I believe these sorts of tut=
orials would be extremely helpful for a number of WGs. =A0Having it during =
the f2f sessions provides an opportunity to ask questions, but then it&#39;=
s available afterwards for those that can&#39;t attend. =A0 We put the link=
 in the minutes in the proceedings, but I&#39;m realizing that it would be =
very useful to have that on the WG wiki (which I&#39;ve now done).=A0<br>
</div><div><div><br></div><div>Mary.=A0</div></div></div></div><div class=
=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Mon, Jul 29, 2013 at=
 6:39 AM, Moriarty, Kathleen <span dir=3D"ltr">&lt;<a href=3D"mailto:kathle=
en.moriarty@emc.com" target=3D"_blank">kathleen.moriarty@emc.com</a>&gt;</s=
pan> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">I will see what I can do and will share back=
 the results. =A0It may not be something that would be useful to all workin=
g groups, but I think it could help mine and some others.<br>

<br>
Thanks,<br>
Kathleen<br>
________________________________________<br>
From: John Levine [<a href=3D"mailto:johnl@taugh.com">johnl@taugh.com</a>]<=
br>
Sent: Saturday, July 27, 2013 6:00 PM<br>
To: <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br>
Cc: Moriarty, Kathleen<br>
Subject: Re: Remote participants, newcomers, and tutorials (was: IETF87 Aud=
io Streaming Info)<br>
<br>
In article &lt;<a href=3D"mailto:8BA59F96-A1DE-460F-9A22-F2CD4CE5F31C@emc.c=
om">8BA59F96-A1DE-460F-9A22-F2CD4CE5F31C@emc.com</a>&gt; you write:<br>
&gt;I think it would be really helpful/useful if working groups could provi=
de short<br>
&gt;video overviews to help people understand the work. =A0This includes ne=
wcomers and<br>
&gt;also interested observers, who may include implementers. =A0Can that be=
<br>
&gt;accommodated, maybe at a future meeting? =A0I am happy to help if I can=
.<br>
<br>
I gather you&#39;re active in the MILE group. =A0How about making a video<b=
r>
overview for it and let us know how it went? =A0If we make videos, we<br>
can put it on the web and not take up time at WG meetings.<br>
<br>
Having made my share of five minute videos, I&#39;ve found that a PC with<b=
r>
a webcam and cheap video recording and editing software (to add a<br>
title and splice together the pieces) is all you need technically, but<br>
coming up with a script, getting the required people to agree that<br>
it&#39;s OK, and recording it in a way that is watchable is a surprisingly<=
br>
large amount of work.<br>
<br>
R&#39;s,<br>
John<br>
</blockquote></div><br></div>

--089e01536dc4a7930604e2a5c44a--

From barryleiba.mailing.lists@gmail.com  Mon Jul 29 05:39:33 2013
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D8A221F9BA2; Mon, 29 Jul 2013 05:39:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.97
X-Spam-Level: 
X-Spam-Status: No, score=-101.97 tagged_above=-999 required=5 tests=[AWL=0.008, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7s2lPovCC7tY; Mon, 29 Jul 2013 05:39:32 -0700 (PDT)
Received: from mail-vb0-x22e.google.com (mail-vb0-x22e.google.com [IPv6:2607:f8b0:400c:c02::22e]) by ietfa.amsl.com (Postfix) with ESMTP id B9C3E21F9DF7; Mon, 29 Jul 2013 05:39:27 -0700 (PDT)
Received: by mail-vb0-f46.google.com with SMTP id p13so250512vbe.5 for <multiple recipients>; Mon, 29 Jul 2013 05:39:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=OY2vCzVv7ci99S5tDaPSMkiUy5X5UeZdpNN8SFO21qc=; b=PnXgyXmA8g60hDaZbBjhcxgllNPVDALZAq+Us0hKncqiRBlD+uMPFlTjdnl04/xPMh qtahkHkzeWqeCBXED4wAGJvyZbjVChJ7t2Cw/9sWy7+fNK/JFGRzwiBBLwRaEuPqeg5S dlqoznBVW6d8LI3I8QbeJb/0Lp2owbOW0xUpU5XkJhKW6886Gvk/fRLOWkNJNBcMHOxn Ux1eCXnoxN/OqcsDw7xLBjATJmUW3Iwm52n+5k3+orKGKkAvS8fXEtNaaZ/xQtvR6nZQ YhliriVhIagZsLgYsydiVKEp/20JbjIR32P1tOY6STqMybGGOvUBfU/GyNIyENUNXoTw 6HpQ==
MIME-Version: 1.0
X-Received: by 10.52.29.106 with SMTP id j10mr20801136vdh.77.1375101566596; Mon, 29 Jul 2013 05:39:26 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.137.227 with HTTP; Mon, 29 Jul 2013 05:39:26 -0700 (PDT)
In-Reply-To: <E1V3mLq-0002oG-00@www.xplot.org>
References: <20130729111753.24528.44252.idtracker@ietfa.amsl.com> <E1V3mLq-0002oG-00@www.xplot.org>
Date: Mon, 29 Jul 2013 08:39:26 -0400
X-Google-Sender-Auth: VJt8_DLezs3l2jHSrlOgbhLik7k
Message-ID: <CAC4RtVC2RjGp=rJhg2MgSUDKD0uXWhf+UFo=Dr4wGtcPa_YLcg@mail.gmail.com>
Subject: Re: [87attendees] [87all] IETF 87 - InterContinental Lunch Options
From: Barry Leiba <barryleiba@computer.org>
To: IETF discussion list <ietf@ietf.org>, 87attendees@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Jul 2013 12:39:33 -0000

> As far as I was able to tell, there were no grab-n-go options for
> lunch anywhere in the hotel today.

Indeed, and this is a serious problem.  We have lunch meetings, and
need these to be available, reasonably priced, and quick.

If people fine some Applications Area working group chairs to be
grumpy this afternoon, it's because most of them didn't have lunch --
they couldn't find it before they had to get to an App chairs lunch
meeting.

Barry

From hartmans@mit.edu  Mon Jul 29 06:10:59 2013
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6828221F9F96 for <ietf@ietfa.amsl.com>; Mon, 29 Jul 2013 06:10:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f5oJQK+G-kOw for <ietf@ietfa.amsl.com>; Mon, 29 Jul 2013 06:10:51 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 02A4021F9EE1 for <ietf@ietf.org>; Mon, 29 Jul 2013 06:10:35 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 855FF201FA; Mon, 29 Jul 2013 09:09:58 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Yx7T4k4iv5W; Mon, 29 Jul 2013 09:09:58 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (dhcp-4332.meeting.ietf.org [130.129.67.50]) (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; Mon, 29 Jul 2013 09:09:58 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id CDE2A87FB2; Mon, 29 Jul 2013 09:10:29 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: "Joseph Salowey \(jsalowey\)" <jsalowey@cisco.com>
Subject: Re: Last Call: <draft-ietf-emu-eap-tunnel-method-07.txt> (Tunnel EAP	Method (TEAP) Version 1) to Proposed Standard
References: <51ED4DBC.5000409@restena.lu> <A95B4818FD85874D8F16607F1AC7C628D8EEF2@xmb-rcd-x09.cisco.com>
Date: Mon, 29 Jul 2013 09:10:29 -0400
Message-ID: <tslr4ehse9m.fsf@mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Jul 2013 13:10:59 -0000

Hi.
While I don't mind clarifying the server ID discussion, I don't see that
server ID has any relation to how the peer validates the name in the
server certificate.
Quoting section 7.6:
7.6.  Server Certificate Validation

   As part of the TLS negotiation, the server presents a certificate to
      the peer.  The peer SHOULD verify the validity of the EAP server
         certificate, and SHOULD also examine the EAP server name presented in
	    the certificate, in order to determine whether the EAP server can be
	       trusted.  When performing server certificate validation
	          implementations MUST provide support rules in [RFC5280] for
		     validating certificates against a known trust anchor.  In addition,
		        implementations MUST support matching the realm portion of the peer's
			   NAI against a SubjectAltName of type dNSName within the server
			      certificate.  However, in certain deployments, this might not be
			         turned on.  Please note that in the case where the EAP authentication
				    is remoted, the EAP server will not reside on the same machine as the
				       authenticator, and therefore the name in the EAP server's certificate
				          cannot be expected to match that of the intended destination.  In
					     this case, a more appropriate test might be whether the EAP server's
					        certificate is signed by a CA controlling the intended domain and
						   whether the authenticator can be authorized by a server in that
						      domain.
						      

According to that text checking against a DNS name SAN is the
mandatory-to-implement naming check for server certificates.
That seems adequate to me.


From stpeter@stpeter.im  Mon Jul 29 06:59:04 2013
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 857AF21F9A29; Mon, 29 Jul 2013 06:59:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.454
X-Spam-Level: 
X-Spam-Status: No, score=-102.454 tagged_above=-999 required=5 tests=[AWL=0.145, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qmKA-OyBZiUa; Mon, 29 Jul 2013 06:58:54 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id AECE711E80F1; Mon, 29 Jul 2013 06:57:43 -0700 (PDT)
Received: from dhcp-10f3.meeting.ietf.org (unknown [130.129.16.243]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 0870B40049; Mon, 29 Jul 2013 07:59:50 -0600 (MDT)
Message-ID: <51F674D4.8010603@stpeter.im>
Date: Mon, 29 Jul 2013 15:57:40 +0200
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: IETF list <ietf@ietf.org>
Subject: Re: [websec] Last Call: <draft-ietf-websec-x-frame-options-07.txt> (HTTP Header	Field X-Frame-Options) to Informational RFC
References: <20130729093755.20677.91084.idtracker@ietfa.amsl.com>
In-Reply-To: <20130729093755.20677.91084.idtracker@ietfa.amsl.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: websec@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Jul 2013 13:59:04 -0000

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

On 7/29/13 11:37 AM, The IESG wrote:
> 
> The IESG has received a request from the Web Security WG (websec)
> to consider the following document: - 'HTTP Header Field
> X-Frame-Options' <draft-ietf-websec-x-frame-options-07.txt> as
> Informational RFC

Section 1 states:

   This specification provides informational documentation about the
   current use and definition of the X-Frame-Options HTTP header field.
   Given that the "X-" construction is deprecated [RFC6648], the X
   -Frame-Options header field will in the future be replaced by the
   Frame-Options directive in the Content Security Policy Version 1.1
   [CSP-1-1].

IMO, RFC 6648 does not necessitate deprecating the X-Frame-Options
header field in favor of the Frame-Options header field, since RFC
6648 is not retroactive. We might want to make the relationship
clearer here.

Peter

- -- 
Peter Saint-Andre
https://stpeter.im/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJR9nTUAAoJEOoGpJErxa2p+j0QAIh/eaMB0hj8C0YwFphmDE6w
bBnOaqLAEtb1A269cx9Uzx0+gjnQz+9PI0wvrev08kKWR4DFNxXNKAGC8rxJx6T/
dXcB3WjwDAg7iinoL+LRcP5ionE9519gU6V65Ff4IpkBpFiY2KhkC6FKV1AgeH7C
EIIpjHNH2dzeDQSBkYY1WGk5xDcXwoo+isUhF8TXhSf9mwY0NrUD2zO3UDDiAf//
ZTWbAH1vvMl4BDduq1bSt0Yt0H4gBtOOjeo86N0EsfHNoPPSOmHQ/4aX18rGa7/A
7ddk5GXFRmaLR6zLXCrOIWc+RSe5rIHOKk1Im2OC/S7D/t1zaDhRROLIekMGZafa
ySOo2dih/tQav7uAkdzDQr1HQ9LRRkzx5EnIdrbrVJGIPuDnOfvZ2ddE+7LDLQB7
SiZdacYVAKa3whaDiY4i2JVduv/2LyHG+JUhMDtD+J8PYSf4gPLRC4l8XqneIri7
9X+3UIW+I34c9mopbzwD+UiB+gPaHcBGKE3+LEBPJM1/+sUh7uM0Pm5SaU9NvXP1
VlR8H9cnvjf7DBm/p+cZ/hQiy78f/Zox/zRobeVlZUoW/+o4jqunYJA0EBNqHSKp
4hm2fBWMfQZZdVhYymHGY8+uhhKGp6U/fqJ95J6fwtlQhvo+O3MwzGywhHFFsgJV
fVAvCigEvz3XX+RfaVJq
=VZfS
-----END PGP SIGNATURE-----

From daedulus@btconnect.com  Mon Jul 29 07:00:43 2013
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8F1F11E80EA for <ietf@ietfa.amsl.com>; Mon, 29 Jul 2013 07:00:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qu8V1tGuKYxD for <ietf@ietfa.amsl.com>; Mon, 29 Jul 2013 07:00:37 -0700 (PDT)
Received: from co1outboundpool.messaging.microsoft.com (co1ehsobe002.messaging.microsoft.com [216.32.180.185]) by ietfa.amsl.com (Postfix) with ESMTP id 63F1A21F9F31 for <ietf@ietf.org>; Mon, 29 Jul 2013 06:59:40 -0700 (PDT)
Received: from mail160-co1-R.bigfish.com (10.243.78.254) by CO1EHSOBE023.bigfish.com (10.243.66.86) with Microsoft SMTP Server id 14.1.225.22; Mon, 29 Jul 2013 13:59:39 +0000
Received: from mail160-co1 (localhost [127.0.0.1])	by mail160-co1-R.bigfish.com (Postfix) with ESMTP id 83C59840131; Mon, 29 Jul 2013 13:59:39 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.254.197; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0711HT004.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -16
X-BigFish: PS-16(zzbb2dI98dI9371I542I1432Izz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz8275ch1de098h1033IL8275dh1de097hz2dh2a8h5a9h668h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1e23h304l1d11m1155h)
Received: from mail160-co1 (localhost.localdomain [127.0.0.1]) by mail160-co1 (MessageSwitch) id 1375106377380206_17880; Mon, 29 Jul 2013 13:59:37 +0000 (UTC)
Received: from CO1EHSMHS019.bigfish.com (unknown [10.243.78.245])	by mail160-co1.bigfish.com (Postfix) with ESMTP id 59004640049; Mon, 29 Jul 2013 13:59:37 +0000 (UTC)
Received: from DB3PRD0711HT004.eurprd07.prod.outlook.com (157.56.254.197) by CO1EHSMHS019.bigfish.com (10.243.66.29) with Microsoft SMTP Server (TLS) id 14.16.227.3; Mon, 29 Jul 2013 13:59:37 +0000
Received: from DB3PRD0411HT002.eurprd04.prod.outlook.com (157.56.253.53) by pod51017.outlook.com (10.255.183.37) with Microsoft SMTP Server (TLS) id 14.16.341.1; Mon, 29 Jul 2013 13:59:33 +0000
Message-ID: <009a01ce8c63$d43de480$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: <dcrocker@bbiw.net>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com>	<E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com>	<6.2.5.6.2.20130726101746.0c8db480@resistor.net>	<2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net><51F3BBB6.5030406@dcrocker.net> <51F42F7B.2060706@gmail.com><E12475C2-B005-42A7-A662-F36F55BB953E@piuha.net> <51F5FCB6.6060006@dcrocker.net>
Subject: Re: Remote participants, newcomers, and tutorials
Date: Mon, 29 Jul 2013 14:59:12 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.253.53]
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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Jul 2013 14:00:43 -0000

Dave

I think the points you make below are good, once the newcomer to the
IETF has found their working group.  This is not always easy.  Fine if
your interest is in OSPF, ISIS, TLS, TCPMaintenance but in other
spheres, the IETF approach of choosing a 'witty' name seems to me less
than welcoming.  Think about it as a stranger to these parts.  What
comes to mind when you encounter; salud, straw drinks insipid lemonade -
behave, kitten vipr, cuss!

If we had some way of measuring the success of a working group, I would
use it to test my hypothesis that the closer the short-form name is to
the subject of a working group, then the more successful that working
group will be.

Tom Petch

----- Original Message -----
From: "Dave Crocker" <dhc@dcrocker.net>
To: "Jari Arkko" <jari.arkko@piuha.net>
Cc: <ietf@ietf.org>
Sent: Monday, July 29, 2013 6:25 AM


> On 7/27/2013 11:01 PM, Jari Arkko wrote:
> >> It reads rudely when taken out of context. But try reading the
whole
> >> paragraph in RFC 3184:
> ...
> >> Exactly. My experience back when I was a newcomer was that it was
> >> easy enough to ask beginner's questions after the meeting, and
obviously
> >> wrong to do so during the session. This remains true years later,
if I
> >> drop into a WG that I'm not familiar with.
> >
> > Let me clarify why I thought it was wrong. I don't think I'm
disagreeing with you, actually. I do agree that asking beginner
questions in a working group meeting would be inappropriate. And I agree
that the meetings are not a place for education. And I agree that we
should not become an organisation where the f2f time gets the primary
role.
> >
> > However. Newcomers are not all alike. The student coming here to
observe the IETF. The researcher who understands the field we are
embarking on. The colleague that has been implementing The Protocol for
the last two years in the office, but is now coming to the IETF for the
first time. The guy who has something to say about the operational
experience of our results. The team who brought their idea to the IETF
to be standardised. And so on.
>
>
> Jari (et al)
>
> I've been finding discussion and actions about newcomers far more
> interesting this year, than most previous ones.  So I think it's worth
> pressing on several fronts, to see how we can both accommodate such
folk
> better, as well as be clear about when and where and how such
> accommodation is /and is not/ appropriate.
>
> Your reply to me, above, lists different types of new folk -- and of
> course the list is reasonable and might be useful -- but I didn't see
> the actual clarification of what you felt was wrong in the target text
> or how you agreed with me an others.  So, now you've got me curious
for
> that detail...
>
>
> And while I've got the floor I'll offer a thought I had after a brief
> conversation with Jari at last night's reception:
>
>       Warning:  This calls for working groups to do a little more
work.
>
> The working group home page and the working group wiki have become
> excellent tools for assembling relevant documents.  For someone trying
> to get started in the wg, these are incredibly helpful.
>
>       My suggestion is for a 'status' page that gives a brief summary
> about the current state of the working group, ideally listing the
> current, near-term vector of the work -- what's the current focus of
> effort -- and major open issues.
>
>       I'll suggest that it be updated after every meeting.
>
> Arguably, this sort of status statement is good to have even without
> newcomers, since it forces working groups to face the question of what
> progress they are and are not making.
>
> An exercise like this can be cast as onerous or helpful, depending
upon
> the surrounding organizational 'tone' we use.  In a supportive
> environment, the exercise is helpful.  In a hostile one, not so much.
>
> Basically, if a wg is being diligent and candid in summarizing its
> problems (as well as progress) the rest of us have an obligation to be

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



From moore@network-heretics.com  Mon Jul 29 08:57:57 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D75C921E8098 for <ietf@ietfa.amsl.com>; Mon, 29 Jul 2013 08:57:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YY5G-nd0pIMK for <ietf@ietfa.amsl.com>; Mon, 29 Jul 2013 08:57:51 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id 8E6B421F9C99 for <ietf@ietf.org>; Mon, 29 Jul 2013 08:57:50 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 86502215D1; Mon, 29 Jul 2013 11:57:49 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute4.internal (MEProxy); Mon, 29 Jul 2013 11:57:49 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=8HJ KV9PcgvrWcCilF90Q3rVfUaU=; b=UMGreDE/ZohI2UyyxGEirBGyzqrrm+j1VUc 6D71OCG/JTOeyBNQTp9Xu5+uhJzgv6Codbm9cTLM2ZHOIdBxG4efpBP23d96hXpW d9ufCskPEVhvOlAnhveZL3WfC2Q8zr3wXuYtUVKu+QxyWD+3AFmMCiXa9cuGL4oE F/YUwfPg=
X-Sasl-enc: RLGUVqe5NkGiBjD9ua4jTseGPS4pkDxNFmGipglBU/0r 1375113468
Received: from dhcp-11c1.meeting.ietf.org (unknown [130.129.17.193]) by mail.messagingengine.com (Postfix) with ESMTPA id BF1D0C00E8B; Mon, 29 Jul 2013 11:57:48 -0400 (EDT)
Subject: Re: Remote participants, newcomers, and tutorials
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: multipart/alternative; boundary=Apple-Mail-1--478207083
From: Keith Moore <moore@network-heretics.com>
X-Priority: 3
In-Reply-To: <009a01ce8c63$d43de480$4001a8c0@gateway.2wire.net>
Date: Mon, 29 Jul 2013 17:57:47 +0200
Message-Id: <440D6E3E-1ED2-44FF-B330-8C220DD68989@network-heretics.com>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com>	<E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com>	<6.2.5.6.2.20130726101746.0c8db480@resistor.net>	<2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net><51F3BBB6.5030406@dcrocker.net> <51F42F7B.2060706@gmail.com><E12475C2-B005-42A7-A662-F36F55BB953E@piuha.net> <51F5FCB6.6060006@dcrocker.net> <009a01ce8c63$d43de480$4001a8c0@gateway.2wire.net>
To: t.p. <daedulus@btconnect.com>
X-Mailer: Apple Mail (2.1085)
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Jul 2013 15:57:57 -0000

--Apple-Mail-1--478207083
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Jul 29, 2013, at 3:59 PM, t.p. wrote:

> I think the points you make below are good, once the newcomer to the
> IETF has found their working group.  This is not always easy.  Fine if
> your interest is in OSPF, ISIS, TLS, TCPMaintenance but in other
> spheres, the IETF approach of choosing a 'witty' name seems to me less
> than welcoming.  Think about it as a stranger to these parts.  What
> comes to mind when you encounter; salud, straw drinks insipid lemonade =
-
> behave, kitten vipr, cuss!

I was thinking this morning that clever short WG names are fine, but we =
shouldn't try too hard to make them acronyms - or at least, we shouldn't =
pretend that the acronyms suffice as descriptions for the WGs.   In =
lists of WGs, we should include brief descriptions of the WGs, not the =
acronym expansions.

Keith


--Apple-Mail-1--478207083
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Jul 29, 2013, at 3:59 PM, t.p. wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">I think the =
points you make below are good, once the newcomer to the<br>IETF has =
found their working group. &nbsp;This is not always easy. &nbsp;Fine =
if<br>your interest is in OSPF, ISIS, TLS, TCPMaintenance but in =
other<br>spheres, the IETF approach of choosing a 'witty' name seems to =
me less<br>than welcoming. &nbsp;Think about it as a stranger to these =
parts. &nbsp;What<br>comes to mind when you encounter; salud, straw =
drinks insipid lemonade -<br>behave, kitten vipr, =
cuss!</span></blockquote></div><br><div>I was thinking this morning that =
clever short WG names are fine, but we shouldn't try too hard to make =
them acronyms - or at least, we shouldn't pretend that the acronyms =
suffice as descriptions for the WGs. &nbsp; In lists of WGs, =
we&nbsp;should include brief descriptions of the WGs, not the acronym =
expansions.</div><div><br></div><div>Keith</div><div><br></div></body></ht=
ml>=

--Apple-Mail-1--478207083--

From danny@tcb.net  Mon Jul 29 10:02:59 2013
Return-Path: <danny@tcb.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2F8611E811E for <ietf@ietfa.amsl.com>; Mon, 29 Jul 2013 10:02:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.437
X-Spam-Level: 
X-Spam-Status: No, score=-100.437 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611,  RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BCkepQ75Du6D for <ietf@ietfa.amsl.com>; Mon, 29 Jul 2013 10:02:51 -0700 (PDT)
Received: from mail.friendswithtools.org (unknown [64.78.239.70]) by ietfa.amsl.com (Postfix) with ESMTP id DA73421F991F for <ietf@ietf.org>; Mon, 29 Jul 2013 09:55:59 -0700 (PDT)
Received: from dspam (unknown [127.0.0.1]) by mail.friendswithtools.org (Postfix) with SMTP id 436CF30004C for <ietf@ietf.org>; Mon, 29 Jul 2013 16:55:32 +0000 (UTC)
Received: from dhcp-138f.meeting.ietf.org (dhcp-138f.meeting.ietf.org [130.129.19.143]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.friendswithtools.org (Postfix) with ESMTPSA id BCDEE30004A; Mon, 29 Jul 2013 10:55:30 -0600 (MDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [karp] Last Call: <draft-ietf-karp-ops-model-07.txt> (Operations Model for	Router Keying) to Informational RFC
From: Danny McPherson <danny@tcb.net>
In-Reply-To: <tsltxjdvhcs.fsf@mit.edu>
Date: Mon, 29 Jul 2013 12:55:26 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <2946F5C1-FA69-4E47-983A-0D3565C9DDFF@tcb.net>
References: <20130729063557.22039.63212.idtracker@ietfa.amsl.com> <tsltxjdwxtv.fsf@mit.edu> <21DC453F-A434-463F-9F69-D036675507FB@tcb.net> <tsltxjdvhcs.fsf@mit.edu>
To: Sam Hartman <hartmans-ietf@mit.edu>
X-Mailer: Apple Mail (2.1508)
X-DSPAM-Result: Innocent
X-DSPAM-Processed: Mon Jul 29 10:55:32 2013
X-DSPAM-Confidence: 1.0000
X-DSPAM-Improbability: 1 in 98689409 chance of being spam
X-DSPAM-Probability: 0.0023
X-DSPAM-Signature: 51f69e8442071354217738
X-DSPAM-Factors: 27, wrong+#+How, 0.40000, 2013+at, 0.40000, to+#+#+#+validation, 0.40000, time+#+#+#+permit, 0.40000, never+digitally, 0.40000, Subject*Model+#+Router, 0.40000, Subject*Router+Keying, 0.40000, Routers+#+to, 0.40000, enough+#+#+#+receivers, 0.40000, that+receivers, 0.40000, Subject*Model+for, 0.40000, of+integrity, 0.40000, a+#+#+be, 0.40000, meant+New, 0.40000, hartmans+#+#+edu, 0.40000, Sam+#+#+these, 0.40000, AM+#+Hartman, 0.40000, Routers+need, 0.40000, Mime-Version*OS+X, 0.40000, enough+time, 0.40000, generation+#+#+protected, 0.40000, Subject*Call+#+Operations, 0.40000, Subject*to+Informational, 0.40000, signing+is, 0.40000, To*Hartman+hartmans-ietf, 0.40000, Sam+#+addressing, 0.40000, Mime-Version*6.5+1508, 0.40000
Cc: ietf@ietf.org, karp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Jul 2013 17:02:59 -0000

On Jul 29, 2013, at 5:35 AM, Sam Hartman <hartmans-ietf@mit.edu> wrote:
>=20
> I like your text below except that signing is the wrong word.
> How about generation of integrity-protected messages?

Yeah, that's what I meant..  New text WFM, thanks [again] Sam for =
addressing these concerns!

-danny



> These messages are almost never digitally signed.

> Proposed text:
>=20
>> Routers need to
>>     have tight enough time synchronization that receivers permit a =
key
>>     to be utilized for validation prior to the first use of that key =
for signing or
>>     availability will be impacted.
>=20



From john-ietf@jck.com  Mon Jul 29 11:18:24 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E523111E80FF for <ietf@ietfa.amsl.com>; Mon, 29 Jul 2013 11:18:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oAqEmKcVC5Go for <ietf@ietfa.amsl.com>; Mon, 29 Jul 2013 11:18:18 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id E75AD21E8086 for <ietf@ietf.org>; Mon, 29 Jul 2013 11:18:17 -0700 (PDT)
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 1V3s1P-000GuN-5l; Mon, 29 Jul 2013 14:18:15 -0400
Date: Mon, 29 Jul 2013 14:18:10 -0400
From: John C Klensin <john-ietf@jck.com>
To: Brian Haberman <brian@innovationslab.net>, ietf@ietf.org
Subject: Re: Remote participants, newcomers, and tutorials
Message-ID: <2985E656A579700D1EB74EF6@JcK-HP8200.jck.com>
In-Reply-To: <51F5FF83.4080308@innovationslab.net>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com> <E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130726101746.0c8db480@resistor.net> <2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net> <51F3BBB6.5030406@dcrocker.net> <51F42F7B.2060706@gmail.com> <E12475C2-B005-42A7-A662-F36F55BB953E@piuha.net> <51F5FCB6.6060006@dcrocker.net> <51F5FF83.4080308@innovationslab.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Jul 2013 18:18:24 -0000

--On Monday, July 29, 2013 01:37 -0400 Brian Haberman
<brian@innovationslab.net> wrote:

>...
> One of the things that I ask the Internet Area chairs to do is
> send in a summary of their WG after each IETF meeting.  Those
> summaries generally give folks a good idea of the current
> state of each WG.  I post those summaries on the Internet Area
> wiki.  An alternative that would work as well is to have each
> WG post summaries to their own wikis.  Each WG has a wiki
> available via their Tools page (e.g.,
> http://trac.tools.ietf.org/wg/6man/trac/wiki).
> 
> I like seeing the summaries from my chairs and I have gotten
> feedback from participants that they find them quite useful
> for keeping up with WGs that are tangential to their primary
> focus.  I would encourage every WG chair to periodically
> summarize the state of their WG/drafts.

Dave and a few other ancients will recall that there was a time
when there was a requirement for ADs to put together per-meeting
"Area Reports", which went into the minutes.  Unless ADs were
masochists who wanted to do all the work themselves, that pretty
much required that sort of status reports that he and Brian are
talking about.  It also ensured that ADs were aware of what was
going on in all of the WGs for which they were responsible and
that, if there were two ADs in an area, they were talking with
each other.  If those expectations were not met, someone
observing that would presumably have something very concrete to
tell the Nomcom.

In the context of the current discussion, a set of well-written
and frequently-updated area reports could also be a big help to
a newcomer trying to navigate WG names and acronyms.   I agree
that it would probably help to be more descriptive about WG
names rather than looking for things that will make cute
acronyms.  Whether we move in that direction or not, most
newcomers and isolated/remote participants are going to find it
easier to identify an Area of interest than a specific WG.  A
well-written Area Report that includes brief descriptions of the
main focus of each WG along with current status information
would be, IMO, a huge help in matching people and specific
interests.

I think a Wiki or equivalent would be a fine way to maintain
such pages but, given how well we do about keeping benchmarks
and similar information up to date and the advantages deadlines
seem to bring, I'd like to see at least snapshots or the
equivalent in meeting minutes.

    john





From david.black@emc.com  Mon Jul 29 04:21:21 2013
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12CA221F9AE9; Mon, 29 Jul 2013 04:21:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=-0.299, BAYES_00=-2.599, J_CHICKENPOX_34=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kk-qraJTTc-f; Mon, 29 Jul 2013 04:21:16 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 858EC21F9FE5; Mon, 29 Jul 2013 04:21:03 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r6TBKZjf015737 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 29 Jul 2013 07:20:36 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd03.lss.emc.com [10.254.221.145]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Mon, 29 Jul 2013 07:20:13 -0400
Received: from mxhub03.corp.emc.com (mxhub03.corp.emc.com [10.254.141.105]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r6TBKClG027092; Mon, 29 Jul 2013 07:20:12 -0400
Received: from mx15a.corp.emc.com ([169.254.1.184]) by mxhub03.corp.emc.com ([10.254.141.105]) with mapi; Mon, 29 Jul 2013 07:20:12 -0400
From: "Black, David" <david.black@emc.com>
To: "ldunbar@huawei.com" <ldunbar@huawei.com>, Donald Eastlake <d3e3e3@gmail.com>, "Radia@alum.mit.edu" <Radia@alum.mit.edu>, "igor@yahoo-inc.com" <igor@yahoo-inc.com>, General Area Review Team <gen-art@ietf.org>
Date: Mon, 29 Jul 2013 07:20:10 -0400
Subject: RE: Gen-ART review of draft-ietf-trill-directory-framework-06
Thread-Topic: Gen-ART review of draft-ietf-trill-directory-framework-06
Thread-Index: Ac6MTZacq8P2IvAoQlCH2H5lCCeKDA==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712984AD61D@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-EMM-MHVC: 1
X-Mailman-Approved-At: Mon, 29 Jul 2013 13:52:17 -0700
Cc: "ietf@ietf.org" <ietf@ietf.org>, "trill@ietf.org" <trill@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Jul 2013 11:21:21 -0000

The -06 version of this draft resolves all of the concerns raised by the Ge=
n-ART
review of the -05 version - the -06 version is ready for publication as an
Informational RFC.

Thanks,
--David

> -----Original Message-----
> From: Black, David
> Sent: Wednesday, July 17, 2013 7:54 PM
> To: ldunbar@huawei.com; Donald Eastlake; Radia@alum.mit.edu; igor@yahoo-
> inc.com; General Area Review Team
> Cc: trill@ietf.org; ietf@ietf.org; Black, David; Ted Lemon
> Subject: Gen-ART review of draft-ietf-trill-directory-framework-05
>=20
> Document: draft-ietf-trill-directory-framework-05
> Reviewer: David L. Black
> Review Date: July 17, 2013
> IETF LC End Date: July 18, 2013
>=20
> Summary:
> This draft is on the right track but has open issues, described in the re=
view.
>=20
> This draft describes a framework for using directory servers to provide
> address mappings (address -> destination RBridge) to TRILL Rbridges as an
> alternative to data plane learning and use of the TRILL ESADI protocol.
>=20
> The draft's generally well written and clear.  I found a couple of minor
> issues.
>=20
> Major issues: None.
>=20
> Minor issues:
>=20
> [1] The last bullet in Section 3.1 says:
>=20
>        - In an environment where VMs migrate, there is a higher chance
>          of cached information becoming invalid, causing traffic to be
>          black-holed by the ingress RBridge, that is, persistently sent
>          to the wrong egress RBridge. If VMs do not flood gratuitous
>          ARP/ND or VDP [802.1Qbg] messages upon arriving at new
>          locations, the ingress nodes might not have MAC entries for the
>          MAC of the newly arrived VMs, causing unknown address flooding.
>=20
> This is incorrect in multiple ways and should just be removed:
>=20
> - Persistent black-holing is rare in practice because all common
> 	VM migration implementations issue the gratuitous messages.
> - VMs don't send the gratuitous messages, hypervisors do.
> - VDP is not flooded.  The receiver's always a bridge.
> - At least one common VM migration implementation actually uses a gratuit=
ous
> 	RARP, not ARP.
> - Flooding is done by the bridges and Rbridges, not the VMs.
>=20
> [2] There are some unfortunate notation problems in Section 5.1 that carr=
y
> into the following sections, based on the logical data structure:
>=20
>    [{IP, MAC/VLAN, {list of attached RBridge nicknames}, {list of
>    interested RBridges}]
>=20
> - The first open curly brace ('{') is unmatched.
> - Subsequent text uses [IP or MAC/VLAN], IP/MAC/VLAN and MAC&VLAN,
> 	none of which appear in that structure.
>=20
> Nits/editorial comments:
>=20
> Section 1 - item 1 in the numbered list does not explain why it makes
> a directory approach attractive.  This should be added, as it is
> present for the other three items .
>=20
> Section 2 - Say that IS-IS is a routing protocol.
> The definition of Station should say that the node or virtual node
> is on a network.  Also, please define or explain "virtual node".
>=20
> Section 3.2 - Add the number of entries to be learned to scenario #1
> in order to parallel the scenario # 2 discussion.
>=20
> Section 4 - remove "(distributed model)" from first paragraph,
> as it's not explained.
>=20
> Section 5.3, top of p.13:
>=20
>    therefore, there needs to be some mechanism by which RBridges that
>    have pulled information that has not expired can be informed when
>    that information changes or the like.
>=20
> "or the like" is vague.  I suggest "or becomes invalid for other
>  reasons".
>=20
> idnits 2.12.17 didn't find any nits that need attention.
>=20
> Thanks,
> --David
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
> +1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-7=
786
> david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> ----------------------------------------------------


From brian.e.carpenter@gmail.com  Mon Jul 29 18:19:36 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A07821F9930 for <ietf@ietfa.amsl.com>; Mon, 29 Jul 2013 18:19:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.554
X-Spam-Level: 
X-Spam-Status: No, score=-102.554 tagged_above=-999 required=5 tests=[AWL=0.045, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TTDtObk2HeH0 for <ietf@ietfa.amsl.com>; Mon, 29 Jul 2013 18:19:35 -0700 (PDT)
Received: from mail-pd0-x235.google.com (mail-pd0-x235.google.com [IPv6:2607:f8b0:400e:c02::235]) by ietfa.amsl.com (Postfix) with ESMTP id 1672E21F96EF for <ietf@ietf.org>; Mon, 29 Jul 2013 18:19:35 -0700 (PDT)
Received: by mail-pd0-f181.google.com with SMTP id g10so2394289pdj.12 for <ietf@ietf.org>; Mon, 29 Jul 2013 18:19:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=5ZWxuloGifBro3sgb/y6cS5xJ2/D0QgDSZ1kHL5wB98=; b=OdxNE01S88KpIdazrWBQ3c+WCV/wvwifJ3r3tLdXGODV/G5+nl2RGvGpLsS5kbqCij ZKavxpsfibzj4Z+thND3l21uAvShWK8aAOPj8Cq1f2/mFJsjvvG73Cuc8o6yKQov1J9N XY2334TpTeifSJ5n5036bgoChneePyZe7aN15CL2UqO6pVda8BTseuWw13/GPDZtVu0D namtkNlpadWc4rbZoBCHHZS6m4f67JJZetHxkz7+iOJeyX1wqBL6bgNMQQVThEE9uZyd /UZPjQtOiRKd6m9c+Ds+OgU0EJwfvEyRuxVhdxvseiztYYjIrLhYHenKg/cEvW52DVsD EcFA==
X-Received: by 10.66.122.41 with SMTP id lp9mr72678034pab.6.1375147174822; Mon, 29 Jul 2013 18:19:34 -0700 (PDT)
Received: from [192.168.178.23] (225.199.69.111.dynamic.snap.net.nz. [111.69.199.225]) by mx.google.com with ESMTPSA id ib9sm79585542pbc.43.2013.07.29.18.19.32 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 29 Jul 2013 18:19:34 -0700 (PDT)
Message-ID: <51F714A5.6080203@gmail.com>
Date: Tue, 30 Jul 2013 13:19:33 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Remote participants, newcomers, and tutorials
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com>	<E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com>	<6.2.5.6.2.20130726101746.0c8db480@resistor.net>	<2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net>	<51F3BBB6.5030406@dcrocker.net> <51F42F7B.2060706@gmail.com>	<E12475C2-B005-42A7-A662-F36F55BB953E@piuha.net>	<51F5FCB6.6060006@dcrocker.net>	<51F5FF83.4080308@innovationslab.net> <2985E656A579700D1EB74EF6@JcK-HP8200.jck.com>
In-Reply-To: <2985E656A579700D1EB74EF6@JcK-HP8200.jck.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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2013 01:19:36 -0000

On 30/07/2013 06:18, John C Klensin wrote:
> 
> --On Monday, July 29, 2013 01:37 -0400 Brian Haberman
> <brian@innovationslab.net> wrote:
> 
>> ...
>> One of the things that I ask the Internet Area chairs to do is
>> send in a summary of their WG after each IETF meeting.  Those
>> summaries generally give folks a good idea of the current
>> state of each WG.  I post those summaries on the Internet Area
>> wiki.  An alternative that would work as well is to have each
>> WG post summaries to their own wikis.  Each WG has a wiki
>> available via their Tools page (e.g.,
>> http://trac.tools.ietf.org/wg/6man/trac/wiki).
>>
>> I like seeing the summaries from my chairs and I have gotten
>> feedback from participants that they find them quite useful
>> for keeping up with WGs that are tangential to their primary
>> focus.  I would encourage every WG chair to periodically
>> summarize the state of their WG/drafts.
> 
> Dave and a few other ancients will recall that there was a time
> when there was a requirement for ADs to put together per-meeting
> "Area Reports", which went into the minutes.  

These were put together from WG Chair's session reports, which
were (and are) mandatory under RFC 2418 (BCP 25):

      Immediately after a session, the WG Chair MUST provide the Area
      Director with a very short report (approximately one paragraph,
      via email) on the session.

That's not quite the same as a WG status report, but makes a good start.

   Brian


Unless ADs were
> masochists who wanted to do all the work themselves, that pretty
> much required that sort of status reports that he and Brian are
> talking about.  It also ensured that ADs were aware of what was
> going on in all of the WGs for which they were responsible and
> that, if there were two ADs in an area, they were talking with
> each other.  If those expectations were not met, someone
> observing that would presumably have something very concrete to
> tell the Nomcom.
> 
> In the context of the current discussion, a set of well-written
> and frequently-updated area reports could also be a big help to
> a newcomer trying to navigate WG names and acronyms.   I agree
> that it would probably help to be more descriptive about WG
> names rather than looking for things that will make cute
> acronyms.  Whether we move in that direction or not, most
> newcomers and isolated/remote participants are going to find it
> easier to identify an Area of interest than a specific WG.  A
> well-written Area Report that includes brief descriptions of the
> main focus of each WG along with current status information
> would be, IMO, a huge help in matching people and specific
> interests.
> 
> I think a Wiki or equivalent would be a fine way to maintain
> such pages but, given how well we do about keeping benchmarks
> and similar information up to date and the advantages deadlines
> seem to bring, I'd like to see at least snapshots or the
> equivalent in meeting minutes.
> 
>     john
> 
> 
> 
> 
> 

From spromano@unina.it  Mon Jul 29 23:40:57 2013
Return-Path: <spromano@unina.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9596421E805F for <ietf@ietfa.amsl.com>; Mon, 29 Jul 2013 23:40:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.718
X-Spam-Level: 
X-Spam-Status: No, score=-100.718 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H9W5TZHeH+2l for <ietf@ietfa.amsl.com>; Mon, 29 Jul 2013 23:40:51 -0700 (PDT)
Received: from smtp1.unina.it (smtp1.unina.it [192.132.34.61]) by ietfa.amsl.com (Postfix) with ESMTP id 7609E21E8053 for <ietf@ietf.org>; Mon, 29 Jul 2013 23:40:51 -0700 (PDT)
Received: from dhcp-1483.meeting.ietf.org (dhcp-1483.meeting.ietf.org [130.129.20.131]) (authenticated bits=0) by smtp1.unina.it (8.14.4/8.14.4) with ESMTP id r6U6ehJt001392 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 30 Jul 2013 08:40:45 +0200
From: Simon Pietro Romano <spromano@unina.it>
Content-Type: multipart/alternative; boundary="Apple-Mail=_B1514F1A-3848-4127-A172-B945E21D8FE0"
Subject: Meetecho MacBook in room Charlottenburg II/III
Date: Tue, 30 Jul 2013 08:40:44 +0200
Message-Id: <18C30997-CD26-4E93-8AB3-05172FDB6530@unina.it>
To: "ietf@ietf.org list" <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1283)
X-Mailer: Apple Mail (2.1283)
Cc: team@meetecho.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2013 06:40:57 -0000

--Apple-Mail=_B1514F1A-3848-4127-A172-B945E21D8FE0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Dear all,

this morning we did not find one of our streaming laptops, which had =
been left (properly locked with a cable lock) in room Charlottenburg =
II/III. As you can imagine, besides being a real scandal, this is going =
to be a serious issue for us, since we are currently covering up to 4 =
sessions in parallel at this IETF and we're running out of HW resources. =
Should you have any useful information for us related to this event, =
please send us an e-mail to the following address: team@meetecho.com.

Thanks a lot in advance,

Simon


                     					       _\\|//_
                           				      ( O-O )
   ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
                    				Simon Pietro Romano
             				 Universita' di Napoli Federico =
II
                		     Computer Engineering Department=20
	             Phone: +39 081 7683823 -- Fax: +39 081 7683816
                                           e-mail: spromano@unina.it

		    <<Molti mi dicono che lo scoraggiamento =CB l'alibi =
degli=20
		    idioti. Ci rifletto un istante; e mi scoraggio>>. =
Magritte.
               			                     oooO
  ~~~~~~~~~~~~~~~~~~~~~~~(   )~~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
					                 \ (            =
(   )
			                                  \_)          ) =
/
                                                                       =
(_/






--Apple-Mail=_B1514F1A-3848-4127-A172-B945E21D8FE0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Dear =
all,<div><br></div><div>this morning we did not find one of our =
streaming laptops, which had been left (properly locked with a =
cable&nbsp;lock) in room Charlottenburg II/III. As you can imagine, =
besides being a real scandal, this is going to be a serious issue for =
us, since we are currently covering up to 4 sessions in parallel at this =
IETF and we're running out of HW resources. Should you have any useful =
information for us related to this event, please send us an e-mail to =
the following address: <a =
href=3D"mailto:team@meetecho.com">team@meetecho.com</a>.</div><div><br></d=
iv><div>Thanks a lot in =
advance,</div><div><br></div><div>Simon</div><div><br></div><div><br><div =
apple-content-edited=3D"true">
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-align: -webkit-auto; text-indent: 0px; text-transform: none; =
white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div>&nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
	</span><span class=3D"Apple-converted-space">&nbsp;</span>&nbsp; =
&nbsp; &nbsp; _\\|//_</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
</span>&nbsp; &nbsp; &nbsp;&nbsp;( O-O )</div><div>&nbsp; =
&nbsp;~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~</div><di=
v>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;<span class=3D"Apple-converted-space">&nbsp;</span><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
</span>Simon Pietro Romano</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;<span class=3D"Apple-tab-span" style=3D"white-space: pre; =
">				</span><span =
class=3D"Apple-converted-space">&nbsp;</span>Universita' di Napoli =
Federico II</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;&nbsp;<span class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
	</span>&nbsp; &nbsp; &nbsp;Computer Engineering =
Department&nbsp;</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	</span>&nbsp; &nbsp; &nbsp;&nbsp; &nbsp; =
&nbsp; &nbsp; Phone: +39 081 7683823 -- Fax: +39 081 =
7683816</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;e-mail: <a =
href=3D"mailto:spromano@unina.it">spromano@unina.it</a></div><div><br></di=
v><div><span class=3D"Apple-tab-span" style=3D"white-space: pre; ">		=
</span>&nbsp; &nbsp; &lt;&lt;Molti mi dicono che lo scoraggiamento =CB =
l'alibi degli&nbsp;</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">		</span>&nbsp;&nbsp; =
&nbsp;idioti. Ci rifletto un istante; e mi scoraggio&gt;&gt;. =
Magritte.</div><div>&nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; =
&nbsp;<span class=3D"Apple-converted-space">&nbsp;</span><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">			=
</span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;oooO</div><div>&nbsp; ~~~~~~~~~~~~~~~~~~~~~~~( &nbsp; =
)~~~&nbsp;Oooo~~~~~~~~~~~~~~~~~~~~~~~~~</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
	</span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;\ ( &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;( &nbsp; =
)</div><div><span class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
		</span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
\_) &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;) /</div><div>&nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp;(_/</div></div><div><br></div></div></span><br =
class=3D"Apple-interchange-newline"></div></span><br =
class=3D"Apple-interchange-newline"></span><br =
class=3D"Apple-interchange-newline">
</div>
<br></div></body></html>=

--Apple-Mail=_B1514F1A-3848-4127-A172-B945E21D8FE0--

From jari.arkko@piuha.net  Tue Jul 30 04:50:50 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1F7821E80BF for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 04:50:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.588
X-Spam-Level: 
X-Spam-Status: No, score=-102.588 tagged_above=-999 required=5 tests=[AWL=0.011, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZVbXSDam0UQ0 for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 04:50:45 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 8C5CC21F9DED for <ietf@ietf.org>; Tue, 30 Jul 2013 04:50:21 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 393D92CC54; Tue, 30 Jul 2013 14:50:20 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vw7ya4XLftRb; Tue, 30 Jul 2013 14:50:19 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 3FF252CC48; Tue, 30 Jul 2013 14:50:19 +0300 (EEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Remote participants, newcomers, and tutorials
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <51F5FCB6.6060006@dcrocker.net>
Date: Tue, 30 Jul 2013 13:50:18 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <C0BD924B-B46F-4417-8C66-FE06E62FE0C1@piuha.net>
References: <016CD35E-2382-4822-8CA3-BF47D489BE96@verilan.com>	<E72C3F8A34B5C834AD25B1E4@JcK-HP8200.jck.com>	<6.2.5.6.2.20130726101746.0c8db480@resistor.net>	<2CA9347C-C4D0-4B6F-AB2F-5C0DF26872D5@piuha.net> <51F3BBB6.5030406@dcrocker.net> <51F42F7B.2060706@gmail.com> <E12475C2-B005-42A7-A662-F36F55BB953E@piuha.net> <51F5FCB6.6060006@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1508)
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2013 11:50:50 -0000

Dave,

> I've been finding discussion and actions about newcomers far more =
interesting this year, than most previous ones.  So I think it's worth =
pressing on several fronts, to see how we can both accommodate such folk =
better, as well as be clear about when and where and how such =
accommodation is /and is not/ appropriate.
>=20
> Your reply to me, above, lists different types of new folk -- and of =
course the list is reasonable and might be useful -- but I didn't see =
the actual clarification of what you felt was wrong in the target text =
or how you agreed with me an others.  So, now you've got me curious for =
that detail=85

The wrong part in the text was suggesting that newcomers should never =
speak up in meetings. I believe they in many cases should, although =
beginner or tutorial questions should not be asked.

> And while I've got the floor I'll offer a thought I had after a brief =
conversation with Jari at last night's reception:
>=20
>     Warning:  This calls for working groups to do a little more work.
>=20
> The working group home page and the working group wiki have become =
excellent tools for assembling relevant documents.  For someone trying =
to get started in the wg, these are incredibly helpful.
>=20
>     My suggestion is for a 'status' page that gives a brief summary =
about the current state of the working group, ideally listing the =
current, near-term vector of the work -- what's the current focus of =
effort -- and major open issues.
>=20
>     I'll suggest that it be updated after every meeting.
>=20
> Arguably, this sort of status statement is good to have even without =
newcomers, since it forces working groups to face the question of what =
progress they are and are not making.
>=20
> An exercise like this can be cast as onerous or helpful, depending =
upon the surrounding organizational 'tone' we use.  In a supportive =
environment, the exercise is helpful.  In a hostile one, not so much.
>=20
> Basically, if a wg is being diligent and candid in summarizing its =
problems (as well as progress) the rest of us have an obligation to be =
helpful.

I like this. =20

Jari


From roland.bless@kit.edu  Tue Jul 30 05:17:33 2013
Return-Path: <roland.bless@kit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2B2211E81CB for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 05:17:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level: 
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vx2CWZW6RtJ2 for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 05:17:28 -0700 (PDT)
Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de [141.3.10.81]) by ietfa.amsl.com (Postfix) with ESMTP id 64BDB11E81DF for <ietf@ietf.org>; Tue, 30 Jul 2013 05:17:27 -0700 (PDT)
Received: from irams1.ira.uni-karlsruhe.de ([141.3.10.5]) by iramx2.ira.uni-karlsruhe.de with esmtps port 25  id 1V48rg-0005nG-Vf for <ietf@ietf.org>; Tue, 30 Jul 2013 14:17:26 +0200
Received: from i72vorta.tm.uni-karlsruhe.de ([141.3.71.26] helo=vorta.tm.kit.edu) by irams1.ira.uni-karlsruhe.de with esmtp port 25  for <ietf@ietf.org> id 1V48rg-0005AM-MV; Tue, 30 Jul 2013 14:17:20 +0200
Received: from [IPv6:::1] (localhost [127.0.0.1]) by vorta.tm.kit.edu (Postfix) with ESMTPS id 73751A806BE for <ietf@ietf.org>; Tue, 30 Jul 2013 14:17:20 +0200 (CEST)
Message-ID: <51F7AED0.2080308@kit.edu>
Date: Tue, 30 Jul 2013 14:17:20 +0200
From: Roland Bless <roland.bless@kit.edu>
Organization: Institute of Telematics, Karlsruhe Institute of Technology (KIT)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.1) Gecko/20060111 Thunderbird/1.5 Mnenhy/0.7.3.0
MIME-Version: 1.0
To: "ietf@ietf.org list" <ietf@ietf.org>
Subject: Bringing back Internet transparency
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-ATIS-AV: ClamAV (irams1.ira.uni-karlsruhe.de)
X-ATIS-AV: Kaspersky (iramx2.ira.uni-karlsruhe.de)
X-ATIS-AV: ClamAV (iramx2.ira.uni-karlsruhe.de)
X-ATIS-Timestamp: iramx2.ira.uni-karlsruhe.de 1375186646.422201000
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2013 12:17:33 -0000

Hi,

my impression from several presentations seen this week at the IETF
as well as at the ISOC Panel on "Improving Internet Experience"
is that we probably need to do something on reducing the number
of _broken_ middleboxes (or their implementations respectively)
- I'm not focusing on NAT boxes here.

We all know that it's actually hard to engineer new innovative
protocols around those broken boxes in the path. I think it's
clear that we will not get rid of them, but if I hear about
boxes that try to do "clever optimization" or "security" by
rewriting TCP sequence numbers (w/o considering them in SACK),
bundling segments and so on, I'm wondering who actually engineered
those boxes; aren't the vendors/engineers participating in the IETF?
Who buys and deploys such boxes, esp. if you consider that todays short-
sighted optimization may prevent usage of a newer transport protocol
that actually may provide a much larger performance improvement than
this middlebox?

It's really sad that we still have many problems due to such
broken implementations that break the Internet transparency
and hinder innovations like SCTP, ECN, various TCP enhancements,
and many others.
What could be IETF efforts to get a better situation for the deployment
of future innovations or do we simply accept that (a few) broken
middleboxes dictate the future level of innovation in the Internet?

Regards,
 Roland

Some prior related work:
https://tools.ietf.org/html/rfc2775 Internet Transparency
https://tools.ietf.org/html/rfc3724 The Rise of the Middle and the
Future of End-to-End: Reflections on the Evolution of the Internet
Architecture
https://tools.ietf.org/html/rfc4924 Reflections on Internet Transparency

From hannes.tschofenig@gmx.net  Tue Jul 30 05:35:13 2013
Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C4BD21E80C0 for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 05:35:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.676
X-Spam-Level: 
X-Spam-Status: No, score=-102.676 tagged_above=-999 required=5 tests=[AWL=-0.077, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L+r4MVufrheS for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 05:35:08 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) by ietfa.amsl.com (Postfix) with ESMTP id 04FB921F8FD8 for <ietf@ietf.org>; Tue, 30 Jul 2013 05:35:06 -0700 (PDT)
Received: from dhcp-13ba.meeting.ietf.org ([130.129.19.186]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0LiDHj-1UGjYR3gjz-00nQbX for <ietf@ietf.org>; Tue, 30 Jul 2013 14:35:04 +0200
Subject: Re: Bringing back Internet transparency
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
In-Reply-To: <51F7AED0.2080308@kit.edu>
Date: Tue, 30 Jul 2013 14:35:02 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <4137B586-FD71-495A-8345-35CA3988E906@gmx.net>
References: <51F7AED0.2080308@kit.edu>
To: Roland Bless <roland.bless@kit.edu>
X-Pgp-Agent: GPGMail 1.4.1
X-Mailer: Apple Mail (2.1085)
X-Provags-ID: V03:K0:IU53U44uw6EmaXpGoykRe/4z4/3Z4uxv4WhKaXnHMz7RZgB/PrU p4nC7OtTNt5DgTV5qO639Dp9KbicC7unsUBqqPYV3wY7ABrOaf0HkUi8o5z2F/etetjmKDO 4/DdqMW4oW6n/l3kcHRYwsaSFD0d0Rj1JjIOje/QikWooS17K2rILY3uGmk30m8vPHONVmU b/RXpfrmDlurNsBP2uUjg==
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2013 12:35:13 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

I raised the need for this transparency in this writeup:=20
http://tools.ietf.org/html/draft-tschofenig-hourglass-00

The document also points to some projects / paper I am aware of that are =
relevant. There may be more.=20

Ciao
Hannes

On Jul 30, 2013, at 2:17 PM, Roland Bless wrote:

> Hi,
>=20
> my impression from several presentations seen this week at the IETF
> as well as at the ISOC Panel on "Improving Internet Experience"
> is that we probably need to do something on reducing the number
> of _broken_ middleboxes (or their implementations respectively)
> - I'm not focusing on NAT boxes here.
>=20
> We all know that it's actually hard to engineer new innovative
> protocols around those broken boxes in the path. I think it's
> clear that we will not get rid of them, but if I hear about
> boxes that try to do "clever optimization" or "security" by
> rewriting TCP sequence numbers (w/o considering them in SACK),
> bundling segments and so on, I'm wondering who actually engineered
> those boxes; aren't the vendors/engineers participating in the IETF?
> Who buys and deploys such boxes, esp. if you consider that todays =
short-
> sighted optimization may prevent usage of a newer transport protocol
> that actually may provide a much larger performance improvement than
> this middlebox?
>=20
> It's really sad that we still have many problems due to such
> broken implementations that break the Internet transparency
> and hinder innovations like SCTP, ECN, various TCP enhancements,
> and many others.
> What could be IETF efforts to get a better situation for the =
deployment
> of future innovations or do we simply accept that (a few) broken
> middleboxes dictate the future level of innovation in the Internet?
>=20
> Regards,
> Roland
>=20
> Some prior related work:
> https://tools.ietf.org/html/rfc2775 Internet Transparency
> https://tools.ietf.org/html/rfc3724 The Rise of the Middle and the
> Future of End-to-End: Reflections on the Evolution of the Internet
> Architecture
> https://tools.ietf.org/html/rfc4924 Reflections on Internet =
Transparency

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
Comment: GPGTools - http://gpgtools.org

iQEcBAEBCgAGBQJR97L3AAoJEGhJURNOOiAt0hkH/ityOYpfqP752++/DL/K0DVZ
6q4gGpmzZwGcAnacUaAUy6Ycdajj7onJQydwGyvG4/nxbjM5g/2PeRpJdCjfSPhU
oUQt+2Xe8GXTRS6/IAwVh2M2DCz1RX3My2prM+4t9cVXWO0T2rpx60d6I6Wz04Ei
aYVAPx1n8IcggxbVy/KiVR4mUmzIzKNA1O2peNhKxntpWyKpkddfHv4GwzIK3Gmj
/pOmAPSyXbdQ+Oi8Nq233GyzXq/NeL513Z66qZvW3e6EYFa+6Wg3eJk7XA0zSk0x
6QZPX9KO72UrE66hPZw7t5lgWNtyKBqo0bTn9SEVqH39M+hwkATVecsydJ1gePE=3D
=3DEhV6
-----END PGP SIGNATURE-----

From jnc@mercury.lcs.mit.edu  Tue Jul 30 06:23:23 2013
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C4D311E81FD for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 06:23:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.427
X-Spam-Level: 
X-Spam-Status: No, score=-6.427 tagged_above=-999 required=5 tests=[AWL=0.172,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HgkXCS2uSocl for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 06:23:12 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id C316921F9343 for <ietf@ietf.org>; Tue, 30 Jul 2013 06:23:08 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 5AA8518C111; Tue, 30 Jul 2013 09:23:05 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: Bringing back Internet transparency
Message-Id: <20130730132305.5AA8518C111@mercury.lcs.mit.edu>
Date: Tue, 30 Jul 2013 09:23:05 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2013 13:23:23 -0000

    > From: Roland Bless <roland.bless@kit.edu>

    > we probably need to do something on reducing the number of _broken_
    > middleboxes (or their implementations respectively) - I'm not focusing
    > on NAT boxes here.
    > ...
    > I think it's clear that we will not get rid of them, but if I hear
    > about boxes that try to do "clever optimization" or "security" by
    > re-writing TCP sequence numbers ... bundling segments and so on, I'm
    > wondering who actually engineered those boxes; aren't the
    > vendors/engineers participating in the IETF? Who buys and deploys such
    > boxes
    > ...
    > What could be IETF efforts to get a better situation for the deployment
    > of future innovations or do we simply accept that (a few) broken
    > middleboxes dictate the future level of innovation in the Internet?

I hear you, but... this is not a simple problem.

I think we need to start by understanding what drives the creation and
deployment of these devices. I think the answer to that has to be that some
people have needs that aren't being met by the IETF, and so there's an
opportunity for private entities to create and sell 'solutions'.

The IETF doesn't have a police force, or any enforcement mechanism. If we're
going to head off these boxes, the only tool we have to do that is to build
better mousetraps - i.e. design stuff that does what people want, is more
cost-effective, and is better than these local 'point deployment' boxes.

Sadly, the IETF has a long history of being hard-headed about 'my way or the
highway', and not carefully listening to what the 'customers' are telling us
about these various aspects of a successful design.

(The most noteable example of this being NAT - which was going to be ugly
anyway, but as a result of the IETF refusing to create an architected NAT
solution - apparently on the theory that if we stuck our fingers in our ears
and went la-la-la-la loud enough, it would Just Go Away - we now have NAT that
is both ugly _and_ brittle [because it's not part of an architected _system_],
difficult to work with because it [mostly] lacks any external control
interface, etc.)

So, sorry, I don't have a simple solution to what I concede is a real problem.
But it's a complicated problem -> no simple solution.

	Noel

From jari.arkko@piuha.net  Tue Jul 30 06:53:33 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E792221F9E9D for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 06:53:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.589
X-Spam-Level: 
X-Spam-Status: No, score=-102.589 tagged_above=-999 required=5 tests=[AWL=0.010, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VhVd8sGt0BYD for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 06:53:21 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 70E2321E80C0 for <ietf@ietf.org>; Tue, 30 Jul 2013 06:53:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id BEC832CC65; Tue, 30 Jul 2013 16:53:18 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ctlOCTM1FoDR; Tue, 30 Jul 2013 16:53:18 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 07B872CC60; Tue, 30 Jul 2013 16:53:17 +0300 (EEST)
From: Jari Arkko <jari.arkko@piuha.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: setting a goal for an inclusive IETF
Date: Tue, 30 Jul 2013 15:53:17 +0200
Message-Id: <EDC539D2-48CE-44D7-A06C-19EEAE42D31C@piuha.net>
To: "ietf@ietf.org list" <ietf@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
Cc: Pete Resnick <presnick@qti.qualcomm.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2013 13:53:33 -0000

We have discussed diversity at the IETF at length. Yesterday, Pete =
Resnick and I wrote an article about what we think the goal for the IETF =
should be, as well as listing some of the early activities that we have =
taken at the IETF. Our goal is making the IETF more inclusive for =
everyone who needs to be working on Internet standards. We are at the =
beginning, however, and a lot of work remains ahead. Here's the article:

http://www.ietf.org/blog/2013/07/a-diverse-ietf/

Also, I wanted to let everyone know that tomorrow in the Administrative =
Plenary, Kathleen Moriarty and Suresh Krishnan will be talking about =
what they have uncovered so far in their efforts in the diversity design =
team. I'm looking very much forward to their report. Their efforts will =
help us understand where we have room to improve - often by much :-) - =
and what kinds of actions we can take to improve our inclusiveness.

Jari


From arturo.servin@gmail.com  Tue Jul 30 07:25:56 2013
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C38A21F9C21 for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 07:25:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SgRhEAYZjBbm for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 07:25:55 -0700 (PDT)
Received: from mail-ve0-x230.google.com (mail-ve0-x230.google.com [IPv6:2607:f8b0:400c:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id 4919111E81F7 for <ietf@ietf.org>; Tue, 30 Jul 2013 07:25:33 -0700 (PDT)
Received: by mail-ve0-f176.google.com with SMTP id b10so1967820vea.21 for <ietf@ietf.org>; Tue, 30 Jul 2013 07:25:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=Xcb/QT2Xw0RzZ8XXgfTgFWLIe7VT//Q8D5T32FyZq0w=; b=VwjQ8NY9Ka7pb3WMfIUjGNRAVOVPG/VeA4aPfT7nbDGesIKSdllM/cp5NG6SPobpVQ BCH9CMN7vPMdcbOZeh4p/spnreVGshNeqh0MssEbiZlg1HZwCGOVkne/KEURptw3Z+oE Ciwz4KGlQqI1qxwsMBZMAqz5zkqI60TSqKTXcnw4u+eo4oOXQC3vEgJ3UQCbx56uRkHI AmSpmqF2GHZWDJHbNasIpUMixkY7J/vbwaWOq/kmCoOC1J9/s/Dd0+JsovCNWy0d8r6H DNKhNeNDBFKxArGHMVsI4UIrRVC2yAYUzuJ8q9TnrQfLVH1zKE8dWb5TgcO6OH4l1WRa ejdQ==
X-Received: by 10.58.226.199 with SMTP id ru7mr26981277vec.68.1375194330486; Tue, 30 Jul 2013 07:25:30 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local ([2001:df8:0:16:dc07:9710:b85d:1730]) by mx.google.com with ESMTPSA id hu9sm3945995vdb.11.2013.07.30.07.25.28 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 30 Jul 2013 07:25:29 -0700 (PDT)
Message-ID: <51F7CCD5.5080202@gmail.com>
Date: Tue, 30 Jul 2013 16:25:25 +0200
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
Subject: IETF-Blog comments (Was Re: setting a goal for an inclusive IETF)
References: <EDC539D2-48CE-44D7-A06C-19EEAE42D31C@piuha.net>
In-Reply-To: <EDC539D2-48CE-44D7-A06C-19EEAE42D31C@piuha.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Pete Resnick <presnick@qti.qualcomm.com>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2013 14:25:56 -0000

Jari, Peter

	Thanks for the article. It is really welcomed to see that "diversity"
is something that the IETF is taking really seriously.

	Now, something general related to the blog. Perhaps it would be good to
enable comments, isn't it?

	I think that it would be good to interact there instead of here. One of
the values of this list is to have important topics, In general
blog-comments do not reach that level of importance, although it is
important to comment about the topic somewhere.

Thanks,
as


On 7/30/13 3:53 PM, Jari Arkko wrote:
> We have discussed diversity at the IETF at length. Yesterday, Pete Resnick and I wrote an article about what we think the goal for the IETF should be, as well as listing some of the early activities that we have taken at the IETF. Our goal is making the IETF more inclusive for everyone who needs to be working on Internet standards. We are at the beginning, however, and a lot of work remains ahead. Here's the article:
> 
> http://www.ietf.org/blog/2013/07/a-diverse-ietf/
> 
> Also, I wanted to let everyone know that tomorrow in the Administrative Plenary, Kathleen Moriarty and Suresh Krishnan will be talking about what they have uncovered so far in their efforts in the diversity design team. I'm looking very much forward to their report. Their efforts will help us understand where we have room to improve - often by much :-) - and what kinds of actions we can take to improve our inclusiveness.
> 
> Jari
> 

From jari.arkko@piuha.net  Tue Jul 30 07:34:27 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE47121F8BCE for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 07:34:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.589
X-Spam-Level: 
X-Spam-Status: No, score=-102.589 tagged_above=-999 required=5 tests=[AWL=0.010, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hGQ4ciWuvi+y for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 07:34:21 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 4B7BF21F9AEB for <ietf@ietf.org>; Tue, 30 Jul 2013 07:34:08 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id C35232CC60; Tue, 30 Jul 2013 17:34:03 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kqEVl17Bpbxs; Tue, 30 Jul 2013 17:34:03 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id D97BC2CC5D; Tue, 30 Jul 2013 17:34:02 +0300 (EEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: IETF-Blog comments (Was Re: setting a goal for an inclusive IETF)
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <51F7CCD5.5080202@gmail.com>
Date: Tue, 30 Jul 2013 16:34:02 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <E248EA0A-33AC-4653-9432-89D07B83F9DD@piuha.net>
References: <EDC539D2-48CE-44D7-A06C-19EEAE42D31C@piuha.net> <51F7CCD5.5080202@gmail.com>
To: Arturo Servin <arturo.servin@gmail.com>
X-Mailer: Apple Mail (2.1508)
Cc: Pete Resnick <presnick@qti.qualcomm.com>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2013 14:34:27 -0000

Arturo:

> 	Now, something general related to the blog. Perhaps it would be =
good to
> enable comments, isn't it?


Yes, that has been issue that has bugged me as well. The IT team tells =
me that it is problematic from a spam perspective, and they do not want =
me spending my time approving/removing comments. I don't have practical =
experience if that's a real issue on this platform (WordPress), though =
in other similar arrangements it has not been a big problem in my =
experience. Maybe the IETF community has some advice to us on this...

Jari


From arturo.servin@gmail.com  Tue Jul 30 07:40:49 2013
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8EF511E80D3 for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 07:40:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OFFCAYmXSi8N for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 07:40:47 -0700 (PDT)
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 0E83621F9CE8 for <ietf@ietf.org>; Tue, 30 Jul 2013 07:40:46 -0700 (PDT)
Received: by mail-yh0-f50.google.com with SMTP id a41so2458146yho.23 for <ietf@ietf.org>; Tue, 30 Jul 2013 07:40:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=B4j1wqBLIklvgRSdsFSRU+d+vwpOZufNX899SUPgNw0=; b=QeflkD4WD8+Is+VHncSI5me0vujHz3X1AfrcPR6IHMuMWl10zLISO5YKGUhzkF6J+o toSH0JC9+n8fr13CvYB0GzUw33oSedj7n+2Vybj0tJr8Fr5VJPZr7dOIJ5NL33yqEF8J lS9O84qVEhvSFgECZKUwMfiE/f/BSE1Q9CVN4ZiQeaqrcgEQ0dT6OFpzf3wN+8H2aTL4 2zMTDhOGp8lFyGkRQeuiSojoYVGawMGzZwBu9bWhlifjO+vF/zUnMFxm0DmVS3oQJuNN dpXZEecFVXeCkfZVcxW5aLMevs261zc4XzfW4sE2Dj32jeSRsEniTRvFFomxPeB6vy9e jYqw==
X-Received: by 10.236.1.100 with SMTP id 64mr27959980yhc.219.1375195246301; Tue, 30 Jul 2013 07:40:46 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local ([2001:df8:0:16:dc07:9710:b85d:1730]) by mx.google.com with ESMTPSA id s47sm91776038yhl.19.2013.07.30.07.40.44 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 30 Jul 2013 07:40:45 -0700 (PDT)
Message-ID: <51F7D06A.9080707@gmail.com>
Date: Tue, 30 Jul 2013 16:40:42 +0200
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: IETF-Blog comments (Was Re: setting a goal for an inclusive IETF)
References: <EDC539D2-48CE-44D7-A06C-19EEAE42D31C@piuha.net> <51F7CCD5.5080202@gmail.com> <E248EA0A-33AC-4653-9432-89D07B83F9DD@piuha.net>
In-Reply-To: <E248EA0A-33AC-4653-9432-89D07B83F9DD@piuha.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Pete Resnick <presnick@qti.qualcomm.com>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2013 14:40:49 -0000

    Captchas? Recaptchas?

    Also, AFAIK WordPress has some good anti-spam add-ons.

Regards,
as




On 7/30/13 4:34 PM, Jari Arkko wrote:
> Arturo:
>
>> 	Now, something general related to the blog. Perhaps it would be good to
>> enable comments, isn't it?
>
> Yes, that has been issue that has bugged me as well. The IT team tells me that it is problematic from a spam perspective, and they do not want me spending my time approving/removing comments. I don't have practical experience if that's a real issue on this platform (WordPress), though in other similar arrangements it has not been a big problem in my experience. Maybe the IETF community has some advice to us on this...
>
> Jari
>


From chair@ietf.org  Tue Jul 30 07:41:11 2013
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82D8A21E80C6 for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 07:41:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iZ2P4nurRPa4 for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 07:41:10 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:15]) by ietfa.amsl.com (Postfix) with ESMTP id 8968621E80D8 for <ietf@ietf.org>; Tue, 30 Jul 2013 07:41:09 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id A0E589FB9D for <ietf@ietf.org>; Tue, 30 Jul 2013 07:41:02 -0700 (PDT)
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 JeL3OAB3Vr0u for <ietf@ietf.org>; Tue, 30 Jul 2013 07:41:02 -0700 (PDT)
Received: from dhcp-14b8.meeting.ietf.org (dhcp-14b8.meeting.ietf.org [130.129.20.184]) by c9a.amsl.com (Postfix) with ESMTPSA id 0AB7C9FB9A for <ietf@ietf.org>; Tue, 30 Jul 2013 07:41:01 -0700 (PDT)
From: IETF Chair <chair@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: PS to IS question from plenary
Message-Id: <F3241893-F062-4F09-BA09-398BE207192F@ietf.org>
Date: Tue, 30 Jul 2013 16:41:06 +0200
To: "ietf@ietf.org list" <ietf@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2013 14:41:11 -0000

Last night there was a question in the plenary about how many PS->IS =
transitions have occurred since RFC 6410 was published in October 2011. =
That RFC changed the three-step standards process to two steps. There =
was also a question of how this compared to previous times before that =
RFC got approved.

Looking at the timeframe from October 2011 to today (22 months), there =
have been four such protocol actions. These results are given by =
searching the IETF Announce mail archive:

0.1000 	12159 	07/16/2013 	Protocol Action: 'Specification of the =
IP Flow Information eXport (IPFIX) Protocol for the Exchange of Flow =
Information' to Internet Standard 	iesg-secretary@ietf.org=20
0.1000 	12036 	06/04/2013 	Protocol Action: DomainKeys Identified =
Mail (DKIM) Signatures to Internet Standard 	iesg-secretary@ietf.org=20=

0.1000 	11609 	01/25/2013 	Protocol Action: 'Extension Mechanisms =
for DNS (EDNS(0))' to Internet Standard =
(draft-ietf-dnsext-rfc2671bis-edns0-10.txt) 	iesg-secretary@ietf.org=20=

0.1000 	11510 	01/03/2013 	Protocol Action: 'Automated Updates of =
DNSSEC Trust Anchors' to Internet Standard (RFC 5011) 	=
iesg-secretary@ietf.org=20

Prior to the publication of RFC 6410, in the preceding 22 months there =
were these 20 actions raising standards to either Draft Standard or Full =
Standard:

0.1000 	9572 	07/12/2011 	Protocol Action: 'DomainKeys Identified =
Mail (DKIM) Signatures' to Draft Standard =
(draft-ietf-dkim-rfc4871bis-15.txt) 	iesg-secretary@ietf.org=20
0.1000 	9427 	06/06/2011 	Protocol Action: 'Transport Layer =
Security (TLS) Transport Model for the Simple Network Management =
Protocol (SNMP)' to Draft Standard 	iesg@ietf.org=20
0.1000 	9402 	05/31/2011 	Protocol Action: 'Transport Security =
Model for the Simple Network Management Protocol (SNMP)' to Draft =
Standard 	iesg-secretary@ietf.org=20
0.1000 	9401 	05/31/2011 	Protocol Action: 'Transport Subsystem =
for the Simple Network Management Protocol (SNMP)' to Draft Standard 	=
iesg-secretary@ietf.org=20
0.1000 	9400 	05/31/2011 	Protocol Action: 'Simple Network =
Management Protocol (SNMP) Context EngineID Discovery' to Draft Standard =
	iesg-secretary@ietf.org=20
0.1000 	7410 	01/25/2010 	Protocol Action: 'ESMTP and LMTP =
Transmission Types Registration' to Draft Standard 	=
iesg-secretary@ietf.org=20
0.1000 	6858 	08/17/2009 	Protocol Action: 'Guidance on =
Interoperation and Implementation Reports for Advancement to Draft =
Standard' to BCP 	iesg-secretary@ietf.org=20
0.1000 	6819 	07/29/2009 	Protocol Action: 'Cryptographic Message =
Syntax (CMS)' to Draft Standard 	iesg-secretary@ietf.org=20
0.1000 	6816 	07/29/2009 	Protocol Action: 'TCP Congestion =
Control' to Draft Standard 	iesg-secretary@ietf.org=20
0.1000 	6256 	03/05/2009 	Protocol Action: 'RPC: Remote Procedure =
Call Protocol Specification Version 2' to Draft Standard 	=
iesg-secretary@ietf.org=20
0.1000 	6069 	01/14/2009 	Protocol Action: 'Capabilities =
Advertisement with BGP-4' to Draft Standard 	iesg-secretary@ietf.org=20=


0.1000 	10108 	12/05/2011 	Protocol Action: 'The Multipart/Report =
Media Type for the Reporting of Mail System Administrative Messages' to =
Full Standard 	iesg-secretary@ietf.org=20
0.1000 	9781 	09/06/2011 	Protocol Action: 'Message Submission for =
Mail' to Full Standard (draft-ietf-yam-rfc4409bis-03.txt) 	=
iesg-secretary@ietf.org=20
2.3656 	8034 	06/21/2010 	Protocol Action: 'Cryptographic Message =
Syntax (CMS)' to Full Standard 	iesg-secretary@ietf.org=20
2.4437 	7668 	03/15/2010 	Protocol Action: 'SMTP Service Extension =
for 8-bit MIME Transport' to Full Standard 	iesg-secretary@ietf.org=20=

2.2366 	6876 	08/19/2009 	Protocol Action: 'Extensible =
Provisioning Protocol (EPP) Transport over TCP' to Full Standard 	=
iesg-secretary@ietf.org=20
2.4694 	6784 	07/20/2009 	Protocol Action: 'Extensible =
Provisioning Protocol (EPP) Contact Mapping' to Full Standard 	=
iesg-secretary@ietf.org=20
2.2972 	6783 	07/20/2009 	Protocol Action: 'Extensible =
Provisioning Protocol (EPP) Host Mapping' to Full Standard 	=
iesg-secretary@ietf.org=20
2.1632 	6782 	07/20/2009 	Protocol Action: 'Extensible =
Provisioning Protocol (EPP) Domain Name Mapping' to Full Standard 	=
iesg-secretary@ietf.org=20
2.5992 	6781 	07/20/2009 	Protocol Action: 'Extensible =
Provisioning Protocol (EPP)' to Full Standard 	iesg-secretary@ietf.org=20=


I should insert here the Standard disclaimer about possibly faulty =
search methodology or records, misunderstanding the question, or the =
hasty interpretation of results. In particular, the above search was not =
easy on ARO, involved manual steps, and I might have easily missed =
something. And I wish I had been able to do a database query instead. =
Feel free to repeat & verify my results...

Jari


From stpeter@stpeter.im  Tue Jul 30 07:42:52 2013
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42CC321E8105 for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 07:42:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.465
X-Spam-Level: 
X-Spam-Status: No, score=-102.465 tagged_above=-999 required=5 tests=[AWL=0.134, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RfIwGIXuG+EF for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 07:42:47 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 03D4011E8219 for <ietf@ietf.org>; Tue, 30 Jul 2013 07:42:46 -0700 (PDT)
Received: from ergon.local (unknown [198.135.0.233]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id C52284010C; Tue, 30 Jul 2013 08:44:52 -0600 (MDT)
Message-ID: <51F7D0DE.1080204@stpeter.im>
Date: Tue, 30 Jul 2013 16:42:38 +0200
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Arturo Servin <arturo.servin@gmail.com>
Subject: Re: IETF-Blog comments (Was Re: setting a goal for an inclusive IETF)
References: <EDC539D2-48CE-44D7-A06C-19EEAE42D31C@piuha.net> <51F7CCD5.5080202@gmail.com> <E248EA0A-33AC-4653-9432-89D07B83F9DD@piuha.net> <51F7D06A.9080707@gmail.com>
In-Reply-To: <51F7D06A.9080707@gmail.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Pete Resnick <presnick@qti.qualcomm.com>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2013 14:42:52 -0000

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

On 7/30/13 4:40 PM, Arturo Servin wrote:
> 
> Captchas? Recaptchas?
> 
> Also, AFAIK WordPress has some good anti-spam add-ons.

Yes, Akismet helps a lot.

But this is probably a better topic for the tools-discuss list, eh? ;-)

Peter

- -- 
Peter Saint-Andre
https://stpeter.im/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJR99DeAAoJEOoGpJErxa2paf0P/ibhxJvhK65617nRN8HUrnWC
gBVEl9qhBVErHjHpR2f3Ah1Zp1+0wcsBHxF99qwVyUQJKuhZXhxMBw99fYaY+NWm
lsUQRpMFvoOXEkKguYyy0tNMO2qelysrD7K7xyqK7rD4i4hqowHxz5pDMMohPyYi
DBzxbUyzltC9OAsdIPcvDJ1KmoMJPs9R/WvqBu5OkhvDhPFFjKVyCrOwe0iPQCVR
b1cpPpZpyFbPhZES45R2aiWu2Mnb6OSyzgfz0J+ffjvSvqfx7hxBhHFGg35HGI/C
H7jp2T2dj9nRuO3DbZD+mnAdf0A2pNIEahx/jCrZtbL2YoYc0+DtOb7OoURIVxBH
iVQ+DSpjZooZ/ntSWi7VWVpphdSQFRlYMuXabV7XMp06TOY2XZa4o8+sXKZDGsGY
1U5h13STpNvNg3X9J6z5tuQxMazbNVSNsBjBNa7IlSLzTg4x3ocgxP65OB05z+Qp
xqWnfNWmwiBGnicLsfLEnbh7I7Wy3OL0W8uK56+8NdTmGaQ1HUtXu3O/WO70VW4p
eOAGX+yLWgXxx+42roHV4UGCrg+yCZw/FhpDKpeuTkLBFWjt99zuznH4r4chzMsS
EO7YOtE+ZMS4QbE3vbg3EiZ2f3Sw8EBFlvw3L1EYhZczItyA/+SuUTGkFii/spX/
c/ZGzK9tXrVZPvWKa/an
=31+l
-----END PGP SIGNATURE-----

From joelja@bogus.com  Tue Jul 30 07:44:10 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD1A211E8222 for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 07:44:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qxeu--USNoG1 for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 07:44:10 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 0C12D11E821B for <ietf@ietf.org>; Tue, 30 Jul 2013 07:44:08 -0700 (PDT)
Received: from dhcp-603a.meeting.ietf.org (dhcp-603a.meeting.ietf.org [130.129.96.58]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r6UEi2jG069634 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Tue, 30 Jul 2013 14:44:04 GMT (envelope-from joelja@bogus.com)
Message-ID: <51F7D134.6020307@bogus.com>
Date: Tue, 30 Jul 2013 16:44:04 +0200
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:23.0) Gecko/20100101 Thunderbird/23.0
MIME-Version: 1.0
To: Arturo Servin <arturo.servin@gmail.com>, Jari Arkko <jari.arkko@piuha.net>
Subject: Re: IETF-Blog comments (Was Re: setting a goal for an inclusive IETF)
References: <EDC539D2-48CE-44D7-A06C-19EEAE42D31C@piuha.net>	<51F7CCD5.5080202@gmail.com>	<E248EA0A-33AC-4653-9432-89D07B83F9DD@piuha.net> <51F7D06A.9080707@gmail.com>
In-Reply-To: <51F7D06A.9080707@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Tue, 30 Jul 2013 14:44:05 +0000 (UTC)
Cc: Pete Resnick <presnick@qti.qualcomm.com>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2013 14:44:11 -0000

On 7/30/13 4:40 PM, Arturo Servin wrote:
>     Captchas? Recaptchas?
>
>     Also, AFAIK WordPress has some good anti-spam add-ons.
the obvious one is simply a requirement to use your ietf tools
credientials to post.
>
> Regards,
> as
>
>
>
>
> On 7/30/13 4:34 PM, Jari Arkko wrote:
>> Arturo:
>>
>>> 	Now, something general related to the blog. Perhaps it would be good to
>>> enable comments, isn't it?
>> Yes, that has been issue that has bugged me as well. The IT team tells me that it is problematic from a spam perspective, and they do not want me spending my time approving/removing comments. I don't have practical experience if that's a real issue on this platform (WordPress), though in other similar arrangements it has not been a big problem in my experience. Maybe the IETF community has some advice to us on this...
>>
>> Jari
>>


From arturo.servin@gmail.com  Tue Jul 30 07:45:22 2013
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2BD721F9963 for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 07:45:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cv0f07Rs2oB2 for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 07:45:21 -0700 (PDT)
Received: from mail-ye0-x233.google.com (mail-ye0-x233.google.com [IPv6:2607:f8b0:4002:c04::233]) by ietfa.amsl.com (Postfix) with ESMTP id 09E3321F92E7 for <ietf@ietf.org>; Tue, 30 Jul 2013 07:44:40 -0700 (PDT)
Received: by mail-ye0-f179.google.com with SMTP id m15so923595yen.24 for <ietf@ietf.org>; Tue, 30 Jul 2013 07:44:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=JB0OTET5rakPX0TmOxCWh3yKlLNnvD7AFGTWsSjQOhU=; b=T7/B/kK23HeD32KcUn23VMhiHiJLiuf2J1cii0d/+4nmmnk17/Y+ZqIJP9ekwTQn+3 Tfdp98aTJtqad95jkd22PpnmWt+vjcY+eLyJd5/oeJaH3pyaktsxfJekw8l2dkGiRHU0 qkoVbpHnbzEiZxXH0OouTntWNHDfExsVbEL5aYbztaa73o797Owpg9y6nxp0bTR+wuyQ VwP33cHDD+LKyB2rLSx2tf5T2Hm6kLjY7h80m4M9GizwYTzB91eQkLxKCYRX9v9bgmgB kuJjmp+lcOQWhF0rabBONf76KIlHzWTzB5z9LWKSXQhq2pK/SUiS242JyZkvRy5renzE l73w==
X-Received: by 10.236.179.135 with SMTP id h7mr4731954yhm.216.1375195480586; Tue, 30 Jul 2013 07:44:40 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local ([2001:df8:0:16:dc07:9710:b85d:1730]) by mx.google.com with ESMTPSA id d68sm91783946yhk.7.2013.07.30.07.44.38 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 30 Jul 2013 07:44:39 -0700 (PDT)
Message-ID: <51F7D156.4070003@gmail.com>
Date: Tue, 30 Jul 2013 16:44:38 +0200
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: IETF-Blog comments (Was Re: setting a goal for an inclusive IETF)
References: <EDC539D2-48CE-44D7-A06C-19EEAE42D31C@piuha.net> <51F7CCD5.5080202@gmail.com> <E248EA0A-33AC-4653-9432-89D07B83F9DD@piuha.net> <51F7D06A.9080707@gmail.com> <51F7D0DE.1080204@stpeter.im>
In-Reply-To: <51F7D0DE.1080204@stpeter.im>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Pete Resnick <presnick@qti.qualcomm.com>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2013 14:45:22 -0000

On 7/30/13 4:42 PM, Peter Saint-Andre wrote:
> On 7/30/13 4:40 PM, Arturo Servin wrote:
>
> > Captchas? Recaptchas?
>
> > Also, AFAIK WordPress has some good anti-spam add-ons.
>
> Yes, Akismet helps a lot.
>
> But this is probably a better topic for the tools-discuss list, eh? ;-)
>
> Peter
>
Peter,

    I thought it was another not-technical reason. Now that is clear,
let's move on.

    Thanks for the quick reply.

/as

From ad707@hermes.cam.ac.uk  Tue Jul 30 07:48:22 2013
Return-Path: <ad707@hermes.cam.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FE1111E8205 for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 07:48:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.949
X-Spam-Level: 
X-Spam-Status: No, score=-1.949 tagged_above=-999 required=5 tests=[AWL=0.650,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KCyu0uDHDUkn for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 07:48:22 -0700 (PDT)
Received: from ppsw-33.csi.cam.ac.uk (ppsw-33.csi.cam.ac.uk [IPv6:2001:630:212:8::e:f33]) by ietfa.amsl.com (Postfix) with ESMTP id 1A20211E81D6 for <ietf@ietf.org>; Tue, 30 Jul 2013 07:48:21 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-2.csi.cam.ac.uk ([131.111.8.54]:54743) by ppsw-33.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:25) with esmtpa (EXTERNAL:ad707) id 1V4BDo-0007X9-gr (Exim 4.80_167-5a66dd3) (return-path <ad707@hermes.cam.ac.uk>); Tue, 30 Jul 2013 15:48:20 +0100
Received: from prayer by hermes-2.csi.cam.ac.uk (hermes.cam.ac.uk) with local (PRAYER:ad707) id 1V4BDo-0001Pb-88 (Exim 4.72) (return-path <ad707@hermes.cam.ac.uk>); Tue, 30 Jul 2013 15:48:20 +0100
Received: from [130.129.82.211] by webmail.hermes.cam.ac.uk with HTTP (Prayer-1.3.5); 30 Jul 2013 15:48:20 +0100
Date: 30 Jul 2013 15:48:20 +0100
From: Aaron Yi DING <Aaron.Ding@cl.cam.ac.uk>
To: arturo.servin@gmail.com
Subject: Re: IETF-Blog comments
Message-ID: <Prayer.1.3.5.1307301548200.2870@hermes-2.csi.cam.ac.uk>
X-Mailer: Prayer v1.3.5
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Sender: Aaron Yi DING <ad707@hermes.cam.ac.uk>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2013 14:48:22 -0000

On 30/07/13 16:34, Jari Arkko wrote:
> Arturo:
>
>> =09Now, something general related to the blog. Perhaps it would be good =
to
>> enable comments, isn't it?
>


understandable. based on the experience running one blog for a=20
organization, if such posts are in English, easily ended up with loads of=
=20
them. either bots or real-human spammer... my impression is that other=20
languages are kinda immune to those, e.g., Finnish ;)

Cheers,
Aaron


>
> Yes, that has been issue that has bugged me as well. The IT team tells=20
> me that it is problematic from a spam perspective, and they do not want=
=20
> me spending my time approving/removing comments. I don't have practical=
=20
> experience if that's a real issue on this platform (WordPress), though in=
=20
> other similar arrangements it has not been a big problem in my=20
> experience. Maybe the IETF community has some advice to us on this...
>
> Jari
>


From ad707@hermes.cam.ac.uk  Tue Jul 30 07:58:27 2013
Return-Path: <ad707@hermes.cam.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5038521E80CC for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 07:58:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.285
X-Spam-Level: 
X-Spam-Status: No, score=-1.285 tagged_above=-999 required=5 tests=[AWL=-0.448, BAYES_00=-2.599, MISSING_SUBJECT=1.762]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A5KDjsjqvj8g for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 07:58:26 -0700 (PDT)
Received: from ppsw-32.csi.cam.ac.uk (ppsw-32.csi.cam.ac.uk [IPv6:2001:630:212:8::e:f32]) by ietfa.amsl.com (Postfix) with ESMTP id 2201021E80C8 for <ietf@ietf.org>; Tue, 30 Jul 2013 07:58:25 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-2.csi.cam.ac.uk ([131.111.8.54]:60152) by ppsw-32.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.156]:25) with esmtpa (EXTERNAL:ad707) id 1V4BNY-0002SH-2q (Exim 4.80_167-5a66dd3) (return-path <ad707@hermes.cam.ac.uk>); Tue, 30 Jul 2013 15:58:24 +0100
Received: from prayer by hermes-2.csi.cam.ac.uk (hermes.cam.ac.uk) with local (PRAYER:ad707) id 1V4BNY-0002Sl-Qo (Exim 4.72) (return-path <ad707@hermes.cam.ac.uk>); Tue, 30 Jul 2013 15:58:24 +0100
Received: from [130.129.82.211] by webmail.hermes.cam.ac.uk with HTTP (Prayer-1.3.5); 30 Jul 2013 15:58:24 +0100
Date: 30 Jul 2013 15:58:24 +0100
From: Aaron Yi DING <Aaron.Ding@cl.cam.ac.uk>
To: joelja@bogus.com
Message-ID: <Prayer.1.3.5.1307301558240.2870@hermes-2.csi.cam.ac.uk>
X-Mailer: Prayer v1.3.5
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset=ISO-8859-1
Sender: Aaron Yi DING <ad707@hermes.cam.ac.uk>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2013 14:58:27 -0000

On 30/07/13 16:44, joel jaeggli wrote:
> On 7/30/13 4:40 PM, Arturo Servin wrote:
>>     Captchas? Recaptchas?
>>
>>     Also, AFAIK WordPress has some good anti-spam add-ons.


> the obvious one is simply a requirement to use your ietf tools
> credientials to post.


+1. the best current practice so far.

Cheers,
Aaron


>>
>> Regards,
>> as
>>
>>
>>
>>
>> On 7/30/13 4:34 PM, Jari Arkko wrote:
>>> Arturo:
>>>
>>>>    Now, something general related to the blog. Perhaps it would be 
>>>> good to enable comments, isn't it?
>>> Yes, that has been issue that has bugged me as well. The IT team tells 
>>> me that it is problematic from a spam perspective, and they do not want 
>>> me spending my time approving/removing comments. I don't have practical 
>>> experience if that's a real issue on this platform (WordPress), though 
>>> in other similar arrangements it has not been a big problem in my 
>>> experience. Maybe the IETF community has some advice to us on this...
>>>
>>> Jari
>>>
>


From stpeter@stpeter.im  Tue Jul 30 08:17:23 2013
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FA4F21F9D9A for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 08:17:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.436
X-Spam-Level: 
X-Spam-Status: No, score=-102.436 tagged_above=-999 required=5 tests=[AWL=0.163, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KonAmxEfKvlS for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 08:17:18 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id A5E7121F9D5A for <ietf@ietf.org>; Tue, 30 Jul 2013 08:17:16 -0700 (PDT)
Received: from ergon.local (unknown [198.135.0.233]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 93DC2F1DDB; Tue, 30 Jul 2013 09:19:27 -0600 (MDT)
Message-ID: <51F7D8F9.9090806@stpeter.im>
Date: Tue, 30 Jul 2013 17:17:13 +0200
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Arturo Servin <arturo.servin@gmail.com>
Subject: Re: IETF-Blog comments (Was Re: setting a goal for an inclusive IETF)
References: <EDC539D2-48CE-44D7-A06C-19EEAE42D31C@piuha.net> <51F7CCD5.5080202@gmail.com> <E248EA0A-33AC-4653-9432-89D07B83F9DD@piuha.net> <51F7D06A.9080707@gmail.com> <51F7D0DE.1080204@stpeter.im> <51F7D156.4070003@gmail.com>
In-Reply-To: <51F7D156.4070003@gmail.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Pete Resnick <presnick@qti.qualcomm.com>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2013 15:17:23 -0000

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

On 7/30/13 4:44 PM, Arturo Servin wrote:
> 
> On 7/30/13 4:42 PM, Peter Saint-Andre wrote:
>> On 7/30/13 4:40 PM, Arturo Servin wrote:
>> 
>>> Captchas? Recaptchas?
>> 
>>> Also, AFAIK WordPress has some good anti-spam add-ons.
>> 
>> Yes, Akismet helps a lot.
>> 
>> But this is probably a better topic for the tools-discuss list,
>> eh? ;-)
>> 
>> Peter
>> 
> Peter,
> 
> I thought it was another not-technical reason. Now that is clear, 
> let's move on.
> 
> Thanks for the quick reply.

Two issues here:

(1) do we want comments? seems like a topic for ietf@ietf.org

(2) if we want comments, how do we handle it? seems like a topic for
tools-discuss@ietf.org

Peter

- -- 
Peter Saint-Andre
https://stpeter.im/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJR99j5AAoJEOoGpJErxa2paPkQAKawmqpicUBrrx6ACDOZy3Lh
tUgMl9/fA5o/MU83TH2WZfalcg6ZrBksrQY8ia/jV9clRHW1RnaW4lMGDHeDRxM6
bNzXVLZ84Y5bclFHz9lQRzFOpVftCwuuHNtZ9nK8M0v/rAG4ViG5bknWBPiFOi2U
qZhbamLY0TJ2mMLpufpd+uQBSbrt8nM5QYRcZj1nIvG1wnpsaRF7lPFHy3Y34a2x
9lo/e1VM1LtYtP/4jaV2rSWGPIPSzLgdvjRHk8m1OqLmXVtrpWVlk0ibH7G0gmQE
X18g6TbgpdDTGrotmctIT19LHkS231fys9YQfOguDRfEZS9FZqOpLm/jEL4xUjUO
wcNoFbDG2eicvZmo/cwV37nMZ9Ayj5HFlzlm3tD38Nl8MEp1l+K1M8gzwo89ZRce
uinNOoQf9FFtVnqQtWC+/263P6DbDV68pmN8ThE1dOX7ySlPrq5z+Lll3eUr9rr5
sh8YUhOw/v/AtpKPOk2SDDvRWMItM6tFO4Kg3MU8trAyUDZLoGMELCx4SlBuP53l
pJXOivUBUNOY5cq/8+YK8CzhQjnhAni0n4l5SNyp48vvJGt+RCZ34DEW2x8uzCJc
y9vmHSIc0CefwZplI77uuptS0IheOn6i9P5v5zf0/rExSgfaXs5lv4iy1XiRat1/
BXSrBkR/tCx4xwxxQBwn
=pt0D
-----END PGP SIGNATURE-----

From moore@network-heretics.com  Tue Jul 30 08:26:02 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 828E321E80DE for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 08:26:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.349
X-Spam-Level: 
X-Spam-Status: No, score=-3.349 tagged_above=-999 required=5 tests=[AWL=0.250,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IRAuwk7GLAy2 for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 08:25:57 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id F413721E8082 for <ietf@ietf.org>; Tue, 30 Jul 2013 08:25:56 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 72E9B208FF; Tue, 30 Jul 2013 11:25:50 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute5.internal (MEProxy); Tue, 30 Jul 2013 11:25:50 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id :references:to; s=smtpout; bh=a0kYUThqRSyITeOdyiWgozhFC5k=; b=ZY 5+MJXp2CkZIn9KoyUQirqloTb8k+WcJbH3ed7uGgUve7FwWBlZB6nsKtsHRzgJrf AB+ux3NCHkMw75YKEZMu96fal1zjbWYrUhtanrKM7stGFpmI9cRQKKF1BiiwbYPo wk7M8NN12XA2mjKtRK21+LJGcf2iBgJMEQvjTdH1E=
X-Sasl-enc: joLcmjNlIIwAj8EMc1PCCkPKOLF3W/Ptv+RoUtTz09P/ 1375197949
Received: from surfer-172-29-8-65-hotspot.internet-for-guests.com (unknown [87.193.195.90]) by mail.messagingengine.com (Postfix) with ESMTPA id A09B4680085; Tue, 30 Jul 2013 11:25:49 -0400 (EDT)
Subject: Re: Bringing back Internet transparency
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <20130730132305.5AA8518C111@mercury.lcs.mit.edu>
Date: Tue, 30 Jul 2013 17:25:48 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <C6586196-4034-4A3D-8B4C-24B2D2ED6E92@network-heretics.com>
References: <20130730132305.5AA8518C111@mercury.lcs.mit.edu>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
X-Mailer: Apple Mail (2.1085)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2013 15:26:02 -0000

On Jul 30, 2013, at 3:23 PM, Noel Chiappa wrote:

>> From: Roland Bless <roland.bless@kit.edu>
>=20
>> we probably need to do something on reducing the number of _broken_
>> middleboxes (or their implementations respectively) - I'm not =
focusing
>> on NAT boxes here.
>> ...
>> I think it's clear that we will not get rid of them, but if I hear
>> about boxes that try to do "clever optimization" or "security" by
>> re-writing TCP sequence numbers ... bundling segments and so on, I'm
>> wondering who actually engineered those boxes; aren't the
>> vendors/engineers participating in the IETF? Who buys and deploys =
such
>> boxes
>> ...
>> What could be IETF efforts to get a better situation for the =
deployment
>> of future innovations or do we simply accept that (a few) broken
>> middleboxes dictate the future level of innovation in the Internet?
>=20
> I hear you, but... this is not a simple problem.
>=20
> I think we need to start by understanding what drives the creation and
> deployment of these devices. I think the answer to that has to be that =
some
> people have needs that aren't being met by the IETF, and so there's an
> opportunity for private entities to create and sell 'solutions'.
>=20
> The IETF doesn't have a police force, or any enforcement mechanism.

That's true, but people do sometimes cite IETF specifications as =
requirements for equipment procurement.   And in many cases it is =
possible to test equipment for conformance to specifications.

> If we're
> going to head off these boxes, the only tool we have to do that is to =
build
> better mousetraps - i.e. design stuff that does what people want, is =
more
> cost-effective, and is better than these local 'point deployment' =
boxes.

That's not the "only tool" (see above), but to the extent we're failing =
to address legitimate needs, we need to identify those needs and see =
what we can do to address them. And we need to do this as early as =
possible, ideally before we've gone down a particular path so far that =
there's too much deployment of a protocol that can't be retro-fitted to =
address those needs.   We have no structure at all for doing this now.

> Sadly, the IETF has a long history of being hard-headed about 'my way =
or the
> highway', and not carefully listening to what the 'customers' are =
telling us
> about these various aspects of a successful design.

I suspect it's worse than that.   We don't even know who our customers =
are.

>=20
> (The most noteable example of this being NAT - which was going to be =
ugly
> anyway, but as a result of the IETF refusing to create an architected =
NAT
> solution - apparently on the theory that if we stuck our fingers in =
our ears
> and went la-la-la-la loud enough, it would Just Go Away - we now have =
NAT that
> is both ugly _and_ brittle [because it's not part of an architected =
_system_],
> difficult to work with because it [mostly] lacks any external control
> interface, etc.)

It's ridiculous to say that we have NAT because we didn't architect NAT. =
 NAT has never been a good idea from any long-term point of view.   The =
only justifications that have ever existed for NAT were short-term =
hacks.     Our mistake, in hindsight, was in not specifying NAT in such =
a way that they provided a transition path away from NATs.   (perhaps =
something like PCP in conjunction with v4/v6 NAT, though there's a huge =
privacy/security problem with that kind of approach that I've never =
figured out how to address, so I'm inclined to think that PCP makes =
things still worse.)  =20

Though of course an underlying problem is that no vendor wants to sell =
hardware that will obsolete itself, unless of course it obsoletes itself =
by requiring the customer to purchase even more expensive hardware than =
it replaces.    It's hard to see how IETF could fight against vendors =
who were making good money by making the network more complex, less =
reliable, and less flexible.

Keith



From sm@resistor.net  Tue Jul 30 08:51:11 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 645BA21E80CC for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 08:51:11 -0700 (PDT)
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=[AWL=0.063, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tpBqlut9bp2g for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 08:51:10 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9304721F9CCA for <ietf@ietf.org>; Tue, 30 Jul 2013 08:51:10 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r6UFp3pD020091; Tue, 30 Jul 2013 08:51:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1375199469; bh=MmCOlpgILAo+flmKtwkJUZtw2WGUdCUaA5j8GaeiZYM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=0ZUUGkF9bkUQXH/jYZtS45ZVoUcl/kpKqWis9QZNt6TllhfsMeosFZDJnNI0k3+jz xT68ArfW8xPJRO9jjjnBpNSzT0jqidRec1tttX4IpsMpKJ2MmRtiyvbX2Ew6otMKqU 0wdwxpJv3jqJMjJa4RAdDTpr2+iSmF5oyYM294es=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1375199469; i=@resistor.net; bh=MmCOlpgILAo+flmKtwkJUZtw2WGUdCUaA5j8GaeiZYM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Dplzn9G/EZgWinkYo2X12Exx94k5OrT1+iz5rBR2ph0r5u/tWacHbPKAXL4FzNdft mo+zdF9pVrUSrJHLp2Gxn4YfWaBs7T8KYWNfdxgETGWUVar/U8gcY2Pb70caKeB/QK q+3Tc3wOvdf57nZWgFC6fN57LqiXru8WFHvUeqXM=
Message-Id: <6.2.5.6.2.20130730080247.0d6ca2e8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 30 Jul 2013 08:47:33 -0700
To: Jari Arkko <jari.arkko@piuha.net>, Pete Resnick <presnick@qti.qualcomm.com>
From: SM <sm@resistor.net>
Subject: Re: setting a goal for an inclusive IETF
In-Reply-To: <EDC539D2-48CE-44D7-A06C-19EEAE42D31C@piuha.net>
References: <EDC539D2-48CE-44D7-A06C-19EEAE42D31C@piuha.net>
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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2013 15:51:11 -0000

Hi Jari, Pete,
At 06:53 30-07-2013, Jari Arkko wrote:
>We have discussed diversity at the IETF at length. Yesterday, Pete 
>Resnick and I wrote an article about what we think the goal for the 
>IETF should be, as well as listing some of the early activities that 
>we have taken at the IETF. Our goal is making the IETF more 
>inclusive for everyone who needs to be working on Internet 
>standards. We are at the beginning, however, and a lot of work 
>remains ahead. Here's the article:

I agree that the word "diversity" is a catch phrase.

There was an exchange between Leaf Yeh and Ted Hardie on this mailing 
list.  It is encouraging to see people from different sides of the 
world having an exchange of opinions.

It's been one IETF meeting since several women spoke at the 
microphone during the plenary.  There aren't that many people from 
different countries speaking at the microphone during a plenary.

I have one question.  The subject line says "setting a goal".  How 
would you assess the results?  Please note that I am not asking about 
how to measure the results.

Regards,
-sm 


From moore@network-heretics.com  Tue Jul 30 08:55:07 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC04B21F9A71 for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 08:54:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.132
X-Spam-Level: 
X-Spam-Status: No, score=-3.132 tagged_above=-999 required=5 tests=[AWL=-0.134, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_12=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0ewClThEthpn for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 08:54:51 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id 0296921F85E6 for <ietf@ietf.org>; Tue, 30 Jul 2013 08:54:50 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 7FA5920EC1; Tue, 30 Jul 2013 11:54:47 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute2.internal (MEProxy); Tue, 30 Jul 2013 11:54:47 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=N6+ aaEswTRf/VEtXWWYM/kYR/HE=; b=a3dmHLkck6N3DQxyJTW3qp68pRH9sShb9bb xFhTahIppYAwzs7SSw8wlGZoEl/AET8sDkJSb65N/ppjSuXKV03Ky0a82ViBJvJV dgqvasEiRyqgRvafa2clIzu9PxqJap+0nSs3CTiT2QnD8jVSr/5++09wyzzDl2UM LPLooxUw=
X-Sasl-enc: ADQvyOZVt9XrCzvpWD3G4qaQHeNNV9ifGOI61i8dIpue 1375199686
Received: from surfer-172-29-8-65-hotspot.internet-for-guests.com (unknown [87.193.195.90]) by mail.messagingengine.com (Postfix) with ESMTPA id 5299DC00E83; Tue, 30 Jul 2013 11:54:46 -0400 (EDT)
Subject: making our meetings more worth the time/expense (was: Re: setting a goal for an inclusive IETF)
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: multipart/alternative; boundary=Apple-Mail-3--391989669
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <EDC539D2-48CE-44D7-A06C-19EEAE42D31C@piuha.net>
Date: Tue, 30 Jul 2013 17:54:45 +0200
Message-Id: <BF2DD745-99D0-420E-B199-7C8F94981BDA@network-heretics.com>
References: <EDC539D2-48CE-44D7-A06C-19EEAE42D31C@piuha.net>
To: Jari Arkko <jari.arkko@piuha.net>
X-Mailer: Apple Mail (2.1085)
Cc: Pete Resnick <presnick@qti.qualcomm.com>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2013 15:55:07 -0000

--Apple-Mail-3--391989669
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Jul 30, 2013, at 3:53 PM, Jari Arkko wrote:

> We have discussed diversity at the IETF at length. Yesterday, Pete =
Resnick and I wrote an article about what we think the goal for the IETF =
should be, as well as listing some of the early activities that we have =
taken at the IETF. Our goal is making the IETF more inclusive for =
everyone who needs to be working on Internet standards. We are at the =
beginning, however, and a lot of work remains ahead. Here's the article:
>=20
> http://www.ietf.org/blog/2013/07/a-diverse-ietf/
>=20
> Also, I wanted to let everyone know that tomorrow in the =
Administrative Plenary, Kathleen Moriarty and Suresh Krishnan will be =
talking about what they have uncovered so far in their efforts in the =
diversity design team. I'm looking very much forward to their report. =
Their efforts will help us understand where we have room to improve - =
often by much :-) - and what kinds of actions we can take to improve our =
inclusiveness.

This is something that I've struggled with for years.   A big part of =
the "problem" (from one point-of-view) is that we've become so =
geographically diverse in our choice of meeting sites that we've =
drastically raised the cost of attending meetings on a regular basis - =
everyone has to travel a lot to so (though people in North America still =
have an easier time of it).   And while there are clearly things that =
could be done to reduce meeting costs, we'd be doing very well to reduce =
total trip cost by more than say 15%.

But earlier today I realized that the problem isn't just the cost of =
attending meetings - it's the value that we get in return for those =
meetings.   I've been taking notes about how ineffectively we use our =
meeting time.   Most of what I've observed won't surprise anybody, but =
here's a summary:

WG meeting sessions aren't scheduled to encourage discussion, but to =
discourage it.   At meeting after meeting, in several different areas, I =
see the lion's share of the time devoted to presentations rather than =
discussion.=20

Similarly, WG meetings generally aren't run in such a way to facilitate =
discussion, but to discourage it.  It's only Tuesday afternoon and I've =
already lost count of how many times I've heard a meeting chair tell =
people that they have to stop discussing things because there are more =
presentations to do.

Rooms are set up not to facilitate discussion, but to discourage it.   =
The lights are dim, the chairs are facing forward rather than other =
participants, the projector screen (not the person facilitating a =
discussion, even if someone is trying to facilitate a discussion) is the =
center of attention.    The chairs are set so close together and with so =
few aisles that it's hard for most of the attendees to get to the mics.  =
 The "microphone discipline" which was intended to facilitate remote =
participation ends up making discussion more difficult for everybody who =
has paid to be on site.=20

In the vast majority of WG sessions, everyone has his nose in a laptop.  =
 (me included).   This is because the information being presented at the =
moment is generally not valuable enough to occupy the attendees' =
attention.  The attendees are there for one of two reasons - either =
they're just trying to absorb some low-value information while still =
doing something else that is more useful, or they're waiting for some =
opportunity to actually interact - either within the context of that WG =
meeting or afterward (perhaps because the best way to catch a particular =
person is often to show up at a WG meeting that that person is =
attending.)

All of these things have been standard practice, in IETF and elsewhere, =
for so long, that hardly anyone questions them.   They have to be that =
way because they're habit, and even if one or two people try to change =
things (and I realize some ADs are trying), they have to contend with =
the mindless habit-driven decisions of everyone else involved.

Well, please excuse my candor, but f*ck habit.   We can't be effective =
engineers if we let bad habits continue to dictate how we work.

------


My expenses for this meeting are around USD 2.500.   Some are paying =
more, some less, but if we multiply average expense times the number of =
people attending, that's a tremendous amount of money.   Add that value =
is dwarfed by the value of the people's time that is being spent here.

We are spending this time to travel to meet face-to-face, not so that we =
can see PowerPoint all day for a week, but so we can interact.   =
Presentations, for the most part, do not help.   They get in the way.

Visual aids can help to facilitate a discussion, but they should be as =
brief as possible, and the room setup, meeting schedule, etc. should not =
be optimized for the visual aids.   They should be optimized for =
discussion.

For 80% of most WG meetings, the lights should be bright, the =
participants should face each other.   If there's a person facilitating =
the discussion that person should be the center of attention.    If =
we're going to use microphones, the rooms should be set up to allow =
everyone in the room to have easy access to them.   We should have =
several microphones, again facing each other, so that several people can =
have a conversation without everyone having to queue up.

And maybe, in addition, we need to provide better places for people to =
hang out and work while trying to get an opportunity to interact with =
specific people.   The terminal rooms are generally placed in =
out-of-the-way corners, but the most effective places to interact with =
people are in the hallways.


Keith


--Apple-Mail-3--391989669
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Jul 30, 2013, at 3:53 PM, Jari Arkko wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div>We =
have discussed diversity at the IETF at length. Yesterday, Pete Resnick =
and I wrote an article about what we think the goal for the IETF should =
be, as well as listing some of the early activities that we have taken =
at the IETF. Our goal is making the IETF more inclusive for everyone who =
needs to be working on Internet standards. We are at the beginning, =
however, and a lot of work remains ahead. Here's the article:<br><br><a =
href=3D"http://www.ietf.org/blog/2013/07/a-diverse-ietf/">http://www.ietf.=
org/blog/2013/07/a-diverse-ietf/</a><br><br>Also, I wanted to let =
everyone know that tomorrow in the Administrative Plenary, Kathleen =
Moriarty and Suresh Krishnan will be talking about what they have =
uncovered so far in their efforts in the diversity design team. I'm =
looking very much forward to their report. Their efforts will help us =
understand where we have room to improve - often by much :-) - and what =
kinds of actions we can take to improve our =
inclusiveness.<br></div></blockquote></div><br><div>This is something =
that I've struggled with for years. &nbsp; A big part of the "problem" =
(from one point-of-view) is that we've become so geographically diverse =
in our choice of meeting sites that we've drastically raised the cost of =
attending meetings on a regular basis - everyone has to travel a lot to =
so (though people in North America still have an easier time of it). =
&nbsp; And while there are clearly things that could be done to reduce =
meeting costs, we'd be doing very well to reduce total trip cost by more =
than say 15%.</div><div><br></div><div>But earlier today I realized that =
the problem isn't just the cost of attending meetings - it's the value =
that we get in return for those meetings. &nbsp; I've been taking notes =
about how ineffectively we use our meeting time. &nbsp; Most of what =
I've observed won't surprise anybody, but here's a =
summary:</div><div><br></div><div>WG meeting sessions aren't scheduled =
to encourage discussion, but to discourage it. &nbsp; At meeting after =
meeting, in several different areas, I see the lion's share of the time =
devoted to presentations rather than =
discussion.&nbsp;</div><div><br></div><div>Similarly, WG meetings =
generally aren't run in such a way to facilitate discussion, but to =
discourage it. &nbsp;It's only Tuesday afternoon and I've already lost =
count of how many times I've heard a meeting chair tell people that they =
have to stop discussing things because there are more =
<i>presentations</i> to do.</div><div><br></div><div>Rooms are set up =
not to facilitate discussion, but to discourage it. &nbsp; The lights =
are dim, the chairs are facing forward rather than other participants, =
the projector screen (not the person facilitating a discussion, even if =
someone is trying to facilitate a discussion) is the center of =
attention. &nbsp; &nbsp;The chairs are set so close together and with so =
few aisles that it's hard for most of the attendees to get to the mics. =
&nbsp; The "microphone discipline" which was intended to facilitate =
remote participation ends up making discussion more difficult for =
everybody who has paid to be on site.&nbsp;</div><div><br></div><div>In =
the vast majority of WG sessions, everyone has his nose in a laptop. =
&nbsp; (me included). &nbsp; This is because the information being =
presented at the moment is generally not valuable enough to occupy the =
attendees' attention. &nbsp;The attendees are there for one of two =
reasons - either they're just trying to absorb some low-value =
information while still doing something else that is more useful, or =
they're waiting for some opportunity to actually interact - either =
within the context of that WG meeting or afterward (perhaps because the =
best way to catch a particular person is often to show up at a WG =
meeting that that person is attending.)</div><div><br></div><div>All of =
these things have been standard practice, in IETF and elsewhere, for so =
long, that hardly anyone questions them. &nbsp; They have to be that way =
because they're habit, and even if one or two people try to change =
things (and I realize some ADs are trying), they have to contend with =
the mindless habit-driven decisions of everyone else =
involved.</div><div><br></div><div>Well, please excuse my candor, but =
f*ck habit. &nbsp; We can't be effective engineers if we let bad habits =
continue to dictate how we =
work.</div><div><br></div><div>------</div><div><br></div><div><br></div><=
div>My expenses for this meeting are around USD 2.500. &nbsp; Some are =
paying more, some less, but if we multiply average expense times the =
number of people attending, that's a tremendous amount of money. &nbsp; =
Add that value is dwarfed by the value of the people's time that is =
being spent here.</div><div><br></div><div>We are spending this time to =
travel to meet face-to-face, not so that we can see PowerPoint all day =
for a week, but so we can interact. &nbsp; Presentations, for the most =
part, do not help. &nbsp; They get in the =
way.</div><div><br></div><div>Visual aids can help to facilitate a =
discussion, but they should be as brief as possible, and the room setup, =
meeting schedule, etc. should not be optimized for the visual aids. =
&nbsp; They should be optimized for =
discussion.</div><div><br></div><div>For 80% of most WG meetings, the =
lights should be bright, the participants should face each other. &nbsp; =
If there's a person facilitating the discussion that person should be =
the center of attention. &nbsp; &nbsp;If we're going to use microphones, =
the rooms should be set up to allow everyone in the room to have easy =
access to them. &nbsp; We should have several microphones, again facing =
each other, so that several people can have a conversation without =
everyone having to queue up.</div><div><br></div><div>And maybe, in =
addition, we need to provide better places for people to hang out and =
work while trying to get an opportunity to interact with specific =
people. &nbsp; The terminal rooms are generally placed in out-of-the-way =
corners, but the most effective places to interact with people are in =
the =
hallways.</div><div><br></div><div><br></div><div>Keith</div><div><br></di=
v></body></html>=

--Apple-Mail-3--391989669--

From Josh.Howlett@ja.net  Tue Jul 30 08:55:20 2013
Return-Path: <Josh.Howlett@ja.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50D7E11E8224 for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 08:55:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hyorYeqe1BoN for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 08:55:12 -0700 (PDT)
Received: from har003676.ukerna.ac.uk (har003676.ukerna.ac.uk [194.82.140.75]) by ietfa.amsl.com (Postfix) with ESMTP id 924FF11E81D7 for <ietf@ietf.org>; Tue, 30 Jul 2013 08:55:12 -0700 (PDT)
Received: from har003676.ukerna.ac.uk (localhost.localdomain [127.0.0.1]) by localhost (Email Security Appliance) with SMTP id 0CCAD4A6B7A_1F7E1DCB; Tue, 30 Jul 2013 15:55:08 +0000 (GMT)
Received: from EXC001.atlas.ukerna.ac.uk (exc001.atlas.ukerna.ac.uk [193.62.83.37]) by har003676.ukerna.ac.uk (Sophos Email Appliance) with ESMTP id 531E74A6B72_1F7E1DBF; Tue, 30 Jul 2013 15:55:07 +0000 (GMT)
Received: from EXC001.atlas.ukerna.ac.uk ([193.62.83.37]) by EXC001 ([193.62.83.37]) with mapi id 14.02.0247.003; Tue, 30 Jul 2013 16:55:07 +0100
From: Josh Howlett <Josh.Howlett@ja.net>
To: Keith Moore <moore@network-heretics.com>, Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: Bringing back Internet transparency
Thread-Topic: Bringing back Internet transparency
Thread-Index: AQHOjSfs8we4Qzt+40qdutNskxC8Npl9Rw4AgAAprgA=
Date: Tue, 30 Jul 2013 15:55:06 +0000
Message-ID: <CE1DA8D5.2337E%Josh.Howlett@ja.net>
In-Reply-To: <C6586196-4034-4A3D-8B4C-24B2D2ED6E92@network-heretics.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.6.130613
x-originating-ip: [194.82.140.76]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <620D0A5989A08F4293A1BC83196EBBB9@ukerna.ac.uk>
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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2013 15:55:20 -0000

>
>Though of course an underlying problem is that no vendor wants to sell
>hardware that will obsolete itself, unless of course it obsoletes itself
>by requiring the customer to purchase even more expensive hardware than
>it replaces.    It's hard to see how IETF could fight against vendors who
>were making good money by making the network more complex, less reliable,
>and less flexible.

Personally I would characterise this as a demand-side problem, not
supply-side: most users plainly aren't willing to pay for Internet
transparency. You can't blame vendors or providers for not making stuff or
operating services that people won't pay for. The issue IMO is the lack or
poor alignment of economic incentives for choosing implementation and
deployment options that promote transparency.

Josh.


Janet(UK) is a trading name of Jisc Collections and Janet Limited, a=20
not-for-profit company which is registered in England under No. 2881024=20
and whose Registered Office is at Lumen House, Library Avenue,
Harwell Oxford, Didcot, Oxfordshire. OX11 0SG. VAT No. 614944238


From moore@network-heretics.com  Tue Jul 30 08:59:51 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 507F721F9A0C for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 08:59:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.399
X-Spam-Level: 
X-Spam-Status: No, score=-3.399 tagged_above=-999 required=5 tests=[AWL=0.200,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BSeHi3brCUOS for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 08:59:39 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id 6E5F521F97E6 for <ietf@ietf.org>; Tue, 30 Jul 2013 08:59:18 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id D9E8C209B8; Tue, 30 Jul 2013 11:59:13 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute5.internal (MEProxy); Tue, 30 Jul 2013 11:59:13 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id :references:to; s=smtpout; bh=KrEE+aQDUZ9IYUlUBmkRkvMNao0=; b=rV kE2anTjjqHzRDr2CjVEng+MlVUHbL1EoXlhfjnWrmDPc+USeLfYV/ZED4ZnuB63X nyrElU2gTvJ/dmVJnB8rTDOBO8uMeaD6eRC/EdK7P7qI0UhNjVfIIORCzwNmX5im iTHWPpVPoofaeTyBBKSHpsJZbDHs+5T4uu/1O9bVI=
X-Sasl-enc: 8+ERHK5575QPsqRySeTygYqQOsm4AWlRIAucoxv8mgAs 1375199953
Received: from surfer-172-29-8-65-hotspot.internet-for-guests.com (unknown [87.193.195.90]) by mail.messagingengine.com (Postfix) with ESMTPA id 305D16800E8; Tue, 30 Jul 2013 11:59:13 -0400 (EDT)
Subject: Re: Bringing back Internet transparency
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <CE1DA8D5.2337E%Josh.Howlett@ja.net>
Date: Tue, 30 Jul 2013 17:59:11 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <F2A870F2-9FC4-429A-B30E-118E3441DA10@network-heretics.com>
References: <CE1DA8D5.2337E%Josh.Howlett@ja.net>
To: Josh Howlett <Josh.Howlett@ja.net>
X-Mailer: Apple Mail (2.1085)
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2013 15:59:51 -0000

On Jul 30, 2013, at 5:55 PM, Josh Howlett wrote:

>>=20
>> Though of course an underlying problem is that no vendor wants to =
sell
>> hardware that will obsolete itself, unless of course it obsoletes =
itself
>> by requiring the customer to purchase even more expensive hardware =
than
>> it replaces.    It's hard to see how IETF could fight against vendors =
who
>> were making good money by making the network more complex, less =
reliable,
>> and less flexible.
>=20
> Personally I would characterise this as a demand-side problem, not
> supply-side: most users plainly aren't willing to pay for Internet
> transparency.

I don't think that's the problem; I think the problem is that most users =
don't realize how much lack of transparency is harming them.   So =
"transparent Internet access" isn't a commodity.    Transparency would =
be cheaper if there were more demand for it, and there would be more =
demand for it if people realized how much more utility they'd get out of =
the Internet if they had it.

Keith


From mcr@sandelman.ca  Tue Jul 30 09:12:27 2013
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 592CC21F997E for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 09:12:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.022
X-Spam-Level: 
X-Spam-Status: No, score=-2.022 tagged_above=-999 required=5 tests=[AWL=-0.023, BAYES_00=-2.599, J_CHICKENPOX_12=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eWqjnxgVU28F for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 09:12:26 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id 4BFFB21F96DA for <ietf@ietf.org>; Tue, 30 Jul 2013 09:12:25 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 052D320250 for <ietf@ietf.org>; Tue, 30 Jul 2013 13:18:19 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 36C2F63A7C; Tue, 30 Jul 2013 12:10:53 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 25D75636AD for <ietf@ietf.org>; Tue, 30 Jul 2013 12:10:53 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "ietf\@ietf.org list" <ietf@ietf.org>
Subject: Re: making our meetings more worth the time/expense (was: Re: setting a goal for an inclusive IETF)
In-Reply-To: <BF2DD745-99D0-420E-B199-7C8F94981BDA@network-heretics.com>
References: <EDC539D2-48CE-44D7-A06C-19EEAE42D31C@piuha.net> <BF2DD745-99D0-420E-B199-7C8F94981BDA@network-heretics.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Tue, 30 Jul 2013 12:10:53 -0400
Message-ID: <20840.1375200653@sandelman.ca>
Sender: mcr@sandelman.ca
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2013 16:12:27 -0000

--=-=-=


Keith Moore <moore@network-heretics.com> wrote:
    > But earlier today I realized that the problem isn't just the cost of attending
    > meetings - it's the value that we get in return for those meetings.   I've been
    > taking notes about how ineffectively we use our meeting time.   Most of what
    > I've observed won't surprise anybody, but here's a summary:

Thanks for this.

    > Rooms are set up not to facilitate discussion, but to discourage it.   The
    > lights are dim, the chairs are facing forward rather than other participants,
    > the projector screen (not the person facilitating a discussion, even if someone
    > is trying to facilitate a discussion) is the center of attention.    The chairs
    > are set so close together and with so few aisles that it's hard for most of the
    > attendees to get to the mics.   The "microphone discipline" which was intended
    > to facilitate remote participation ends up making discussion more difficult for
    > everybody who has paid to be on site.

I think that these physical things are something that we can do some
experiments about.

    > Well, please excuse my candor, but f*ck habit.   We can't be effective
    > engineers if we let bad habits continue to dictate how we work.

I agree.

    > For 80% of most WG meetings, the lights should be bright, the participants
    > should face each other.   If there's a person facilitating the discussion that
    > person should be the center of attention.    If we're going to use microphones,
    > the rooms should be set up to allow everyone in the room to have easy access to
    > them.   We should have several microphones, again facing each other, so that
    > several people can have a conversation without everyone having to queue up.

Can we please try this in Vancouver?
This would work especially well for BOFs.
Maybe we can start there.
Chairs will need training as *facilitators*

    > And maybe, in addition, we need to provide better places for people to hang out
    > and work while trying to get an opportunity to interact with specific people.
    > The terminal rooms are generally placed in out-of-the-way corners, but the most
    > effective places to interact with people are in the hallways.

I agree.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [




--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works



--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUBUfflioqHRg3pndX9AQJ1ngQAveDKN9iLIU/PX5pzqFjlEwlMXcPvSGZA
T3YrQilPYyPRTWBE8eqdXB3MYT9AOJCDpU0cnEF7YkivOIcvNhILpys0PeBQ7SDX
3T3Usyst3S1VgTmm9IfZcJ+LOnDnytQe4WDQRPHX9R/i+77PgDEMRVV8+bn/+3RY
pRNwlrNa+84=
=f/QS
-----END PGP SIGNATURE-----
--=-=-=--

From Josh.Howlett@ja.net  Tue Jul 30 09:16:00 2013
Return-Path: <Josh.Howlett@ja.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E740421F9E6A for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 09:16:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h5BGE7vXLnji for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 09:15:54 -0700 (PDT)
Received: from egw002.ukerna.ac.uk (egw002.ukerna.ac.uk [194.81.3.65]) by ietfa.amsl.com (Postfix) with ESMTP id 96D7D21F9E5E for <ietf@ietf.org>; Tue, 30 Jul 2013 09:15:54 -0700 (PDT)
Received: from egw002.ukerna.ac.uk (localhost.localdomain [127.0.0.1]) by localhost (Email Security Appliance) with SMTP id CA95B20C96EA_1F7E6B5B; Tue, 30 Jul 2013 16:15:49 +0000 (GMT)
Received: from EXC001.atlas.ukerna.ac.uk (exc001.atlas.ukerna.ac.uk [193.62.83.37]) by egw002.ukerna.ac.uk (Sophos Email Appliance) with ESMTP id 99B8E20C713B_1F7E6B5F; Tue, 30 Jul 2013 16:15:49 +0000 (GMT)
Received: from EXC001.atlas.ukerna.ac.uk ([193.62.83.37]) by EXC001 ([193.62.83.37]) with mapi id 14.02.0247.003; Tue, 30 Jul 2013 17:15:49 +0100
From: Josh Howlett <Josh.Howlett@ja.net>
To: Keith Moore <moore@network-heretics.com>
Subject: Re: Bringing back Internet transparency
Thread-Topic: Bringing back Internet transparency
Thread-Index: AQHOjSfs8we4Qzt+40qdutNskxC8Npl9Rw4AgAAprgD//9+mgIAAJiOA
Date: Tue, 30 Jul 2013 16:15:48 +0000
Message-ID: <CE1DB04F.233BB%Josh.Howlett@ja.net>
In-Reply-To: <F2A870F2-9FC4-429A-B30E-118E3441DA10@network-heretics.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.6.130613
x-originating-ip: [194.82.140.76]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <434A1CAF4247B049A20121293447C12F@ukerna.ac.uk>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2013 16:16:01 -0000

>>=20
>> Personally I would characterise this as a demand-side problem, not
>> supply-side: most users plainly aren't willing to pay for Internet
>> transparency.
>
>I don't think that's the problem; I think the problem is that most users
>don't realize how much lack of transparency is harming them.

Sure, but that's really just the 'opportunity cost' side of the same coin.
Converting that opportunity cost into a tangible value proposition for the
user is probably the most important part of a solution.

Josh.


Janet(UK) is a trading name of Jisc Collections and Janet Limited, a=20
not-for-profit company which is registered in England under No. 2881024=20
and whose Registered Office is at Lumen House, Library Avenue,
Harwell Oxford, Didcot, Oxfordshire. OX11 0SG. VAT No. 614944238


From ynir@checkpoint.com  Tue Jul 30 09:34:26 2013
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A810421F99F1 for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 09:34:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.215
X-Spam-Level: 
X-Spam-Status: No, score=-10.215 tagged_above=-999 required=5 tests=[AWL=-0.216, BAYES_00=-2.599, J_CHICKENPOX_12=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZVwgykBH4ix2 for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 09:34:12 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id AEA1311E820D for <ietf@ietf.org>; Tue, 30 Jul 2013 09:33:03 -0700 (PDT)
Received: from IL-EX10.ad.checkpoint.com ([194.29.34.147]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r6UGWj7a021244; Tue, 30 Jul 2013 19:32:45 +0300
X-CheckPoint: {51F7EAAD-28-1B221DC2-1FFFF}
Received: from DAG-EX10.ad.checkpoint.com ([169.254.3.90]) by IL-EX10.ad.checkpoint.com ([169.254.2.105]) with mapi id 14.02.0342.003; Tue, 30 Jul 2013 19:32:45 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Subject: Re: making our meetings more worth the time/expense (was: Re: setting	a goal for an inclusive IETF)
Thread-Topic: making our meetings more worth the time/expense (was: Re: setting	a goal for an inclusive IETF)
Thread-Index: AQHOjT+gKK906tE5SUqv966YnkvjVZl9OAsA
Date: Tue, 30 Jul 2013 16:32:44 +0000
Message-ID: <71541C93-8914-405D-919B-7BF089B4B4E8@checkpoint.com>
References: <EDC539D2-48CE-44D7-A06C-19EEAE42D31C@piuha.net> <BF2DD745-99D0-420E-B199-7C8F94981BDA@network-heretics.com> <20840.1375200653@sandelman.ca>
In-Reply-To: <20840.1375200653@sandelman.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.20.53]
x-kse-antivirus-interceptor-info: protection disabled
x-cpdlp: 113bb5e542e80eae0e79b6b2602a52de9918b9f3b3
Content-Type: text/plain; charset="us-ascii"
Content-ID: <A8867DC44062804DAFFAF75F6EE3C35F@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2013 16:34:30 -0000

On Jul 30, 2013, at 6:10 PM, Michael Richardson <mcr+ietf@sandelman.ca>
 wrote:

>=20
> Keith Moore <moore@network-heretics.com> wrote:
>=20
>> Rooms are set up not to facilitate discussion, but to discourage it.   T=
he
>> lights are dim, the chairs are facing forward rather than other particip=
ants,
>> the projector screen (not the person facilitating a discussion, even if =
someone
>> is trying to facilitate a discussion) is the center of attention.    The=
 chairs
>> are set so close together and with so few aisles that it's hard for most=
 of the
>> attendees to get to the mics.   The "microphone discipline" which was in=
tended
>> to facilitate remote participation ends up making discussion more diffic=
ult for
>> everybody who has paid to be on site.
>=20
> I think that these physical things are something that we can do some
> experiments about.
>=20
>> Well, please excuse my candor, but f*ck habit.   We can't be effective
>> engineers if we let bad habits continue to dictate how we work.
>=20
> I agree.
>=20
>> For 80% of most WG meetings, the lights should be bright, the participan=
ts
>> should face each other.   If there's a person facilitating the discussio=
n that
>> person should be the center of attention.    If we're going to use micro=
phones,
>> the rooms should be set up to allow everyone in the room to have easy ac=
cess to
>> them.   We should have several microphones, again facing each other, so =
that
>> several people can have a conversation without everyone having to queue =
up.
>=20
> Can we please try this in Vancouver?
> This would work especially well for BOFs.
> Maybe we can start there.
> Chairs will need training as *facilitators*

The IETF is not tasked with inventing "discussion" or even "collaborative d=
esign". This things already exist, and we can maybe look around and see wha=
t works in other places. Many of us work for vendors or other groups where =
designs are created in collaboration. At least where I work now, we don't d=
o design by facing forward while someone presents. The usual way is 2-4 peo=
ple standing next to a whiteboard drawing stuff. Photographing the whiteboa=
rd with a smartphone has become a new addition, and using a flip-chart is a=
 fine variation. There are the larger design meetings (usually attended by =
a manager, some QA people, a technical documenter, and other "stakeholders"=
). Those tend to have some slides, but the whiteboard is still there and pe=
ople generally sit around a table.=20

Even those larger meetings rarely go over 10-12 people. This experience doe=
sn't transfer well to working groups with 50-100 participants, some of whic=
h are remote. So what is one to do?

Well, one option is to move most of the discussion out of these "main event=
s". Sure, you can still have small design sessions at an IETF meeting, but =
I think the bulk of the documents that we work on have less than 12 people =
actively working on them (yes, http/2.0 is an outlier here). These people c=
an meet often virtually, and there are several tools that allow these virtu=
al interim meetings that even allow you to shared a whiteboard.=20

The results of such meetings can and should be reported to the WG mailing l=
ist for feed-back, and then we can have real presentations at the face-to-f=
ace meetings, where we solicit comments by those who are not part of the co=
re group, and are not following closely. I just don't believe in effective =
discussion among a group of 50-100 people. The best we can hope for is a Q&=
A session with the design team. If you want another example of an ineffecti=
ve discussion in a group of 100+ people, just take a look at your local par=
liament / congress. There's a reason why all of them have formed committees=
, and why the executive branch has usurped much of their power in many coun=
tries. Trying to force such a body to effective discussion will not work.

Yoav


From dave@cridland.net  Tue Jul 30 09:34:33 2013
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0256A21F99B0 for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 09:34:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.678
X-Spam-Level: 
X-Spam-Status: No, score=-0.678 tagged_above=-999 required=5 tests=[AWL=1.299,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CQj9VNnPZf5N for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 09:34:30 -0700 (PDT)
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 EA2C411E822C for <ietf@ietf.org>; Tue, 30 Jul 2013 09:33:18 -0700 (PDT)
Received: by mail-ob0-f177.google.com with SMTP id f8so7091142obp.36 for <ietf@ietf.org>; Tue, 30 Jul 2013 09:33:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=leSeQuJ/M22kcVo5RnYBCSEYHOc97KaSR0K5RuBLMb8=; b=Oqvz243LxDhEn+v0uq28nLqZiv0i/2/sPxO35gQk5qRurwvjv3xD9bl0XCrfop6kk4 awnp1tobFurcWZYomCKI+TNF7D3dGUc9LUp0xCQ8EE5UO50kaPnYlymt3sbP2K5qXERH S2nH+e6dbktO/BIce/mPddV5r6nnpQUMdUpFE=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=leSeQuJ/M22kcVo5RnYBCSEYHOc97KaSR0K5RuBLMb8=; b=By6dPCLYYwTv4zv9xB/Skfl7cUMXXXJuXr8r75C1+n0vON8RmNHdecPTTjDUsk8Lfk JFDYxjCYKc0MDKj5OjD4zYqNQe3MYgxySqhsinQGj65pgwc3wBjKeam1vCBrJqKU1yNB +cKGOa0cLWKRVFChpURB56Qcw8CupfNsX+4n934N/SdS0+V/GAMWTAfSKPejYPLlcBoa tNBBVbL45FxyFFZM8sKqgLu13Ynwox6ymsQkN8QqC9giYdySWnFc+pt37cX1p46hf9QG BkneedNNduDeUyYLPxYoxaFITFRqcZwPx92Y2odvUVzbdVHjlEKvzAIjHbRsc1lJ/A5+ PN2A==
MIME-Version: 1.0
X-Received: by 10.182.52.202 with SMTP id v10mr57285219obo.73.1375201996318; Tue, 30 Jul 2013 09:33:16 -0700 (PDT)
Received: by 10.60.178.234 with HTTP; Tue, 30 Jul 2013 09:33:16 -0700 (PDT)
In-Reply-To: <C6586196-4034-4A3D-8B4C-24B2D2ED6E92@network-heretics.com>
References: <20130730132305.5AA8518C111@mercury.lcs.mit.edu> <C6586196-4034-4A3D-8B4C-24B2D2ED6E92@network-heretics.com>
Date: Tue, 30 Jul 2013 17:33:16 +0100
Message-ID: <CAKHUCzxOi5qL17t=HwRLLUy7zRULcO0SMWt3DWcvmQSDUDZNkQ@mail.gmail.com>
Subject: Re: Bringing back Internet transparency
From: Dave Cridland <dave@cridland.net>
To: Keith Moore <moore@network-heretics.com>
Content-Type: multipart/alternative; boundary=089e013c68dc7c396704e2bd2ab4
X-Gm-Message-State: ALoCoQmYCJCmCZTKWmPUnI9+saz8UY3YSJIrSd6/oNps5750UJF7lq6J1zjq4o5RiH76AVhmjPnM
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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2013 16:34:34 -0000

--089e013c68dc7c396704e2bd2ab4
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On Tue, Jul 30, 2013 at 4:25 PM, Keith Moore <moore@network-heretics.com>wr=
ote:

>
> On Jul 30, 2013, at 3:23 PM, Noel Chiappa wrote:
> > The IETF doesn't have a police force, or any enforcement mechanism.
>
> That's true, but people do sometimes cite IETF specifications as
> requirements for equipment procurement.   And in many cases it is possibl=
e
> to test equipment for conformance to specifications.
>
>

{{citation-needed}} - I've only ever seen specification conformance in
procurement documents for military systems, never for anything else.

And moreover, I suspect that this doesn't matter; the kinds of people
who're procuring, as such - rather than either buying or just living with
what someone else bought - are a tiny minority. Real people, who drive most
of the internet's use, wouldn't know or care if their new router supported
RFC 6592.

Maybe this could be addressed by having a Marketing Label=99 to attach to
internet access, in the same way that WiFi=99 has helped 802.11a/b/g/n do s=
o
well. I'm pretty sure than if (for example) Skype stamped on its box that
you were recommended to have Halfway Decent=99 bandwidth, that an ISP could
start to market their Halfway Decent=99 offering, and would be procuring
Halfway Decent=99 equipment. And for what it's worth, I'd happily pay -
indeed, do happily pay - a premium to have Halfway Decent=99 internet acces=
s.
But I'm not sure this is an IETF activity - perhaps an ISOC one though.

Dave.

--089e013c68dc7c396704e2bd2ab4
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Tue, Jul 30, 2013 at 4:25 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"><div class=3D"im"><br>
On Jul 30, 2013, at 3:23 PM, Noel Chiappa wrote:<br>&gt; The IETF doesn&#39=
;t have a police force, or any enforcement mechanism.<br>
<br>
</div>That&#39;s true, but people do sometimes cite IETF specifications as =
requirements for equipment procurement. =A0 And in many cases it is possibl=
e to test equipment for conformance to specifications.<br>
<div class=3D"im"><br></div></blockquote><div><br></div><div><br></div><div=
>{{citation-needed}} - I&#39;ve only ever seen specification conformance in=
 procurement documents for military systems, never for anything else.</div>
<div><br></div><div>And moreover, I suspect that this doesn&#39;t matter; t=
he kinds of people who&#39;re procuring, as such - rather than either buyin=
g or just living with what someone else bought - are a tiny minority. Real =
people, who drive most of the internet&#39;s use, wouldn&#39;t know or care=
 if their new router supported RFC 6592.</div>
<div><br></div><div>Maybe this could be addressed by having a Marketing Lab=
el=99 to attach to internet access, in the same way that WiFi=99 has helped=
 802.11a/b/g/n do so well. I&#39;m pretty sure than if (for example) Skype =
stamped on its box that you were recommended to have Halfway Decent=99 band=
width, that an ISP could start to market their Halfway Decent=99 offering, =
and would be procuring Halfway Decent=99 equipment. And for what it&#39;s w=
orth, I&#39;d happily pay - indeed, do happily pay - a premium to have Half=
way Decent=99 internet access. But I&#39;m not sure this is an IETF activit=
y - perhaps an ISOC one though.</div>
<div><br></div><div>Dave.</div></div></div></div>

--089e013c68dc7c396704e2bd2ab4--

From jnc@mercury.lcs.mit.edu  Tue Jul 30 09:37:27 2013
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 266AA11E8245 for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 09:37:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.446
X-Spam-Level: 
X-Spam-Status: No, score=-6.446 tagged_above=-999 required=5 tests=[AWL=0.153,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TD-JTFm4leus for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 09:37:11 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id C175411E80EE for <ietf@ietf.org>; Tue, 30 Jul 2013 09:35:04 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 455E918C10F; Tue, 30 Jul 2013 12:35:02 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: making our meetings more worth the time/expense (was: Re: setting a goal for an inclusive IETF)
Message-Id: <20130730163502.455E918C10F@mercury.lcs.mit.edu>
Date: Tue, 30 Jul 2013 12:35:02 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2013 16:37:33 -0000

    > From: Keith Moore <moore@network-heretics.com>

Great message. One idea:

    > WG meeting sessions aren't scheduled to encourage discussion, but to
    > discourage it. At meeting after meeting, in several different areas, I
    > see the lion's share of the time devoted to presentations rather than
    > discussion.

Easy fix: 'slide' (well, nobody uses real slides anymore :-) rationing.

E.g. if a presenter has a 10 minute slot, maximum of 3 'slides'
(approximately; maybe less). That will force the slides to be 'discussion
frameworks', rather than 'detailed overview of the design'.

	Noel

From Ted.Lemon@nominum.com  Tue Jul 30 09:59:24 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 290AF11E80FE for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 09:59:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.232
X-Spam-Level: 
X-Spam-Status: No, score=-106.232 tagged_above=-999 required=5 tests=[AWL=-0.233, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5tenuHrSGf19 for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 09:59:17 -0700 (PDT)
Received: from exprod7og115.obsmtp.com (exprod7og115.obsmtp.com [64.18.2.217]) by ietfa.amsl.com (Postfix) with ESMTP id A24F321F9D34 for <ietf@ietf.org>; Tue, 30 Jul 2013 09:59:16 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob115.postini.com ([64.18.6.12]) with SMTP ID DSNKUffw45qXjSQjXX5P446l0QZe/0HZrf7r@postini.com; Tue, 30 Jul 2013 09:59:16 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id DFD4D1B81DA for <ietf@ietf.org>; Tue, 30 Jul 2013 09:59:14 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id D99A2190065; Tue, 30 Jul 2013 09:59:14 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Tue, 30 Jul 2013 09:59:14 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Dave Cridland <dave@cridland.net>
Subject: Re: Bringing back Internet transparency
Thread-Topic: Bringing back Internet transparency
Thread-Index: AQHOjSfs0UYaDQsK+0mby2jysvHoWZl9zSsAgAAS2QCAAAdAgA==
Date: Tue, 30 Jul 2013 16:59:14 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775238DA5@mbx-01.win.nominum.com>
References: <20130730132305.5AA8518C111@mercury.lcs.mit.edu> <C6586196-4034-4A3D-8B4C-24B2D2ED6E92@network-heretics.com> <CAKHUCzxOi5qL17t=HwRLLUy7zRULcO0SMWt3DWcvmQSDUDZNkQ@mail.gmail.com>
In-Reply-To: <CAKHUCzxOi5qL17t=HwRLLUy7zRULcO0SMWt3DWcvmQSDUDZNkQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <43E68885EBEABE4CA6F2B66EF5F9B12F@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>, Keith Moore <moore@network-heretics.com>, Noel Chiappa <jnc@mercury.lcs.mit.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2013 16:59:24 -0000

On Jul 30, 2013, at 6:33 PM, Dave Cridland <dave@cridland.net> wrote:
> {{citation-needed}} - I've only ever seen specification conformance in pr=
ocurement documents for military systems, never for anything else.

It's quite common to see a list of supported RFCs in the spec sheet for a p=
iece of network hardware.   University of New Hampshire testing lab does a =
lot of testing, including home gateway testing, TRILL testing, and so on.

> And moreover, I suspect that this doesn't matter; the kinds of people who=
're procuring, as such - rather than either buying or just living with what=
 someone else bought - are a tiny minority. Real people, who drive most of =
the internet's use, wouldn't know or care if their new router supported RFC=
 6592.

No, they don't, but they care that Comcast says it works, because they know=
 what happens if they use a router that Comcast doesn't say works.

> Maybe this could be addressed by having a Marketing Label=99 to attach to=
 internet access, in the same way that WiFi=99 has helped 802.11a/b/g/n do =
so well. I'm pretty sure than if (for example) Skype stamped on its box tha=
t you were recommended to have Halfway Decent=99 bandwidth, that an ISP cou=
ld start to market their Halfway Decent=99 offering, and would be procuring=
 Halfway Decent=99 equipment. And for what it's worth, I'd happily pay - in=
deed, do happily pay - a premium to have Halfway Decent=99 internet access.=
 But I'm not sure this is an IETF activity - perhaps an ISOC one though.

Yes, labeling is another very good solution=97see the V6Ready label that wa=
s used for the World IPv6 launch.


From melinda.shore@gmail.com  Tue Jul 30 10:21:16 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1286211E80ED for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 10:21:14 -0700 (PDT)
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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c76T3-8BFeYb for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 10:21:11 -0700 (PDT)
Received: from mail-pa0-x234.google.com (mail-pa0-x234.google.com [IPv6:2607:f8b0:400e:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id AD15611E80D5 for <ietf@ietf.org>; Tue, 30 Jul 2013 10:21:10 -0700 (PDT)
Received: by mail-pa0-f52.google.com with SMTP id kq13so7377898pab.11 for <ietf@ietf.org>; Tue, 30 Jul 2013 10:21:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=yezBOc9HEayCB/hFR9hAoYF0KrT9Jvo7BHAmRGSD78M=; b=o2SPnPCBiL0cT3l5cK4rODcvj5T5O9VYZXRyzWzKWQx86kuaG6+CqOocqf77afyH7y KaeZuBk+4hGOk4sNIVQOEkuJlrTNaCn8TROxGTpVUcPBRvg+YVfLnDTEyoBOquSyKyN2 P90Qbds5M/Epi8HNwZVI9/zAL9y1fd/aqqrdtaigb0JXW7h0B+j9qFIuNQYviNqxe19r 60GwRCkGe4+mf43AW5INbat0hdfORSdnurt+wWgX26b5eGzldebmgxxDMBBFy14kB4YQ gIdOq9X+rLZsRpR8KWehmeg61OXyoEVzYqkXf8Z5+Y/KUpdzx+eX1iNGnCWdqZD4hSxW Cg0g==
X-Received: by 10.66.227.2 with SMTP id rw2mr35355003pac.131.1375204864689; Tue, 30 Jul 2013 10:21:04 -0700 (PDT)
Received: from spandex.local (66-230-85-245-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.85.245]) by mx.google.com with ESMTPSA id kd1sm2580927pab.20.2013.07.30.10.21.03 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 30 Jul 2013 10:21:03 -0700 (PDT)
Message-ID: <51F7F5FD.8040508@gmail.com>
Date: Tue, 30 Jul 2013 09:21:01 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Bringing back Internet transparency
References: <CE1DA8D5.2337E%Josh.Howlett@ja.net> <F2A870F2-9FC4-429A-B30E-118E3441DA10@network-heretics.com>
In-Reply-To: <F2A870F2-9FC4-429A-B30E-118E3441DA10@network-heretics.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2013 17:21:16 -0000

On 7/30/13 7:59 AM, Keith Moore wrote:
> I don't think that's the problem; I think the problem is that most
> users don't realize how much lack of transparency is harming them.
> So "transparent Internet access" isn't a commodity.    Transparency
> would be cheaper if there were more demand for it, and there would be
> more demand for it if people realized how much more utility they'd
> get out of the Internet if they had it.

<n> decades in, I suspect that if there were going to be demand
for "transparency" we'd be seeing it by now.  If VoIP wasn't the
kick in the pants that's been needed to change things, it's
difficult to imagine what else might be.

Melinda

From braden@isi.edu  Tue Jul 30 10:48:12 2013
Return-Path: <braden@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93D1821E8063 for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 10:48:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n9+kwHreGBe7 for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 10:48:05 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 3031911E810B for <ietf@ietf.org>; Tue, 30 Jul 2013 10:48:05 -0700 (PDT)
Received: from [128.9.168.81] (rtb.isi.edu [128.9.168.81]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r6UHlLcQ024160 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 30 Jul 2013 10:47:21 -0700 (PDT)
Message-ID: <51F7FC29.2000407@isi.edu>
Date: Tue, 30 Jul 2013 10:47:21 -0700
From: Bob Braden <braden@isi.edu>
Organization: USC/ISI
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: making our meetings more worth the time/expense (was: Re: setting a goal for an inclusive IETF)
References: <20130730163502.455E918C10F@mercury.lcs.mit.edu>
In-Reply-To: <20130730163502.455E918C10F@mercury.lcs.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: braden@isi.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: braden@isi.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, 30 Jul 2013 17:48:12 -0000

On 7/30/2013 9:35 AM, Noel Chiappa wrote:
>
> Easy fix: 'slide' (well, nobody uses real slides anymore :-) rationing.
>
> E.g. if a presenter has a 10 minute slot, maximum of 3 'slides'
> (approximately; maybe less). That will force the slides to be 'discussion
> frameworks', rather than 'detailed overview of the design'.
>
> 	Noel

Noel,

I tried the 3 slide limit in the End2end Research Group some years ago, 
and it did not work very well.
Presenters just can't discipline themselves that much, no matter how 
hard you beat on them.

Bob Braden


From john-ietf@jck.com  Tue Jul 30 11:28:08 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C4D711E81DF; Tue, 30 Jul 2013 11:28:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6DyODqF5vy-Q; Tue, 30 Jul 2013 11:28:02 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 8F2D711E822A; Tue, 30 Jul 2013 11:28:02 -0700 (PDT)
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 1V4EeP-000J4o-Ng; Tue, 30 Jul 2013 14:28:01 -0400
Date: Tue, 30 Jul 2013 14:27:56 -0400
From: John C Klensin <john-ietf@jck.com>
To: IETF Chair <chair@ietf.org>, "ietf@ietf.org list" <ietf@ietf.org>
Subject: Re: PS to IS question from plenary
Message-ID: <D2354ED434665515542E74E4@JcK-HP8200.jck.com>
In-Reply-To: <F3241893-F062-4F09-BA09-398BE207192F@ietf.org>
References: <F3241893-F062-4F09-BA09-398BE207192F@ietf.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: sob@harvard.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2013 18:28:08 -0000

--On Tuesday, July 30, 2013 16:41 +0200 IETF Chair
<chair@ietf.org> wrote:

> Last night there was a question in the plenary about how many
> PS->IS transitions have occurred since RFC 6410 was published
> in October 2011. That RFC changed the three-step standards
> process to two steps. There was also a question of how this
> compared to previous times before that RFC got approved.
> 
> Looking at the timeframe from October 2011 to today (22
> months), there have been four such protocol actions. These
> results are given by searching the IETF Announce mail archive:
>...
> Prior to the publication of RFC 6410, in the preceding 22
> months there were these 20 actions raising standards to either
> Draft Standard or Full Standard:
>...
> I should insert here the Standard disclaimer about possibly
> faulty search methodology or records, misunderstanding the
> question, or the hasty interpretation of results. In
> particular, the above search was not easy on ARO, involved
> manual steps, and I might have easily missed something. And I
> wish I had been able to do a database query instead. Feel free
> to repeat & verify my results...

Jari,

Thanks for this.

Disclaimers and possible small classification errors aside and
being careful to avoid making causal assumptions, I believe that
the implication of the above is that there is no evidence that
the 3 -> 2 transition has increased the number of documents
being moved or promoted out of Proposed Standard.   If one were
to assume a causal relationship and an absence of external
confounding variates or processes, one might even conclude the
the 3 -> 2 transition has made things quite a lot worse.
Conversely, it seems to me that one could argue that the change
has made things better only by demonstrating the existence of a
process that would have led to considerably fewer than four
documents being moved out of Proposed Standard in the last 22
months in the absence of the change.

While the apparently-significant reduction in documents moved
out of Proposed Standard is far worse than we expected, is it
time for Scott Bradner and myself to review
draft-bradner-restore-proposed-00, issue a new version, and
start a serious discussion about that model of a solution?
Would be willing to sponsor such a draft or, if you prefer,
organize a WG or equivalent to consider it?

thanks,
   john


From brian.e.carpenter@gmail.com  Tue Jul 30 13:19:12 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1654011E8159; Tue, 30 Jul 2013 13:19:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.556
X-Spam-Level: 
X-Spam-Status: No, score=-102.556 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id owjqssOf8NS6; Tue, 30 Jul 2013 13:19:11 -0700 (PDT)
Received: from mail-pb0-x22f.google.com (mail-pb0-x22f.google.com [IPv6:2607:f8b0:400e:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 7488E11E8237; Tue, 30 Jul 2013 13:19:03 -0700 (PDT)
Received: by mail-pb0-f47.google.com with SMTP id rr13so6423984pbb.6 for <multiple recipients>; Tue, 30 Jul 2013 13:19:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=YklxJGLzUCxGyD6v/EQ8WJTaR+pMvZX13pxy12b+TVs=; b=hccsjrpIpVWQtXQBl2Z9vDWd5qDtZbTyAQ1w0YZNy2E0bO+GyLGSJQTebvDtEpkn2E 2r1Mcp90fYCL6own16yIyPsGtnFiTI4vHB5s8nlnd7C9IqLhwVy1djwhHtLAy0kYgzDc vgM8VIEdqEkc4R/jbJzD1gwsvBpRM4djsFtQnT8a38BvDpgcfYSSSs01T7U4aJCyUGuK 8a4UhULbuqsGGzERJBUzUhQxR9kx/UhD2fB2XGY2rbJqrEmkQFA4ZOU7LdCscqGuq/jv tcgthV+hi/qEusxPPiKHN6PpMyoIINVJOGp9mX217KmZl+vzQ+b6FGx94tHQJ2fDbxMZ lzUA==
X-Received: by 10.68.163.165 with SMTP id yj5mr75385237pbb.141.1375215543117;  Tue, 30 Jul 2013 13:19:03 -0700 (PDT)
Received: from [192.168.178.23] (193.199.69.111.dynamic.snap.net.nz. [111.69.199.193]) by mx.google.com with ESMTPSA id ib9sm84728084pbc.43.2013.07.30.13.19.00 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 30 Jul 2013 13:19:02 -0700 (PDT)
Message-ID: <51F81FB8.5030404@gmail.com>
Date: Wed, 31 Jul 2013 08:19:04 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: PS to IS question from plenary
References: <F3241893-F062-4F09-BA09-398BE207192F@ietf.org> <D2354ED434665515542E74E4@JcK-HP8200.jck.com>
In-Reply-To: <D2354ED434665515542E74E4@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF Chair <chair@ietf.org>, "ietf@ietf.org list" <ietf@ietf.org>, sob@harvard.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2013 20:19:12 -0000

On 31/07/2013 06:27, John C Klensin wrote:
> 
> --On Tuesday, July 30, 2013 16:41 +0200 IETF Chair
> <chair@ietf.org> wrote:
> 
>> Last night there was a question in the plenary about how many
>> PS->IS transitions have occurred since RFC 6410 was published
>> in October 2011. That RFC changed the three-step standards
>> process to two steps. There was also a question of how this
>> compared to previous times before that RFC got approved.
>>
>> Looking at the timeframe from October 2011 to today (22
>> months), there have been four such protocol actions. These
>> results are given by searching the IETF Announce mail archive:
>> ...
>> Prior to the publication of RFC 6410, in the preceding 22
>> months there were these 20 actions raising standards to either
>> Draft Standard or Full Standard:
>> ...
>> I should insert here the Standard disclaimer about possibly
>> faulty search methodology or records, misunderstanding the
>> question, or the hasty interpretation of results. In
>> particular, the above search was not easy on ARO, involved
>> manual steps, and I might have easily missed something. And I
>> wish I had been able to do a database query instead. Feel free
>> to repeat & verify my results...
> 
> Jari,
> 
> Thanks for this.
> 
> Disclaimers and possible small classification errors aside and
> being careful to avoid making causal assumptions, I believe that
> the implication of the above is that there is no evidence that
> the 3 -> 2 transition has increased the number of documents
> being moved or promoted out of Proposed Standard.   If one were
> to assume a causal relationship and an absence of external
> confounding variates or processes, one might even conclude the
> the 3 -> 2 transition has made things quite a lot worse.
> Conversely, it seems to me that one could argue that the change
> has made things better only by demonstrating the existence of a
> process that would have led to considerably fewer than four
> documents being moved out of Proposed Standard in the last 22
> months in the absence of the change.
> 
> While the apparently-significant reduction in documents moved
> out of Proposed Standard is far worse than we expected, is it
> time for Scott Bradner and myself to review
> draft-bradner-restore-proposed-00, issue a new version, and
> start a serious discussion about that model of a solution?
> Would be willing to sponsor such a draft or, if you prefer,
> organize a WG or equivalent to consider it?

I would rephrase it as performing the inverse operation to RFC 4450.
I don't think it needs to be a fully-fledged experiment under RFC 3933;
just a large batch of PS->IS promotions in one go under RFC 6410.

It is a good idea.

    Brian

From brian.e.carpenter@gmail.com  Tue Jul 30 13:29:58 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EBB121F9931 for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 13:29:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.558
X-Spam-Level: 
X-Spam-Status: No, score=-102.558 tagged_above=-999 required=5 tests=[AWL=0.041, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W4XMhLfXpFVr for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 13:29:57 -0700 (PDT)
Received: from mail-pd0-x22a.google.com (mail-pd0-x22a.google.com [IPv6:2607:f8b0:400e:c02::22a]) by ietfa.amsl.com (Postfix) with ESMTP id C71C121F9930 for <ietf@ietf.org>; Tue, 30 Jul 2013 13:29:57 -0700 (PDT)
Received: by mail-pd0-f170.google.com with SMTP id x10so2624362pdj.29 for <ietf@ietf.org>; Tue, 30 Jul 2013 13:29:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Y1UndwcPOlrQ800gRJvk7Suqj1wOzcvlIsQCAuPUMXk=; b=QP/ej/KiUwSMTnd8G2rp+V32/8ke/HwzqmXHUkYzpPCnkEV8DZtZtMeFbK3GmbSr+C o4qERxon1n3Ka/KvDpva+eWJUuzpOJIZYabojjJB++OsNrTKdtgRbVS80ULl5UkiyV59 HL2ErxP5l/isorxlMZPPN8b+mMJogz/UwxwNfxsTI0CLkQNADBFb2zMxmgr2f+K09oXD Ac83DgDVqkR3bAXbER4HN6NvN5WYOfqv2n2+YRFaFCKYaCTpapSMet4PRRaI1pQSWUgR ajgIOUGeEqNPGDH0mB96QTGg8atJn0nQ5VLU6VNcwlnVkS6+Pzs0xKNMljRsRKvAcO2e LTcA==
X-Received: by 10.66.120.145 with SMTP id lc17mr12430852pab.182.1375216197559;  Tue, 30 Jul 2013 13:29:57 -0700 (PDT)
Received: from [192.168.178.23] (193.199.69.111.dynamic.snap.net.nz. [111.69.199.193]) by mx.google.com with ESMTPSA id wr9sm84875607pbc.7.2013.07.30.13.29.55 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 30 Jul 2013 13:29:56 -0700 (PDT)
Message-ID: <51F82246.9000108@gmail.com>
Date: Wed, 31 Jul 2013 08:29:58 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: Bringing back Internet transparency
References: <CE1DA8D5.2337E%Josh.Howlett@ja.net>	<F2A870F2-9FC4-429A-B30E-118E3441DA10@network-heretics.com> <51F7F5FD.8040508@gmail.com>
In-Reply-To: <51F7F5FD.8040508@gmail.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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2013 20:29:58 -0000

On 31/07/2013 05:21, Melinda Shore wrote:
> On 7/30/13 7:59 AM, Keith Moore wrote:
>> I don't think that's the problem; I think the problem is that most
>> users don't realize how much lack of transparency is harming them.
>> So "transparent Internet access" isn't a commodity.    Transparency
>> would be cheaper if there were more demand for it, and there would be
>> more demand for it if people realized how much more utility they'd
>> get out of the Internet if they had it.
> 
> <n> decades in, I suspect that if there were going to be demand
> for "transparency" we'd be seeing it by now.  If VoIP wasn't the
> kick in the pants that's been needed to change things, it's
> difficult to imagine what else might be.

Users want applications to just work, but they (and many business
managers in our "industry") don't understand that when applications
fail unpredictably, it's often because of glitches in what we call
transparency.

However, we are in an arms race here. Every step to improve transparency
will be met by a further step in middleboxes that nibbles away at
transparency. We've been debating this for 15 years; have you seen
any real change in the balance of power?

    Brian

From moore@network-heretics.com  Tue Jul 30 13:30:26 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B284021F99E3 for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 13:30:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.439
X-Spam-Level: 
X-Spam-Status: No, score=-3.439 tagged_above=-999 required=5 tests=[AWL=0.160,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cC6yjKnYUEuD for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 13:30:21 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id 8F60821F99DE for <ietf@ietf.org>; Tue, 30 Jul 2013 13:30:21 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 8F17220E9B; Tue, 30 Jul 2013 16:30:16 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Tue, 30 Jul 2013 16:30:17 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id :references:to; s=smtpout; bh=DWXPJPUrGP7qMzHQzI2PPVMCHDc=; b=Zw KW8EKAoP3HA4Um+Sey8ij2zK0P+4aGRJcbQmHkyHIo4PRkWPkI89IejFNTe1clXn 1WeEO6wS19rdGsV3R8FHqFAu9gsokQ6oVWU5HWEy1dMX5c2B1ppRGyCznq/eMslv ypl//uYeXzKpCXCz061uTttgGp518uvtZ16uJdD24=
X-Sasl-enc: zIQRHREEnEcynjWbrdMHBgnTZyVW2gQiMVWbuqJL4Ilx 1375216216
Received: from surfer-172-29-8-65-hotspot.internet-for-guests.com (unknown [87.193.195.90]) by mail.messagingengine.com (Postfix) with ESMTPA id A7469C00E81; Tue, 30 Jul 2013 16:30:15 -0400 (EDT)
Subject: Re: making our meetings more worth the time/expense (was: Re: setting a goal for an inclusive IETF)
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <51F7FC29.2000407@isi.edu>
Date: Tue, 30 Jul 2013 22:30:13 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <2CC6EA8D-7FCF-4536-97A5-E056FD4F4B6A@network-heretics.com>
References: <20130730163502.455E918C10F@mercury.lcs.mit.edu> <51F7FC29.2000407@isi.edu>
To: braden@isi.edu
X-Mailer: Apple Mail (2.1085)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2013 20:30:26 -0000

On Jul 30, 2013, at 7:47 PM, Bob Braden wrote:

> On 7/30/2013 9:35 AM, Noel Chiappa wrote:
>>=20
>> Easy fix: 'slide' (well, nobody uses real slides anymore :-) =
rationing.
>>=20
>> E.g. if a presenter has a 10 minute slot, maximum of 3 'slides'
>> (approximately; maybe less). That will force the slides to be =
'discussion
>> frameworks', rather than 'detailed overview of the design'.
>>=20
>> 	Noel
>=20
> Noel,
>=20
> I tried the 3 slide limit in the End2end Research Group some years =
ago, and it did not work very well.
> Presenters just can't discipline themselves that much, no matter how =
hard you beat on them.

Maybe the first step is to stop having "presenters".

Keith


From brian.e.carpenter@gmail.com  Tue Jul 30 13:38:26 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0B8F11E8163 for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 13:38:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.56
X-Spam-Level: 
X-Spam-Status: No, score=-102.56 tagged_above=-999 required=5 tests=[AWL=0.039, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KDxeYZtUOUfk for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 13:38:26 -0700 (PDT)
Received: from mail-pd0-x235.google.com (mail-pd0-x235.google.com [IPv6:2607:f8b0:400e:c02::235]) by ietfa.amsl.com (Postfix) with ESMTP id 4BC3A11E80F6 for <ietf@ietf.org>; Tue, 30 Jul 2013 13:38:26 -0700 (PDT)
Received: by mail-pd0-f181.google.com with SMTP id g10so3451819pdj.12 for <ietf@ietf.org>; Tue, 30 Jul 2013 13:38:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=0uLVkUS55XYg6wgmasU3pJsrfq2VDi9appLM6bvGiV4=; b=SF5ShVKNUt6LPjizdJXYPaWwHX76HVZj+lo+k75Yc3jxHLgKMN0/VeTnYx8lbY2B9b qWAHz8+08oZQXjs1XwSI+JPyYcOrAIIpkdHCp5F7+r+KnafDk/FGnkJiT3fjkuqkjnSh n1vr7xobQ5Cu5nr/oyl1cqDW/53ReT0mZ9Vz852DwNGy/y1Zv/uygnwo0y2LrRZuxfjr JPhT+29OdBcwY4Yadac6ujY3HA/Ij3Xm6rIZW5ecf26u8HPSJkgYJPRrMvc5mxnabDlB MZ63xP9cFE0qfhOA9w3Yis0ETzwXMOxivWf+FLSt23TLaRAfYg3K7Y/Z1mvfT1+bWvD3 i+zQ==
X-Received: by 10.68.162.36 with SMTP id xx4mr30789135pbb.47.1375216706031; Tue, 30 Jul 2013 13:38:26 -0700 (PDT)
Received: from [192.168.178.23] (193.199.69.111.dynamic.snap.net.nz. [111.69.199.193]) by mx.google.com with ESMTPSA id w8sm28844006pab.12.2013.07.30.13.38.23 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 30 Jul 2013 13:38:25 -0700 (PDT)
Message-ID: <51F82442.4000404@gmail.com>
Date: Wed, 31 Jul 2013 08:38:26 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: braden@isi.edu
Subject: Re: making our meetings more worth the time/expense
References: <20130730163502.455E918C10F@mercury.lcs.mit.edu> <51F7FC29.2000407@isi.edu>
In-Reply-To: <51F7FC29.2000407@isi.edu>
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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2013 20:38:26 -0000

On 31/07/2013 05:47, Bob Braden wrote:
> On 7/30/2013 9:35 AM, Noel Chiappa wrote:
>>
>> Easy fix: 'slide' (well, nobody uses real slides anymore :-) rationing.
>>
>> E.g. if a presenter has a 10 minute slot, maximum of 3 'slides'
>> (approximately; maybe less). That will force the slides to be 'discussion
>> frameworks', rather than 'detailed overview of the design'.
>>
>>     Noel
> 
> Noel,
> 
> I tried the 3 slide limit in the End2end Research Group some years ago,
> and it did not work very well.
> Presenters just can't discipline themselves that much, no matter how
> hard you beat on them.

It's been pointed out before that in a group with very diverse languages,
written words are usually better understood than speech. It's a fact of life
that you can't have a full-speed cut-and-thrust discussion in a group
of 100 people, half of whom are speaking a foreign language. Sitting in
a circle does not fix this.

Also, remote participants need full text slides; the soundtrack simply
isn't enough.

The old days are gone.

   Brian

From sm@resistor.net  Tue Jul 30 14:00:52 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15B4621F9B18 for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 14:00:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.541
X-Spam-Level: 
X-Spam-Status: No, score=-102.541 tagged_above=-999 required=5 tests=[AWL=0.058, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MHM5UkOTVaV3 for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 14:00:51 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BE0A21F9B14 for <ietf@ietf.org>; Tue, 30 Jul 2013 14:00:49 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r6UL0eCl011730; Tue, 30 Jul 2013 14:00:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1375218046; bh=/GyTXzoV5inwjivkPnDGZhOqKo2c7X8jZwKbh/WL7dc=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=kR8ueQhblT88ErxRrdNgLPUdGfW6OiVBi5C18CDB/Ih/H3nnbw8r1CBcnYG8p0Ro3 EZHj9zqrxrNvmX7DHkC0bOM1R8IGo7f5vE24ytsIkdzETpVyFWWDlrB86YoXLVqe4U EdIMkOmYqFASRZCF8141DpZ04VNRB2QviSpRwO8Q=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1375218046; i=@resistor.net; bh=/GyTXzoV5inwjivkPnDGZhOqKo2c7X8jZwKbh/WL7dc=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=ZjPQ6iI2LMshIk6YrGFTJaHSvXb4RcNtgyTq+iK0gwL1ehCBFPOPdt4ZPc0mxUwIK /fCXel1D33xdpyV+Agpj+XiuNB5FY2v05rgoDnApct0zcFQVBJzlNLMRIT1o7S1OCW 1R2EYGsAvBoZRQLJkLOwC58t8zVi9BjkEwabCfzg=
Message-Id: <6.2.5.6.2.20130730115827.0d632fe8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 30 Jul 2013 14:00:00 -0700
To: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: PS to IS question from plenary
In-Reply-To: <D2354ED434665515542E74E4@JcK-HP8200.jck.com>
References: <F3241893-F062-4F09-BA09-398BE207192F@ietf.org> <D2354ED434665515542E74E4@JcK-HP8200.jck.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: sob@harvard.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2013 21:00:52 -0000

At 11:27 30-07-2013, John C Klensin wrote:
>Disclaimers and possible small classification errors aside and
>being careful to avoid making causal assumptions, I believe that
>the implication of the above is that there is no evidence that
>the 3 -> 2 transition has increased the number of documents
>being moved or promoted out of Proposed Standard.   If one were
>to assume a causal relationship and an absence of external
>confounding variates or processes, one might even conclude the
>the 3 -> 2 transition has made things quite a lot worse.
>Conversely, it seems to me that one could argue that the change
>has made things better only by demonstrating the existence of a
>process that would have led to considerably fewer than four
>documents being moved out of Proposed Standard in the last 22
>months in the absence of the change.

"Changing the Internet Standards Process from three maturity levels 
to two is intended to create an environment where lessons from 
implementation and deployment experience are used to improve 
specifications".   The change could be rated as a non-change if there 
were only four specification moved to Internet Standard since then.

The hurdle in moving a specification (not a RFC) from PS to IS is 
that the draft goes through IESG Evaluation again.  As for public 
review, it can be a hurdle too as the pervious discussions can be 
rehashed.  A PS specification which sticks to what goes over the wire 
turns these hurdles into a lesser effort.

draft-bradner-restore-proposed-00 proposes a nice fix and it might 
even help lessen time to publication.

Regards,
-sm

P.S. Olaf asked the question to the correct body. 


From melinda.shore@gmail.com  Tue Jul 30 14:02:41 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75D2321F9B8F for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 14:02:41 -0700 (PDT)
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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8i+IguOVR8r2 for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 14:02:41 -0700 (PDT)
Received: from mail-pd0-x22a.google.com (mail-pd0-x22a.google.com [IPv6:2607:f8b0:400e:c02::22a]) by ietfa.amsl.com (Postfix) with ESMTP id F13C821F9B8C for <ietf@ietf.org>; Tue, 30 Jul 2013 14:02:40 -0700 (PDT)
Received: by mail-pd0-f170.google.com with SMTP id x10so2664873pdj.1 for <ietf@ietf.org>; Tue, 30 Jul 2013 14:02:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=VJ/xVgL9OF4nLeekYVaB305KP5KpwLUdriP2k5zTThA=; b=FJug0z9yHJJNVFnJZn9S2lGg++eNWGxnz7iy0olXgIeQbCWHzk96gAgt0/I+GhSRWa dWBhclRStb5AXjAYiLLxlhJAEASAdYkHJERc8347ItXlt8OY/P6fIXqA9y6NePReJNUK colIZF/mFF3mIjHTmbt2yYSSqSCXHa4Hlt6i5OXtM5eCNY7neo/vfyXmoSeOMB4RtIIA pHlFWBAzF2/xCdohC9FvVa32C8FVZOybhDds+qwQCrEeR2vpUO2R/gFOMNnj9fAYPDAS rsGlWUJaQR97ULeuDkaESaZwygkH6fFyuY5tMbIebNrKNLAjm/DNn4XUlNg/LpjSie1Y luhQ==
X-Received: by 10.68.230.131 with SMTP id sy3mr5746747pbc.34.1375218160663; Tue, 30 Jul 2013 14:02:40 -0700 (PDT)
Received: from spandex.local (66-230-85-245-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.85.245]) by mx.google.com with ESMTPSA id pq1sm84916717pbb.26.2013.07.30.14.02.39 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 30 Jul 2013 14:02:39 -0700 (PDT)
Message-ID: <51F829ED.9040600@gmail.com>
Date: Tue, 30 Jul 2013 13:02:37 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Bringing back Internet transparency
References: <CE1DA8D5.2337E%Josh.Howlett@ja.net>	<F2A870F2-9FC4-429A-B30E-118E3441DA10@network-heretics.com> <51F7F5FD.8040508@gmail.com> <51F82246.9000108@gmail.com>
In-Reply-To: <51F82246.9000108@gmail.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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2013 21:02:41 -0000

On 7/30/13 12:29 PM, Brian E Carpenter wrote:
> Users want applications to just work, but they (and many business
> managers in our "industry") don't understand that when applications
> fail unpredictably, it's often because of glitches in what we call
> transparency.

I suspect applications are not failing unpredictably often enough,
seriously enough, or impossible-to-fix-edly enough (thank you, I'm
here all week) to provide incentive for radical change in the
network, which elimination of problematic middleboxes would
certainly represent.  There are several things going on now
that I think hold some promise for overall approaches to improving
the situation but it's just hard to work on middlebox problems
in the IETF because you can't avoid getting bogged down in rehashing
the same ideological debates over and over and over again.  Yes,
problematic middlebox behavior causes real-world problems but
cursing the darkness hasn't yet been productive and I'm reasonably
sure that it never will be, particularly in a world where vendors
are churning out those cursed boxes and network operators and data
centers are buying them.

> However, we are in an arms race here. Every step to improve transparency
> will be met by a further step in middleboxes that nibbles away at
> transparency. We've been debating this for 15 years; have you seen
> any real change in the balance of power?

I'm not sure there is a balance of power between the people selling
middleboxes and the IETF.  In fact, I'm rather certain there isn't.

Melinda


From dhc@dcrocker.net  Tue Jul 30 14:11:28 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC14211E80FB for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 14:11:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oHDCqI2iB9Ke for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 14:11:23 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id D73D711E81E3 for <ietf@ietf.org>; Tue, 30 Jul 2013 14:11:23 -0700 (PDT)
Received: from [192.168.1.203] (g231112037.adsl.alicedsl.de [92.231.112.37]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r6ULBCJ2010529 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 30 Jul 2013 14:11:20 -0700
Message-ID: <51F82BED.6000508@dcrocker.net>
Date: Tue, 30 Jul 2013 23:11:09 +0200
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: PS to IS question from plenary
References: <F3241893-F062-4F09-BA09-398BE207192F@ietf.org> <D2354ED434665515542E74E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130730115827.0d632fe8@resistor.net>
In-Reply-To: <6.2.5.6.2.20130730115827.0d632fe8@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Tue, 30 Jul 2013 14:11:23 -0700 (PDT)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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, 30 Jul 2013 21:11:28 -0000

On 7/30/2013 11:00 PM, SM wrote:
> The hurdle in moving a specification (not a RFC) from PS to IS is that
> the draft goes through IESG Evaluation again.  As for public review, it
> can be a hurdle too as the pervious discussions can be rehashed.


And, of course, if it "can" be reshashed, in the IETF it will be.

However the specification for the new two-stage model provides criteria 
for the second stage, and it does not include re-evaluating the 
technology or its details.  Instead it focuses on adoption and use.

No doubt, there will continue to be IESG and other IETF participants who 
insist on treating consideration of Full standard as an excuse to 
discuss first principles, but it's not within scope.

Over time, as more specifications are processed to Full, the community 
will learn to be a bit more efficient about it.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From roland.bless@kit.edu  Tue Jul 30 15:35:28 2013
Return-Path: <roland.bless@kit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E179C11E80E2 for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 15:35:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level: 
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IEDYGObZD-vd for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 15:35:22 -0700 (PDT)
Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de [141.3.10.81]) by ietfa.amsl.com (Postfix) with ESMTP id 5C59B11E80E1 for <ietf@ietf.org>; Tue, 30 Jul 2013 15:35:21 -0700 (PDT)
Received: from irams1.ira.uni-karlsruhe.de ([141.3.10.5]) by iramx2.ira.uni-karlsruhe.de with esmtps port 25  id 1V4IVd-0007HW-AD; Wed, 31 Jul 2013 00:35:19 +0200
Received: from i72vorta.tm.uni-karlsruhe.de ([141.3.71.26] helo=vorta.tm.kit.edu) by irams1.ira.uni-karlsruhe.de with esmtp port 25  id 1V4IVd-0004qL-3n; Wed, 31 Jul 2013 00:35:13 +0200
Received: from [IPv6:::1] (localhost [127.0.0.1]) by vorta.tm.kit.edu (Postfix) with ESMTPS id B104AA806BE; Wed, 31 Jul 2013 00:35:12 +0200 (CEST)
Message-ID: <51F83F9E.9040100@kit.edu>
Date: Wed, 31 Jul 2013 00:35:10 +0200
From: Roland Bless <roland.bless@kit.edu>
Organization: Institute of Telematics, Karlsruhe Institute of Technology (KIT)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.1) Gecko/20060111 Thunderbird/1.5 Mnenhy/0.7.3.0
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: Bringing back Internet transparency
References: <20130730132305.5AA8518C111@mercury.lcs.mit.edu>
In-Reply-To: <20130730132305.5AA8518C111@mercury.lcs.mit.edu>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-ATIS-AV: ClamAV (irams1.ira.uni-karlsruhe.de)
X-ATIS-AV: Kaspersky (iramx2.ira.uni-karlsruhe.de)
X-ATIS-AV: ClamAV (iramx2.ira.uni-karlsruhe.de)
X-ATIS-Timestamp: iramx2.ira.uni-karlsruhe.de 1375223719.807819000
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2013 22:35:29 -0000

Hi Noel,

On 30.07.2013 15:23, Noel Chiappa wrote:
> I hear you, but... this is not a simple problem.

Yes, and I wasn't expecting it to be simple...

> I think we need to start by understanding what drives the creation and
> deployment of these devices. I think the answer to that has to be that some
> people have needs that aren't being met by the IETF, and so there's an
> opportunity for private entities to create and sell 'solutions'.

Agree, that would be one possible action...

> The IETF doesn't have a police force, or any enforcement mechanism. If we're

Yep, that's true and I'm fully aware of it.

> going to head off these boxes, the only tool we have to do that is to build
> better mousetraps - i.e. design stuff that does what people want, is more
> cost-effective, and is better than these local 'point deployment' boxes.

... NAT ...

> is both ugly _and_ brittle [because it's not part of an architected _system_],
> difficult to work with because it [mostly] lacks any external control
> interface, etc.)

That is a little bit more along my direction. Maybe we can at least give
advice what to strictly avoid and how to leave a path open for
innovation, e.g., do expect that other transport protocols may exist in
the future, so do not assume that only TCP and UDP are in use, or:
be prepared to process/bypass extension headers etc.

> So, sorry, I don't have a simple solution to what I concede is a real problem.
> But it's a complicated problem -> no simple solution.

I wasn't expecting that. :-)

Regards,
 Roland


From touch@isi.edu  Tue Jul 30 15:36:21 2013
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C35D21E80ED for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 15:36:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.049
X-Spam-Level: 
X-Spam-Status: No, score=-106.049 tagged_above=-999 required=5 tests=[AWL=0.550, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y162JyZus7Mp for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 15:36:15 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 355F221E80EC for <ietf@ietf.org>; Tue, 30 Jul 2013 15:36:15 -0700 (PDT)
Received: from [128.9.184.218] ([128.9.184.218]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id r6UMZmJ8015556 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 30 Jul 2013 15:35:48 -0700 (PDT)
Message-ID: <51F83FC6.9000400@isi.edu>
Date: Tue, 30 Jul 2013 15:35:50 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Roland Bless <roland.bless@kit.edu>
Subject: Re: Bringing back Internet transparency
References: <51F7AED0.2080308@kit.edu>
In-Reply-To: <51F7AED0.2080308@kit.edu>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2013 22:36:21 -0000

On 7/30/2013 5:17 AM, Roland Bless wrote:
> Hi,
>
> my impression from several presentations seen this week at the IETF
> as well as at the ISOC Panel on "Improving Internet Experience"
> is that we probably need to do something on reducing the number
> of _broken_ middleboxes (or their implementations respectively)
> - I'm not focusing on NAT boxes here.

Hmm. I don't know what a non-broken middlebox is then ;-)

Joe

From touch@isi.edu  Tue Jul 30 15:43:05 2013
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9614E21E80E3 for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 15:43:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.091
X-Spam-Level: 
X-Spam-Status: No, score=-104.091 tagged_above=-999 required=5 tests=[AWL=-1.492, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q6SA9HNs0huL for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 15:42:58 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id B0FF821E80B4 for <ietf@ietf.org>; Tue, 30 Jul 2013 15:42:58 -0700 (PDT)
Received: from [128.9.184.218] ([128.9.184.218]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id r6UMfsOQ012095 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 30 Jul 2013 15:41:55 -0700 (PDT)
Message-ID: <51F84135.3070906@isi.edu>
Date: Tue, 30 Jul 2013 15:41:57 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: Bringing back Internet transparency
References: <20130730132305.5AA8518C111@mercury.lcs.mit.edu>
In-Reply-To: <20130730132305.5AA8518C111@mercury.lcs.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2013 22:43:05 -0000

On 7/30/2013 6:23 AM, Noel Chiappa wrote:
> The IETF doesn't have a police force, or any enforcement mechanism. If we're
> going to head off these boxes, the only tool we have to do that is to build
> better mousetraps - i.e. design stuff that does what people want, is more
> cost-effective, and is better than these local 'point deployment' boxes.

Although I appreciate the sentiment, "what people want" (ISP operators, 
or at least some of them), was an artificial way to differentiate home 
customers from commercial providers.

I.e., they wanted to create a differentiation that wasn't part of the 
Internet architecture, so they put one in.

NATs did other things (reuse addresses, block services, etc.), but IMO 
mostly as a by-product of this primary motivation.

It's very hard to do "what people want" when what they want is to defeat 
the core concept of the architecture - that all endpoints are 'equal'.

Joe


From jnc@mercury.lcs.mit.edu  Tue Jul 30 16:53:15 2013
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17CBD21E80AE for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 16:53:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.462
X-Spam-Level: 
X-Spam-Status: No, score=-6.462 tagged_above=-999 required=5 tests=[AWL=0.138,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rSEhEWPutmf9 for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 16:53:10 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id EA2EA21E80AC for <ietf@ietf.org>; Tue, 30 Jul 2013 16:53:09 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id B798918C0FA; Tue, 30 Jul 2013 19:53:06 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: Bringing back Internet transparency
Message-Id: <20130730235306.B798918C0FA@mercury.lcs.mit.edu>
Date: Tue, 30 Jul 2013 19:53:06 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2013 23:53:15 -0000

    > From: Joe Touch <touch@isi.edu>

    > "what people want" (ISP operators, or at least some of them), was an
    > artificial way to differentiate home customers from commercial
    > providers.
    > I.e., they wanted to create a differentiation that wasn't part of the
    > Internet architecture, so they put one in.
    > NATs did other things ... but IMO mostly as a by-product of this
    > primary motivation.

I'm not so sure about that.

For the first couple of years that I had an ISP connection (which soon had an
early NAT box on it), whenever I called up the ISP (then, and still, one of
the largest in the US) with a service call, the first thing I had to do was
unplug the NAT box and plug in a host directly!

It was only after everyone's house had multiple PC's (which was really only
after wireless became common - I don't think too many people were willing to
wire their houses for Ethernet :-) that they kind of expected there to be a
NAT box there.


But in any event, it's doesn't void my point: if people want something, we
have two choices: i) blow people off, and they'll adopt some point solution
that interacts poorly with everything else, or ii) give people the
_capabilities_ they need/want (and thereby have some chance at minimizing the
brain damage - since generally people don't care _how_ it works, as long as it
_does_ what they want).

I guess this is just a long-winded, engineering take on 'the customer is
always right'.

	Noel

From mcr@sandelman.ca  Tue Jul 30 18:05:21 2013
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3643411E8105; Tue, 30 Jul 2013 18:05:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.355
X-Spam-Level: 
X-Spam-Status: No, score=-2.355 tagged_above=-999 required=5 tests=[AWL=0.244,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bpATEegw1h3N; Tue, 30 Jul 2013 18:05:20 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id 5A73411E80E7; Tue, 30 Jul 2013 18:05:19 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 06E8220168; Tue, 30 Jul 2013 22:11:16 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 627A163A7C; Tue, 30 Jul 2013 21:03:48 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 1F2FE63A5E; Tue, 30 Jul 2013 21:03:47 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "ietf\@ietf.org list" <ietf@ietf.org>
Subject: Re: PS to IS question from plenary
In-Reply-To: <D2354ED434665515542E74E4@JcK-HP8200.jck.com>
References: <F3241893-F062-4F09-BA09-398BE207192F@ietf.org> <D2354ED434665515542E74E4@JcK-HP8200.jck.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Tue, 30 Jul 2013 21:03:47 -0400
Message-ID: <4776.1375232627@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: John C Klensin <john-ietf@jck.com>, IETF Chair <chair@ietf.org>, sob@harvard.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Jul 2013 01:05:21 -0000

--=-=-=


Just to make sure we have good data, can we go back a few more years?
Specifically, did we not previously have a restriction forbidding references
FS->DS, and {FS,DS}->PS?.... RFC3967 was in Dec. 2004, but I thought that we
had some other work more recently (2008?) that attempted to unjam things.

What I'm wondering is if the 20 actions prior to 6410 was an anomaly,
and really the historical rate of upgrade is really lower.

I think it is also important to understand how many new PS could have been
even ready at a given point for an upgrade.  I don't have a good/simple
metric for determining this, I think it takes some significant semi-expert
review.  Perhaps someone has an Information Science (?!) or Economics
graduate student who wants to mine the data and write a paper :-)

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works



--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUBUfhib4qHRg3pndX9AQIKrQQAmF6ecENRBocj4XCg9TvfA13WNmImgodI
Jkel+ITOmhroYBE+8iNqwqFMdlfvmsgyUXWs/rz8tgBIj1BMWLL+TGrv8VWgh0kj
qsTg1lBUNgy2Iz+3v7JZy7ttUbnT5xtz4hxIVweGDqfwIYwqoif1mjkFRXn1yWRT
cFs6z4Tl7HQ=
=e2Ye
-----END PGP SIGNATURE-----
--=-=-=--

From ajs@anvilwalrusden.com  Tue Jul 30 19:23:34 2013
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1A9211E8132 for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 19:23:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.834
X-Spam-Level: 
X-Spam-Status: No, score=-0.834 tagged_above=-999 required=5 tests=[AWL=0.006,  BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xSzPj17ukFh3 for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 19:23:28 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id C82E511E8124 for <ietf@ietf.org>; Tue, 30 Jul 2013 19:23:28 -0700 (PDT)
Received: from mx1.yitter.info (dhcp-4661.meeting.ietf.org [130.129.70.97]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 3F0888A031 for <ietf@ietf.org>; Wed, 31 Jul 2013 02:23:27 +0000 (UTC)
Date: Tue, 30 Jul 2013 22:23:28 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: making our meetings more worth the time/expense
Message-ID: <20130731022327.GA53174@mx1.yitter.info>
References: <20130730163502.455E918C10F@mercury.lcs.mit.edu> <51F7FC29.2000407@isi.edu> <51F82442.4000404@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <51F82442.4000404@gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Jul 2013 02:23:34 -0000

On Wed, Jul 31, 2013 at 08:38:26AM +1200, Brian E Carpenter wrote:
> 
> It's been pointed out before that in a group with very diverse languages,
> written words are usually better understood than speech. It's a fact of life
> that you can't have a full-speed cut-and-thrust discussion in a group
> of 100 people, half of whom are speaking a foreign language. Sitting in
> a circle does not fix this.

While that is true, I think it misses the point of the objections to
the sit-and-watch-PowerPointTV.

First, I observe that we already _have_ a great deal of written words:
the drafts.  I continue to believe that altogether too much time in WG
meetings is spent "introducing", "presenting", or otherwise showing
off ideas in an existing draft to participants in the WG.  I
acknowledge that (particularly in early stages of WG life, in topics
with a lot of different work, and in cross-WG presentations) these
"intro" presentations are a fact of life.  But I think we are
extremely bad at holding the reigns on them.

In a WG meeting, I think such "intro" presentations about drafts
really can be kept to three pieces of information: the name of the
draft, a slogan describing the problem it is supposed to solve, and a
pointer to the beginning(s) of discussion thread(s) on the draft.  If
the person promoting the draft can't give the elevator pitch, they
don't know their own draft well enough to summarize it and shouldn't
be presenting it.  Any additional discussion in the presentation ought
to be exploring, as much as possible, one or more of the following
topics:

    - a particular issue
    - is $issue a real problem
    - alternatives for solving $issue
    - motivation for $issue solution choices

Each such slide, it seems to me, ought to encourage at most a couple
minutes of exposition and then some discussion.  The _reason_ to get
together in a big room with other people is to use the high-bandwidth
opportunity to hash out the extent of a problem.  The back and forth
of "you forgot this", "no that won't work because it explodes foo",
and so on, is the value here.  

Notice that none of that includes complicated flow-chart diagrams that
explain in detail a proposal.  There _is_ a place for those, however:
an actual presentation that gets made after significant discussion on
the list has made it clear that nobody understands the proposal.  At
that point, those 10-15 minute presentations of some proposed
mechanism are important, if only to inspire commenters to go back to
the list and say, "Ok, _now_ I get what you were trying to say, and
your text needs to be improved along the following lines."  But these
full explanation presentations happen too often when there has not
been such confusion.

Of course, all of the above depends on us going back to the list and
working out the details there, and it depends on people having read
the drafts and having a list of questions themselves that have been
deferred from the list for the face to face discussion.

I believe presentations in meetings are also sometimed useful if they
are exploring a problem space.  In that case, I believe what one needs
is _short_ presentations of the sort, "Here's what I think the
problems are," and then a lot of well-moderated discussion.

Unfortunately, actually running meetings this way is a lot of work,
requires fairly careful planning, and requires an indifference to
nasty remarks on the part of presenters who would much rather listen
to themselves for 20 minutes than to others.  But I think it'd make
for better meetings.  (Yes, along with room layouts that were more
suited to getting people to the mic.)
 
> The old days are gone.

Yes, and we need to figure out how to use meeting time effectively
here in the new days.  That effective use does not, I think, involve
expanding to fill all the time in the year with 20 minute low-content
presentations summarizing the draft that you can read in the span of
the time it takes to get through the presentation.  (Perhaps I'm
wrong.  Perhaps people find that the only time they have now to read
the drafts is during the presentation of the draft.  I sure hope not.)

Best,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From hallam@gmail.com  Tue Jul 30 20:04:41 2013
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F84D11E814C for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 20:04:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.495
X-Spam-Level: 
X-Spam-Status: No, score=-2.495 tagged_above=-999 required=5 tests=[AWL=0.104,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TZe6JV3NuiMZ for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 20:04:40 -0700 (PDT)
Received: from mail-wi0-x230.google.com (mail-wi0-x230.google.com [IPv6:2a00:1450:400c:c05::230]) by ietfa.amsl.com (Postfix) with ESMTP id 3FD9511E80E4 for <ietf@ietf.org>; Tue, 30 Jul 2013 20:04:39 -0700 (PDT)
Received: by mail-wi0-f176.google.com with SMTP id f14so3095561wiw.3 for <ietf@ietf.org>; Tue, 30 Jul 2013 20:04:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=/35Cmf2cjRv2fRuSIjtv/gPKTdwiQvkCEOpMv7xqF4w=; b=rNHoWNY+KkT9fDUB3NAppooxHOBjlHWxccJ1qgldeJMh699bRjkmKNQvMP8TUHFiVY /zNlbvmTrkTGoDdhWKiEQAyXJGFbCRHdqJlxiFDxWAfWafYa1aIdCN6/AFY0bypp5Krp xLptIDCfRcJT8yEHZ4YXeN7XJPuktzMNlFKosq7xgZIrm2cYscSc0PaAh28R6jtCvIbv NuIovYLKS8+Je6UPHSAA79w4HLDbvxIk4c+IUdX90+7qP45pPE+D+bG0QDIbVEmVvJcb BRX22yEB1ezgnJVRpKHFD2L4sbz7g91F/TceHJytkYTkgpIOv4Gt2yDOoPpyC3tlwuZO LlmQ==
MIME-Version: 1.0
X-Received: by 10.194.219.233 with SMTP id pr9mr9966836wjc.8.1375239879128; Tue, 30 Jul 2013 20:04:39 -0700 (PDT)
Received: by 10.194.6.65 with HTTP; Tue, 30 Jul 2013 20:04:39 -0700 (PDT)
In-Reply-To: <51F82246.9000108@gmail.com>
References: <CE1DA8D5.2337E%Josh.Howlett@ja.net> <F2A870F2-9FC4-429A-B30E-118E3441DA10@network-heretics.com> <51F7F5FD.8040508@gmail.com> <51F82246.9000108@gmail.com>
Date: Tue, 30 Jul 2013 23:04:39 -0400
Message-ID: <CAMm+Lwh6nJfmjSEuHWmp=G9-J0t3q0wGd3mGwG4AzqNPcc3J+g@mail.gmail.com>
Subject: Re: Bringing back Internet transparency
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c1b7e679fe7704e2c5fcb7
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Jul 2013 03:04:41 -0000

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

On Tue, Jul 30, 2013 at 4:29 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> On 31/07/2013 05:21, Melinda Shore wrote:
> > On 7/30/13 7:59 AM, Keith Moore wrote:
> >> I don't think that's the problem; I think the problem is that most
> >> users don't realize how much lack of transparency is harming them.
> >> So "transparent Internet access" isn't a commodity.    Transparency
> >> would be cheaper if there were more demand for it, and there would be
> >> more demand for it if people realized how much more utility they'd
> >> get out of the Internet if they had it.
> >
> > <n> decades in, I suspect that if there were going to be demand
> > for "transparency" we'd be seeing it by now.  If VoIP wasn't the
> > kick in the pants that's been needed to change things, it's
> > difficult to imagine what else might be.
>
> Users want applications to just work, but they (and many business
> managers in our "industry") don't understand that when applications
> fail unpredictably, it's often because of glitches in what we call
> transparency.
>
> However, we are in an arms race here. Every step to improve transparency
> will be met by a further step in middleboxes that nibbles away at
> transparency. We've been debating this for 15 years; have you seen
> any real change in the balance of power?
>
>     Brian
>

Well this is the real issue. I really could not care whether my IP
addresses are constant end to end or change on each hop if the packets get
there.

What I do care a lot about is being able to work out what my network is
doing and which piece of equipment is responsible for any given fault.

One of the architectural shortcomings of the current situation is that the
Internet was originally designed to fill the gaps between the networks, the
inter-network. We now use the same architecture inside the local network.
Only it isn't optimized for network use in quite the same way or at least
the home user does not have a toolset that is as powerful for their
purposes as the Internet backbone providers have for theirs.

Instead what happened was that network devices that were poorly architected
to run under novel or windows or appletalk sprouted IP as a transport
choice. And in many cases this was done in a really shoddy way.
Filesharing, printers, the rest all hang off the network in ad hoc fashion.


Keith's obsession with NAT boxes is totally irrelevant to the core problem
which is that home networks don't use DNS as their
naming/directory/discovery infrastructure which is what they would do if
they were really Internet based. There is no model of what is 'normal' in
the network so no way to detect abnormal situations or the cause.

NAT is here to stay until the last IPv4 address is withdrawn which is 30
years off at minimum. And it will remain even then because there are so
many fun games to play with NAT.

--001a11c1b7e679fe7704e2c5fcb7
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, Jul 30, 2013 at 4:29 PM, Brian E Carpenter <span dir=3D"ltr=
">&lt;<a href=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_blank">bria=
n.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"HOEnZb"><div class=3D"h5">On 3=
1/07/2013 05:21, Melinda Shore wrote:<br>
&gt; On 7/30/13 7:59 AM, Keith Moore wrote:<br>
&gt;&gt; I don&#39;t think that&#39;s the problem; I think the problem is t=
hat most<br>
&gt;&gt; users don&#39;t realize how much lack of transparency is harming t=
hem.<br>
&gt;&gt; So &quot;transparent Internet access&quot; isn&#39;t a commodity. =
=A0 =A0Transparency<br>
&gt;&gt; would be cheaper if there were more demand for it, and there would=
 be<br>
&gt;&gt; more demand for it if people realized how much more utility they&#=
39;d<br>
&gt;&gt; get out of the Internet if they had it.<br>
&gt;<br>
&gt; &lt;n&gt; decades in, I suspect that if there were going to be demand<=
br>
&gt; for &quot;transparency&quot; we&#39;d be seeing it by now. =A0If VoIP =
wasn&#39;t the<br>
&gt; kick in the pants that&#39;s been needed to change things, it&#39;s<br=
>
&gt; difficult to imagine what else might be.<br>
<br>
</div></div>Users want applications to just work, but they (and many busine=
ss<br>
managers in our &quot;industry&quot;) don&#39;t understand that when applic=
ations<br>
fail unpredictably, it&#39;s often because of glitches in what we call<br>
transparency.<br>
<br>
However, we are in an arms race here. Every step to improve transparency<br=
>
will be met by a further step in middleboxes that nibbles away at<br>
transparency. We&#39;ve been debating this for 15 years; have you seen<br>
any real change in the balance of power?<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
=A0 =A0 Brian<br>
</font></span></blockquote></div><br>
</div><div class=3D"gmail_extra">Well this is the real issue. I really coul=
d not care whether my IP addresses are constant end to end or change on eac=
h hop if the packets get there.</div><div class=3D"gmail_extra"><br></div>
<div class=3D"gmail_extra">What I do care a lot about is being able to work=
 out what my network is doing and which piece of equipment is responsible f=
or any given fault.</div><div class=3D"gmail_extra"><br></div><div class=3D=
"gmail_extra">
One of the architectural shortcomings of the current situation is that the =
Internet was originally designed to fill the gaps between the networks, the=
 inter-network. We now use the same architecture inside the local network. =
Only it isn&#39;t optimized for network use in quite the same way or at lea=
st the home user does not have a toolset that is as powerful for their purp=
oses as the Internet backbone providers have for theirs.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Instead wha=
t happened was that network devices that were poorly architected to run und=
er novel or windows or appletalk sprouted IP as a transport choice. And in =
many cases this was done in a really shoddy way. Filesharing, printers, the=
 rest all hang off the network in ad hoc fashion.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra"><br></div><=
div class=3D"gmail_extra">Keith&#39;s obsession with NAT boxes is totally i=
rrelevant to the core problem which is that home networks don&#39;t use DNS=
 as their naming/directory/discovery infrastructure which is what they woul=
d do if they were really Internet based. There is no model of what is &#39;=
normal&#39; in the network so no way to detect abnormal situations or the c=
ause.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">NAT is here=
 to stay until the last IPv4 address is withdrawn which is 30 years off at =
minimum. And it will remain even then because there are so many fun games t=
o play with NAT.</div>
<div class=3D"gmail_extra"><br></div></div>

--001a11c1b7e679fe7704e2c5fcb7--

From tterribe@xiph.org  Tue Jul 30 20:43:11 2013
Return-Path: <tterribe@xiph.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 111D511E8155; Tue, 30 Jul 2013 20:43:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.677
X-Spam-Level: 
X-Spam-Status: No, score=-2.677 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SXhN21rlwFL2; Tue, 30 Jul 2013 20:43:02 -0700 (PDT)
Received: from smtp.mozilla.org (mx2.corp.phx1.mozilla.com [63.245.216.70]) by ietfa.amsl.com (Postfix) with ESMTP id 26B9411E80E4; Tue, 30 Jul 2013 20:43:01 -0700 (PDT)
Received: from [192.168.15.42] (unknown [213.23.104.157]) (Authenticated sender: tterriberry@mozilla.com) by mx2.mail.corp.phx1.mozilla.com (Postfix) with ESMTPSA id C5ADAF223F;  Tue, 30 Jul 2013 20:43:00 -0700 (PDT)
Message-ID: <51F887C3.6070802@xiph.org>
Date: Tue, 30 Jul 2013 20:42:59 -0700
From: "Timothy B. Terriberry" <tterribe@xiph.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 SeaMonkey/2.16
MIME-Version: 1.0
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Subject: Re: [payload] Last Call: <draft-ietf-payload-vp8-08.txt> (RTP Payload Format for	VP8 Video) to Proposed Standard
References: <20130604222555.32402.16024.idtracker@ietfa.amsl.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1135E7A62@xmb-aln-x02.cisco.com> <51EFB31A.3010506@xiph.org> <C5E08FE080ACFD4DAE31E4BDBF944EB113617E32@xmb-aln-x02.cisco.com>
In-Reply-To: <C5E08FE080ACFD4DAE31E4BDBF944EB113617E32@xmb-aln-x02.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>, "payload@ietf.org" <payload@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Jul 2013 03:43:11 -0000

Cullen Jennings (fluffy) wrote:
> I can't imagine how I could implement the frame buffers in VP8 in VLSI without having an upper limit on both the width and height of the image. How do you deal with that?

The one hardware VP8 decoder I have any experience with so far is mostly 
throughput-limited, not resolution limited (nor even limited by the 
number of streams... I was surprised to find this out, too). There are 
width/height limits, I'm sure, just because the size of the addresses 
must be finite, but they're not the bottleneck on any video you'd 
actually want to send. I could easily see how that might not be true on 
all (or even most) hardware implementations, however.

> I don't know if you ever got the Google VHDL code for VP8 but I have never got it so I don't know what it does but if you do, that would be great.

No, I dropped the ball here, so I don't know what it does either.

From scott.brim@gmail.com  Tue Jul 30 22:22:38 2013
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 732BD21F9F98 for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 22:22:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ATs8GCsBHcXJ for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 22:22:38 -0700 (PDT)
Received: from mail-oa0-x22b.google.com (mail-oa0-x22b.google.com [IPv6:2607:f8b0:4003:c02::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 086CB21F9F97 for <ietf@ietf.org>; Tue, 30 Jul 2013 22:22:36 -0700 (PDT)
Received: by mail-oa0-f43.google.com with SMTP id i10so599622oag.30 for <ietf@ietf.org>; Tue, 30 Jul 2013 22:22:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=YgGNZCWLl7ljn/mu6Hk3326MYyje0QR8aojXVgCz2M4=; b=R3S9kVs6lwVG3aA/HjwwBIcnmKv6AEK2sJGP4vXmJtj+dorfqEM7fprlNpTF6C6Tp3 GTVdT9NGBnKU6Q/2abfbOf+II7DnQyNmHsKjR/7l/uMug/Ft7W31FMnRqtp4LDjHc9yp Qd/aiqZOhoi1pVpirr/F0K3goH1Co5bZEMl2UOPOCWcWxoq5xTNBJ6ko+sFcKYCJCWG5 PNPwD+fmazdYGLoCY8mXsOwvnzAsECGYDYT7DE65JJF4Cscz9s0R+MjeyMGhom9S8FdN +FiH6Rstov/tgXO+pp+GoM88YZNGtK/YjG3pHIT3J2czrJtGaNKQW4QWS7moSB0/j9EN bu1A==
MIME-Version: 1.0
X-Received: by 10.60.123.112 with SMTP id lz16mr66323082oeb.88.1375248156544;  Tue, 30 Jul 2013 22:22:36 -0700 (PDT)
Received: by 10.182.44.105 with HTTP; Tue, 30 Jul 2013 22:22:36 -0700 (PDT)
In-Reply-To: <20130731022327.GA53174@mx1.yitter.info>
References: <20130730163502.455E918C10F@mercury.lcs.mit.edu> <51F7FC29.2000407@isi.edu> <51F82442.4000404@gmail.com> <20130731022327.GA53174@mx1.yitter.info>
Date: Wed, 31 Jul 2013 07:22:36 +0200
Message-ID: <CAPv4CP-Mhx_7+4my3Ywim7-joDo=kvX_To0cOK0RjO8+hP-=-w@mail.gmail.com>
Subject: Re: making our meetings more worth the time/expense
From: Scott Brim <scott.brim@gmail.com>
To: IETF discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=047d7b5d4f2ed954b104e2c7e9ba
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Jul 2013 05:22:38 -0000

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

http://tools.ietf.org/wg/intarea/trac/wiki/MeetingTimePrioritization

--047d7b5d4f2ed954b104e2c7e9ba
Content-Type: text/html; charset=ISO-8859-1

<a href="http://tools.ietf.org/wg/intarea/trac/wiki/MeetingTimePrioritization">http://tools.ietf.org/wg/intarea/trac/wiki/MeetingTimePrioritization</a>

--047d7b5d4f2ed954b104e2c7e9ba--

From moore@network-heretics.com  Tue Jul 30 23:35:59 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7EEC21F9FD8 for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 23:35:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.466
X-Spam-Level: 
X-Spam-Status: No, score=-3.466 tagged_above=-999 required=5 tests=[AWL=0.133,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pnhmVI4aAzgr for <ietf@ietfa.amsl.com>; Tue, 30 Jul 2013 23:35:54 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id BB5E021F9A3B for <ietf@ietf.org>; Tue, 30 Jul 2013 23:35:54 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 4A43620DC8; Wed, 31 Jul 2013 02:35:53 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute3.internal (MEProxy); Wed, 31 Jul 2013 02:35:53 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id :references:to; s=smtpout; bh=C0MUJTHDlqXnqFvBnHEftuTvDFE=; b=Wb uZZAwuYQAU2QR9Z0dDH7pUpHeLTvafftoEJ2JuP8jhYDNy7ipIzzvvq96il28cX/ +2uufIrIqPT1OlUcu5Bbq4hqd4jjPFs0EptfiXLV9e6nE9LPrC7CgVXdvgdrmNTf RuhYI7oH0N4qtl/xAHzkuSeUQw7YdUh4WuqbDYZZ0=
X-Sasl-enc: khHnoXlz4xTPzNfUpcrQv57t3zgLZNmD6IwrpLiuSqKg 1375252552
Received: from surfer-172-29-8-65-hotspot.internet-for-guests.com (unknown [87.193.195.90]) by mail.messagingengine.com (Postfix) with ESMTPA id 32F87C00E83; Wed, 31 Jul 2013 02:35:52 -0400 (EDT)
Subject: Re: making our meetings more worth the time/expense
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <51F82442.4000404@gmail.com>
Date: Wed, 31 Jul 2013 08:35:50 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <BB6564A3-80F7-479F-9336-04A0916F5989@network-heretics.com>
References: <20130730163502.455E918C10F@mercury.lcs.mit.edu> <51F7FC29.2000407@isi.edu> <51F82442.4000404@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1085)
Cc: braden@isi.edu, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Jul 2013 06:36:00 -0000

On Jul 30, 2013, at 10:38 PM, Brian E Carpenter wrote:

> It's been pointed out before that in a group with very diverse =
languages,
> written words are usually better understood than speech. It's a fact =
of life
> that you can't have a full-speed cut-and-thrust discussion in a group
> of 100 people, half of whom are speaking a foreign language. Sitting =
in
> a circle does not fix this.

Yes, but most of the people in a typical WG meeting today aren't really =
participating in the meeting anyway.   They're not contributing input, =
they're not paying attention.  Their noses are in laptops.   It's hard =
to tell how many of them would be participating if the meeting were more =
useful, but the very fact that the room contains so many nonparticipants =
is itself a deterrent to getting work done in the meeting.   If nothing =
else, whenever someone tries to get a sense of the room, it's very =
misleading - people may be humming when they haven't even been =
listening, or it may appear that there's no significant support for =
something when there really is significant support among those who are =
interested in the topic.


> Also, remote participants need full text slides; the soundtrack simply
> isn't enough.

You seem to be assuming that the purpose of WG meetings is to have =
presentations.   I emphatically disagree.

If we decide to make WG meetings fora for interaction and discussion, we =
can adopt or invent disciplines and tools to better accommodate =
interaction and discussion between people of diverse languages and =
including those at other locations.   But the disciplines and tools that =
we've adopted at the moment are designed to accommodate an audience, not =
active participants.

> The old days are gone.

It sounds like you are saying that IETF is doomed to become irrelevant =
because it's stuck in habits that do not work.  I hope you're wrong =
about that.

Keith


From d3e3e3@gmail.com  Wed Jul 31 01:39:40 2013
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A09221F9F21 for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 01:39:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.3
X-Spam-Level: 
X-Spam-Status: No, score=-102.3 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_12=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1AQJ-+YVBPYt for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 01:39:26 -0700 (PDT)
Received: from mail-ob0-x22f.google.com (mail-ob0-x22f.google.com [IPv6:2607:f8b0:4003:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id EC00421F9C90 for <ietf@ietf.org>; Wed, 31 Jul 2013 01:31:31 -0700 (PDT)
Received: by mail-ob0-f175.google.com with SMTP id xn12so803943obc.20 for <ietf@ietf.org>; Wed, 31 Jul 2013 01:30:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=xcFlaNqfoL4b31lRZaP3q2G5I4aTcWyGNMTzSNSqp7c=; b=nIQLdS5Xd3D+ky3Bqv8KkIPGDWVVeVGQ8fXvWmSB6HHT7OSXYK+fOlcmdYX2FWveR6 AkSfKg4YYAeAXoJ+eouKGiIBfwxbiHiciPfwz4ChW70J+m9rIXR51CwgDhuBevFvRy/A yxOmq8eeEbw4eP47T7It4SlG3NAy/6dGhCb6yVoBEYi1hCj/FyWwMeAD+YWm1A1htkve rN8WrgZ7Of0QR1ig8NzR8Um+/e+KJLGA3YLXwpINKOsBxeVZsbx0fXtbWo8a/72JBt3M v3/RvKiMqdZiic6jZFgP9bAelNmnp3KKGTI8tREpLe3Oy0QPcVYgB4rnDOLvByjuXfPB XtXg==
X-Received: by 10.60.140.168 with SMTP id rh8mr65907134oeb.17.1375259446574; Wed, 31 Jul 2013 01:30:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.131.7 with HTTP; Wed, 31 Jul 2013 01:30:26 -0700 (PDT)
In-Reply-To: <20840.1375200653@sandelman.ca>
References: <EDC539D2-48CE-44D7-A06C-19EEAE42D31C@piuha.net> <BF2DD745-99D0-420E-B199-7C8F94981BDA@network-heretics.com> <20840.1375200653@sandelman.ca>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Wed, 31 Jul 2013 04:30:26 -0400
Message-ID: <CAF4+nEHS0fH8+ewhiWXoYwUfAa27wfrXDR8fZLYid-Z-mc7ZSw@mail.gmail.com>
Subject: Re: making our meetings more worth the time/expense (was: Re: setting a goal for an inclusive IETF)
To: "ietf@ietf.org list" <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Jul 2013 08:39:44 -0000

The most valuable part of IETF meeting is and has always been the hall
conversations and side meetings

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

On Tue, Jul 30, 2013 at 12:10 PM, Michael Richardson
<mcr+ietf@sandelman.ca> wrote:
>
> Keith Moore <moore@network-heretics.com> wrote:
>     > But earlier today I realized that the problem isn't just the cost of attending
>     > meetings - it's the value that we get in return for those meetings.   I've been
>     > taking notes about how ineffectively we use our meeting time.   Most of what
>     > I've observed won't surprise anybody, but here's a summary:
>
> Thanks for this.
>
>     > Rooms are set up not to facilitate discussion, but to discourage it.   The
>     > lights are dim, the chairs are facing forward rather than other participants,
>     > the projector screen (not the person facilitating a discussion, even if someone
>     > is trying to facilitate a discussion) is the center of attention.    The chairs
>     > are set so close together and with so few aisles that it's hard for most of the
>     > attendees to get to the mics.   The "microphone discipline" which was intended
>     > to facilitate remote participation ends up making discussion more difficult for
>     > everybody who has paid to be on site.
>
> I think that these physical things are something that we can do some
> experiments about.
>
>     > Well, please excuse my candor, but f*ck habit.   We can't be effective
>     > engineers if we let bad habits continue to dictate how we work.
>
> I agree.
>
>     > For 80% of most WG meetings, the lights should be bright, the participants
>     > should face each other.   If there's a person facilitating the discussion that
>     > person should be the center of attention.    If we're going to use microphones,
>     > the rooms should be set up to allow everyone in the room to have easy access to
>     > them.   We should have several microphones, again facing each other, so that
>     > several people can have a conversation without everyone having to queue up.
>
> Can we please try this in Vancouver?
> This would work especially well for BOFs.
> Maybe we can start there.
> Chairs will need training as *facilitators*
>
>     > And maybe, in addition, we need to provide better places for people to hang out
>     > and work while trying to get an opportunity to interact with specific people.
>     > The terminal rooms are generally placed in out-of-the-way corners, but the most
>     > effective places to interact with people are in the hallways.
>
> I agree.
>
> --
> ]               Never tell me the odds!                 | ipv6 mesh networks [
> ]   Michael Richardson, Sandelman Software Works        | network architect  [
> ]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [
>
>
>
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>
>

From chair@ietf.org  Wed Jul 31 01:45:55 2013
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8F1821F93BF for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 01:45:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bon93FWGCLwg for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 01:45:47 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.21]) by ietfa.amsl.com (Postfix) with ESMTP id EB0AE21E80B3 for <ietf@ietf.org>; Wed, 31 Jul 2013 01:37:12 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id D50B4A6098; Wed, 31 Jul 2013 01:36:43 -0700 (PDT)
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 6tjpg0Mf_3sz; Wed, 31 Jul 2013 01:36:43 -0700 (PDT)
Received: from dhcp-1519.meeting.ietf.org (dhcp-1519.meeting.ietf.org [130.129.21.25]) by c9a.amsl.com (Postfix) with ESMTPSA id DC48D9FB28; Wed, 31 Jul 2013 01:36:42 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: PS to IS question from plenary
From: IETF Chair <chair@ietf.org>
In-Reply-To: <4776.1375232627@sandelman.ca>
Date: Wed, 31 Jul 2013 10:36:51 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <6886C7F7-0300-4106-B2A3-B85E1923EA85@ietf.org>
References: <F3241893-F062-4F09-BA09-398BE207192F@ietf.org> <D2354ED434665515542E74E4@JcK-HP8200.jck.com> <4776.1375232627@sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.1508)
Cc: John C Klensin <john-ietf@jck.com>, "ietf@ietf.org list" <ietf@ietf.org>, sob@harvard.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Jul 2013 08:45:55 -0000

> Just to make sure we have good data, can we go back a few more years?
> Specifically, did we not previously have a restriction forbidding =
references
> FS->DS, and {FS,DS}->PS?.... RFC3967 was in Dec. 2004, but I thought =
that we
> had some other work more recently (2008?) that attempted to unjam =
things.
>=20
> What I'm wondering is if the 20 actions prior to 6410 was an anomaly,
> and really the historical rate of upgrade is really lower.

A quick couple of seconds with mail search and grep says that in the =
four years preceding publication of RFC 6410, we made 28 actions. As =
noted earlier, 20 of those happened in the 22 months preceding the =
publication of RFC 6410. So in the 2+ years before that only 8 were =
produced.

I'd love to have a graph that plots DS/FS/IS progression per year, over =
time. But I don't have time to make that today. Unless someone else =
wants to...

Jari


From mcr@sandelman.ca  Wed Jul 31 02:15:27 2013
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1491921F9C88 for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 02:15:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.365
X-Spam-Level: 
X-Spam-Status: No, score=-2.365 tagged_above=-999 required=5 tests=[AWL=0.234,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pZ2+DsNrEJNa for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 02:15:26 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id 5F88911E8181 for <ietf@ietf.org>; Wed, 31 Jul 2013 02:10:33 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 9A2F620251; Wed, 31 Jul 2013 06:16:27 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id CF7E063A7C; Wed, 31 Jul 2013 05:08:57 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id BB89E636AD; Wed, 31 Jul 2013 05:08:57 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Donald Eastlake <d3e3e3@gmail.com>
Subject: Re: making our meetings more worth the time/expense (was: Re: setting a goal for an inclusive IETF)
In-Reply-To: <CAF4+nEHS0fH8+ewhiWXoYwUfAa27wfrXDR8fZLYid-Z-mc7ZSw@mail.gmail.com>
References: <EDC539D2-48CE-44D7-A06C-19EEAE42D31C@piuha.net> <BF2DD745-99D0-420E-B199-7C8F94981BDA@network-heretics.com> <20840.1375200653@sandelman.ca> <CAF4+nEHS0fH8+ewhiWXoYwUfAa27wfrXDR8fZLYid-Z-mc7ZSw@mail.gmail.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Wed, 31 Jul 2013 05:08:57 -0400
Message-ID: <13501.1375261737@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Jul 2013 09:15:27 -0000

--=-=-=


Donald Eastlake <d3e3e3@gmail.com> wrote:
    > The most valuable part of IETF meeting is and has always been the hall
    > conversations and side meetings

So that implies to me that we should use our session time extremely
efficiently, always finish sessions early (to facilitate time for ad-hoc
conversations), and that the number of simultaneous sessions should be
reduced so that people have more free time.

We should in fact discourage discussions at the mic, because they take up
time.  Maybe only have presentations, and prepared written questions?

(What a curious email address. Is it code, or is it just all the good ones
were taken?)

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works



--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUBUfjUJ4qHRg3pndX9AQKIrAQAjsrTtQ3nosYOHAfvgjem+cWo1XVvq5v4
IejuVcZRPKTTj8lmSGQPoEJK5ru8hzPc34eUi3I4/XRH7AVuayCi1P8oDn4fnng8
nCIKOnb2v5aN7ucRw+B7kLS51rGohJgTJ1dpOcxLwaNDT1BOc7uERMfHTua5ylD1
8FYrN+I+V3w=
=0q6T
-----END PGP SIGNATURE-----
--=-=-=--

From sm@resistor.net  Wed Jul 31 03:14:17 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C85421F9F70 for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 03:14:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.545
X-Spam-Level: 
X-Spam-Status: No, score=-102.545 tagged_above=-999 required=5 tests=[AWL=0.054, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zr6BXrOaWWw9 for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 03:14:12 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F27821F9FCF for <ietf@ietf.org>; Wed, 31 Jul 2013 03:14:12 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r6VAE2HY013923; Wed, 31 Jul 2013 03:14:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1375265647; bh=z7qsIM2Y2eHbkuaQGCWI8OQPlFftOS2NFT6uSh1htJY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Zt+8JI+UkEq6JjF+aU0ILoxpxL9pIrIhRrisnlmh4fydbmwlBgrzr00qZ4Syj3KU9 f8JJYF5y5OU0bucq1sllvzGYDrm7WejclIol+iklIROf/cWZ5mi895u5HbK8CQAgPd O9XovWbDU25CIbgqXKONVUnqZwth4MuGlk27pnus=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1375265647; i=@resistor.net; bh=z7qsIM2Y2eHbkuaQGCWI8OQPlFftOS2NFT6uSh1htJY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=e2qR1Ntd7bfwYGXY6bQJcUY8U4wFk3cwF8iOD0JvdCvXFOJxLoRGSXDuVCa1S0Tvn kxGFwqXzXpS8HwAygpLXTxXVf+lJ7h85wE08GRFZ/BeQQgc+zU6U+k37EUvRS0I5Ln pZakHHeZmen9i9VPaYi7W4OmBT0xvtCP80AJZkJI=
Message-Id: <6.2.5.6.2.20130730144417.0cf320a8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 31 Jul 2013 02:28:43 -0700
To: dcrocker@bbiw.net
From: SM <sm@resistor.net>
Subject: Re: PS to IS question from plenary
In-Reply-To: <51F82BED.6000508@dcrocker.net>
References: <F3241893-F062-4F09-BA09-398BE207192F@ietf.org> <D2354ED434665515542E74E4@JcK-HP8200.jck.com> <6.2.5.6.2.20130730115827.0d632fe8@resistor.net> <51F82BED.6000508@dcrocker.net>
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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Jul 2013 10:14:17 -0000

Hi Dave,
At 14:11 30-07-2013, Dave Crocker wrote:
>And, of course, if it "can" be reshashed, in the IETF it will be.

Agreed.

>However the specification for the new two-stage model provides 
>criteria for the second stage, and it does not include re-evaluating 
>the technology or its details.  Instead it focuses on adoption and use.

RFC 5011 is one of the rare RFCs which does not have any 
erratum.  The move wasn't problematic.  It is not clear whether RFC 
6891 is an odd case or symptomatic of the difficulties in updating a 
specification.

The easier way not to have a re-evaluation is not to reopen the RFC 
(e.g. RFC 5011).  Anything else means having two consensus calls on 
the text.  draft-bradner-restore-proposed-00 proposes an alternative 
where the specification is not expected to be complete and comprehensive.

Here's a minimum standards profile published in 2009:

   SMTP IETF STD 10 (RFC 821, 1869, 1870)

   DNS IETF STD 13 (RFC 1034, 1035)

   HTTP v1.1 (RFC 2616), URL (RFC 1738), URI (RFC 2396)

   IPv4 (RFC 791, 792, 919, 922, 1112)

   BGP4 (RFC 1771)

The ex-IAB Chair explains that RFC 1035 is an Internet Standard.  He 
then explains that an Experimental Standard (RFC 1183) updates that 
Internet Standard.  The Internet Standard is updated by a Best 
Current Practices (RFC 6895).  There is also a Proposed Standard ( 
RFC 1982) which updates the Internet Standard.  He recommends RFC 
2026 for further information.  He receives an enquiry afterwards 
about immature specifications.  He decides to ask the question at the 
plenary.  The community thanks him for his valiant efforts.

The alternative is to settle for Informational Standards as that 
requires less effort.

Regards,
-sm 


From kvivek@broadcom.com  Wed Jul 31 03:54:56 2013
Return-Path: <kvivek@broadcom.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9375A11E817A; Wed, 31 Jul 2013 03:54:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FGVg7ZOriMhF; Wed, 31 Jul 2013 03:54:52 -0700 (PDT)
Received: from mms2.broadcom.com (mms2.broadcom.com [216.31.210.18]) by ietfa.amsl.com (Postfix) with ESMTP id 9519711E8177; Wed, 31 Jul 2013 03:54:50 -0700 (PDT)
Received: from [10.9.208.55] by mms2.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.5)); Wed, 31 Jul 2013 03:48:36 -0700
X-Server-Uuid: 4500596E-606A-40F9-852D-14843D8201B2
Received: from SJEXCHCAS06.corp.ad.broadcom.com (10.16.203.14) by IRVEXCHCAS07.corp.ad.broadcom.com (10.9.208.55) with Microsoft SMTP Server (TLS) id 14.1.438.0; Wed, 31 Jul 2013 03:54:40 -0700
Received: from SJEXCHMB09.corp.ad.broadcom.com ( [fe80::3da7:665e:cc78:181f]) by SJEXCHCAS06.corp.ad.broadcom.com ( [::1]) with mapi id 14.01.0438.000; Wed, 31 Jul 2013 03:54:40 -0700
From: "Vivek Kumar" <kvivek@broadcom.com>
To: "ietf@ietf.org" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-mip-mep-map-08.txt> (Per-Interface MIP Addressing Requirements and Design Considerations) to Informational RFC
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-tp-mip-mep-map-08.txt> (Per-Interface MIP Addressing Requirements and Design Considerations) to Informational RFC
Thread-Index: AQHOjdNux/GOoGjWDU6B2XZkLqx4o5l+md1Q
Date: Wed, 31 Jul 2013 10:54:39 +0000
Message-ID: <3C086BA39C55B9418AE8FEA3F3EFDEC42AE28738@SJEXCHMB09.corp.ad.broadcom.com>
References: <20130731094847.1312.52261.idtracker@ietfa.amsl.com>
In-Reply-To: <20130731094847.1312.52261.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.16.203.100]
MIME-Version: 1.0
X-WSS-ID: 7DE6340E1R070934870-01-01
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: "mpls@ietf.org" <mpls@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Jul 2013 10:54:56 -0000

Hi Authors,

In  the terminology section ( section 3) of draft , the in-mip and out-mip =
are defined using forwarding engine as reference .
But the term forwarding engine has not been explained in terminology sectio=
n. Since the  forwarding engine ( FW) is used in all the diagram in the dra=
ft , I feel it will be helpful if you could add some description in termino=
logy section to state what does the forwarding engine means here . =20

Regards,
Vivek

=20

-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of The=
 IESG
Sent: Wednesday, July 31, 2013 3:19 PM
To: IETF-Announce
Cc: mpls@ietf.org
Subject: [mpls] Last Call: <draft-ietf-mpls-tp-mip-mep-map-08.txt> (Per-Int=
erface MIP Addressing Requirements and Design Considerations) to Informatio=
nal RFC


The IESG has received a request from the Multiprotocol Label Switching WG
(mpls) to consider the following document:
- 'Per-Interface MIP Addressing Requirements and Design Considerations'
  <draft-ietf-mpls-tp-mip-mep-map-08.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 2013-08-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


   The Framework for Operations, Administration and Maintenance (OAM)
   within the MPLS Transport Profile (MPLS-TP) describes how Maintenance
   Entity Group Intermediate Points (MIPs) may be situated within
   network nodes at the incoming and outgoing interfaces.

   This document elaborates on important considerations for internal MIP
   addressing.  More precisely it describes important restrictions for
   any mechanism that specifies a way of forming OAM messages so that
   they can be targeted at MIPs on incoming or MIPs on outgoing
   interfaces and forwarded correctly through the forwarding engine.
   Furthermore, the document includes considerations for node
   implementations where there is no distinction between the incoming
   and outgoing MIP.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-mip-mep-map/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-mip-mep-map/ballot/


No IPR declarations have been submitted directly on this I-D.


_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls



From abdussalambaryun@gmail.com  Wed Jul 31 04:51:04 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E7A821E80E0 for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 04:51:01 -0700 (PDT)
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=[AWL=-0.300,  BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_12=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R3fR9AXgXeoZ for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 04:51:00 -0700 (PDT)
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 A067C21F92E7 for <ietf@ietf.org>; Wed, 31 Jul 2013 04:50:47 -0700 (PDT)
Received: by mail-pa0-f49.google.com with SMTP id bi5so766268pad.36 for <ietf@ietf.org>; Wed, 31 Jul 2013 04:50:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=2w3pQ89mPV0U65L1qpmolWHMwJrZMef1baLzqW+pj6c=; b=biYYAYEVHFGyORxXKvO4ESjLfUya4patRGtNHfyzl+/BPVQEzEiiQJ3h10uztv8QAx R0OuH9L6mOZSbac5tm9j6D6qET5z9NhsQuvOa7phtaKQQzraQuTQCr22QzsGAHvZMAbv 4SLtIEwNrieyU/nmrZA1toZxrFOHMfEL0ovvNcy2vBNWGHRM+JeWL/eE7RgcjNaCwczf tVjMX+/CbSNEIaZG0apNSBh3ltX4GoVsufOC7rC7hqQ2uNcOkDHLNc0k41mqP0ucdD65 lBkOjPYidf4+JPhxTBWZ1EN3Y+964SsnZD0XvGNg/mSzdAYp05PQ4W/g17dx6jmFROu1 4a8w==
MIME-Version: 1.0
X-Received: by 10.68.220.1 with SMTP id ps1mr73888258pbc.30.1375271446722; Wed, 31 Jul 2013 04:50:46 -0700 (PDT)
Received: by 10.68.250.133 with HTTP; Wed, 31 Jul 2013 04:50:46 -0700 (PDT)
In-Reply-To: <BF2DD745-99D0-420E-B199-7C8F94981BDA@network-heretics.com>
References: <EDC539D2-48CE-44D7-A06C-19EEAE42D31C@piuha.net> <BF2DD745-99D0-420E-B199-7C8F94981BDA@network-heretics.com>
Date: Wed, 31 Jul 2013 12:50:46 +0100
Message-ID: <CADnDZ8-ZzqHt=E69gN0p_5VLL9Lu4Uigex5_aqnHvDVYnSPhvA@mail.gmail.com>
Subject: Re: making our meetings more worth the time/expense (was: Re: setting a goal for an inclusive IETF)
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Keith Moore <moore@network-heretics.com>
Content-Type: multipart/alternative; boundary=e89a8ff1ca780d3c7f04e2cd5658
Cc: Pete Resnick <presnick@qti.qualcomm.com>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Jul 2013 11:51:04 -0000

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

I agree with some of your points, thanks, comments below,

On Tue, Jul 30, 2013 at 4:54 PM, Keith Moore <moore@network-heretics.com>wrote:

>
>
> http://www.ietf.org/blog/2013/07/a-diverse-ietf/
>
> Also, I wanted to let everyone know that tomorrow in the Administrative
> Plenary, Kathleen Moriarty and Suresh Krishnan will be talking about what
> they have uncovered so far in their efforts in the diversity design team.
> I'm looking very much forward to their report. Their efforts will help us
> understand where we have room to improve - often by much :-) - and what
> kinds of actions we can take to improve our inclusiveness.
>
> This is something that I've struggled with for years.   A big part of the
> "problem" (from one point-of-view) is that we've become so geographically
> diverse in our choice of meeting sites that we've drastically raised the
> cost of attending meetings on a regular basis - everyone has to travel a
> lot to so (though people in North America still have an easier time of it).
>   And while there are clearly things that could be done to reduce meeting
> costs, we'd be doing very well to reduce total trip cost by more than say
> 15%.
>
> But earlier today I realized that the problem isn't just the cost of
> attending meetings - it's the value that we get in return for those
> meetings.   I've been taking notes about how ineffectively we use our
> meeting time.   Most of what I've observed won't surprise anybody, but
> here's a summary:
>
> WG meeting sessions aren't scheduled to encourage discussion, but to
> discourage it.   At meeting after meeting, in several different areas, I
> see the lion's share of the time devoted to presentations rather than
> discussion.
>
> Similarly, WG meetings generally aren't run in such a way to facilitate
> discussion, but to discourage it.  It's only Tuesday afternoon and I've
> already lost count of how many times I've heard a meeting chair tell people
> that they have to stop discussing things because there are more *
> presentations* to do.
>

I think I was told that IESG is in charge of management of the meeting, so
we should ask it to clarify its position, WHY it was done that way?
However, I mentioned that time management was not done well in MANET WG in
previous meetings but no one cares of my comments. I hope your will get
through to IESG.

>
> Rooms are set up not to facilitate discussion, but to discourage it.   The
> lights are dim, the chairs are facing forward rather than other
> participants, the projector screen (not the person facilitating a
> discussion, even if someone is trying to facilitate a discussion) is the
> center of attention.    The chairs are set so close together and with so
> few aisles that it's hard for most of the attendees to get to the mics.
> The "microphone discipline" which was intended to facilitate remote
> participation ends up making discussion more difficult for everybody who
> has paid to be on site.
>

I mentioned before that I was discouraged while I was remote participant,
but seems like even some f2f participants get that feelings from time to
time. The management of meetings should respond to your comments (not a
person but the body, which I expect IESG).

>
> In the vast majority of WG sessions, everyone has his nose in a laptop.
> (me included).   This is because the information being presented at the
> moment is generally not valuable enough to occupy the attendees' attention.
>  The attendees are there for one of two reasons - either they're just
> trying to absorb some low-value information while still doing something
> else that is more useful, or they're waiting for some opportunity to
> actually interact - either within the context of that WG meeting or
> afterward (perhaps because the best way to catch a particular person is
> often to show up at a WG meeting that that person is attending.)
>

I usually will blame the IETF chairs to do better attraction to
participants including remote ones on jabber.

>
> All of these things have been standard practice, in IETF and elsewhere,
> for so long, that hardly anyone questions them.   They have to be that way
> because they're habit, and even if one or two people try to change things
> (and I realize some ADs are trying), they have to contend with the mindless
> habit-driven decisions of everyone else involved.
>

We can change meetings management, and I don't think there is a standard
practice for management of this meeting and others. We need an RFC for how
to best manage the meeting, which can update from time to time, however, I
mentioned to the venue selectors to be involved because selecting venue
affects the meeting management capacity.

>
> Well, please excuse my candor, but f*ck habit.   We can't be effective
> engineers if we let bad habits continue to dictate how we work.
>

You keep repeating habit as it is not good, but I think we need it, but we
need management to make people's habit in the direction of the IETF habits
:-)

AB

>
> ------
>
>
> My expenses for this meeting are around USD 2.500.   Some are paying more,
> some less, but if we multiply average expense times the number of people
> attending, that's a tremendous amount of money.   Add that value is dwarfed
> by the value of the people's time that is being spent here.
>
> We are spending this time to travel to meet face-to-face, not so that we
> can see PowerPoint all day for a week, but so we can interact.
> Presentations, for the most part, do not help.   They get in the way.
>
> Visual aids can help to facilitate a discussion, but they should be as
> brief as possible, and the room setup, meeting schedule, etc. should not be
> optimized for the visual aids.   They should be optimized for discussion.
>
> For 80% of most WG meetings, the lights should be bright, the participants
> should face each other.   If there's a person facilitating the discussion
> that person should be the center of attention.    If we're going to use
> microphones, the rooms should be set up to allow everyone in the room to
> have easy access to them.   We should have several microphones, again
> facing each other, so that several people can have a conversation without
> everyone having to queue up.
>
> And maybe, in addition, we need to provide better places for people to
> hang out and work while trying to get an opportunity to interact with
> specific people.   The terminal rooms are generally placed in
> out-of-the-way corners, but the most effective places to interact with
> people are in the hallways.
>
>
> Keith
>
>

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

<div dir=3D"ltr">I agree with some of your points, thanks, comments below,<=
div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, Jul 30, 20=
13 at 4:54 PM, Keith Moore <span dir=3D"ltr">&lt;<a href=3D"mailto:moore@ne=
twork-heretics.com" target=3D"_blank">moore@network-heretics.com</a>&gt;</s=
pan> wrote:<br>
<blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-=
color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class=
=3D"gmail_quote"><div style=3D"word-wrap:break-word"><br><div><div><br><a h=
ref=3D"http://www.ietf.org/blog/2013/07/a-diverse-ietf/" target=3D"_blank">=
http://www.ietf.org/blog/2013/07/a-diverse-ietf/</a><br>
<br>Also, I wanted to let everyone know that tomorrow in the Administrative=
 Plenary, Kathleen Moriarty and Suresh Krishnan will be talking about what =
they have uncovered so far in their efforts in the diversity design team. I=
&#39;m looking very much forward to their report. Their efforts will help u=
s understand where we have room to improve - often by much :-) - and what k=
inds of actions we can take to improve our inclusiveness.<br>
</div></div><br><div>This is something that I&#39;ve struggled with for yea=
rs. =A0 A big part of the &quot;problem&quot; (from one point-of-view) is t=
hat we&#39;ve become so geographically diverse in our choice of meeting sit=
es that we&#39;ve drastically raised the cost of attending meetings on a re=
gular basis - everyone has to travel a lot to so (though people in North Am=
erica still have an easier time of it). =A0 And while there are clearly thi=
ngs that could be done to reduce meeting costs, we&#39;d be doing very well=
 to reduce total trip cost by more than say 15%.</div>
<div><br></div><div>But earlier today I realized that the problem isn&#39;t=
 just the cost of attending meetings - it&#39;s the value that we get in re=
turn for those meetings. =A0 I&#39;ve been taking notes about how ineffecti=
vely we use our meeting time. =A0 Most of what I&#39;ve observed won&#39;t =
surprise anybody, but here&#39;s a summary:</div>
<div><br></div><div>WG meeting sessions aren&#39;t scheduled to encourage d=
iscussion, but to discourage it. =A0 At meeting after meeting, in several d=
ifferent areas, I see the lion&#39;s share of the time devoted to presentat=
ions rather than discussion.=A0</div>
<div><br></div><div>Similarly, WG meetings generally aren&#39;t run in such=
 a way to facilitate discussion, but to discourage it. =A0It&#39;s only Tue=
sday afternoon and I&#39;ve already lost count of how many times I&#39;ve h=
eard a meeting chair tell people that they have to stop discussing things b=
ecause there are more <i>presentations</i> to do.</div>
</div></blockquote><div>=A0</div><div>I think I was told that IESG is in ch=
arge of management of the meeting, so we should ask it to clarify its posit=
ion, WHY it was done that way? However, I mentioned that time management wa=
s not done well in MANET WG in previous meetings but no one cares of my com=
ments. I hope your will get through to IESG.=A0</div>
<blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-=
color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class=
=3D"gmail_quote"><div style=3D"word-wrap:break-word"><div><br></div><div>Ro=
oms are set up not to facilitate discussion, but to discourage it. =A0 The =
lights are dim, the chairs are facing forward rather than other participant=
s, the projector screen (not the person facilitating a discussion, even if =
someone is trying to facilitate a discussion) is the center of attention. =
=A0 =A0The chairs are set so close together and with so few aisles that it&=
#39;s hard for most of the attendees to get to the mics. =A0 The &quot;micr=
ophone discipline&quot; which was intended to facilitate remote participati=
on ends up making discussion more difficult for everybody who has paid to b=
e on site.=A0</div>
</div></blockquote><div>=A0</div><div>I mentioned before that I was discour=
aged while I was remote participant, but seems like even some f2f participa=
nts=A0get that feelings from time to time. The management of meetings shoul=
d respond to your comments (not a person but the body, which I expect IESG)=
.=A0</div>
<blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-=
color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class=
=3D"gmail_quote"><div style=3D"word-wrap:break-word"><div><br></div><div>In=
 the vast majority of WG sessions, everyone has his nose in a laptop. =A0 (=
me included). =A0 This is because the information being presented at the mo=
ment is generally not valuable enough to occupy the attendees&#39; attentio=
n. =A0The attendees are there for one of two reasons - either they&#39;re j=
ust trying to absorb some low-value information while still doing something=
 else that is more useful, or they&#39;re waiting for some opportunity to a=
ctually interact - either within the context of that WG meeting or afterwar=
d (perhaps because the best way to catch a particular person is often to sh=
ow up at a WG meeting that that person is attending.)</div>
</div></blockquote><div>=A0</div><div>I usually will blame the IETF chairs =
to do better attraction to participants including remote ones on jabber.=A0=
</div><blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border=
-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid"=
 class=3D"gmail_quote">
<div style=3D"word-wrap:break-word"><div><br></div><div>All of these things=
 have been standard practice, in IETF and elsewhere, for so long, that hard=
ly anyone questions them. =A0 They have to be that way because they&#39;re =
habit, and even if one or two people try to change things (and I realize so=
me ADs are trying), they have to contend with the mindless habit-driven dec=
isions of everyone else involved.</div>
</div></blockquote><div>=A0</div><div>We can change meetings management, an=
d=A0I don&#39;t think there is a standard practice for management of=A0this=
 meeting=A0and others. We need an RFC for how to best manage the meeting, w=
hich can update from time to time, however, I mentioned to the venue select=
ors to be involved because selecting venue affects the meeting management c=
apacity.</div>
<blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-=
color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class=
=3D"gmail_quote"><div style=3D"word-wrap:break-word"><div><br></div><div>We=
ll, please excuse my candor, but f*ck habit. =A0 We can&#39;t be effective =
engineers if we let bad habits continue to dictate how we work.</div>
</div></blockquote><div>=A0</div><div>You keep repeating habit as it is not=
 good, but I think we need it, but we need management to make people&#39;s =
habit in the direction of the IETF habits :-)</div><div>=A0</div><div>AB=A0=
</div>
<blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-=
color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class=
=3D"gmail_quote"><div style=3D"word-wrap:break-word"><div><br></div><div>--=
----</div>
<div><br></div><div><br></div><div>My expenses for this meeting are around =
USD 2.500. =A0 Some are paying more, some less, but if we multiply average =
expense times the number of people attending, that&#39;s a tremendous amoun=
t of money. =A0 Add that value is dwarfed by the value of the people&#39;s =
time that is being spent here.</div>
<div><br></div><div>We are spending this time to travel to meet face-to-fac=
e, not so that we can see PowerPoint all day for a week, but so we can inte=
ract. =A0 Presentations, for the most part, do not help. =A0 They get in th=
e way.</div>
<div><br></div><div>Visual aids can help to facilitate a discussion, but th=
ey should be as brief as possible, and the room setup, meeting schedule, et=
c. should not be optimized for the visual aids. =A0 They should be optimize=
d for discussion.</div>
<div><br></div><div>For 80% of most WG meetings, the lights should be brigh=
t, the participants should face each other. =A0 If there&#39;s a person fac=
ilitating the discussion that person should be the center of attention. =A0=
 =A0If we&#39;re going to use microphones, the rooms should be set up to al=
low everyone in the room to have easy access to them. =A0 We should have se=
veral microphones, again facing each other, so that several people can have=
 a conversation without everyone having to queue up.</div>
<div><br></div><div>And maybe, in addition, we need to provide better place=
s for people to hang out and work while trying to get an opportunity to int=
eract with specific people. =A0 The terminal rooms are generally placed in =
out-of-the-way corners, but the most effective places to interact with peop=
le are in the hallways.</div>
<span class=3D"HOEnZb"><font color=3D"#888888"><div><br></div><div><br></di=
v><div>Keith</div><div><br></div></font></span></div></blockquote></div><br=
></div></div>

--e89a8ff1ca780d3c7f04e2cd5658--

From abdussalambaryun@gmail.com  Wed Jul 31 04:52:41 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 927A311E8109 for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 04:52:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.562
X-Spam-Level: 
X-Spam-Status: No, score=-2.562 tagged_above=-999 required=5 tests=[AWL=0.037,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rmFcfi319l2I for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 04:52:40 -0700 (PDT)
Received: from mail-pb0-x234.google.com (mail-pb0-x234.google.com [IPv6:2607:f8b0:400e:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id 53E7C11E80F0 for <ietf@ietf.org>; Wed, 31 Jul 2013 04:52:40 -0700 (PDT)
Received: by mail-pb0-f52.google.com with SMTP id wz12so677100pbc.25 for <ietf@ietf.org>; Wed, 31 Jul 2013 04:52:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=by+dl5dddJbDQUHUngyZV6nmVS13k9uiCuqm+CgcHkE=; b=zeq5JSK2yBx7bbOsnlHCsdq9EI93pG5GxEupEaLziUrY+nl78jziskSi4hSNXsjOFt wmj2f2eP0dG5yOLG6D0PSDBPUlHfLQOlmAxT8rebotgkVf81ORoWJ2FPYqvedYSY0zF6 2IzA4LdKZWGm7hlRAPrKjKdBsPDJleXVw8/y1SSMHFsHbGsXsftOMrYppRppfY7EXBIs drGYtS5E8JLvCQMbZTJEPPj2XMBwOrKUWXrPRlOBD3RzUN1pt/8aduJKGQwE3Bdxifpw 6IDi0jFk3qkUAYWzQqUqt5f+zPx3gf7HW9JEIOu1Xn1/XRWJNwamQZ/t5fbW//7ruKRZ NE9g==
MIME-Version: 1.0
X-Received: by 10.68.175.33 with SMTP id bx1mr7584629pbc.21.1375271559926; Wed, 31 Jul 2013 04:52:39 -0700 (PDT)
Received: by 10.68.250.133 with HTTP; Wed, 31 Jul 2013 04:52:39 -0700 (PDT)
In-Reply-To: <2CC6EA8D-7FCF-4536-97A5-E056FD4F4B6A@network-heretics.com>
References: <20130730163502.455E918C10F@mercury.lcs.mit.edu> <51F7FC29.2000407@isi.edu> <2CC6EA8D-7FCF-4536-97A5-E056FD4F4B6A@network-heretics.com>
Date: Wed, 31 Jul 2013 12:52:39 +0100
Message-ID: <CADnDZ8-EVPQqBfJyJ1sD2VLciB0-eFe9LuQL1MGJOKiC+ZJh3w@mail.gmail.com>
Subject: Re: making our meetings more worth the time/expense (was: Re: setting a goal for an inclusive IETF)
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Keith Moore <moore@network-heretics.com>
Content-Type: multipart/alternative; boundary=047d7bd6b2aecc998104e2cd5c0e
Cc: Robert Braden <braden@isi.edu>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Jul 2013 11:52:42 -0000

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

IMHO, The presenters are MUST, but the time channel for presenting is the
problem or boring factor. I mentioned before that we need short
presentations 5 minutes, and more discussions.

AB


On Tue, Jul 30, 2013 at 9:30 PM, Keith Moore <moore@network-heretics.com>wrote:

>
> On Jul 30, 2013, at 7:47 PM, Bob Braden wrote:
>
> > On 7/30/2013 9:35 AM, Noel Chiappa wrote:
> >>
> >> Easy fix: 'slide' (well, nobody uses real slides anymore :-) rationing.
> >>
> >> E.g. if a presenter has a 10 minute slot, maximum of 3 'slides'
> >> (approximately; maybe less). That will force the slides to be
> 'discussion
> >> frameworks', rather than 'detailed overview of the design'.
> >>
> >>      Noel
> >
> > Noel,
> >
> > I tried the 3 slide limit in the End2end Research Group some years ago,
> and it did not work very well.
> > Presenters just can't discipline themselves that much, no matter how
> hard you beat on them.
>
> Maybe the first step is to stop having "presenters".
>
> Keith
>
>

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

<div dir=3D"ltr"><div>IMHO, The presenters are MUST, but the time channel f=
or presenting is the problem or boring factor. I mentioned before that we n=
eed short presentations 5 minutes, and more discussions.</div><div>=A0</div=
>
<div>AB</div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_q=
uote">On Tue, Jul 30, 2013 at 9:30 PM, Keith Moore <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:moore@network-heretics.com" target=3D"_blank">moore@network=
-heretics.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"HOEnZb"><div class=3D"h5"><br>
On Jul 30, 2013, at 7:47 PM, Bob Braden wrote:<br>
<br>
&gt; On 7/30/2013 9:35 AM, Noel Chiappa wrote:<br>
&gt;&gt;<br>
&gt;&gt; Easy fix: &#39;slide&#39; (well, nobody uses real slides anymore :=
-) rationing.<br>
&gt;&gt;<br>
&gt;&gt; E.g. if a presenter has a 10 minute slot, maximum of 3 &#39;slides=
&#39;<br>
&gt;&gt; (approximately; maybe less). That will force the slides to be &#39=
;discussion<br>
&gt;&gt; frameworks&#39;, rather than &#39;detailed overview of the design&=
#39;.<br>
&gt;&gt;<br>
&gt;&gt; =A0 =A0 =A0Noel<br>
&gt;<br>
&gt; Noel,<br>
&gt;<br>
&gt; I tried the 3 slide limit in the End2end Research Group some years ago=
, and it did not work very well.<br>
&gt; Presenters just can&#39;t discipline themselves that much, no matter h=
ow hard you beat on them.<br>
<br>
</div></div>Maybe the first step is to stop having &quot;presenters&quot;.<=
br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Keith<br>
<br>
</font></span></blockquote></div><br></div>

--047d7bd6b2aecc998104e2cd5c0e--

From abdussalambaryun@gmail.com  Wed Jul 31 04:59:56 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D131E21E8134 for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 04:59:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.266
X-Spam-Level: 
X-Spam-Status: No, score=-2.266 tagged_above=-999 required=5 tests=[AWL=-0.267, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_12=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 53r0zGxfXWzi for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 04:59:54 -0700 (PDT)
Received: from mail-pb0-x232.google.com (mail-pb0-x232.google.com [IPv6:2607:f8b0:400e:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id CCE9521E80FF for <ietf@ietf.org>; Wed, 31 Jul 2013 04:59:44 -0700 (PDT)
Received: by mail-pb0-f50.google.com with SMTP id uo5so689003pbc.37 for <ietf@ietf.org>; Wed, 31 Jul 2013 04:59:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=1czl25zk5lodGT1Ge5MVCZczusejesAtI5Z9/bzWKws=; b=bgaowLElJ+CUmupiLt0XIUSphJEwiHLfRknQh5OIXtLlaaSpf32zrK/ErDg5RQHjqM BrjeGliAbTLvfjl+KhOLpYDt685FsqV8xyazUa8/3MQil8k3FM89kJizs4NCA9V84rTx GBtPDypNug/K+60AWYj9i+XdTkgIP9kixKjjoZOw/4ozYPWFLOjb69FEY9NltHQpwM64 ApK4gpgAhkBUbGMx1/1hVS0yfuZIDroWNjNr/mWbr2dVAChvTF/5KBc1wGrraW9z3n4t P6O+FIq2oY3Myxl/QHQH8hvOWncwWDMKThkYC3jIsN+U7TPD/MFaLz5FVQ7w7NjffbSl cH2g==
MIME-Version: 1.0
X-Received: by 10.66.189.225 with SMTP id gl1mr80989040pac.22.1375271984457; Wed, 31 Jul 2013 04:59:44 -0700 (PDT)
Received: by 10.68.250.133 with HTTP; Wed, 31 Jul 2013 04:59:44 -0700 (PDT)
In-Reply-To: <CAF4+nEHS0fH8+ewhiWXoYwUfAa27wfrXDR8fZLYid-Z-mc7ZSw@mail.gmail.com>
References: <EDC539D2-48CE-44D7-A06C-19EEAE42D31C@piuha.net> <BF2DD745-99D0-420E-B199-7C8F94981BDA@network-heretics.com> <20840.1375200653@sandelman.ca> <CAF4+nEHS0fH8+ewhiWXoYwUfAa27wfrXDR8fZLYid-Z-mc7ZSw@mail.gmail.com>
Date: Wed, 31 Jul 2013 12:59:44 +0100
Message-ID: <CADnDZ88Vmm=VOU+Nf_v90StKpbFDxriPbrgVxOPkApgh2Pzrxw@mail.gmail.com>
Subject: Re: making our meetings more worth the time/expense (was: Re: setting a goal for an inclusive IETF)
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Content-Type: multipart/alternative; boundary=047d7bdc17701a6be804e2cd76f0
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Jul 2013 11:59:57 -0000

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

I think *side meetings* are killing IETF, I call it *hidden meetings*,
there is no input for IETF when we have side meetings. The input to IETF in
through meeting sessions and discussion lists. So I agree with Keith that
meeting sessions have low discussions, and may discourage remote
participants to discuss as well.

I think why you feel that side meetings are valuable, is because it has
short presenting, each person talks for less than 5 minutes and discussion
time is interesting. So you and Keith seem to be having same aim to exclude
long presentations of issues. Furthermore, I will add that we need not to
only ask questions and discuss with the authors/presenters, we should be
discussing to the IETF WG with the meeting. This way the habit will be not
boring and ALL will be attracted.

AB


On Wed, Jul 31, 2013 at 9:30 AM, Donald Eastlake <d3e3e3@gmail.com> wrote:

> The most valuable part of IETF meeting is and has always been the hall
> conversations and side meetings
>
> Thanks,
> Donald
> =============================
>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>  155 Beaver Street, Milford, MA 01757 USA
>  d3e3e3@gmail.com
>
> On Tue, Jul 30, 2013 at 12:10 PM, Michael Richardson
> <mcr+ietf@sandelman.ca> wrote:
> >
> > Keith Moore <moore@network-heretics.com> wrote:
> >     > But earlier today I realized that the problem isn't just the cost
> of attending
> >     > meetings - it's the value that we get in return for those
> meetings.   I've been
> >     > taking notes about how ineffectively we use our meeting time.
> Most of what
> >     > I've observed won't surprise anybody, but here's a summary:
> >
> > Thanks for this.
> >
> >     > Rooms are set up not to facilitate discussion, but to discourage
> it.   The
> >     > lights are dim, the chairs are facing forward rather than other
> participants,
> >     > the projector screen (not the person facilitating a discussion,
> even if someone
> >     > is trying to facilitate a discussion) is the center of attention.
>    The chairs
> >     > are set so close together and with so few aisles that it's hard
> for most of the
> >     > attendees to get to the mics.   The "microphone discipline" which
> was intended
> >     > to facilitate remote participation ends up making discussion more
> difficult for
> >     > everybody who has paid to be on site.
> >
> > I think that these physical things are something that we can do some
> > experiments about.
> >
> >     > Well, please excuse my candor, but f*ck habit.   We can't be
> effective
> >     > engineers if we let bad habits continue to dictate how we work.
> >
> > I agree.
> >
> >     > For 80% of most WG meetings, the lights should be bright, the
> participants
> >     > should face each other.   If there's a person facilitating the
> discussion that
> >     > person should be the center of attention.    If we're going to use
> microphones,
> >     > the rooms should be set up to allow everyone in the room to have
> easy access to
> >     > them.   We should have several microphones, again facing each
> other, so that
> >     > several people can have a conversation without everyone having to
> queue up.
> >
> > Can we please try this in Vancouver?
> > This would work especially well for BOFs.
> > Maybe we can start there.
> > Chairs will need training as *facilitators*
> >
> >     > And maybe, in addition, we need to provide better places for
> people to hang out
> >     > and work while trying to get an opportunity to interact with
> specific people.
> >     > The terminal rooms are generally placed in out-of-the-way corners,
> but the most
> >     > effective places to interact with people are in the hallways.
> >
> > I agree.
> >
> > --
> > ]               Never tell me the odds!                 | ipv6 mesh
> networks [
> > ]   Michael Richardson, Sandelman Software Works        | network
> architect  [
> > ]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on
> rails    [
> >
> >
> >
> >
> > --
> > Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
> >
> >
>

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

<div dir=3D"ltr"><div>I think *side meetings* are killing IETF, I call it *=
hidden meetings*, there is no input for IETF when we have side meetings. Th=
e input to IETF in through meeting sessions and discussion lists. So I agre=
e with Keith that meeting sessions have low discussions, and may discourage=
 remote participants to discuss as well. </div>
<div>=A0</div><div>I think why you feel that side meetings are valuable, is=
 because it has short presenting, each person talks for less than 5 minutes=
 and discussion time is interesting. So you and Keith seem to be having sam=
e aim to exclude long presentations of issues. Furthermore, I will add that=
 we need not to only ask questions and discuss with the authors/presenters,=
 we should be discussing to the IETF WG with the meeting. This way the habi=
t will be not boring and ALL will be attracted.</div>
<div>=A0</div><div>AB</div></div><div class=3D"gmail_extra"><br><br><div cl=
ass=3D"gmail_quote">On Wed, Jul 31, 2013 at 9:30 AM, Donald Eastlake <span =
dir=3D"ltr">&lt;<a href=3D"mailto:d3e3e3@gmail.com" target=3D"_blank">d3e3e=
3@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 most valuable part of IETF meeting is an=
d has always been the hall<br>
conversations and side meetings<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>
On Tue, Jul 30, 2013 at 12:10 PM, Michael Richardson<br>
&lt;<a href=3D"mailto:mcr%2Bietf@sandelman.ca">mcr+ietf@sandelman.ca</a>&gt=
; wrote:<br>
&gt;<br>
&gt; Keith Moore &lt;<a href=3D"mailto:moore@network-heretics.com">moore@ne=
twork-heretics.com</a>&gt; wrote:<br>
&gt; =A0 =A0 &gt; But earlier today I realized that the problem isn&#39;t j=
ust the cost of attending<br>
&gt; =A0 =A0 &gt; meetings - it&#39;s the value that we get in return for t=
hose meetings. =A0 I&#39;ve been<br>
&gt; =A0 =A0 &gt; taking notes about how ineffectively we use our meeting t=
ime. =A0 Most of what<br>
&gt; =A0 =A0 &gt; I&#39;ve observed won&#39;t surprise anybody, but here&#3=
9;s a summary:<br>
&gt;<br>
&gt; Thanks for this.<br>
&gt;<br>
&gt; =A0 =A0 &gt; Rooms are set up not to facilitate discussion, but to dis=
courage it. =A0 The<br>
&gt; =A0 =A0 &gt; lights are dim, the chairs are facing forward rather than=
 other participants,<br>
&gt; =A0 =A0 &gt; the projector screen (not the person facilitating a discu=
ssion, even if someone<br>
&gt; =A0 =A0 &gt; is trying to facilitate a discussion) is the center of at=
tention. =A0 =A0The chairs<br>
&gt; =A0 =A0 &gt; are set so close together and with so few aisles that it&=
#39;s hard for most of the<br>
&gt; =A0 =A0 &gt; attendees to get to the mics. =A0 The &quot;microphone di=
scipline&quot; which was intended<br>
&gt; =A0 =A0 &gt; to facilitate remote participation ends up making discuss=
ion more difficult for<br>
&gt; =A0 =A0 &gt; everybody who has paid to be on site.<br>
&gt;<br>
&gt; I think that these physical things are something that we can do some<b=
r>
&gt; experiments about.<br>
&gt;<br>
&gt; =A0 =A0 &gt; Well, please excuse my candor, but f*ck habit. =A0 We can=
&#39;t be effective<br>
&gt; =A0 =A0 &gt; engineers if we let bad habits continue to dictate how we=
 work.<br>
&gt;<br>
&gt; I agree.<br>
&gt;<br>
&gt; =A0 =A0 &gt; For 80% of most WG meetings, the lights should be bright,=
 the participants<br>
&gt; =A0 =A0 &gt; should face each other. =A0 If there&#39;s a person facil=
itating the discussion that<br>
&gt; =A0 =A0 &gt; person should be the center of attention. =A0 =A0If we&#3=
9;re going to use microphones,<br>
&gt; =A0 =A0 &gt; the rooms should be set up to allow everyone in the room =
to have easy access to<br>
&gt; =A0 =A0 &gt; them. =A0 We should have several microphones, again facin=
g each other, so that<br>
&gt; =A0 =A0 &gt; several people can have a conversation without everyone h=
aving to queue up.<br>
&gt;<br>
&gt; Can we please try this in Vancouver?<br>
&gt; This would work especially well for BOFs.<br>
&gt; Maybe we can start there.<br>
&gt; Chairs will need training as *facilitators*<br>
&gt;<br>
&gt; =A0 =A0 &gt; And maybe, in addition, we need to provide better places =
for people to hang out<br>
&gt; =A0 =A0 &gt; and work while trying to get an opportunity to interact w=
ith specific people.<br>
&gt; =A0 =A0 &gt; The terminal rooms are generally placed in out-of-the-way=
 corners, but the most<br>
&gt; =A0 =A0 &gt; effective places to interact with people are in the hallw=
ays.<br>
&gt;<br>
&gt; I agree.<br>
&gt;<br>
&gt; --<br>
&gt; ] =A0 =A0 =A0 =A0 =A0 =A0 =A0 Never tell me the odds! =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 | ipv6 mesh networks [<br>
&gt; ] =A0 Michael Richardson, Sandelman Software Works =A0 =A0 =A0 =A0| ne=
twork architect =A0[<br>
&gt; ] =A0 =A0 <a href=3D"mailto:mcr@sandelman.ca">mcr@sandelman.ca</a> =A0=
<a href=3D"http://www.sandelman.ca/" target=3D"_blank">http://www.sandelman=
.ca/</a> =A0 =A0 =A0 =A0| =A0 ruby on rails =A0 =A0[<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; --<br>
&gt; Michael Richardson &lt;<a href=3D"mailto:mcr%2BIETF@sandelman.ca">mcr+=
IETF@sandelman.ca</a>&gt;, Sandelman Software Works<br>
&gt;<br>
&gt;<br>
</div></div></blockquote></div><br></div>

--047d7bdc17701a6be804e2cd76f0--

From abdussalambaryun@gmail.com  Wed Jul 31 05:19:05 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F91721F9CDF for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 05:19:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.539
X-Spam-Level: 
X-Spam-Status: No, score=-2.539 tagged_above=-999 required=5 tests=[AWL=0.060,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DSMF5K3dumqP for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 05:19:04 -0700 (PDT)
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 4F34521F9D4F for <ietf@ietf.org>; Wed, 31 Jul 2013 05:18:59 -0700 (PDT)
Received: by mail-pd0-f171.google.com with SMTP id bv13so486348pdb.30 for <ietf@ietf.org>; Wed, 31 Jul 2013 05:18:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ValSDzguiGjtn7o8KTh1ICT/0mXojtodC+eUfBwFSe4=; b=ywCwmv9fi/9y97AqnZDiO5HQujAarANAw5xjP4VE6rorcwUAXe+Qw6WGvpIdoQ88QG r57t5LSjJl9baJJJg5QxkuFsISF4TxIh6NZxukjlNgrZyPmLh6Dhh3p5pkIkcwcpvdRL L5qQGylu4rw2b/eQfc6VzbPa9gzKjZxr5ciM2MAZtp44B1oxLpvdNmVzJyrrZ17omQZ1 FC8dcGKa/HdmBhNzaR2aluexeRpb3+8HQ0RK42W4E33SNIaN3sRA1Q5sk3o09kHdn6Xa PCztir/GSakrUJwhhPsS2HTxiLFEIIRovphmSDDTrQj2AXraHvHbwTscItrTL5TTkF0/ m2ag==
MIME-Version: 1.0
X-Received: by 10.66.160.3 with SMTP id xg3mr50994907pab.28.1375273138500; Wed, 31 Jul 2013 05:18:58 -0700 (PDT)
Received: by 10.68.250.133 with HTTP; Wed, 31 Jul 2013 05:18:58 -0700 (PDT)
In-Reply-To: <20130731022327.GA53174@mx1.yitter.info>
References: <20130730163502.455E918C10F@mercury.lcs.mit.edu> <51F7FC29.2000407@isi.edu> <51F82442.4000404@gmail.com> <20130731022327.GA53174@mx1.yitter.info>
Date: Wed, 31 Jul 2013 13:18:58 +0100
Message-ID: <CADnDZ88cSa8xgFxh0k9H0j64LOH5ffw8oAmQ6_XSUedhqXwScA@mail.gmail.com>
Subject: Re: making our meetings more worth the time/expense
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Content-Type: multipart/alternative; boundary=047d7b6d967ae3bbc104e2cdba7a
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Jul 2013 12:19:05 -0000

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

comments below


On Wed, Jul 31, 2013 at 3:23 AM, Andrew Sullivan <ajs@anvilwalrusden.com>wrote:

> On Wed, Jul 31, 2013 at 08:38:26AM +1200, Brian E Carpenter wrote:
> >
> > It's been pointed out before that in a group with very diverse languages,
> > written words are usually better understood than speech. It's a fact of
> life
> > that you can't have a full-speed cut-and-thrust discussion in a group
> > of 100 people, half of whom are speaking a foreign language. Sitting in
> > a circle does not fix this.
>
> While that is true, I think it misses the point of the objections to
> the sit-and-watch-PowerPointTV.
>
> First, I observe that we already _have_ a great deal of written words:
> the drafts.  I continue to believe that altogether too much time in WG
> meetings is spent "introducing", "presenting", or otherwise showing
> off ideas in an existing draft to participants in the WG.  I
> acknowledge that (particularly in early stages of WG life, in topics
> with a lot of different work, and in cross-WG presentations) these
> "intro" presentations are a fact of life.  But I think we are
> extremely bad at holding the reigns on them.
>

The presenter SHOULD focus on taking WG feedback by asking WG Questions
like : do you think explaining in a section XXX will be good? then the WG
hummms,

>
> In a WG meeting, I think such "intro" presentations about drafts
> really can be kept to three pieces of information: the name of the
> draft, a slogan describing the problem it is supposed to solve, and a
> pointer to the beginning(s) of discussion thread(s) on the draft.  If
> the person promoting the draft can't give the elevator pitch, they
> don't know their own draft well enough to summarize it and shouldn't
> be presenting it.  Any additional discussion in the presentation ought
> to be exploring, as much as possible, one or more of the following
> topics:
>
>     - a particular issue
>     - is $issue a real problem
>     - alternatives for solving $issue
>     - motivation for $issue solution choices
>
> Each such slide, it seems to me, ought to encourage at most a couple
> minutes of exposition and then some discussion.  The _reason_ to get
> together in a big room with other people is to use the high-bandwidth
> opportunity to hash out the extent of a problem.  The back and forth
> of "you forgot this", "no that won't work because it explodes foo",
> and so on, is the value here.
>

Please note that we SHOULD not only blame the presenter/author for this
problem of boring and presentation format, but I also blame the WG
participants, why the don't READ, READ, READ, the DRAFTS under AGENDA. If
they do READ then they can input please take my questions, 1, 2, 3 and
please take my recommendations 1, 2,3, and please take my
requests/comments, 1,2,3.


>
> Notice that none of that includes complicated flow-chart diagrams that
> explain in detail a proposal.  There _is_ a place for those, however:
> an actual presentation that gets made after significant discussion on
> the list has made it clear that nobody understands the proposal.  At
> that point, those 10-15 minute presentations of some proposed
> mechanism are important, if only to inspire commenters to go back to
> the list and say, "Ok, _now_ I get what you were trying to say, and
> your text needs to be improved along the following lines."  But these
> full explanation presentations happen too often when there has not
> been such confusion.
>

I agree with this above point.

>
> Of course, all of the above depends on us going back to the list and
> working out the details there, and it depends on people having read
> the drafts and having a list of questions themselves that have been
> deferred from the list for the face to face discussion.
>

I agree with you,


>
> I believe presentations in meetings are also sometimed useful if they
> are exploring a problem space.  In that case, I believe what one needs
> is _short_ presentations of the sort, "Here's what I think the
> problems are," and then a lot of well-moderated discussion.
>
I agree as if you ment short as less/equal than 5 minutes. The IETF Chair
and WG Chairs SHOULD consider these issues you raised.

>
> Unfortunately, actually running meetings this way is a lot of work,
> requires fairly careful planning, and requires an indifference to
> nasty remarks on the part of presenters who would much rather listen
> to themselves for 20 minutes than to others.  But I think it'd make
> for better meetings.  (Yes, along with room layouts that were more
> suited to getting people to the mic.)
>

I will add that We need with the author/presenter, to know the reviewers of
the draft, and get their short comments, so that will help the WG to decide
when asked for their opinion. So the reviewers are as a supervisor to the
WG, and the WG Chair is arranging their input in the session to make the
meeting valuable.

>
> > The old days are gone.
>
> Yes, and we need to figure out how to use meeting time effectively
> here in the new days.  That effective use does not, I think, involve
> expanding to fill all the time in the year with 20 minute low-content
> presentations summarizing the draft that you can read in the span of
> the time it takes to get through the presentation.  (Perhaps I'm
> wrong.  Perhaps people find that the only time they have now to read
> the drafts is during the presentation of the draft.  I sure hope not.)
>

New draft proposals can be done in the last times of the session, and will
need to be discussed first on the list before presented. However, even
thoes proposals I will think they should be less than 5 minutes, and
discussions for them less than 10. For WG drafts the valuable
discussions SHOULD be more than 10 minutes, otherwise, we maybe done
side/hidden meetings.

AB

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

<div dir=3D"ltr">comments below<div class=3D"gmail_extra"><br><br><div clas=
s=3D"gmail_quote">On Wed, Jul 31, 2013 at 3:23 AM, Andrew Sullivan <span di=
r=3D"ltr">&lt;<a href=3D"mailto:ajs@anvilwalrusden.com" target=3D"_blank">a=
js@anvilwalrusden.com</a>&gt;</span> wrote:<br>
<blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-=
color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class=
=3D"gmail_quote"><div class=3D"im">On Wed, Jul 31, 2013 at 08:38:26AM +1200=
, Brian E Carpenter wrote:<br>

&gt;<br>
&gt; It&#39;s been pointed out before that in a group with very diverse lan=
guages,<br>
&gt; written words are usually better understood than speech. It&#39;s a fa=
ct of life<br>
&gt; that you can&#39;t have a full-speed cut-and-thrust discussion in a gr=
oup<br>
&gt; of 100 people, half of whom are speaking a foreign language. Sitting i=
n<br>
&gt; a circle does not fix this.<br>
<br>
</div>While that is true, I think it misses the point of the objections to<=
br>
the sit-and-watch-PowerPointTV.<br>
<br>
First, I observe that we already _have_ a great deal of written words:<br>
the drafts. =A0I continue to believe that altogether too much time in WG<br=
>
meetings is spent &quot;introducing&quot;, &quot;presenting&quot;, or other=
wise showing<br>
off ideas in an existing draft to participants in the WG. =A0I<br>
acknowledge that (particularly in early stages of WG life, in topics<br>
with a lot of different work, and in cross-WG presentations) these<br>
&quot;intro&quot; presentations are a fact of life. =A0But I think we are<b=
r>
extremely bad at holding the reigns on them.<br></blockquote><div>=A0</div>=
<div>The presenter SHOULD focus on taking WG feedback by asking WG Question=
s like : do you think explaining in a section XXX will be good? then the WG=
 hummms,=A0</div>
<blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-=
color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class=
=3D"gmail_quote">
<br>
In a WG meeting, I think such &quot;intro&quot; presentations about drafts<=
br>
really can be kept to three pieces of information: the name of the<br>
draft, a slogan describing the problem it is supposed to solve, and a<br>
pointer to the beginning(s) of discussion thread(s) on the draft. =A0If<br>
the person promoting the draft can&#39;t give the elevator pitch, they<br>
don&#39;t know their own draft well enough to summarize it and shouldn&#39;=
t<br>
be presenting it. =A0Any additional discussion in the presentation ought<br=
>
to be exploring, as much as possible, one or more of the following<br>
topics:<br>
<br>
=A0 =A0 - a particular issue<br>
=A0 =A0 - is $issue a real problem<br>
=A0 =A0 - alternatives for solving $issue<br>
=A0 =A0 - motivation for $issue solution choices<br>
<br>
Each such slide, it seems to me, ought to encourage at most a couple<br>
minutes of exposition and then some discussion. =A0The _reason_ to get<br>
together in a big room with other people is to use the high-bandwidth<br>
opportunity to hash out the extent of a problem. =A0The back and forth<br>
of &quot;you forgot this&quot;, &quot;no that won&#39;t work because it exp=
lodes foo&quot;,<br>
and so on, is the value here.<br></blockquote><div>=A0</div><div>Please not=
e that we=A0SHOULD not only blame the presenter/author for this problem of =
boring and presentation format, but I also blame the WG participants, why t=
he don&#39;t=A0READ, READ, READ, the DRAFTS under AGENDA. If they do READ t=
hen they can input please take my questions, 1, 2, 3 and please take my rec=
ommendations 1, 2,3, and please take my requests/comments, 1,2,3.</div>
<div>=A0</div><blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-left:1e=
x;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-styl=
e:solid" class=3D"gmail_quote">
<br>
Notice that none of that includes complicated flow-chart diagrams that<br>
explain in detail a proposal. =A0There _is_ a place for those, however:<br>
an actual presentation that gets made after significant discussion on<br>
the list has made it clear that nobody understands the proposal. =A0At<br>
that point, those 10-15 minute presentations of some proposed<br>
mechanism are important, if only to inspire commenters to go back to<br>
the list and say, &quot;Ok, _now_ I get what you were trying to say, and<br=
>
your text needs to be improved along the following lines.&quot; =A0But thes=
e<br>
full explanation presentations happen too often when there has not<br>
been such confusion.<br></blockquote><div>=A0</div><div>I agree with this a=
bove point.=A0</div><blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-l=
eft:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-lef=
t-style:solid" class=3D"gmail_quote">

<br>
Of course, all of the above depends on us going back to the list and<br>
working out the details there, and it depends on people having read<br>
the drafts and having a list of questions themselves that have been<br>
deferred from the list for the face to face discussion.<br></blockquote><di=
v>=A0</div><div>I agree with you,</div><div>=A0</div><blockquote style=3D"m=
argin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204)=
;border-left-width:1px;border-left-style:solid" class=3D"gmail_quote">

<br>
I believe presentations in meetings are also sometimed useful if they<br>
are exploring a problem space. =A0In that case, I believe what one needs<br=
>
is _short_ presentations of the sort, &quot;Here&#39;s what I think the<br>
problems are,&quot; and then a lot of well-moderated discussion.<br></block=
quote><div>I agree as if you ment short as less/equal than 5 minutes.=A0The=
 IETF Chair and WG Chairs=A0SHOULD consider these issues you raised.</div>
<blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-=
color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class=
=3D"gmail_quote">
<br>
Unfortunately, actually running meetings this way is a lot of work,<br>
requires fairly careful planning, and requires an indifference to<br>
nasty remarks on the part of presenters who would much rather listen<br>
to themselves for 20 minutes than to others. =A0But I think it&#39;d make<b=
r>
for better meetings. =A0(Yes, along with room layouts that were more<br>
suited to getting people to the mic.)<br></blockquote><div>=A0</div><div>I =
will add that We need with the author/presenter, to know the reviewers of t=
he draft, and get their short comments, so that will help the WG to decide =
when asked for their opinion. So the reviewers are as a supervisor to the W=
G, and the WG=A0Chair is arranging their input in the session to make the m=
eeting valuable.=A0</div>
<blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-=
color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class=
=3D"gmail_quote">
<div class=3D"im"><br>
&gt; The old days are gone.<br>
<br>
</div>Yes, and we need to figure out how to use meeting time effectively<br=
>
here in the new days. =A0That effective use does not, I think, involve<br>
expanding to fill all the time in the year with 20 minute low-content<br>
presentations summarizing the draft that you can read in the span of<br>
the time it takes to get through the presentation. =A0(Perhaps I&#39;m<br>
wrong. =A0Perhaps people find that the only time they have now to read<br>
the drafts is during the presentation of the draft. =A0I sure hope not.)<br=
></blockquote><div>=A0</div><div>New draft proposals can be done in the las=
t times of the session, and will need to be discussed first on the list bef=
ore presented. However, even thoes proposals I will think they should be le=
ss than 5 minutes, and discussions for them less than 10. For=A0WG drafts t=
he valuable discussions=A0SHOULD be more than 10 minutes, otherwise, we may=
be done side/hidden meetings.</div>
<div>=A0</div><div>AB</div></div></div></div>

--047d7b6d967ae3bbc104e2cdba7a--

From abdussalambaryun@gmail.com  Wed Jul 31 05:45:32 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54C1921F9F4F; Wed, 31 Jul 2013 05:45:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.545
X-Spam-Level: 
X-Spam-Status: No, score=-2.545 tagged_above=-999 required=5 tests=[AWL=0.054,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nZe4cPpDwFGr; Wed, 31 Jul 2013 05:45:31 -0700 (PDT)
Received: from mail-pd0-x230.google.com (mail-pd0-x230.google.com [IPv6:2607:f8b0:400e:c02::230]) by ietfa.amsl.com (Postfix) with ESMTP id 6C42921F9F21; Wed, 31 Jul 2013 05:45:31 -0700 (PDT)
Received: by mail-pd0-f176.google.com with SMTP id q10so709312pdj.35 for <multiple recipients>; Wed, 31 Jul 2013 05:45:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=eclRGXxlNvs2X1vEBKzdccd2/lGsfQ+99ww9C7v3JR0=; b=ZIbsUcgqUHGUKaRWd2vJQ2/W3DbPAO2mT0cJ4MWw0avVwIaZSy529/UIH7FftYoUXy zi5YuVVdOm2FyYRI998jihOkAXp/SoOu9lunWD+1G1DJoc3WDACcXC2wMYC5X7h21erh 5Kl8ezYN+K46CItJAzgAl0rGTfxqmR0wdZC2kS4B3pUtMBdHQezXKSORe8dDFHhpN/em 5v300mz7FWJWZRvvLiaB2JmtoAdABRF6nQcoa6IEjbnG2HAion2EsCPTtJ60OrIxwT5w itnRfhwCFc+ipffocfYhCAZGOUT7fC4iY5ZqIQcCd9hgPfkn6q+ogaDROwZXY45KPjFp Gcwg==
MIME-Version: 1.0
X-Received: by 10.68.130.163 with SMTP id of3mr40066027pbb.181.1375274731047;  Wed, 31 Jul 2013 05:45:31 -0700 (PDT)
Received: by 10.68.250.133 with HTTP; Wed, 31 Jul 2013 05:45:31 -0700 (PDT)
Date: Wed, 31 Jul 2013 13:45:31 +0100
Message-ID: <CADnDZ8-mqRsPyurtg9z9S=VHZmEKAoW+x46rKrS4m_VNiqDEfA@mail.gmail.com>
Subject: Re: setting a goal for an inclusive IETF
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Jari Arkko <jari.arkko@piuha.net>
Content-Type: multipart/alternative; boundary=047d7b15a7f3d0121e04e2ce1977
Cc: "diversity@ietf.org" <diversity@ietf.org>, Pete Resnick <presnick@qti.qualcomm.com>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Jul 2013 12:45:32 -0000

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

Hi Jari,

I have gave many feedback on the diversity issue, and I thank you for the
article, I agree with iot totally. I will repeat my comment, that the
design team of diversity SHOULD make clear what is its goals and
milestones, therefore, we can give better feedback, but leaving that hidden
to management, then only the special people listed in your article, I would
prefer that the design team are selected by diversity parameters ( gender,
region, age, necomer-oldcomer, etc). Thanks again,

AB


On Tue, Jul 30, 2013 at 2:53 PM, Jari Arkko <jari.arkko@piuha.net> wrote:

> We have discussed diversity at the IETF at length. Yesterday, Pete Resnick
> and I wrote an article about what we think the goal for the IETF should be,
> as well as listing some of the early activities that we have taken at the
> IETF. Our goal is making the IETF more inclusive for everyone who needs to
> be working on Internet standards. We are at the beginning, however, and a
> lot of work remains ahead. Here's the article:
>
> http://www.ietf.org/blog/2013/07/a-diverse-ietf/
>
> Also, I wanted to let everyone know that tomorrow in the Administrative
> Plenary, Kathleen Moriarty and Suresh Krishnan will be talking about what
> they have uncovered so far in their efforts in the diversity design team.
> I'm looking very much forward to their report. Their efforts will help us
> understand where we have room to improve - often by much :-) - and what
> kinds of actions we can take to improve our inclusiveness.
>
> Jari
>
>

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

<div dir=3D"ltr"><div>Hi Jari,</div><div>=A0</div><div>I have gave many fee=
dback on the diversity issue, and I thank you for the article, I agree with=
 iot totally. I will repeat my comment, that the design team of diversity S=
HOULD make clear what is its goals and milestones, therefore, we can give b=
etter feedback, but leaving that hidden to management, then only the specia=
l people listed in your article, I would prefer that the design team are se=
lected by diversity parameters ( gender, region, age, necomer-oldcomer, etc=
). Thanks again,</div>
<div>=A0</div><div>AB</div><div class=3D"gmail_extra"><br><br><div class=3D=
"gmail_quote">On Tue, Jul 30, 2013 at 2:53 PM, Jari Arkko <span dir=3D"ltr"=
>&lt;<a href=3D"mailto:jari.arkko@piuha.net" target=3D"_blank">jari.arkko@p=
iuha.net</a>&gt;</span> wrote:<br>
<blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-=
color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class=
=3D"gmail_quote">We have discussed diversity at the IETF at length. Yesterd=
ay, Pete Resnick and I wrote an article about what we think the goal for th=
e IETF should be, as well as listing some of the early activities that we h=
ave taken at the IETF. Our goal is making the IETF more inclusive for every=
one who needs to be working on Internet standards. We are at the beginning,=
 however, and a lot of work remains ahead. Here&#39;s the article:<br>

<br>
<a href=3D"http://www.ietf.org/blog/2013/07/a-diverse-ietf/" target=3D"_bla=
nk">http://www.ietf.org/blog/2013/07/a-diverse-ietf/</a><br>
<br>
Also, I wanted to let everyone know that tomorrow in the Administrative Ple=
nary, Kathleen Moriarty and Suresh Krishnan will be talking about what they=
 have uncovered so far in their efforts in the diversity design team. I&#39=
;m looking very much forward to their report. Their efforts will help us un=
derstand where we have room to improve - often by much :-) - and what kinds=
 of actions we can take to improve our inclusiveness.<br>

<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Jari<br>
<br>
</font></span></blockquote></div><br></div></div>

--047d7b15a7f3d0121e04e2ce1977--

From moore@network-heretics.com  Wed Jul 31 05:48:41 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11F6821F9EE9 for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 05:48:41 -0700 (PDT)
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=[AWL=-0.233, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XwZZkScYPnnP for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 05:48:36 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id C798021F9C6B for <ietf@ietf.org>; Wed, 31 Jul 2013 05:48:35 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 0BA3721426; Wed, 31 Jul 2013 08:48:35 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute4.internal (MEProxy); Wed, 31 Jul 2013 08:48:35 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=references:in-reply-to:mime-version :content-transfer-encoding:content-type:message-id:cc:from :subject:date:to; s=smtpout; bh=1A2xH9BMSiv5Imaw1FMVx85/4zQ=; b= StX2lhnsPh0SowT/hCiE0pXCtoKv64IYhkj7i4BdcZqJ+YPa5EHYv700ohn8QuyR 4IT9WHjqK+vZ6sMy+kvnVIHsYWyRLlalxHvdyQuMosC/t/Qg6OaNVsyxnzGQPbkd ScSZzJUZP1rCT1RnUhRltimLa4qlmz6T4PeiuI/+GLw=
X-Sasl-enc: KrMWALn6VLJNEpSiwx6hCM4cDmX5HLqHSINDDuC/St0N 1375274914
Received: from [130.129.64.231] (unknown [130.129.64.231]) by mail.messagingengine.com (Postfix) with ESMTPA id A9B61C00E85; Wed, 31 Jul 2013 08:48:34 -0400 (EDT)
References: <20130730163502.455E918C10F@mercury.lcs.mit.edu> <51F7FC29.2000407@isi.edu> <2CC6EA8D-7FCF-4536-97A5-E056FD4F4B6A@network-heretics.com> <CADnDZ8-EVPQqBfJyJ1sD2VLciB0-eFe9LuQL1MGJOKiC+ZJh3w@mail.gmail.com>
In-Reply-To: <CADnDZ8-EVPQqBfJyJ1sD2VLciB0-eFe9LuQL1MGJOKiC+ZJh3w@mail.gmail.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: 7bit
Content-Type: multipart/alternative; boundary=Apple-Mail-6817F2B7-6C74-4126-BF4B-B0AAD22AC309
Message-Id: <4D7FB89A-8C81-4744-AADA-A927ADFB95D9@network-heretics.com>
X-Mailer: iPhone Mail (10B329)
From: Keith Moore <moore@network-heretics.com>
Subject: Re: making our meetings more worth the time/expense (was: Re: setting a goal for an inclusive IETF)
Date: Wed, 31 Jul 2013 14:48:34 +0200
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Cc: Robert Braden <braden@isi.edu>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Jul 2013 12:48:41 -0000

--Apple-Mail-6817F2B7-6C74-4126-BF4B-B0AAD22AC309
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

There are occasions when presentations are appropriate, but they should be t=
he exception rather than the rule or default assumption.

Sent from my iPhone

On Jul 31, 2013, at 1:52 PM, Abdussalam Baryun <abdussalambaryun@gmail.com> w=
rote:

> IMHO, The presenters are MUST, but the time channel for presenting is the p=
roblem or boring factor. I mentioned before that we need short presentations=
 5 minutes, and more discussions.
> =20
> AB
>=20
>=20
> On Tue, Jul 30, 2013 at 9:30 PM, Keith Moore <moore@network-heretics.com> w=
rote:
>>=20
>> On Jul 30, 2013, at 7:47 PM, Bob Braden wrote:
>>=20
>> > On 7/30/2013 9:35 AM, Noel Chiappa wrote:
>> >>
>> >> Easy fix: 'slide' (well, nobody uses real slides anymore :-) rationing=
.
>> >>
>> >> E.g. if a presenter has a 10 minute slot, maximum of 3 'slides'
>> >> (approximately; maybe less). That will force the slides to be 'discuss=
ion
>> >> frameworks', rather than 'detailed overview of the design'.
>> >>
>> >>      Noel
>> >
>> > Noel,
>> >
>> > I tried the 3 slide limit in the End2end Research Group some years ago,=
 and it did not work very well.
>> > Presenters just can't discipline themselves that much, no matter how ha=
rd you beat on them.
>>=20
>> Maybe the first step is to stop having "presenters".
>>=20
>> Keith
>=20

--Apple-Mail-6817F2B7-6C74-4126-BF4B-B0AAD22AC309
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: 7bit

<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>There are occasions when presentations are appropriate, but they should be the exception rather than the rule or default assumption.<br><br>Sent from my iPhone</div><div><br>On Jul 31, 2013, at 1:52 PM, Abdussalam Baryun &lt;<a href="mailto:abdussalambaryun@gmail.com">abdussalambaryun@gmail.com</a>&gt; wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr"><div>IMHO, The presenters are MUST, but the time channel for presenting is the problem or boring factor. I mentioned before that we need short presentations 5 minutes, and more discussions.</div><div>&nbsp;</div>
<div>AB</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jul 30, 2013 at 9:30 PM, Keith Moore <span dir="ltr">&lt;<a href="mailto:moore@network-heretics.com" target="_blank">moore@network-heretics.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5"><br>
On Jul 30, 2013, at 7:47 PM, Bob Braden wrote:<br>
<br>
&gt; On 7/30/2013 9:35 AM, Noel Chiappa wrote:<br>
&gt;&gt;<br>
&gt;&gt; Easy fix: 'slide' (well, nobody uses real slides anymore :-) rationing.<br>
&gt;&gt;<br>
&gt;&gt; E.g. if a presenter has a 10 minute slot, maximum of 3 'slides'<br>
&gt;&gt; (approximately; maybe less). That will force the slides to be 'discussion<br>
&gt;&gt; frameworks', rather than 'detailed overview of the design'.<br>
&gt;&gt;<br>
&gt;&gt; &nbsp; &nbsp; &nbsp;Noel<br>
&gt;<br>
&gt; Noel,<br>
&gt;<br>
&gt; I tried the 3 slide limit in the End2end Research Group some years ago, and it did not work very well.<br>
&gt; Presenters just can't discipline themselves that much, no matter how hard you beat on them.<br>
<br>
</div></div>Maybe the first step is to stop having "presenters".<br>
<span class="HOEnZb"><font color="#888888"><br>
Keith<br>
<br>
</font></span></blockquote></div><br></div>
</div></blockquote></body></html>
--Apple-Mail-6817F2B7-6C74-4126-BF4B-B0AAD22AC309--

From arturo.servin@gmail.com  Wed Jul 31 06:36:18 2013
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B668C21F9E73; Wed, 31 Jul 2013 06:36:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SNPbwzQMP-jD; Wed, 31 Jul 2013 06:36:18 -0700 (PDT)
Received: from mail-ve0-x22e.google.com (mail-ve0-x22e.google.com [IPv6:2607:f8b0:400c:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id B86FB21F9F62; Wed, 31 Jul 2013 06:36:17 -0700 (PDT)
Received: by mail-ve0-f174.google.com with SMTP id d10so740454vea.5 for <multiple recipients>; Wed, 31 Jul 2013 06:36:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=Rc2dv9IprZdUSP4XlDl0dN9wib5f73dKMfpDOEjjbic=; b=yY6fL19pzWjkzUZr4mWZ7d0ZR8SEBA7LUd2y9y+k/Gqun7Icfnx1pkinLfVlLlLYKD pP2wGzf5NeuYXPL9tafIePkm+/IGnN7e+LEG5koOPxz3xTeBIndePgtgOl9TKEgvBAys uQ/vTqSFns0CF/5Y48B2j0v20x2fNgN0NwR9V3j7L4TrTbIWNN9pz+d06IyHdT11NVMT kx8yveyYfNnEjoY4VMT2MKvMf/OPleEu5DZawE04uc6/dqw+Fk/D4Bylm8FoJcvQFe8o b1vuzSnn35hoaXrHRNNL8KNpCPCJBm1a9Dhmu0E2FV7VPIQCY1eDGF1BaNqqLf84UPpf lz4Q==
X-Received: by 10.58.80.38 with SMTP id o6mr29036522vex.69.1375277776029; Wed, 31 Jul 2013 06:36:16 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local ([2001:df8:0:16:a982:cfe7:e278:88]) by mx.google.com with ESMTPSA id tu6sm207741vec.2.2013.07.31.06.36.14 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 31 Jul 2013 06:36:15 -0700 (PDT)
Message-ID: <51F912CF.3030203@gmail.com>
Date: Wed, 31 Jul 2013 15:36:15 +0200
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: [Diversity] setting a goal for an inclusive IETF
References: <CADnDZ8-mqRsPyurtg9z9S=VHZmEKAoW+x46rKrS4m_VNiqDEfA@mail.gmail.com>
In-Reply-To: <CADnDZ8-mqRsPyurtg9z9S=VHZmEKAoW+x46rKrS4m_VNiqDEfA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "diversity@ietf.org" <diversity@ietf.org>, Pete Resnick <presnick@qti.qualcomm.com>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Jul 2013 13:36:19 -0000

    AFAIK anyone can participate. You just have to said "I".

Regards,
as

On 7/31/13 2:45 PM, Abdussalam Baryun wrote:
> I would prefer that the design team are selected by diversity
> parameters ( gender, region, age, necomer-oldcomer, etc). Thanks again,


From mcr@sandelman.ca  Wed Jul 31 06:49:28 2013
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFA9D11E8182 for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 06:49:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.493
X-Spam-Level: 
X-Spam-Status: No, score=-2.493 tagged_above=-999 required=5 tests=[AWL=0.106,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ck90bIxgDqFU for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 06:49:24 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id 8024D11E817E for <ietf@ietf.org>; Wed, 31 Jul 2013 06:49:24 -0700 (PDT)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id 1D1F820252; Wed, 31 Jul 2013 10:55:21 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id EB22F63A7C; Wed, 31 Jul 2013 09:47:50 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id C3006636AD; Wed, 31 Jul 2013 09:47:50 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: ietf@ietf.org, iana@iana.org
Subject: stability of iana.org URLs
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Wed, 31 Jul 2013 09:47:50 -0400
Message-ID: <24093.1375278470@sandelman.ca>
Sender: mcr@sandelman.ca
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Jul 2013 13:49:29 -0000

--=-=-=
Content-Transfer-Encoding: quoted-printable


I just followed http://www.iana.org/assignments/enterprise-numbers.html
From=20RFC3315 (DHCPv6)'s reference section.  Ten years later, the URL
doesn't work.

I know that things were reworked when we went to XML based storage, but
I thought that the old URLs would at least have a 301 error on them.

I discovered that dropping the .html gets me the right data at:
  http://www.iana.org/assignments/enterprise-numbers

but I had to walk through the list of protocol numbers to find this.
I feel relatively confident that I found the right list, but other people
looking for registries that are more confusing (ikev1 vs ikev2, etc) might
not wind up at the right place.

=2D-
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works



--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUBUfkVg4qHRg3pndX9AQJI/wP/drNa6v7XwHAqO6X4dkUIz/0XpcbM34dX
Eko3wFlQia2nqs+KkX7s/fhYnnDadtKy7LFRypIdil+Q6krC63CBU/WQGe/Q15q0
t+aKdj+LipKTuJp3srzyt/yc3L5NNh5BK707TvTihrHNv31FeuitFA7fX23gxMVi
CQgkJ6CiQNo=
=ce2E
-----END PGP SIGNATURE-----
--=-=-=--

From ad707@hermes.cam.ac.uk  Wed Jul 31 06:54:41 2013
Return-Path: <ad707@hermes.cam.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EDF321F9FA1; Wed, 31 Jul 2013 06:54:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.054
X-Spam-Level: 
X-Spam-Status: No, score=-2.054 tagged_above=-999 required=5 tests=[AWL=0.545,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nS6tqOdkbeYX; Wed, 31 Jul 2013 06:54:39 -0700 (PDT)
Received: from ppsw-52.csi.cam.ac.uk (ppsw-52.csi.cam.ac.uk [IPv6:2001:630:212:8::e:f52]) by ietfa.amsl.com (Postfix) with ESMTP id 717EE11E8186; Wed, 31 Jul 2013 06:54:39 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-2.csi.cam.ac.uk ([131.111.8.54]:40624) by ppsw-52.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.158]:25) with esmtpa (EXTERNAL:ad707) id 1V4WrO-0000Fo-D2 (Exim 4.80_167-5a66dd3) (return-path <ad707@hermes.cam.ac.uk>); Wed, 31 Jul 2013 14:54:38 +0100
Received: from prayer by hermes-2.csi.cam.ac.uk (hermes.cam.ac.uk) with local (PRAYER:ad707) id 1V4WrN-0005Do-UM (Exim 4.72) (return-path <ad707@hermes.cam.ac.uk>); Wed, 31 Jul 2013 14:54:37 +0100
Received: from [130.129.82.211] by webmail.hermes.cam.ac.uk with HTTP (Prayer-1.3.5); 31 Jul 2013 14:54:37 +0100
Date: 31 Jul 2013 14:54:37 +0100
From: Aaron Yi DING <Aaron.Ding@cl.cam.ac.uk>
To: abdussalambaryun@gmail.com
Subject: Re: [Diversity] setting a goal for an inclusive IETF
Message-ID: <Prayer.1.3.5.1307311454370.10428@hermes-2.csi.cam.ac.uk>
X-Mailer: Prayer v1.3.5
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset=ISO-8859-1
Sender: Aaron Yi DING <ad707@hermes.cam.ac.uk>
Cc: diversity@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Jul 2013 13:54:41 -0000

Hi,

On 31/07/13 14:45, Abdussalam Baryun wrote:
> Hi Jari,
>  
> I have gave many feedback on the diversity issue, and I thank you for 
> the article, I agree with iot totally. I will repeat my comment, that the 
> design team of diversity SHOULD make clear what is its goals and 
> milestones, therefore, we can give better feedback, but leaving that 
> hidden to management, then only the special people listed in your 
> article, I would prefer that the design team are selected by diversity 
> parameters ( gender, region, age, necomer-oldcomer, etc). Thanks again,



The list has been publicly distributed by Design Team Chair. 

It actually saves time if you could just kindly search those names using 
whatever engines and read a bit, before step into quick judgement.

Thanks,
Aaron


PS: parts of Suresh's email to ietf list on 17/06/2013

"
Design team members

===================

Narelle Clark

Dave Crocker

Aaron Yi Ding

Lars Eggert

SM

Monique Morrow

Hugo Salgado

Arturo Servin

Margaret Wasserman

Scott Weeks

"


>  
> AB
>
>
> On Tue, Jul 30, 2013 at 2:53 PM, Jari Arkko <jari.arkko@piuha.net> wrote:
>
>     We have discussed diversity at the IETF at length. Yesterday, Pete 
> Resnick and I wrote an article about what we think the goal for the IETF 
> should be, as well as listing some of the early activities that we have 
> taken at the IETF. Our goal is making the IETF more inclusive for 
> everyone who needs to be working on Internet standards. We are at the 
> beginning, however, and a lot of work remains ahead. Here's the article:
>
>     http://www.ietf.org/blog/2013/07/a-diverse-ietf/
>
>     Also, I wanted to let everyone know that tomorrow in the 
> Administrative Plenary, Kathleen Moriarty and Suresh Krishnan will be 
> talking about what they have uncovered so far in their efforts in the 
> diversity design team. I'm looking very much forward to their report. 
> Their efforts will help us understand where we have room to improve - 
> often by much :-) - and what kinds of actions we can take to improve our 
> inclusiveness.
>
>     Jari
>
> _______________________________________________
> diversity mailing list
> diversity@ietf.org
> https://www.ietf.org/mailman/listinfo/diversity


From barryleiba.mailing.lists@gmail.com  Wed Jul 31 07:00:40 2013
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B392B11E8187 for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 07:00:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.973
X-Spam-Level: 
X-Spam-Status: No, score=-101.973 tagged_above=-999 required=5 tests=[AWL=0.005, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UBX4NJsSndxC for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 07:00:40 -0700 (PDT)
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 2560621F8475 for <ietf@ietf.org>; Wed, 31 Jul 2013 07:00:40 -0700 (PDT)
Received: by mail-ve0-f180.google.com with SMTP id pb11so790681veb.11 for <ietf@ietf.org>; Wed, 31 Jul 2013 07:00:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=vdDhw8kZqjVNf4H++3oM+poaPFIMhyxKPNVKNh5wd9M=; b=1AeHrVqtgKBYIBZQwTvTNf6wsXc2JOiDaWL9fNd3TGS8OWXM1Wx8BhQFkICyQERtIn 87PmkFmeLjn9boif2iOKDP3bGOKR42WEDY48E9hK79mbgVUexUra1/eF5cWggBawXOcz odZWnG61kTnbzr24tr2o28jjkKXH6z2SI+8C8s3UsvnV0FSc7SwSX5XOu6F4AtgaAtI5 FnUGST5nUIAYea2wxmAoeJHWteP958mdIsdUi2Sugl2upCOpyt7TJPu/Bn7SntmshyL7 TrKmCEtTrOHMK4/rWa+E7pmG4AbRODQDyt36PajJPzvgvrNlsW8ieGIBir9FNlaywIMZ PwyA==
MIME-Version: 1.0
X-Received: by 10.52.165.239 with SMTP id zb15mr24017958vdb.44.1375279239257;  Wed, 31 Jul 2013 07:00:39 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.137.227 with HTTP; Wed, 31 Jul 2013 07:00:39 -0700 (PDT)
In-Reply-To: <CADnDZ88Vmm=VOU+Nf_v90StKpbFDxriPbrgVxOPkApgh2Pzrxw@mail.gmail.com>
References: <EDC539D2-48CE-44D7-A06C-19EEAE42D31C@piuha.net> <BF2DD745-99D0-420E-B199-7C8F94981BDA@network-heretics.com> <20840.1375200653@sandelman.ca> <CAF4+nEHS0fH8+ewhiWXoYwUfAa27wfrXDR8fZLYid-Z-mc7ZSw@mail.gmail.com> <CADnDZ88Vmm=VOU+Nf_v90StKpbFDxriPbrgVxOPkApgh2Pzrxw@mail.gmail.com>
Date: Wed, 31 Jul 2013 10:00:39 -0400
X-Google-Sender-Auth: oKiAyM5gMF_9H3C-G-LLj5IYkPY
Message-ID: <CAC4RtVDLvo+yANAEvotgGOkqTat3gsmY3=pOjM8LpMPB-ds-Lw@mail.gmail.com>
Subject: Re: making our meetings more worth the time/expense (was: Re: setting a goal for an inclusive IETF)
From: Barry Leiba <barryleiba@computer.org>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Jul 2013 14:00:40 -0000

>> The most valuable part of IETF meeting is and has always been the hall
>> conversations and side meetings
>
> I think *side meetings* are killing IETF, I call it *hidden meetings*, there
> is no input for IETF when we have side meetings. The input to IETF in
> through meeting sessions and discussion lists.

I have no argument with your last sentence; it's absolutely correct.

But I think you misunderstand the point Donald is making about things
such as small hallway conversations.

Example: A few people get together in a corner and one says, "About
that point I made on the list that you brushed off... here's what I'm
talking about:", and five or ten minutes of discussion ensues.  At the
end, either the guy with the point now understands why he's wrong (or
why his point isn't practical), or the document editor says, "OK, I
get your point now.  Let me work up some proposed text and post it to
the list."

Example: A few people get together during a session time they have
free, and they bash out some text to resolve an issue that came up.
They come to the working group meeting session with an explanation of
their conversation and the proposed text, and it's discussed in the
meeting session (and posted to the list afterward).

Example: Someone has an idea for a new document or other new work, so
he gathers some people to have breakfast one morning, explains his
idea, bashes it around with his colleagues, and as a result of that
breakfast chat he goes home after the IETF meeting and writes up an
Internet Draft.

None of this is hidden; none of this is secret.  It's all the way work
gets done efficiently: a small group of people crack some tough nuts,
and present the results to a wider audience.

Barry

From barryleiba.mailing.lists@gmail.com  Wed Jul 31 07:06:45 2013
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F0E621F9C60 for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 07:06:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.973
X-Spam-Level: 
X-Spam-Status: No, score=-101.973 tagged_above=-999 required=5 tests=[AWL=0.005, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0PZKBO3LZs8T for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 07:06:44 -0700 (PDT)
Received: from mail-ve0-x230.google.com (mail-ve0-x230.google.com [IPv6:2607:f8b0:400c:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id 2E66221F9CA4 for <ietf@ietf.org>; Wed, 31 Jul 2013 07:06:07 -0700 (PDT)
Received: by mail-ve0-f176.google.com with SMTP id b10so797267vea.7 for <ietf@ietf.org>; Wed, 31 Jul 2013 07:06:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=y9RBx0PLN3O9F5K78AAAlq55rNxfeCd67r2NXSLaIrg=; b=ZJPc6RnSk7t02VPOw0vZ0L03Y85sWi+Xalv9J1J1tZef41/Aw/44F7AmYvi2CBefFi qKjnQlcQIROnesDiQG7nnKfJl8RGOntzNMRJNUzre5GsuVuHnLaEiakyvX6+EFYsTXi1 z6FbaSt2zrB08VVmzSguTvIwm6RoiLGH9SIi5liqciJA+XirRaQARj0ashVE2ZMT3/i9 fH/f3FZE65fzYtZdJ2oq4DdFKcxAXknmHBLBo4AzBkt7kqAVmmvU3c0PsNEBDKrZSAdU 157kT2MfUGnOzjkXYzYI0fi6pZhQ40tGbvi80vQcLGouwCJ5BuY+D523+55one7bjBNl GnUA==
MIME-Version: 1.0
X-Received: by 10.58.34.69 with SMTP id x5mr28882030vei.11.1375279566544; Wed, 31 Jul 2013 07:06:06 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.137.227 with HTTP; Wed, 31 Jul 2013 07:06:06 -0700 (PDT)
In-Reply-To: <24093.1375278470@sandelman.ca>
References: <24093.1375278470@sandelman.ca>
Date: Wed, 31 Jul 2013 10:06:06 -0400
X-Google-Sender-Auth: rYPVO53EiCtQWmOsIna6WLhzl34
Message-ID: <CAC4RtVA_BQ=mMjSJCZEW3tpzadgJuk+KmaR8zR0Bjo_EqDoihg@mail.gmail.com>
Subject: Re: stability of iana.org URLs
From: Barry Leiba <barryleiba@computer.org>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: text/plain; charset=ISO-8859-1
Cc: iana@iana.org, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Jul 2013 14:06:45 -0000

> I just followed http://www.iana.org/assignments/enterprise-numbers.html
> From RFC3315 (DHCPv6)'s reference section.  Ten years later, the URL
> doesn't work.
>
> I know that things were reworked when we went to XML based storage, but
> I thought that the old URLs would at least have a 301 error on them.
>
> I discovered that dropping the .html gets me the right data at:
>   http://www.iana.org/assignments/enterprise-numbers

Yes: that's the form that IANA would like you to use.  They changed
their registries from HTML to XML, and the URLs changed.  Supposed
they should decide to turn them all into JSON (aieeeeeeeee!)... the
URLs would change again.  But the suffix-less version will always
work.

When I've done AD reviews of documents that cite IANA URLs, I've given
the authors that feedback, and suggested the change to the suffix-less
URLs.  I also intend to suggest to IANA (thanks to a document author,
and I've since forgotten who it was; sorry) that they post permalinks
in all the registries, so people will know which URL they ought to
use, and not have to guess.

Barry, Applications AD

From stpeter@stpeter.im  Wed Jul 31 07:11:25 2013
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC4CD11E81A1 for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 07:11:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.482
X-Spam-Level: 
X-Spam-Status: No, score=-102.482 tagged_above=-999 required=5 tests=[AWL=0.117, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BcmSde-jJ2Xx for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 07:11:20 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 1070121F9CC2 for <ietf@ietf.org>; Wed, 31 Jul 2013 07:11:18 -0700 (PDT)
Received: from che-vpn-cluster-2-456.cisco.com (unknown [198.135.0.233]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 9FAD3414D8; Wed, 31 Jul 2013 08:13:31 -0600 (MDT)
Message-ID: <51F91B02.2040000@stpeter.im>
Date: Wed, 31 Jul 2013 16:11:14 +0200
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: stability of iana.org URLs
References: <24093.1375278470@sandelman.ca> <CAC4RtVA_BQ=mMjSJCZEW3tpzadgJuk+KmaR8zR0Bjo_EqDoihg@mail.gmail.com>
In-Reply-To: <CAC4RtVA_BQ=mMjSJCZEW3tpzadgJuk+KmaR8zR0Bjo_EqDoihg@mail.gmail.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: iana@iana.org, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Jul 2013 14:11:25 -0000

On 7/31/13 4:06 PM, Barry Leiba wrote:
>> I just followed http://www.iana.org/assignments/enterprise-numbers.html
>> From RFC3315 (DHCPv6)'s reference section.  Ten years later, the URL
>> doesn't work.
>>
>> I know that things were reworked when we went to XML based storage, but
>> I thought that the old URLs would at least have a 301 error on them.
>>
>> I discovered that dropping the .html gets me the right data at:
>>   http://www.iana.org/assignments/enterprise-numbers
> 
> Yes: that's the form that IANA would like you to use.  They changed
> their registries from HTML to XML, and the URLs changed.

That's true, but cool URIs don't change:

http://www.w3.org/Provider/Style/URI.html

IMHO it'd be easy enough to put general redirects in place.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From kathleen.moriarty@emc.com  Wed Jul 31 07:12:30 2013
Return-Path: <kathleen.moriarty@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F85221F9E1D; Wed, 31 Jul 2013 07:12:30 -0700 (PDT)
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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wmz6bntKLah8; Wed, 31 Jul 2013 07:12:25 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 2A26611E81A5; Wed, 31 Jul 2013 07:12:24 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r6VECKDU027964 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 31 Jul 2013 10:12:23 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd05.lss.emc.com [10.254.222.129]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Wed, 31 Jul 2013 10:12:04 -0400
Received: from mxhub25.corp.emc.com (mxhub25.corp.emc.com [10.254.110.181]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r6VEC1NB020783; Wed, 31 Jul 2013 10:12:01 -0400
Received: from mx15a.corp.emc.com ([169.254.1.184]) by mxhub25.corp.emc.com ([10.254.110.181]) with mapi; Wed, 31 Jul 2013 10:12:01 -0400
From: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
To: Arturo Servin <arturo.servin@gmail.com>
Date: Wed, 31 Jul 2013 10:11:46 -0400
Subject: Re: [Diversity] setting a goal for an inclusive IETF
Thread-Topic: [Diversity] setting a goal for an inclusive IETF
Thread-Index: Ac6N9+QR6O/NbMI5Qo+BCXok3fvOxw==
Message-ID: <0451AC4A-3CA4-4038-B02A-2B6E145D55F5@emc.com>
References: <CADnDZ8-mqRsPyurtg9z9S=VHZmEKAoW+x46rKrS4m_VNiqDEfA@mail.gmail.com> <51F912CF.3030203@gmail.com>
In-Reply-To: <51F912CF.3030203@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "diversity@ietf.org" <diversity@ietf.org>, Pete Resnick <presnick@qti.qualcomm.com>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Jul 2013 14:12:30 -0000

That is correct, the diversity list is open and we will have a summary of s=
uggested initiatives for the design team to research tonight.  To the speci=
fic point below, we will do our best to also do outreach to speak with a wi=
de range of people. =20

Thank you!
Kathleen=20

Sent from my iPhone

On Jul 31, 2013, at 3:37 PM, "Arturo Servin" <arturo.servin@gmail.com> wrot=
e:

>=20
>    AFAIK anyone can participate. You just have to said "I".
>=20
> Regards,
> as
>=20
> On 7/31/13 2:45 PM, Abdussalam Baryun wrote:
>> I would prefer that the design team are selected by diversity
>> parameters ( gender, region, age, necomer-oldcomer, etc). Thanks again,
>=20
> _______________________________________________
> diversity mailing list
> diversity@ietf.org
> https://www.ietf.org/mailman/listinfo/diversity
>=20

From barryleiba.mailing.lists@gmail.com  Wed Jul 31 07:13:32 2013
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E3EB11E819F for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 07:13:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.974
X-Spam-Level: 
X-Spam-Status: No, score=-101.974 tagged_above=-999 required=5 tests=[AWL=0.004, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LNBKJcm5MGHD for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 07:13:31 -0700 (PDT)
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 5741911E818B for <ietf@ietf.org>; Wed, 31 Jul 2013 07:13:31 -0700 (PDT)
Received: by mail-vb0-f53.google.com with SMTP id i3so726396vbh.40 for <ietf@ietf.org>; Wed, 31 Jul 2013 07:13:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=9chmG0YUOqG/nZx92aFku40L/ExDiOAOeONuL5hcSfw=; b=vensGsuK0xJ05BNKNdIuyAC+gHGzQGF0aBw8rK/u948rHvk+9bio+djo1PCfnMxsVO ilf+w57CnTXSiWdU/ivSTuL09aKVeAqNPlF3ctEa4UTiopP3PVzqsky26wrylrg1Mhfl QTphnPbNuQXEmuTACkTCu9xYwkmj1C4c7SMT2oP9BohooyNbk4aoMX1JwIpSCBfNVkyM ZvUglAnAP24PTkdT3YLKNPzQjbuzJcArwNKbRXsVJePvd9eBXXH5qLbUaxKDNKT7Ssvo uLzsN8M0KO4RQSNx11qhRJ5G7O6u5NpcDoCXopUkPGGRjSfZ3vu8vRHTW9uUYJeCBqNr jAZA==
MIME-Version: 1.0
X-Received: by 10.220.95.201 with SMTP id e9mr1564384vcn.71.1375280010775; Wed, 31 Jul 2013 07:13:30 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.137.227 with HTTP; Wed, 31 Jul 2013 07:13:30 -0700 (PDT)
In-Reply-To: <51F91B02.2040000@stpeter.im>
References: <24093.1375278470@sandelman.ca> <CAC4RtVA_BQ=mMjSJCZEW3tpzadgJuk+KmaR8zR0Bjo_EqDoihg@mail.gmail.com> <51F91B02.2040000@stpeter.im>
Date: Wed, 31 Jul 2013 10:13:30 -0400
X-Google-Sender-Auth: sMtvvuVZyvaR3LQ3z0MISqXWM1c
Message-ID: <CAC4RtVCrO73fgTidAYr7duaF6NAtz2pFkTHmELjoGh5p0D51mw@mail.gmail.com>
Subject: Re: stability of iana.org URLs
From: Barry Leiba <barryleiba@computer.org>
To: Peter Saint-Andre <stpeter@stpeter.im>
Content-Type: text/plain; charset=ISO-8859-1
Cc: iana@iana.org, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Jul 2013 14:13:32 -0000

>>> I discovered that dropping the .html gets me the right data at:
>>>   http://www.iana.org/assignments/enterprise-numbers
>>
>> Yes: that's the form that IANA would like you to use.  They changed
>> their registries from HTML to XML, and the URLs changed.
>
> That's true, but cool URIs don't change:
>
> http://www.w3.org/Provider/Style/URI.html
>
> IMHO it'd be easy enough to put general redirects in place.

They have: they are keyed off the suffix-less URIs.  That's why they
want us to use those.

Barry

From jnc@mercury.lcs.mit.edu  Wed Jul 31 07:22:38 2013
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14B0321E80D4 for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 07:22:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.474
X-Spam-Level: 
X-Spam-Status: No, score=-6.474 tagged_above=-999 required=5 tests=[AWL=0.125,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hx+lH430rfiV for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 07:22:29 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 6655511E8194 for <ietf@ietf.org>; Wed, 31 Jul 2013 07:22:26 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 8D87118C115; Wed, 31 Jul 2013 10:22:20 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: stability of iana.org URLs
Message-Id: <20130731142220.8D87118C115@mercury.lcs.mit.edu>
Date: Wed, 31 Jul 2013 10:22:20 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: iana@iana.org, jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Jul 2013 14:22:39 -0000

    > From: Barry Leiba <barryleiba@computer.org>

    > They have: they are keyed off the suffix-less URIs. That's why they
    > want us to use those.

That doesn't change the point that breaking URLs in _previously-published,
static_ documents is a Bad Thing.

	Noel

From moore@network-heretics.com  Wed Jul 31 07:24:23 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1AD411E819F for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 07:24:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.075
X-Spam-Level: 
X-Spam-Status: No, score=-3.075 tagged_above=-999 required=5 tests=[AWL=0.524,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XE5s-go7xyjO for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 07:24:17 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id 4C02F11E81A0 for <ietf@ietf.org>; Wed, 31 Jul 2013 07:24:16 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id C444120E2D; Wed, 31 Jul 2013 10:24:13 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute2.internal (MEProxy); Wed, 31 Jul 2013 10:24:13 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id :references:to; s=smtpout; bh=Qb0IRBeo9J/FgmemcfkMCJMGDIc=; b=RZ Hd1cat/G8dJ6qB6Y2UMqw+7KSiNx64LyPRZXlXrpqKENsvLOwJWukqq43ok2/WDm qO4LCFbd75wrSLx1DwBh+eBdOKEi4o47CJll1yB0QUn2JzrEjlL8p1XNAdsxBEwq 5fog5Tq9s125kc2XWh/5mNPYh6IDglmmElrSBeQTU=
X-Sasl-enc: oaPaI7eHBM706Q9WHi5GMssaJjDrU0Rrz0kTi2qkyjR8 1375280653
Received: from dhcp-11c1.meeting.ietf.org (unknown [130.129.17.193]) by mail.messagingengine.com (Postfix) with ESMTPA id 5795BC00E80; Wed, 31 Jul 2013 10:24:13 -0400 (EDT)
Subject: Re: making our meetings more worth the time/expense (was: Re: setting a goal for an inclusive IETF)
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <CAF4+nEHS0fH8+ewhiWXoYwUfAa27wfrXDR8fZLYid-Z-mc7ZSw@mail.gmail.com>
Date: Wed, 31 Jul 2013 16:24:11 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <FB191A35-9290-42DC-BF4A-00B2DF54EAF6@network-heretics.com>
References: <EDC539D2-48CE-44D7-A06C-19EEAE42D31C@piuha.net> <BF2DD745-99D0-420E-B199-7C8F94981BDA@network-heretics.com> <20840.1375200653@sandelman.ca> <CAF4+nEHS0fH8+ewhiWXoYwUfAa27wfrXDR8fZLYid-Z-mc7ZSw@mail.gmail.com>
To: Donald Eastlake <d3e3e3@gmail.com>
X-Mailer: Apple Mail (2.1085)
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Jul 2013 14:24:24 -0000

On Jul 31, 2013, at 10:30 AM, Donald Eastlake wrote:

> The most valuable part of IETF meeting is and has always been the hall
> conversations and side meetings

The hall conversations and side meetings will continue to be immensely =
valuable.   But working group sessions can, and should, also be =
valuable.=20

This gets back to my original point, which is that if we want to =
encourage broader participation in IETF we need to make participation in =
IETF work the participants' time and money.

Also, if we help working group sessions make better use of their time, =
WGs will reach closure more quickly.   Hardly anybody, I suspect, would =
mind that.

Keith


From roland.bless@kit.edu  Wed Jul 31 07:27:28 2013
Return-Path: <roland.bless@kit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D01221F9EED for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 07:27:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level: 
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dHrEYiUu55wG for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 07:27:17 -0700 (PDT)
Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de [141.3.10.81]) by ietfa.amsl.com (Postfix) with ESMTP id DC85621F867B for <ietf@ietf.org>; Wed, 31 Jul 2013 07:27:12 -0700 (PDT)
Received: from irams1.ira.uni-karlsruhe.de ([141.3.10.5]) by iramx2.ira.uni-karlsruhe.de with esmtps port 25  id 1V4XMl-0000h6-9i; Wed, 31 Jul 2013 16:27:11 +0200
Received: from i72vorta.tm.uni-karlsruhe.de ([141.3.71.26] helo=vorta.tm.kit.edu) by irams1.ira.uni-karlsruhe.de with esmtp port 25  id 1V4XMl-0006Ee-2K; Wed, 31 Jul 2013 16:27:03 +0200
Received: from [IPv6:::1] (localhost [127.0.0.1]) by vorta.tm.kit.edu (Postfix) with ESMTPS id D68ECA800FE; Wed, 31 Jul 2013 16:27:02 +0200 (CEST)
Message-ID: <51F91EB6.5090902@kit.edu>
Date: Wed, 31 Jul 2013 16:27:02 +0200
From: Roland Bless <roland.bless@kit.edu>
Organization: Institute of Telematics, Karlsruhe Institute of Technology (KIT)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.1) Gecko/20060111 Thunderbird/1.5 Mnenhy/0.7.3.0
MIME-Version: 1.0
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Subject: Re: Bringing back Internet transparency
References: <51F7AED0.2080308@kit.edu> <4137B586-FD71-495A-8345-35CA3988E906@gmx.net>
In-Reply-To: <4137B586-FD71-495A-8345-35CA3988E906@gmx.net>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-ATIS-AV: ClamAV (irams1.ira.uni-karlsruhe.de)
X-ATIS-AV: Kaspersky (iramx2.ira.uni-karlsruhe.de)
X-ATIS-AV: ClamAV (iramx2.ira.uni-karlsruhe.de)
X-ATIS-Timestamp: iramx2.ira.uni-karlsruhe.de 1375280831.465090000
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Jul 2013 14:27:28 -0000

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

Hi Hannes,

On 30.07.2013 14:35, Hannes Tschofenig wrote:
> I raised the need for this transparency in this writeup: 
> http://tools.ietf.org/html/draft-tschofenig-hourglass-00
> 
> The document also points to some projects / paper I am aware of
> that are relevant. There may be more.

Thanks for the pointer. However, the tone of the
draft seems to suggest accepting that we now have
to stick to TCP/HTTP(S) only...

Section 5 (Will IPv6 reverse the shift?) is interesting,
but I disagree with the conclusion:

   Another reason is that the IPv6 Internet will certainly be filled
   with firewalls, and if history is any guide for the future, only TCP
   and UDP are likely to work through such firewalls.

That shows exactly the point that we need to work on. I see no reason
why IPv6 firewalls should be constrained to let only UDP/TCP through.
We should rather provide some guidance so that we still leave open
the way for deploying innovations in the network. I clearly see the
need for deploying security solutions like firewalls, IDSs and so on.
But IMHO that doesn't mean to block every future useful development, too.

Regards,
 Roland
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlH5HrEACgkQ1YyfLd659kenNACg9gslo28of/rhA3MA78voB9Yf
kT0AoKfCSL8ncmXIIyQhsjJvajHvsUzV
=2ZZ4
-----END PGP SIGNATURE-----

From jari.arkko@piuha.net  Wed Jul 31 07:51:29 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0826E21F9AE9 for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 07:51:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.466
X-Spam-Level: 
X-Spam-Status: No, score=-102.466 tagged_above=-999 required=5 tests=[AWL=0.133, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wu7cDabfVGWF for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 07:51:15 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 6FFEF21F859A for <ietf@ietf.org>; Wed, 31 Jul 2013 07:50:58 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id C70CB2CC54 for <ietf@ietf.org>; Wed, 31 Jul 2013 17:50:56 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cuoX6dtFPjjr for <ietf@ietf.org>; Wed, 31 Jul 2013 17:50:56 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 55C962CC48 for <ietf@ietf.org>; Wed, 31 Jul 2013 17:50:56 +0300 (EEST)
From: Jari Arkko <jari.arkko@piuha.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: volunteers to take notes in the plenary
Message-Id: <C9E613DC-7A01-4650-AB9D-16F0E209A2F8@piuha.net>
Date: Wed, 31 Jul 2013 16:50:56 +0200
To: "ietf@ietf.org list" <ietf@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Jul 2013 14:51:29 -0000

I'd like to get a couple of volunteers to take notes in the plenary. =
Please send mail, or see me at the front before the meeting. Thanks.

Jari


From ned+ietf@mauve.mrochek.com  Wed Jul 31 08:56:05 2013
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2658221F9CA4 for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 08:56:05 -0700 (PDT)
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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bwLfIGcpD9fC for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 08:56:00 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id A70BB21F9CA1 for <ietf@ietf.org>; Wed, 31 Jul 2013 08:56:00 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OWNOVDY7U8000XPH@mauve.mrochek.com> for ietf@ietf.org; Wed, 31 Jul 2013 08:50:58 -0700 (PDT)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OWGOYH1YHC00004R@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Wed, 31 Jul 2013 08:50:53 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OWNOVBGV6I00004R@mauve.mrochek.com>
Date: Wed, 31 Jul 2013 08:49:44 -0700 (PDT)
Subject: Re: stability of iana.org URLs
In-reply-to: "Your message dated Wed, 31 Jul 2013 16:11:14 +0200" <51F91B02.2040000@stpeter.im>
References: <24093.1375278470@sandelman.ca> <CAC4RtVA_BQ=mMjSJCZEW3tpzadgJuk+KmaR8zR0Bjo_EqDoihg@mail.gmail.com> <51F91B02.2040000@stpeter.im>
To: Peter Saint-Andre <stpeter@stpeter.im>
Cc: Barry Leiba <barryleiba@computer.org>, IETF discussion list <ietf@ietf.org>, iana@iana.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Jul 2013 15:56:05 -0000

> On 7/31/13 4:06 PM, Barry Leiba wrote:
> >> I just followed http://www.iana.org/assignments/enterprise-numbers.html
> >> From RFC3315 (DHCPv6)'s reference section.  Ten years later, the URL
> >> doesn't work.
> >>
> >> I know that things were reworked when we went to XML based storage, but
> >> I thought that the old URLs would at least have a 301 error on them.
> >>
> >> I discovered that dropping the .html gets me the right data at:
> >>   http://www.iana.org/assignments/enterprise-numbers
> >
> > Yes: that's the form that IANA would like you to use.  They changed
> > their registries from HTML to XML, and the URLs changed.

> That's true, but cool URIs don't change:

> http://www.w3.org/Provider/Style/URI.html

> IMHO it'd be easy enough to put general redirects in place.

+1. mod_rewrite is nobody's friend, but it can be tamed and put to good use.

				Ned

From abdussalambaryun@gmail.com  Wed Jul 31 09:09:24 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E04AE11E8109 for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 09:09:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.553
X-Spam-Level: 
X-Spam-Status: No, score=-2.553 tagged_above=-999 required=5 tests=[AWL=0.046,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N6K-HpJqNRrW for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 09:09:22 -0700 (PDT)
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 E49DB21F9EFB for <ietf@ietf.org>; Wed, 31 Jul 2013 09:09:21 -0700 (PDT)
Received: by mail-pd0-f171.google.com with SMTP id bv13so721767pdb.2 for <ietf@ietf.org>; Wed, 31 Jul 2013 09:09:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=ExxtC7aruw6ddMm2whGRvT5Pod8eVaxCN9g1MDDBz5s=; b=lG44SrTmctTZjWwF5IlgrBU/C3209nQqkLg+9PMTKTxQEskGocSUkkOX+lg/RI/ksm K+3bmzRfffu7LJoKezdtIIQ1zylu6tGtQL0tfAmKiywBSt2RpUYq/sgog6syPZt8Wx93 wLJYAOmRooG/ybUfbpkSPYkxm6LjzuCTd0VVYeudL3qXFM7Hl41DER0fW3Krdmc1oHfa uLFHfpycrc+l07Ai5UUajn3rQLFWGH7uhNMQhguiKHzuyo0f4tFvB4CUtvwG+BsgypS2 cXbC1hqlyV6ygItQ9A5uL84dBUjV9yW3kM3lWoCoN19H+LDOg3brNP2dji0zins9707Y uMAQ==
MIME-Version: 1.0
X-Received: by 10.68.137.201 with SMTP id qk9mr2614967pbb.199.1375286961635; Wed, 31 Jul 2013 09:09:21 -0700 (PDT)
Received: by 10.68.250.133 with HTTP; Wed, 31 Jul 2013 09:09:21 -0700 (PDT)
Date: Wed, 31 Jul 2013 17:09:21 +0100
Message-ID: <CADnDZ8-rRqAyF-1M7ND7k1wGFWN5rscvofiNP=4Bes0bq4LHkA@mail.gmail.com>
Subject: Re: making our meetings more worth the time/expense (was: Re: setting a goal for an inclusive IETF)
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Content-Type: multipart/alternative; boundary=047d7b2e3f2ed005a904e2d0f25e
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Jul 2013 16:09:24 -0000

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

Hi Barry,

Sorry for long meesage,

I will give you a real example which I experienced that includes my request
regarding a WG ietf draft that has no presenter but two people in the WG
that want discuss it in meetings as below real story. I want to confirm my
statement of hidden discuss/information related to IETF work,  because
there are intentions/encourages by some to do hidden meetings, and hidden
reviews (they are acknowledged in draft with reviews that are not listed or
hidden, on the other hand, once I have not been acknowledged-listed when I
published my review even), however, I think it can be fixed in future. I am
not against the side meeting but against not documenting information
(excluding side info, and reviews, and comments, that change the work we
are doing).

 A live WG example in IETF is for this Berline-meeting: A request for
discussion was raised [1] by a participant that will attend, and I (as
remote-meeter) support for that request that I did raise [2]. The author
suggested that he has no presentation and would like time within the week
(i.e. I understand it was side meeting) to discuss with that attended
participant [3] (as hidden meeting, but still no reply to the remote
requester, was that remote participant discouraged, maybe). However, it was
nice that the first discuss-requester has added request to only do
discussions in WG meeting (not side meetings) [4].

[1] http://www.ietf.org/mail-archive/web/manet/current/msg15521.html
[2] http://www.ietf.org/mail-archive/web/manet/current/msg15523.html
[3] http://www.ietf.org/mail-archive/web/manet/current/msg15534.html
[4] http://www.ietf.org/mail-archive/web/manet/current/msg15535.html

My comment we need to encourage the discussions to be done in the IETF, and
even if we done a discussion in a side meeting as per your examples, we
SHOULD quickly write it down into the IETF lists (as some participants do,
e.g. the chair's article of diversity done this month). My addition
comments below,

AB


On Wed, Jul 31, 2013 at 3:00 PM, Barry Leiba <barryleiba@computer.org>wrote:

> >> The most valuable part of IETF meeting is and has always been the hall
> >> conversations and side meetings
> >
> > I think *side meetings* are killing IETF, I call it *hidden meetings*,
> there
> > is no input for IETF when we have side meetings. The input to IETF in
> > through meeting sessions and discussion lists.
>
> I have no argument with your last sentence; it's absolutely correct.
>
> But I think you misunderstand the point Donald is making about things
> such as small hallway conversations.
>
> Example: A few people get together in a corner and one says, "About
> that point I made on the list that you brushed off... here's what I'm
> talking about:", and five or ten minutes of discussion ensues.  At the
> end, either the guy with the point now understands why he's wrong (or
> why his point isn't practical), or the document editor says, "OK, I
> get your point now.  Let me work up some proposed text and post it to
> the list."
>

In this example, they (discussion team) should add the result of discussion
into the IETF WG lists, they should document it

>
> Example: A few people get together during a session time they have
> free, and they bash out some text to resolve an issue that came up.
> They come to the working group meeting session with an explanation of
> their conversation and the proposed text, and it's discussed in the
> meeting session (and posted to the list afterward).
>
In this example, they should document the result of discussion and the
event into the IETF WG lists (if they think useful).

>


> Example: Someone has an idea for a new document or other new work, so
> he gathers some people to have breakfast one morning, explains his
> idea, bashes it around with his colleagues, and as a result of that
> breakfast chat he goes home after the IETF meeting and writes up an
> Internet Draft.
>
So the result is already an input draft, IMHO, that side meeting is
respected by IETF because it is a usual birth of any draft/idea. That side
meeting is not hidden, but also not related to any IETF document. I was
arguing discuss that are related to IETF document which has a value that
will direct the IETF draft.

>
> None of this is hidden; none of this is secret.  It's all the way work
> gets done efficiently: a small group of people crack some tough nuts,
> and present the results to a wider audience.
>

When the discussion is done or encouraged by human habit to make it in a
special TEAM, I will say it is SECRET, as long as it ended there. I hope
our diversity team is not secret because still I seem not to know what is
happening there, nothing is announced on their lists regarding targets.
Furthermore, please see my point above of my real example on one WG, it
happends in IETF that they discuss issues out side the lists/meetings and
then the results of such TEAM/SIDE/HIDDEN meeting is not given (can be
forgotten, because most are bussy, which is always the excuse that can be
used) to the community, but an announced-action is done/listed resulting
from such hidden-discussion (i.e. unlisted).

AB

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

<div dir=3D"ltr"><div>Hi Barry,</div><div>=A0</div><div>Sorry for long mees=
age, </div><div>=A0</div><div>I will give you=A0a real example which I expe=
rienced that includes my=A0request regarding a WG ietf=A0draft that has no =
presenter but=A0two=A0people in the WG that want discuss it in meetings as =
below real=A0story. I want to confirm my statement of hidden discuss/inform=
ation related to IETF work,=A0=A0because there are intentions/encourages by=
 some to do hidden meetings, and hidden reviews (they are acknowledged in d=
raft with reviews that are not listed or hidden, on the other hand, once=A0=
I have not been acknowledged-listed when I published my review even), howev=
er, I think it can be fixed in future. I am not against the side meeting bu=
t against not documenting information (excluding side info, and reviews, an=
d comments, that change the work we are doing).</div>
<div>=A0</div><div>=A0A live WG=A0example in IETF is for this Berline-meeti=
ng: A request for discussion was raised [1] by a participant that will atte=
nd, and I (as remote-meeter) support for that request that I did raise [2].=
 The author suggested that he has no presentation and would like time withi=
n the week (i.e. I understand it was side meeting) to discuss with that att=
ended participant=A0[3]=A0(as hidden meeting, but still no reply to the rem=
ote requester, was that remote participant discouraged, maybe). However, it=
 was nice that the first discuss-requester has added=A0request to only do d=
iscussions in WG meeting (not side meetings) [4].</div>
<div>=A0</div><div>[1] <a href=3D"http://www.ietf.org/mail-archive/web/mane=
t/current/msg15521.html">http://www.ietf.org/mail-archive/web/manet/current=
/msg15521.html</a></div><div>[2] <a href=3D"http://www.ietf.org/mail-archiv=
e/web/manet/current/msg15523.html">http://www.ietf.org/mail-archive/web/man=
et/current/msg15523.html</a></div>
<div>[3] <a href=3D"http://www.ietf.org/mail-archive/web/manet/current/msg1=
5534.html">http://www.ietf.org/mail-archive/web/manet/current/msg15534.html=
</a></div><div>[4] <a href=3D"http://www.ietf.org/mail-archive/web/manet/cu=
rrent/msg15535.html">http://www.ietf.org/mail-archive/web/manet/current/msg=
15535.html</a></div>
<div>=A0</div><div>My comment we need to encourage the discussions to be do=
ne in the IETF, and even if we done a discussion in a side meeting as per y=
our examples, we SHOULD quickly write it down into the IETF lists (as some =
participants do, e.g. the chair&#39;s article of diversity done this month)=
. My addition comments below,</div>
<div>=A0</div><div>AB</div><div class=3D"gmail_extra"><br><br><div class=3D=
"gmail_quote">On Wed, Jul 31, 2013 at 3:00 PM, Barry Leiba <span dir=3D"ltr=
">&lt;<a href=3D"mailto:barryleiba@computer.org" target=3D"_blank">barrylei=
ba@computer.org</a>&gt;</span> wrote:<br>
<blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-=
color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class=
=3D"gmail_quote"><div class=3D"im">&gt;&gt; The most valuable part of IETF =
meeting is and has always been the hall<br>

&gt;&gt; conversations and side meetings<br>
&gt;<br>
</div><div class=3D"im">&gt; I think *side meetings* are killing IETF, I ca=
ll it *hidden meetings*, there<br>
&gt; is no input for IETF when we have side meetings. The input to IETF in<=
br>
&gt; through meeting sessions and discussion lists.<br>
<br>
</div>I have no argument with your last sentence; it&#39;s absolutely corre=
ct.<br>
<br>
But I think you misunderstand the point Donald is making about things<br>
such as small hallway conversations.<br>
<br>
Example: A few people get together in a corner and one says, &quot;About<br=
>
that point I made on the list that you brushed off... here&#39;s what I&#39=
;m<br>
talking about:&quot;, and five or ten minutes of discussion ensues. =A0At t=
he<br>
end, either the guy with the point now understands why he&#39;s wrong (or<b=
r>
why his point isn&#39;t practical), or the document editor says, &quot;OK, =
I<br>
get your point now. =A0Let me work up some proposed text and post it to<br>
the list.&quot;<br></blockquote><div>=A0</div><div>In this example, they (d=
iscussion team)=A0should add the result of discussion into the IETF WG list=
s, they should document it</div><blockquote style=3D"margin:0px 0px 0px 0.8=
ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1p=
x;border-left-style:solid" class=3D"gmail_quote">

<br>
Example: A few people get together during a session time they have<br>
free, and they bash out some text to resolve an issue that came up.<br>
They come to the working group meeting session with an explanation of<br>
their conversation and the proposed text, and it&#39;s discussed in the<br>
meeting session (and posted to the list afterward).<br></blockquote><div><d=
iv>In this example, they should document=A0the result of discussion and the=
 event=A0into the IETF WG lists (if they think useful).</div><blockquote st=
yle=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,=
204,204);border-left-width:1px;border-left-style:solid" class=3D"gmail_quot=
e">
=A0</blockquote></div><blockquote style=3D"margin:0px 0px 0px 0.8ex;padding=
-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-l=
eft-style:solid" class=3D"gmail_quote">
<br>
Example: Someone has an idea for a new document or other new work, so<br>
he gathers some people to have breakfast one morning, explains his<br>
idea, bashes it around with his colleagues, and as a result of that<br>
breakfast chat he goes home after the IETF meeting and writes up an<br>
Internet Draft.<br></blockquote><div>So the result is already an input draf=
t, IMHO,=A0that side meeting is respected by IETF because it is a usual bir=
th of any draft/idea.=A0That side meeting is not hidden, but also not relat=
ed to any IETF document. I was arguing discuss that are related to IETF doc=
ument which has a value that will direct the IETF draft.</div>
<blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-=
color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class=
=3D"gmail_quote">
<br>
None of this is hidden; none of this is secret. =A0It&#39;s all the way wor=
k<br>
gets done efficiently: a small group of people crack some tough nuts,<br>
and present the results to a wider audience.<br></blockquote><div>=A0</div>=
<div>When the discussion is done or encouraged by human habit to make it in=
 a special TEAM, I will say it is SECRET, as long as it ended there. I hope=
 our diversity team is not secret because still I seem not to know what is =
happening there, nothing is announced on their lists regarding targets. Fur=
thermore, please see my point above=A0of my real example on one WG, it happ=
ends in IETF that they discuss issues out side the lists/meetings and then =
the results of such TEAM/SIDE/HIDDEN meeting=A0is not given (can be forgott=
en, because most are bussy, which is always the excuse that can be used)=A0=
to the community, but an announced-action is done/listed resulting from suc=
h hidden-discussion (i.e. unlisted).</div>
<div>=A0</div><div>AB</div></div><br></div></div>

--047d7b2e3f2ed005a904e2d0f25e--

From jari.arkko@piuha.net  Wed Jul 31 10:58:17 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 318D521E80D8 for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 10:58:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.499
X-Spam-Level: 
X-Spam-Status: No, score=-102.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5VijHhLCLSPM for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 10:58:11 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 4A76611E8186 for <ietf@ietf.org>; Wed, 31 Jul 2013 10:57:54 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 7A8082CC54; Wed, 31 Jul 2013 20:57:52 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mmOVhBgGjfTC; Wed, 31 Jul 2013 20:57:50 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id A87A02CC48; Wed, 31 Jul 2013 20:57:50 +0300 (EEST)
From: Jari Arkko <jari.arkko@piuha.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: plenary slides
Message-Id: <1D04EBCC-E8C5-4A9F-99F0-E910D147F1C3@piuha.net>
Date: Wed, 31 Jul 2013 19:57:50 +0200
To: John C Klensin <john-ietf@jck.com>, "ietf@ietf.org list" <ietf@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Jul 2013 17:58:17 -0000

The missing two (diversity, IAOC) plenary slides have been uploaded. I'm =
sorry that they were missed in the heat of the preparations for the =
meeting.=20

All materials are available at:

https://datatracker.ietf.org/meeting/87/materials.html

Jari


From peter@akayla.com  Wed Jul 31 13:50:23 2013
Return-Path: <peter@akayla.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7100911E8116; Wed, 31 Jul 2013 13:50:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.299
X-Spam-Level: 
X-Spam-Status: No, score=-0.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MANGLED_LIST=2.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hHh94lkNA+XC; Wed, 31 Jul 2013 13:50:13 -0700 (PDT)
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 7B2A421F9CFB; Wed, 31 Jul 2013 13:50:13 -0700 (PDT)
Received: from [130.129.69.200] ([130.129.69.200]) by p3plsmtpa08-09.prod.phx3.secureserver.net with  id 78q11m00J4KFYsJ018q6Qj; Wed, 31 Jul 2013 13:50:12 -0700
User-Agent: Microsoft-MacOutlook/14.3.5.130515
Date: Wed, 31 Jul 2013 13:50:06 -0700
Subject: Gen-ART review of draft-ietf-geopriv-res-gw-lis-discovery-05
From: Peter Yee <peter@akayla.com>
To: <draft-ietf-geopriv-res-gw-lis-discovery.all@tools.ietf.org>
Message-ID: <CE1EC68E.5B19%peter@akayla.com>
Thread-Topic: Gen-ART review of draft-ietf-geopriv-res-gw-lis-discovery-05
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: gen-art@ietf.org, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Jul 2013 20:50:23 -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>

Document: draft-ietf-geopriv-res-gw-lis-discovery-05
Reviewer: Peter Yee
Review Date: Jul-31-2013
IETF LC End Date: Jul-31-2013
IESG Telechat date: TBD

Summary: This draft is basically ready for publication, but has nits that
should be fixed before publication. [Ready with nits.]

The draft describes a means by which Devices behind a residential gateway
may discover the correct Location Information Server on the access network
providing Internet access to residential gateway.  The Device may thereby
gain access to certain location-based services.

Major issues: None

Minor issues: None

Nits:

Section 1, 1st paragraph, 2nd sentence: should "data" be appended
after "location"?  The wording is otherwise odd.

Page 7, 3rd paragraph: change "which" to "that".

Page 9, section 4.2, 2nd paragraph, 1st sentence: I'll admit my ignorance
of the finer points of the DNS and inquire what this sentence is supposed
to mean.  To what are the additional domain names added and how does this
allow a DNS record to cover a larger set of addresses?  Perhaps it's just
the wording or my lack of knowledge, but I didn't follow this point fully.

Page 9, section 4.2, 2nd bullet item: change "sucessively" to
"successively".

Page 11, section 4.6, 1st paragraph, 4th sentence: insert "a" before
"STUN server" or change "server" to "servers" depending on how many
need to be configured.

Page 12, 1st sentence: delete "a".

Page 12, 1st sentence: What about /56 for IPv6?

Page 14, 3rd paragraph, 2nd sentence: delete "a" before
"IP addresses" or change "addresses" to "address" depending on
how many false addresses you mean.

Page 14, 6th paragraph, last sentence: Are there any concrete
suggestions on who a device might determine accuracy?


 





From brian.e.carpenter@gmail.com  Wed Jul 31 13:55:40 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 204C421F9A1E for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 13:55:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.561
X-Spam-Level: 
X-Spam-Status: No, score=-102.561 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zaYuk8RVAOd7 for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 13:55:39 -0700 (PDT)
Received: from mail-pd0-x22c.google.com (mail-pd0-x22c.google.com [IPv6:2607:f8b0:400e:c02::22c]) by ietfa.amsl.com (Postfix) with ESMTP id A4D8221E80C1 for <ietf@ietf.org>; Wed, 31 Jul 2013 13:55:37 -0700 (PDT)
Received: by mail-pd0-f172.google.com with SMTP id z11so451768pdj.17 for <ietf@ietf.org>; Wed, 31 Jul 2013 13:55:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=VK7+/sfmkHuPJzbMFxZhBVhyJMvo6GptMtzADDMWYgw=; b=buYf0n/bFFoLArJKoQFVS6/ty9tZwRvpcFoEvD/TXPFZdMt8zwz/aWr4smqL//wxZh sDEE/qpzR4p+CRIY3o4ZX/o0QaoIcO3pWmTzouhl4dR85Ax5/qz770yo7F1zWk++aKEq NPbRhdbIimhORrJGIEco4lQhUt8qZm93JYiCwPxVGTzGZ47Xs4VbPn4MSnUN4rEzjr2K C2af8RLVlXj3jq0OOVtylln9n0qllTkQBuGfjFlXjjpmBqpDmQJfc7N0UJZwhLmXFC+J u5kKi+rBE/u51qSM+Ay4pAGWyFbuFmmL9FiF+ENvEepEJlLD38FP5MzuqERbXmkLCEPu 5U3Q==
X-Received: by 10.68.170.37 with SMTP id aj5mr82988049pbc.79.1375304137253; Wed, 31 Jul 2013 13:55:37 -0700 (PDT)
Received: from [192.168.178.23] (220.199.69.111.dynamic.snap.net.nz. [111.69.199.220]) by mx.google.com with ESMTPSA id bs3sm81285pbc.42.2013.07.31.13.55.34 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 31 Jul 2013 13:55:36 -0700 (PDT)
Message-ID: <51F979CD.8040808@gmail.com>
Date: Thu, 01 Aug 2013 08:55:41 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: making our meetings more worth the time/expense
References: <20130730163502.455E918C10F@mercury.lcs.mit.edu> <51F7FC29.2000407@isi.edu> <51F82442.4000404@gmail.com> <BB6564A3-80F7-479F-9336-04A0916F5989@network-heretics.com>
In-Reply-To: <BB6564A3-80F7-479F-9336-04A0916F5989@network-heretics.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: braden@isi.edu, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Jul 2013 20:55:40 -0000

Hi Keith,

On 31/07/2013 18:35, Keith Moore wrote:
> On Jul 30, 2013, at 10:38 PM, Brian E Carpenter wrote:
> 
>> It's been pointed out before that in a group with very
>> diverse languages, written words are usually better
>> understood than speech. It's a fact of life that you can't
>> have a full-speed cut-and-thrust discussion in a group of
>> 100 people, half of whom are speaking a foreign language.
>> Sitting in a circle does not fix this.
> 
> Yes, but most of the people in a typical WG meeting today
> aren't really participating in the meeting anyway.   They're
> not contributing input, they're not paying attention.  Their
> noses are in laptops.   

The last sentence there doesn't imply the previous one. I can
only speak for myself (and I'm not in Berlin), but I am often
looking at the slides, the draft and the jabber session while
listening to the speaker; no need to look up in order to pay
attention. Alternatively I am working on something else while
waiting for the topic I'm interested in to start; or I'm
checking whether it's time to move across to a clashing session.

Of course I have no idea what fraction of attendees are doing this.

> It's hard to tell how many of them
> would be participating if the meeting were more useful, but
> the very fact that the room contains so many nonparticipants
> is itself a deterrent to getting work done in the meeting.
> If nothing else, whenever someone tries to get a sense of the
> room, it's very misleading - people may be humming when they
> haven't even been listening, or it may appear that there's no
> significant support for something when there really is
> significant support among those who are interested in the
> topic.

That's true; I am much more suspicious of "sense of the room"
consensus calls than I am of "sense of the mailing list" calls.
But pretty much all WG Chairs do what they're supposed to by
confirming the consensus on the list.

>> Also, remote participants need full text slides; the
>> soundtrack simply isn't enough.
> 
> You seem to be assuming that the purpose of WG meetings is to
> have presentations.   I emphatically disagree.

The purpose is to communicate, including communication with
remote participants. Sometimes that means explaining things that
are, perhaps, badly explained in the draft - and getting back
comments that show what needs to be changed in the draft.

> If we decide to make WG meetings fora for interaction and
> discussion, we can adopt or invent disciplines and tools to
> better accommodate interaction and discussion between people
> of diverse languages and including those at other locations.
> But the disciplines and tools that we've adopted at the
> moment are designed to accommodate an audience, not active
> participants.

I don't think it's fair to blame the tools. We should be asking
questions about how we use the tools.

>> The old days are gone.
> 
> It sounds like you are saying that IETF is doomed to become
> irrelevant because it's stuck in habits that do not work.  I
> hope you're wrong about that.

No, I mean that we have to deal with a very diverse community
and the style of discussion that was successful when you or I
first started coming to the IETF isn't going to come back. I
don't, unfortunately, have the magic formula.

On 31/07/2013 14:23, Andrew Sullivan wrote:

> First, I observe that we already _have_ a great deal of written words:
> the drafts.  I continue to believe that altogether too much time in WG
> meetings is spent "introducing", "presenting", or otherwise showing
> off ideas in an existing draft to participants in the WG.  I
> acknowledge that (particularly in early stages of WG life, in topics
> with a lot of different work, and in cross-WG presentations) these
> "intro" presentations are a fact of life.  But I think we are
> extremely bad at holding the reigns on them.
> 
> In a WG meeting, I think such "intro" presentations about drafts
> really can be kept to three pieces of information: the name of the
> draft, a slogan describing the problem it is supposed to solve, and a
> pointer to the beginning(s) of discussion thread(s) on the draft.  If
> the person promoting the draft can't give the elevator pitch, they
> don't know their own draft well enough to summarize it and shouldn't
> be presenting it.  

That's a bit hard on people early in their IETF career who may
be among the most creative. So I disagree, when we are talking
about a piece of new work that has attracted interest on the
mailing list - we should be reasonably liberal at that stage.
Once. After that, I agree; repeat intros and non-substantive
discussions shouldn't be given meeting time. But I've been in
vey useful sessions where people have showed slides to
illustrate open issues, and got very productive feedback that
clarifies the options. I've been in other sessions where after a
few seconds I switch off after 2 slides and wait for the chairs
to call time.

<deleted several paragraphs that I strongly agree with>

...
> Unfortunately, actually running meetings this way is a lot of work,
> requires fairly careful planning, and requires an indifference to
> nasty remarks on the part of presenters who would much rather listen
> to themselves for 20 minutes than to others.  But I think it'd make
> for better meetings.  (Yes, along with room layouts that were more
> suited to getting people to the mic.)

I absolutely agree.

>> > The old days are gone.
> 
> Yes, and we need to figure out how to use meeting time effectively
> here in the new days.  That effective use does not, I think, involve
> expanding to fill all the time in the year with 20 minute low-content
> presentations summarizing the draft that you can read in the span of
> the time it takes to get through the presentation.  (Perhaps I'm
> wrong.  Perhaps people find that the only time they have now to read
> the drafts is during the presentation of the draft.  I sure hope not.)

I agree here too. It really all depends on strong session
control by the chairs and a much stronger "this is not a
conference" message to participants.

   Brian


From moore@network-heretics.com  Wed Jul 31 14:23:23 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3283A21F9995 for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 14:23:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.623
X-Spam-Level: 
X-Spam-Status: No, score=-3.623 tagged_above=-999 required=5 tests=[AWL=-0.025, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zLAZlXOrDmWN for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 14:23:16 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id A345C11E8111 for <ietf@ietf.org>; Wed, 31 Jul 2013 14:22:09 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id A17CD20DBC; Wed, 31 Jul 2013 17:22:08 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute2.internal (MEProxy); Wed, 31 Jul 2013 17:22:08 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=dOE MCFClpPvGXmT1qrV+ITykKZc=; b=rgmaJbXygab4ZIBTlaGEc7vMjw2yc4k/BYY 49CHKfaERc/sEWd/FWOso0Q+Fbf4Uj5KFui7aWK+ZL8OUv+Dr5Ua8/fr4k39VPw2 p0SPBnB0LMzOcdPzeF+DHuko1pAlkW7FuuLcVV36CP2CZrfWVaaitKg4oGN+tw5W FSuwmgJ4=
X-Sasl-enc: vNcic6ynuftVbxEEO5XWVY6TOEgZnwPu0DXfZg8sCLHF 1375305727
Received: from surfer-172-29-8-65-hotspot.internet-for-guests.com (unknown [87.193.195.90]) by mail.messagingengine.com (Postfix) with ESMTPA id 54951C00E80; Wed, 31 Jul 2013 17:22:06 -0400 (EDT)
Subject: Re: making our meetings more worth the time/expense
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: multipart/alternative; boundary=Apple-Mail-5--285953526
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <51F979CD.8040808@gmail.com>
Date: Wed, 31 Jul 2013 23:22:01 +0200
Message-Id: <30E3DE3C-D782-42C5-A175-4AB9AE553834@network-heretics.com>
References: <20130730163502.455E918C10F@mercury.lcs.mit.edu> <51F7FC29.2000407@isi.edu> <51F82442.4000404@gmail.com> <BB6564A3-80F7-479F-9336-04A0916F5989@network-heretics.com> <51F979CD.8040808@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1085)
Cc: braden@isi.edu, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Jul 2013 21:23:23 -0000

--Apple-Mail-5--285953526
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Jul 31, 2013, at 10:55 PM, Brian E Carpenter wrote:
>=20
>> It's hard to tell how many of them
>> would be participating if the meeting were more useful, but
>> the very fact that the room contains so many nonparticipants
>> is itself a deterrent to getting work done in the meeting.
>> If nothing else, whenever someone tries to get a sense of the
>> room, it's very misleading - people may be humming when they
>> haven't even been listening, or it may appear that there's no
>> significant support for something when there really is
>> significant support among those who are interested in the
>> topic.
>=20
> That's true; I am much more suspicious of "sense of the room"
> consensus calls than I am of "sense of the mailing list" calls.
> But pretty much all WG Chairs do what they're supposed to by
> confirming the consensus on the list.

When binding decisions are being made, this is of course the right thing =
to do.   But we still need an accurate sense of the room (from active =
participants) just to make good use of meeting time - so (for example) =
we can know whether or not it appears that a problem has been discussed =
sufficiently and/or addressed.   Of course we have to consult the =
mailing list in order to be sure we have rough consensus, but it's also =
very important to take advantage of face-to-face time to attempt to work =
out solutions to thorny problems.   So the failure to get an accurate =
sense of the room might not necessarily mean that the wrong decision is =
made, it might mean that the decision doesn't get made until much later =
- maybe after there have been another one or two meetings. =20

>=20
>>> Also, remote participants need full text slides; the
>>> soundtrack simply isn't enough.
>>=20
>> You seem to be assuming that the purpose of WG meetings is to
>> have presentations.   I emphatically disagree.
>=20
> The purpose is to communicate, including communication with
> remote participants. Sometimes that means explaining things that
> are, perhaps, badly explained in the draft - and getting back
> comments that show what needs to be changed in the draft.

Sometimes, yes.   But I doubt that should occupy the bulk of our meeting =
time.

>> If we decide to make WG meetings fora for interaction and
>> discussion, we can adopt or invent disciplines and tools to
>> better accommodate interaction and discussion between people
>> of diverse languages and including those at other locations.
>> But the disciplines and tools that we've adopted at the
>> moment are designed to accommodate an audience, not active
>> participants.
>=20
> I don't think it's fair to blame the tools. We should be asking
> questions about how we use the tools.

Some people don't see this, but I'm very convinced that the tools do =
have a significant effect on how we choose to convey our messages.   =
Partly because of the hardware, partly because of the software, these =
tools are optimized for certain things and pessimized for others.    =
It's pretty obvious that a laptop with a full-size keyboard and a poor =
pointing/drawing device is going to be much better at putting text on a =
screen than drawing diagrams.    It's very easy to do what the tool =
makes it easy to do (typically put a few words of text on a screen) =
while losing sight of your purpose (typically to facilitate an =
interactive discussion with input from several parties).   Part of the =
problem is indeed the tool's fault, or perhaps our fault for choosing =
the wrong tool for the job out of habit.  =20

It's not that visual aids are inherently bad.  Properly chosen visual =
aids can really help facilitate a discussion.   But a few words in large =
type on a small screen is rarely effective, and these screens aren't big =
enough and the projectors often lack the resolution needed to display =
adequate diagrams.   Also, the tools are generally designed to produce =
static content, rather than let you manipulate the content while it's on =
screen (say to illustrate the answer to a question).


>=20
>>> The old days are gone.
>>=20
>> It sounds like you are saying that IETF is doomed to become
>> irrelevant because it's stuck in habits that do not work.  I
>> hope you're wrong about that.
>=20
> No, I mean that we have to deal with a very diverse community
> and the style of discussion that was successful when you or I
> first started coming to the IETF isn't going to come back. I
> don't, unfortunately, have the magic formula.

I'm not arguing that we need the same style of discussion that worked =
for IETF when it was ~300 people.   You're right that we have a much =
larger and more diverse community now; we also have a much more diverse =
set of needs to consider in our designs.     Because of all of this =
diversity, it's even more important that we let diverse voices be heard. =
  We certainly need a better way to moderate discussions than either =
having the loudest people speak whenever they want, or forcing people to =
queue up at microphones.    And yet, I think what we're doing now is =
actually far worse (even for our current circumstances) than what IETF =
was doing in 1990.   We've taken huge steps in the wrong direction.

Keith


--Apple-Mail-5--285953526
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On Jul 31, 2013, at 10:55 PM, Brian E Carpenter =
wrote:</div><blockquote type=3D"cite"><div><font =
class=3D"Apple-style-span" color=3D"#000000"><br></font><blockquote =
type=3D"cite">It's hard to tell how many of =
them<br></blockquote><blockquote type=3D"cite">would be participating if =
the meeting were more useful, but<br></blockquote><blockquote =
type=3D"cite">the very fact that the room contains so many =
nonparticipants<br></blockquote><blockquote type=3D"cite">is itself a =
deterrent to getting work done in the =
meeting.<br></blockquote><blockquote type=3D"cite">If nothing else, =
whenever someone tries to get a sense of the<br></blockquote><blockquote =
type=3D"cite">room, it's very misleading - people may be humming when =
they<br></blockquote><blockquote type=3D"cite">haven't even been =
listening, or it may appear that there's no<br></blockquote><blockquote =
type=3D"cite">significant support for something when there really =
is<br></blockquote><blockquote type=3D"cite">significant support among =
those who are interested in the<br></blockquote><blockquote =
type=3D"cite">topic.<br></blockquote><br>That's true; I am much more =
suspicious of "sense of the room"<br>consensus calls than I am of "sense =
of the mailing list" calls.<br>But pretty much all WG Chairs do what =
they're supposed to by<br>confirming the consensus on the =
list.<br></div></blockquote><div><br></div>When binding decisions are =
being made, this is of course the right thing to do. &nbsp; But we still =
need an accurate sense of the room (from active participants) just to =
make good use of meeting time - so (for example) we can know whether or =
not it appears that a problem has been discussed sufficiently and/or =
addressed. &nbsp; Of course we have to consult the mailing list in order =
to be sure we have rough consensus, but it's also very important to take =
advantage of face-to-face time to attempt to work out solutions to =
thorny problems. &nbsp; So the failure to get an accurate sense of the =
room might not necessarily mean that the wrong decision is made, it =
might mean that the decision doesn't get made until much later - maybe =
after there have been another one or two meetings. =
&nbsp;</div><div><br><blockquote type=3D"cite"><div><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">Also, remote participants need =
full text slides; the<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">soundtrack simply isn't =
enough.<br></blockquote></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">You seem to be =
assuming that the purpose of WG meetings is =
to<br></blockquote><blockquote type=3D"cite">have presentations. =
&nbsp;&nbsp;I emphatically disagree.<br></blockquote><br>The purpose is =
to communicate, including communication with<br>remote participants. =
Sometimes that means explaining things that<br>are, perhaps, badly =
explained in the draft - and getting back<br>comments that show what =
needs to be changed in the =
draft.<br></div></blockquote><div><br></div>Sometimes, yes. &nbsp; But I =
doubt that should occupy the bulk of our meeting =
time.</div><div><br><blockquote type=3D"cite"><div><blockquote =
type=3D"cite">If we decide to make WG meetings fora for interaction =
and<br></blockquote><blockquote type=3D"cite">discussion, we can adopt =
or invent disciplines and tools to<br></blockquote><blockquote =
type=3D"cite">better accommodate interaction and discussion between =
people<br></blockquote><blockquote type=3D"cite">of diverse languages =
and including those at other locations.<br></blockquote><blockquote =
type=3D"cite">But the disciplines and tools that we've adopted at =
the<br></blockquote><blockquote type=3D"cite">moment are designed to =
accommodate an audience, not active<br></blockquote><blockquote =
type=3D"cite">participants.<br></blockquote><br>I don't think it's fair =
to blame the tools. We should be asking<br>questions about how we use =
the tools.<br></div></blockquote><div><br></div>Some people don't see =
this, but I'm very convinced that the tools do have a significant effect =
on how we choose to convey our messages. &nbsp; Partly because of the =
hardware, partly because of the software, these tools are optimized for =
certain things and pessimized for others. &nbsp; &nbsp;It's pretty =
obvious that a laptop with a full-size keyboard and a poor =
pointing/drawing device is going to be much better at putting text on a =
screen than drawing diagrams. &nbsp; &nbsp;It's very easy to do what the =
tool makes it easy to do (typically put a few words of text on a screen) =
while losing sight of your purpose (typically to facilitate an =
interactive discussion with input from several parties). &nbsp; Part of =
the problem is indeed the tool's fault, or perhaps our fault for =
choosing the wrong tool for the job out of habit. =
&nbsp;&nbsp;</div><div><br></div><div>It's not that visual aids are =
inherently bad. &nbsp;Properly chosen visual aids can really help =
facilitate a discussion. &nbsp; But a few words in large type on a small =
screen is rarely effective, and these screens aren't big enough and the =
projectors often lack the resolution needed to display adequate =
diagrams. &nbsp; Also, the tools are generally designed to produce =
static content, rather than let you manipulate the content while it's on =
screen (say to illustrate the answer to a =
question).</div><div><br></div><div><br></div><div><blockquote =
type=3D"cite"><div><br><blockquote type=3D"cite"><blockquote =
type=3D"cite">The old days are =
gone.<br></blockquote></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">It sounds like =
you are saying that IETF is doomed to become<br></blockquote><blockquote =
type=3D"cite">irrelevant because it's stuck in habits that do not work. =
&nbsp;I<br></blockquote><blockquote type=3D"cite">hope you're wrong =
about that.<br></blockquote><br>No, I mean that we have to deal with a =
very diverse community<br>and the style of discussion that was =
successful when you or I<br>first started coming to the IETF isn't going =
to come back. I<br>don't, unfortunately, have the magic =
formula.<br></div></blockquote><div><br></div><div>I'm not arguing that =
we need the same style of discussion that worked for IETF when it was =
~300 people. &nbsp; You're right that we have a much larger and more =
diverse community now; we also have a much more diverse set of needs to =
consider in our designs. &nbsp; &nbsp; Because of all of this diversity, =
it's even more important that we let diverse voices be heard. &nbsp; We =
certainly need a better way to moderate discussions than either having =
the loudest people speak whenever they want, or forcing people to queue =
up at microphones. &nbsp; &nbsp;And yet, I think what we're doing now is =
actually far worse (even for our current circumstances) than what IETF =
was doing in 1990. &nbsp; We've taken huge steps in the wrong =
direction.</div><div><br></div><div>Keith</div><div><br></div></div></body=
></html>=

--Apple-Mail-5--285953526--

From melinda.shore@gmail.com  Wed Jul 31 14:34:25 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1F3A11E8116 for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 14:34:24 -0700 (PDT)
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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yAkKZlW3oI-z for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 14:34:24 -0700 (PDT)
Received: from mail-pb0-x230.google.com (mail-pb0-x230.google.com [IPv6:2607:f8b0:400e:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id 4EA0B11E80FD for <ietf@ietf.org>; Wed, 31 Jul 2013 14:34:24 -0700 (PDT)
Received: by mail-pb0-f48.google.com with SMTP id ma3so1263245pbc.35 for <ietf@ietf.org>; Wed, 31 Jul 2013 14:34:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=Dv1IQX7AWYNxN+ugtE+WB8eSfd1wsPMWk2N9hpQnKoA=; b=gWBa85wma0kHK+FxdiQd+cjuyUEASKNoVUvCUdcNhJTBHIsHM79sFstH2r2vxjeHRU YTkGWRBMTEnjL6sxWglrcgIdeM77tK52qIzW6RO5vl2aEweSJCka/FEJDv9FCVyr0PCd uNlqVy0D2NjMPkeKNCJI4aKUPnlk3prShPB6yzuAbbhaAZLAx9yIkWAL1u8e98lj9ux0 bvWV0E906lwQ67Bgs/A2hZxeiDKTFH70PO5zzyDPIIhCD65ozBKP84JUSBbcTO8LbvFW 0IMps6kF3DxGXZcMslQEjw1h8P03JLQ5uQpM/zYpOdz1++wfvDelPkDN16CKSZuQf8K9 pQ4Q==
X-Received: by 10.66.4.6 with SMTP id g6mr297831pag.96.1375306464079; Wed, 31 Jul 2013 14:34:24 -0700 (PDT)
Received: from spandex.local (66-230-112-156-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.112.156]) by mx.google.com with ESMTPSA id qv4sm233428pbc.16.2013.07.31.14.34.22 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 31 Jul 2013 14:34:23 -0700 (PDT)
Message-ID: <51F982DD.4070201@gmail.com>
Date: Wed, 31 Jul 2013 13:34:21 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: making our meetings more worth the time/expense
References: <20130730163502.455E918C10F@mercury.lcs.mit.edu> <51F7FC29.2000407@isi.edu> <51F82442.4000404@gmail.com> <BB6564A3-80F7-479F-9336-04A0916F5989@network-heretics.com> <51F979CD.8040808@gmail.com> <30E3DE3C-D782-42C5-A175-4AB9AE553834@network-heretics.com>
In-Reply-To: <30E3DE3C-D782-42C5-A175-4AB9AE553834@network-heretics.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Jul 2013 21:34:25 -0000

I have to say that I was very impressed with how the oauth
session went.  There was minimal presentation and maximal
discussion, and the discussion was not interrupted until it
started getting circular.

But, I suspect that this is a reflection of the fact that
there's some substantial disagreement about not just
narrowly-defined issues, but some architectural models that
people are working from, that there's a very large number
of interested parties, there are time pressures and
expectations from external bodies, etc.  The discussion
would have been lively no matter how the meeting was
managed.  But, I thought it was very well-done.  The
challenge is how to have meetings that productive when
there are far fewer interested parties, fewer disagreements,
etc.  It may be the case in some instances that if
it's going to be nothing but presentations there may not
be a need for a working group to meet at all.

Melinda

From moore@network-heretics.com  Wed Jul 31 19:35:35 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB8A421F9C81 for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 19:35:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.621
X-Spam-Level: 
X-Spam-Status: No, score=-3.621 tagged_above=-999 required=5 tests=[AWL=-0.022, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vRnVBRdk8LZL for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 19:35:30 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id C2E5C21F9C7E for <ietf@ietf.org>; Wed, 31 Jul 2013 19:35:30 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 422C820EC4; Wed, 31 Jul 2013 22:35:29 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Wed, 31 Jul 2013 22:35:29 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=uQm 9LbBLzemeAsi8HhUlVNnkFUA=; b=Xr55mqP3ViBA9fHdhLSQJCNJ58GZtZaY/4u TjTQ2OPX57rmvIub2bhVKyuHjdmZb1wMjZLO2huuziDFe8qeiHnqgNKGUSlE398D ixytXvP7r4+FsCi6ldA0gLmRaxZ6Yo8x9k1GBXXkLhM5LcRK1lm+z3Fv81sonAQk vBKbjSLA=
X-Sasl-enc: je2Zm53nbXmtllXuZoc/UCViB1lvHMU42tHnI2X3ovd6 1375324528
Received: from surfer-172-29-8-65-hotspot.internet-for-guests.com (unknown [87.193.195.90]) by mail.messagingengine.com (Postfix) with ESMTPA id 88BDBC00E7F; Wed, 31 Jul 2013 22:35:28 -0400 (EDT)
Subject: Re: making our meetings more worth the time/expense
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: multipart/alternative; boundary=Apple-Mail-6--267147597
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <51F982DD.4070201@gmail.com>
Date: Thu, 1 Aug 2013 04:35:27 +0200
Message-Id: <736EDF26-57F5-4A24-9837-C26EF50B0183@network-heretics.com>
References: <20130730163502.455E918C10F@mercury.lcs.mit.edu> <51F7FC29.2000407@isi.edu> <51F82442.4000404@gmail.com> <BB6564A3-80F7-479F-9336-04A0916F5989@network-heretics.com> <51F979CD.8040808@gmail.com> <30E3DE3C-D782-42C5-A175-4AB9AE553834@network-heretics.com> <51F982DD.4070201@gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
X-Mailer: Apple Mail (2.1085)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Aug 2013 02:35:36 -0000

--Apple-Mail-6--267147597
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Jul 31, 2013, at 11:34 PM, Melinda Shore wrote:

> It may be the case in some instances that if
> it's going to be nothing but presentations there may not
> be a need for a working group to meet at all.

+1.   If nothing else, when a WG agenda starts to shape up like this, =
this should be a big red flag for chairs and ADs.

Keith


--Apple-Mail-6--267147597
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On Jul 31, 2013, at 11:34 PM, Melinda Shore wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">It may be the =
case in some instances that if<br>it's going to be nothing but =
presentations there may not<br>be a need for a working group to meet at =
all.</span></blockquote></div><br><div>+1. &nbsp; If nothing else, when =
a WG agenda starts to shape up like this, this should be a big red flag =
for chairs and =
ADs.</div><div><br></div><div>Keith</div><div><br></div></body></html>=

--Apple-Mail-6--267147597--

From dhc@dcrocker.net  Wed Jul 31 22:51:07 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E9EA21F9D4C for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 22:51:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MiAHGW3h9hjn for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 22:51:02 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 9E01A21F9D09 for <ietf@ietf.org>; Wed, 31 Jul 2013 22:51:02 -0700 (PDT)
Received: from [192.168.1.203] (e178125099.adsl.alicedsl.de [85.178.125.99]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r715oqse030937 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Wed, 31 Jul 2013 22:50:57 -0700
Message-ID: <51F9F730.8020105@dcrocker.net>
Date: Thu, 01 Aug 2013 07:50:40 +0200
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: making our meetings more worth the time/expense
References: <20130730163502.455E918C10F@mercury.lcs.mit.edu> <51F7FC29.2000407@isi.edu> <51F82442.4000404@gmail.com> <20130731022327.GA53174@mx1.yitter.info>
In-Reply-To: <20130731022327.GA53174@mx1.yitter.info>
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, 31 Jul 2013 22:50:59 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Aug 2013 05:51:07 -0000

On 7/31/2013 4:23 AM, Andrew Sullivan wrote:
> While that is true, I think it misses the point of the objections to
> the sit-and-watch-PowerPointTV.
>
> First, I observe that we already_have_  a great deal of written words:
> the drafts.  I continue to believe that altogether too much time in WG
> meetings is spent "introducing", "presenting", or otherwise showing
> off ideas in an existing draft to participants in the WG.  I
> acknowledge that (particularly in early stages of WG life, in topics
> with a lot of different work, and in cross-WG presentations) these
> "intro" presentations are a fact of life.  But I think we are
> extremely bad at holding the reigns on them.


I'm a fan of powerpoint, but with careful discipline in its use.

"The drafts" are the bible for detail, of course.  They must be the 
ultimate arbiter of current truth.  But while consulting the drafts for 
very specific concerns is often essential, using them during a 
discussion often is distracting.  Forest-vs-tree distinctions come to mind.

I see properly done slides as serving two important purposes:

    1. Concise summary of issues

    2. Helpful synchronization for those not fully up to speed and
       especially those not native English speakers

The first requires the presenter to distill things beforehand and in 
their head, and that's always useful discipline for a discussion and 
even more so for a debate.  The exercise of producing the distillation 
serves to ensure that the speaker, at least, has a concise sense of the 
issues.

The latter is just good group management, especially for a group trying 
to be... inclusive.

The challenge is how to balance detail with summary -- verbosity with 
terseness -- in the slides. And how to use the slides.

I used to do slides that were very cryptic.  Just keywords.  As I had to 
do presentations with non-native speakers, I was taught to make the 
slides stand alone so that they were useful even without anyone speaking 
to them.  "Telegraphic" language is roughly where that landed.  More 
than just keywords but much, much less than full narrative.

As for how to use the slides, I try not to read them, but instead to 
speak in a way that covers what the slides cover, albeit in full 
sentences.  So there should be correlation, but not verbatim recitation. 
  (I said "try".)




On 7/31/2013 7:22 AM, Scott Brim wrote:
 > http://tools.ietf.org/wg/intarea/trac/wiki/MeetingTimePrioritization

I might argue that that specific list is overly fussy and possibly 
Procrustean, but the gist of it definitely looks like the right kind of 
thinking, to focus wg face-time on resolving things rather than chatting 
and teaching.



d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net
